BSOD with todays update???

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.)

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.

How will this fix be deployed pk ?

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.

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.

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

BSOD’s here too this morning.

Lets see how it goes tomorrow am ::slight_smile:

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?

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.

It has already been resolved so you should stick with the latest version of avast. See avast team member, drake127’s post in Reply #25.

What about posting some intructions how to get a crippled Windows back to working status?

A little bit more help from Avast would be nice.

Maybe a little late but here are my two ways of fixing the Problem:

On my laptop I started windows in safe mode, uninstalled Avast free, boot in normal mode, reinstall and reconfigure Avast completely.

On my PC I also started windows into safe mode with network! First I tried to start Avast and make a normal update. Unfortunately it did not work.
Then I went to control panel → Programs and Function, selected Avast Pro entry and hit the Uninstall/Change button.
In the uninstallation wizard I discovered the “Update” Tab and tried that before uninstall. This update completed successfully and I was able to restart my PC in normal mode without any further action.

How is it resolved? I’m on 8.0.1489 and still get blue screen (same error code and page fault) when starting several games like fifa 13. Shutting down shields allows me to start these games most of the time but if I alt-tab to windows I get same BSOD. Been like this since avast 8 and its pretty annoying that I can’t play any games…

PS I never noticed an “emergency update” ?

Vistax64

Only drawing attention to the post by one of the avast team in Reply #25.