Author Topic: BSOD unlimited!  (Read 1383 times)

0 Members and 1 Guest are viewing this topic.

Offline Gov

  • Newbie
  • *
  • Posts: 1
BSOD unlimited!
« on: August 04, 2020, 01:53:48 AM »
For 11 long years I have had excellent experience with Avast with almost no false positives and also successfully blocking real viruses.
From today not anymore. For many months I have been experiencing BSODs unlimilted edition introduced by Avast. There were series of watch dog timer BSODs, then there were driver IO verify something error. BSODs are not limited to just one type of error. Avast finds new way to create a BSOD every week!

Many BSODs are attached here (no dump files are allowed to upload here!), and the same are uploaded to one drive, and links are below:

Set of five BSODs from 2020.06.27:
https://1drv.ms/u/s!AmNQ5fGL0GEfgqoeQAPQadKpOa4v6Q?e=A7quzR

July 2nd and 5th:

Set of five BSODs from today:
https://1drv.ms/u/s!AmNQ5fGL0GEfgqohxFLJGlMhapzWJA?e=0mODuk

Good Bye.

Offline Spec8472

  • Avast team
  • Sr. Member
  • *
  • Posts: 279
Re: BSOD unlimited!
« Reply #1 on: August 04, 2020, 08:38:03 AM »
Hello Gov,

thank you for the report. There is a problem in aswNetHub.sys driver, which will be fixed ASAP. The BSOD itself is triggered by active driver verifier (there wouldn't be any BSOD without driver verifier). So as workaround I suggest to disable the driver verifier. Execute Verifier.exe -> select "Delete Existing Settings" -> press "Finish"

Offline allan3159

  • Newbie
  • *
  • Posts: 1
Re: BSOD unlimited!
« Reply #2 on: August 04, 2020, 09:42:38 AM »
I have just encountered this problem tonight after Avast being pretty solid for the last 15 years. I'm on version 20.6.2420. i went back to a restore point and had no issues, updated avast and BOooOOM BSOD over and over. What is annoying it happens in the background of the log in screen and to get back in is frustrating.

I have done what suggested above and "deleted existing settings" What has this done and do I need to do anything else once you have patched the problem. When will this be patched ?

Also note I have managed to avoid the BSOD and log in by going into safe mode and removing everything but file, Web, mail and ransomware shields, everything else uninstalled and removed and seems stable while I logged in and did the "deleted existing settings" from the verifier.exe. I couldn't get as far as running the verifier previously as the BSOD happens after 20-30 secs.

Waiting for fix
Allan 

Offline Spec8472

  • Avast team
  • Sr. Member
  • *
  • Posts: 279
Re: BSOD unlimited!
« Reply #3 on: August 04, 2020, 09:54:39 AM »
Hi Allan,

your problem can be something completely different. Can you please provide a memory dumps from c:\Windows\minidump folder?

Offline MartinK

  • Avast team
  • Jr. Member
  • *
  • Posts: 56
Re: BSOD unlimited!
« Reply #4 on: August 04, 2020, 02:14:22 PM »
Hi Gov,
thank you for reporting. Your BSODs have two sources. The first, verifer BSOD is probably already fixed in our internal Avast build and this fix will be released in the next version 20.7.
Second one is probably caused by CM10664.sys driver and I don't see any connection to Avast there.

Offline tk6

  • Newbie
  • *
  • Posts: 18
  • Technology Critic escaped from tech industry
Re: BSOD unlimited!
« Reply #5 on: August 10, 2020, 03:16:17 AM »
Hello Gov,

thank you for the report. There is a problem in aswNetHub.sys driver, which will be fixed ASAP. The BSOD itself is triggered by active driver verifier (there wouldn't be any BSOD without driver verifier). So as workaround I suggest to disable the driver verifier. Execute Verifier.exe -> select "Delete Existing Settings" -> press "Finish"

Sorry, but verifier.exe should be doing NOTHING on a system that is not used for driver development.  Indeed, when I check its current status everything is tagged as "disabled" yet I'm being dumped on by these BSODs.  I assume "will be fixed ASAP" means it will be rolled out as an emergency update?  If not, someone needs to re-examine the bug's priority!

I must agree with another poster about this surprise in Avast quality...  The past several updates have had some other weird problems that can be worked around, but this one needs a fix ASAP -- not in just 20.7!

From the last ~48 hours, at every shutdown and at least once with serial port activity, version 20.6.2420, build 20.6.5495.588:
---
CANCEL_STATE_IN_COMPLETED_IRP

Technical information:

*** STOP: 0x00000048 (0xFFFFFA8016583650,0xFFFFF88004973D24,0x0000000000000000,0x0000000000000000)

*** aswNetHub sys — Address - FFFFF88004973D24 base at FFFFF8800493BOOO, Datestamp 5F197E1f
---
CANCEL_STATE_IN_COMPLETED_IRP

Technical information:

*** STOP: 0x00000048 (0xFFFFFA800D92FA20,0xFFFFF88004973D24,0x0000000000000000,0x0000000000000000)

*** aswNetHub.sys — Address FFFFF88004973D24 base at FFFFF8800493B000, Datestamp 5f197e1f
---
CANCEL_STATE_IN_COMPLETED_IRP

Technical information:

*** STOP: 0x00000048 (OXFFFFFA80lA3ED5A0,0XFFFFF880051AAD24,0x0000000000000000,0x0000000000000000)

*** aswNetHub.sys - Address FFFFF880051AAD24 base at FFFFF88005172000, Datestamp 5f197e1F
---