Simply put when I restart my PC be it for updates or whatever, Avast 8 will cause one or two Bsod while Windows 7 64bit is booting. This only happens when I restart my system, never from a cold start the next day after powering down for the night. I went to a Windows 7 forums for a crash dump analysis which came back saying aswSP.SYS was the cause. I have tried a clean install using the aswclean program in safe mode, no difference. This only started happening when I updated from Avast 7 to 8.
Please upload your minidump(s) here: ftp://ftp.avast.com/incoming/
or send them via email to kurtin@avast.com
Sent via email
I have/had the same issue on Windows 7 64-Bit (I did upgrade from Avast 7 to 8 as well). Only on restart I will get BSOD. But I won’t even get the crash dump file it would just freeze up. So I got rid of Avast. Did they solve your issue? Please let me know, thanks.
I never got a fix or a response about my problem being fixed in a update of the program. I removed Avast as well and never got this problem again with MSE.
Did you try the latest version 1485…??
that’s sad, tho I think it might be fixed in the 1485 RC2 beta … http://forum.avast.com/index.php?topic=120986.0
I planned to give the developers some time to roll out a few updates. With being busy with the end of my semesters I didn’t want to fiddle with anything that cause system issues. Although the chance of having a major system issue are slim I don’t want anything that could risk my work. I will try Avast 8 again in May during my break.
Just tried Avast 8 tonight. Installed, updated, restarted. Bsod. Got into Windows after restarting from the Bsod. Bsods in a minute after logging in. Quota_Underflow Bsod. Booted to safe mode uninstalled Avast. Botted normally no Bsod. Grabbed the removal tool, removed leftovers in safe mode. Booted normally.
just please again send / update your new minidumps , thanks in advance
Tried Avast again after 5 months of not using it. Blue screen of death on windows loading before the login screen. Uploaded the dump file to kurtin@avast.com
Thought you were a comodo fanboy.
Have you changed your allegiance?
Whatever this problem is it must be specific to a particular system/set-up because if Avast was crashing Win7 64bit on restart the forum posts and complaints would be arriving in an avalanche. That is clearly not the case but I’d be interested to know the cause of this trouble.
I’m gearing up to get my almost finished self-build desktop up and running, using Win7 64 bit for the first time. So if there is still some conflict or issue with Avast and certain set ups when using Win7 64 bit I’m concerned.
Wouldn’t say I am an fanboy at all. I just never saw the reason to switch as I was never told Comobo and Avast conflicts were causing the BSODs. Besides Im not using their AV just the Firewall. I still feel Avast is the superior AV program hence why I keep trying it to see if my issue is resolved, or at least I would be told if it was something I could fix like a driver conflict or fresh install of windows. Comobo was updated to a new version so I was hoping my previous issue was due to using the previous version of Comodo. The only messages I received about my issue were about two dump reports being about Ntfs.sys which only happened with Avast, nothing else. Looking back through my dumps files listed as the cause seem to be all windows system files but I have no idea what I am doing when anaylsing dumps. The folks at the windows 7 forum who analysed my dump files told me it was Avast causing the BSODs so again I saw no reason to dump a firewall that worked without conflict. Heck the new BSOD told me to uninstall my AV. One BSOD mentioned something about IRQ not equal or whatever. The other told me an error code and the bit about the AV.
I wouldn’t worry about my issues being common for everyone. It could be due to a number of reasons isolated to my system; drivers, hardware, software. etc. Besides my BSODs are only happening during the OS loading screen prior to the login screen. I no longer have BSODs after logging into the OS. I had an uptime of 8 hours with Avast, did a full scan with custom settings. It wasn’t until my 3rd restart that I had a BSOD. Give Avast a try and take it from there. Chance are it will work fine.
I formatted after AVG 2014 came up with rootkits it couldn’t fix although no other AV found these files. I reinstalled my OS, updated it along with M/B, sound and GPU drivers. I found that the tech that replaced my M/B borked the OS install a year ago. My SSD had the normal partition for files and the small one windows creates for installation. Yet it had two extra partitions that were not detected in the OS or anything other program I used. I install a fresh d/l of Avast and Comodo. No issues until I turned on Comodo HIPS which caused a BSOD instantly twice. I started adding Comodo processes to Avast’s file and behavior shields exclusion list. I added the few Avast processes to the Comodo HIPS allowed apps and corrected the auto assigned Avast files from custom to allowed apps. After I turned HIPS back on without issues. So my issues could have been due to the screwed up partitions, leftover AV/CF files from previous version or a failure for updated AV/CF to copy exclusion over properly.
I will update the thread if I run into anymore issues.
BSOD are restart, uploaded new dump to kurtin@avast.com. Disabling CF HIPS to see if it makes a difference