There have been complaints about bsods in the last update of avast… and in fact, it has gotten quite common these days… Is there going to be a fix soon or will it be included in the next minor update (probrably a month or so by now i guess)? >:(
Please send me an e-mail (and tell me what operating system are you using). I’ll respond to it by sending you an updated test version of the avast! driver.
This applies to anyone having the same problem.
We’re working hard to solve this issue asap. I believe the update will be released as soon as the problem is solved, in this case…
Thanks
Vlk
Same problem here, too, on both Win2K and WinXP. Aswmod2.sys causes a BSOD page fault - not with Diskeeper 7, but with PerfectDisk 6. Get BSOD right in the middle of Analyzing hard drive with PD6.
However, without PD6 (and using Diskeeper 7 instead), I am often told it cannot defragment due to disk “inconsistencies”, and to run chkdsk. Once I do that, it appears nothing was repaired during the chkdsk, and the system operates normally after that - for awhile, anyway.
Any fixes for this?
I installed Avast! 4 three days ago and since then my PC rebooted three times (BSOD), only once while I was in front of it. The other two time the system was on the screen saver, but I had IE7 running watching my eBay bids…
I am running Win Vista32.
Should I uninstall Avast!4 and re-install McAfee ? I never had a BSOD?
Thanks for your advice on ths…
You must ensure that McAfee was completely removed, lots of options below as I don’t know what you had.
McAfee has an uninstall tool that you could run to ensure any possible remnants are removed.
http://download.mcafee.com/products/licensed/cust_support_patches/VSCleanupTool.exe
2007 version - http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe
Also see - How do I uninstall SecurityCenter? http://ts.mcafeehelp.com/faq3.asp?docid=71525
It is hard to say why a BSOD is caused and even harder when there is no information on it. There is usually an error name like IRQL_NOT_LESS_OR_EQUAL somewhere in the text and a stop error number, like Stop: 0x0000000A and other numbers in brackets, you can try a google search for the error name or stop error number and see if that reveals any useful information.