system
1
Running Windows 7 x64 Pro I got a BSOD five minutes ago, says aswSnx.sys is the culprit. I have zipped windows\minidump and memory and am ready to upload it anywhere. Where?
BTW, the timestamp of the minidump says Nov 15th 11:09. That is strange, because the BSOD right now was on Nov 16th 15:27. But the minidump contains only one file, so if the BSOD really did write a minidump, it should be this one.
Regards
Hajo
system
2
Hi,
You can upload the most recent .mdmp files from C:\Windows\mindunp and Memory.dmp file from C:\Windows and upload it to the ftp site
ftp://ftp.avast.com/incoming/
avast! will take care rest of the things.
Have a wonderful day. Good k@rma!
Asyn
3
system
6
[OT]
JFYI, this is the “thank you” (not just for Asyn BTW) numbered… Well, several “thank you’s” for the same exact correction to the same user. Sorry for the OT.
[/OT]
system
7
Thanks, uploading the file now. avast-bsod-topic-88520.zip
HJ
system
9
Hi there,
I just had another BSOD. Strange. Avast was stable until monday.
The odd thing however is: The Blue Screen says “writing memory dump…” and “100%” complete, so I guess I would get a memory.dump. The windows\memory.dmp file however has a wrong date and the minidump directory contains only one dump, which also has a date that is a few days ago, rather than today.
Could it be that the avast BSOD somehow interferes with windows ability to write a minidump?
Did the dump I uploaded to the ftp server contain any useful information for you?
Regards
Hajo
system
10
Maybe you should double check the current settings for memory dumps (mini, kernel, full), the size limits and locations.
You could search (Windows Explorer) for other dumps in other locations too.