Author Topic: BSOD with todays update???  (Read 17181 times)

0 Members and 1 Guest are viewing this topic.

Offline dirtyharry

  • Newbie
  • *
  • Posts: 3
BSOD with todays update???
« 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

Offline CraigB

  • Avast √úberevangelist
  • Serious Graphoman
  • *****
  • Posts: 11095
  • No support PM's thanks
Re: BSOD with todays update???
« Reply #1 on: June 27, 2013, 01:34:12 PM »
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?

Offline dirtyharry

  • Newbie
  • *
  • Posts: 3
Re: BSOD with todays update???
« Reply #2 on: June 27, 2013, 01:39:03 PM »
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.

Offline Haahka

  • Newbie
  • *
  • Posts: 1
Re: BSOD with todays update???
« Reply #3 on: June 27, 2013, 01:40:26 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

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.

Offline DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 84889
  • No support PMs thanks
Re: BSOD with todays update???
« Reply #4 on: June 27, 2013, 01:46:36 PM »
@  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:
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 21.3.2459 (build 21.3.6164.561) UI 1.0.609/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline dirtyharry

  • Newbie
  • *
  • Posts: 3
Re: BSOD with todays update???
« Reply #5 on: June 27, 2013, 01:58:02 PM »
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.

Offline Tetsuo

  • Poster
  • *
  • Posts: 594
Re: BSOD with todays update???
« Reply #6 on: June 27, 2013, 02:28:55 PM »
This morning there was an Emergency Update (for W7, I believe).
It might be related...

Offline 3000ad

  • Newbie
  • *
  • Posts: 1
Re: BSOD with todays update???
« Reply #7 on: June 27, 2013, 02:42:27 PM »
Definitely an Avast problem.

3 Win 7 systems crash this morning, removing Avast in safe mode fixes issue.


Offline abruptum

  • Super Poster
  • ***
  • Posts: 2237
Re: BSOD with todays update???
« Reply #8 on: June 27, 2013, 03:18:58 PM »
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.

Offline moserdk

  • Newbie
  • *
  • Posts: 2
Re: BSOD with todays update???
« Reply #9 on: June 27, 2013, 03:31:07 PM »
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

Offline miguelgrado

  • Poster
  • *
  • Posts: 644
  • Admin ForoAntispyware
    • Foroantispyware
Re: BSOD with todays update???
« Reply #10 on: June 27, 2013, 03:31:12 PM »
I had an emergency update this evening and everything is fine. (vps 130626-1)  windows 7 pro 64 bits
miguel:CPU:intel core 2 quad q9400 2.7 ghz-ram 8 g ddr3 1333 mhz-grafica nvidia g force 220gt 1 g ram-SO windows 10 pro 64 bits-Seguridad:Avast Premium Security- Malwarebytes Premiun-

Offline tyraarane

  • Newbie
  • *
  • Posts: 17
Re: BSOD with todays update???
« Reply #11 on: June 27, 2013, 03:35:54 PM »
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!)

Offline JadeFalcon

  • Newbie
  • *
  • Posts: 1
Re: BSOD with todays update???
« Reply #12 on: June 27, 2013, 03:37:16 PM »
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

Offline moserdk

  • Newbie
  • *
  • Posts: 2
Re: BSOD with todays update???
« Reply #13 on: June 27, 2013, 03:57:03 PM »
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 ;)
« Last Edit: June 27, 2013, 04:03:08 PM by moserdk »

Offline Denniss

  • Newbie
  • *
  • Posts: 5
Re: BSOD with todays update???
« Reply #14 on: June 27, 2013, 04:23:56 PM »
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).