BSOD with todays update???

[doingsteel]

5 System down here with the same problem.... And one we are still working on because it will not uninstall from safe mode... Fun stuff

[essexboy]

I have just fixed one where comodo blocked the emergency update, do any of you use comodo ?

[Jack91]

Yes i saw your other reply, the file i mentioned requesting access. I granted that so surely it allowed it?

[essexboy]

No it was just a thought as other users appear to have received the EMU and had no problems

[TigTex]

Same here... all my windows 7 x64 systems failed to boot. after 2 hours of debugging, i found that avast was the problem... Please, fix this ASAP! Crucial problem!

[tyraarane]

I have just fixed one where comodo blocked the emergency update, do any of you use comodo ?

Don't use Comodo here, just the Windows Firewall. Also no BSODs.

Is there an easy way to check and see if I got any updates to/from Avast's emergency updater? I know Avast itself hasn't updated anything beyond the virus definitions in the past 24 hours, but I may have missed something pushed out by the emergency updater. I think the EMU may have run yesterday morning, but I can't be sure.

Someone up-thread mentioned that affected systems have an aswSP.sys file with a digital signature from June 24, buuuut...my aswSP.sys has a digital signature of June 24, 2013 @ 6:10:22AM. And again, no BSODs.

I think it's likely that a bad update got pushed out somewhere (from the emergency update service or in the virus definitions), and was then pulled back by Avast. It's possible that some of us missed that update entirely due to time zones, and that's why we're not having any problems. (I'm in the US, Eastern Standard time zone. So if the bad emergency update did come out 8+ hours ago like people are saying, well...I was asleep and my PC was off at the time, which may explain why I'm not experiencing any issues. Never got the update.)

[pk]

We apologize for the inconvenience, BSOD can happen on some x64 systems only (except XP x64) and after your first reboot.
This update was released due to Windows 8.1 Preview.
We've already fixed the problem, thank you for your feedback.

[DavidR]

How will this fix be deployed pk ?

[slybo]

I am not having any problems but reading this would like to know how do you tell you had an emergency update, I can not find it in the logs, maybe looking at the wrong one? Also is 130626-1 the latest update, by this time I usually would have had 130627-0? thanks

[tyraarane]

I am not having any problems but reading this would like to know how do you tell you had an emergency update, I can not find it in the logs, maybe looking at the wrong one? Also is 130626-1 the latest update, by this time I usually would have had 130627-0? thanks

I just checked and have been updated to 130627-1. Is this the fix? Will I get caught in a BSOD roundabout the next time I reboot? I have no idea. More communication from Avast on this issue would definitely have been helpful.

[drake127]

If you already received the update, you should have aswSnx.sys file in your drivers directory (C:\Windows\System32\drivers) with MD5 hash 8C0800CDB501CFC1164B286A0478DC10 (there is also aswSnx.sys.sum file where you can find the hash). Valid for Windows x64.

[miguelgrado]

I received last night an emergency update and now I have just received another.no problem with the two (luckily) 

[drummerman]

BSOD's here too this morning.

Lets see how it goes tomorrow am 

[kidd232]

My 3 computers got BSOD past 12 hours.
If  I dont want to remove avast, how can I resolve the problem?
replace files? or will get patch to fix it?

[jmarc_syd]

Yep blue screen  on 4 PCs Windows 7 x64 yesterday after reboot. Great!

Uninstall in safe mode works fine.

I've reverted to version 8.0.1483. No issue anymore.

I'll stay tuned for any update from Avast.