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