It happened when windows was loading after the reboot. I updated to 5.1.889 via the gui from 5.1.864 (it was the installation that I repaired thanks to Vlk’s suggestions here: http://forum.avast.com/index.php?topic=68569.0).
Thankfully, windows managed to repair itself but I think I should install avast from scratch. Should I do that?
My system info: Vista Home Premium 64bit SP2, admin account with UAC on, windows firewall
I sent the minidump file to pk
got your minidump, the first one with 889 build ;D
unfortunately, minidump isn’t enough to find out what exactly was wrong there - you need to configure your OS to generate fulldump (it’ll be stored in \Windows\memory.dmp).
howto: regedit.exe (HKLM\SYSTEM\CurrentControlSet\Control\CrashControl → set CrashDumpEnabled=1)
now go to Control Panel → System → Advanced System Settings → Startup and Recovery → Settings and choose “Complete memory dump”
I remember that a long time ago I configured windows to create a full dump instead of a minidump only. I also have a MEMORY.DMP file in C:\Windows\ but it is only 402MB :-\ and I have 4 gigs of ram.
It was set to 2 ??? but I changed it to 1.
It was set like this already.
Now, how to reproduce this bsod? ATM windows and avast seem to be running ok.
I’ll send the file to you right now.
Thanks pk!
“2” means kernel dump: http://technet.microsoft.com/en-us/library/cc976050.aspx
please note, after changing to “1” you need to restart the computer
if you have time & free inet line, you can compress & upload your memory.dmp to our ftp, I’d have a look at it
thanks.
Sure. I’m sending you the file called (Silent Assassin)MEMORY.7z. It’s 55MB big.
Thanks
just on a side note: if you’re on Seven, full dump isn’t available as an option from Windows UI (just mini and kernel). This can be tweaked. But I doubt Avast want full dumps ;D … on systems that have more than 2GB of RAM.
I started a thread about that a year ago, where everything’s explained
http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/b9b51aa0-abb3-4074-8028-ead89ed166f6
edit: oups… I now see that pk already described that 
yeaaaah, I need full (complete) memory dump… 
Well, if PK said he needs the full dump, we do, I’m afraid.
Sure, the size of the dump makes it kinda hard to transfer… but sometimes there’s no other way. I occasionally send PK my 8GB dumps… though yeah, locally it’s easy.
okay … (I already edited my post above because I missed some of pk’s post in the first place)
The upload has finished. Thanks
Could you please try to generate that complete memory dump? Thanks.
I’m afraid not :-[. I uninstalled the 5.1.889, installed 5.1.864 and updated to 5.1.889 from the gui in hope I would get the same bsod. But I didn’t.
It seems that the ‘repaired’ version from which I was updating to the latest one and which gave me the bsod wasn’t 100% functional.
ATM avast seems to be running perfectly fine.
Thanks and sorry
So today I get BSOD 1 hour after application of version 889. I don’t have any BSOD’s before installation of new 889. But now it seems to be ok.