Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: dirtyharry on June 27, 2013, 12:49:15 PM
-
hey guys
anyone else experiencing BSOD with todays update?
I have 2 Lenovo laptops and 1 desktop and they all received some kind of avast update today. (windows 7 64bit)
and they are all blue screening with each boot up.
uninstalling avast stops the blue screening.
also running diag on the dump file reveals the file aswSP.SYS as the issue.
anyone else having the same issue. and can it be fixed please
-
No problems here on my three systems and I've not noticed any reports on the forum with the problem your mentioning, is there any other security software installed that is common to your three systems?
-
nope no other software (antivirus).
only that's common is the brand...
but they are different models....so yeah..unless they are all sharing some common component or driver... but I find it hard to believe.
-
hey guys
anyone else experiencing BSOD with todays update?
I have 2 Lenovo laptops and 1 desktop and they all received some kind of avast update today. (windows 7 64bit)
and they are all blue screening with each boot up.
uninstalling avast stops the blue screening.
also running diag on the dump file reveals the file aswSP.SYS as the issue.
anyone else having the same issue. and can it be fixed please
Hi, I had the same proplem this morning. Every boot came whit same BSOD code 0x50 and the minidumb file said aswSP.sys was the cause.
It was fixed with erasing Avast, then reinstall and update. No proplem, works again. Atleast for now, fingers crossed.
-
@ dirtyharry
No problem on my two systems.
If there is any sort of driver conflict removing one would eliminate the conflict, but it wouldn't identify the culprit.
You don't say what version of avast you have installed, 8.0.1489 being the latest ?
If you have the latest you could upload the minidump/dump files to avast for analysis.
~~~~
- Upload any minidump or memory.dmp files, zipped to reduce size. Give the zip file you are uploading a unique name (e.g. forumusername-mem-dump.zip, etc), so they can identify it. It might not be a bad idea to create a text file (readme.txt) with any relevant information, avast topic URL, user name, etc. etc. in the zip file. Not to mention posting the name of the file you uploaded in the topic, this acts as another searchable reference.
- Memory dump locations, Mini Dump files in, C:\Windows\Minidump\ - Full Kernel dump file, C:\windows\memory.dmp
Upload the zip file to the ftp server ftp://ftp.avast.com/incoming (ftp://ftp.avast.com/incoming):
-
ok ive uploaded the file
and the version I have is version 8.0.1489
I noticed 1 of my laptops was running version 7..something so I decided to updated it...
after the update blue screen.
uninstalling and reinstalling doesn't fix it either cause once I install it and reboot...I get blue screen and doesn't go anywhere.
-
This morning there was an Emergency Update (for W7, I believe).
It might be related...
-
Definitely an Avast problem.
3 Win 7 systems crash this morning, removing Avast in safe mode fixes issue.
-
No problems here with Windows 7 SP1 32-bit
Avast Free 8.0.1489
Virus def. 130626-1
I didn't have any emergency Windows update today.
-
I'm having same issues on my lenovo, windows 7, 64 bit
Uninstall in safe mode and a re-install seems to have solved the problem
-
I had an emergency update this evening and everything is fine. (vps 130626-1) windows 7 pro 64 bits
-
No BSODs here either with Win 7 x64 Professional, and Avast 8.0.1489.
Do we think this was caused by an engine update, or virus definitions update? Because I did notice that the latest virus definitions update I can get is 130626-1, from yesterday (June 26) at 6pm. Not sure if that's my local time or not.
Usually when I boot up my PC I get an definitions update with a date matching that day's date. So for instance this morning I should've gotten an update labeled 130627. Is it possible Avast rolled out a bad definitions update that caused the BSODs, realized what happened and pulled it back?
That would explain why some of us didn't get any BSODs (because we never got the update), and why reinstalling/updating Avast fixed it for everyone else (because the bad update had been pulled back, so they wouldn't have received it a second time).
No emergency update from Windows/Microsoft here either, for the record. Windows Update says my last updates were installed June 25, and it's not showing any new updates that need to be installed either. (Outside some optional garbage like Bing Desktop. No thank you!)
-
can confirm that when my girlfriend booted the system up this morning, it immediately BSOD'd with 0x00000050 page fault in non paged area
system is win7-64bit / i7-3770k / 16gig ram / GTX680
On Thu 27/06/2013 08:56:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062713-21996-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x42A3E)
Bugcheck code: 0x50 (0xFFFFF80006241700, 0x8, 0xFFFFF80006241700, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
-
I had an emergency update from avast about 7 hours ago to 8.0.0.0 got home from work and then it wouldn't boot and had constant BSOD. Now with 8.0.1489 its running, but wont update virusdefinitions. Anybody else having this problem?
Update: After 1 hour of trying, avast suddenly succeded in updating definitions, so we're now back on track ;)
-
Seems to be limited to 64Bit systems only, my Win7x64 is not yet affected though (Win 7 Professional, German, IE9, no emergency Update popped up and nothing on manual search) but I use hybernation and usually reboot once per month (after patchday).
On affected systems the aswSP.sys with digital sign of June 24th seems to be the problem for whatever reason (missing Windoze digital signature updates perhaps).
-
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
-
I have just fixed one where comodo blocked the emergency update, do any of you use comodo ?
-
Yes i saw your other reply, the file i mentioned requesting access. I granted that so surely it allowed it?
-
No it was just a thought as other users appear to have received the EMU and had no problems
-
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!
-
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.)
-
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 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 ::)
-
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.
-
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.
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.