BSOD DUE TO ASWBIDDRIVER.SYS

Avast Free Antivirus / Premium Security
1

I have a new DELL Vostro 3671 running Win10Pro version 20H2. In the last 2 months it has given me BSOD and easily rebooted.
Using the program WhoCrashedEx, it read the full memory dump and concluded:

This was probably caused by the following module: aswbidsdriver.sys (aswbidsdriver+0x1FC1D)
Bugcheck code: 0x18 (0x0, 0xFFFF970971E2FC10, 0x10, 0x1)
Error: REFERENCE_BY_POINTER
file path: C:\WINDOWS\system32\drivers\aswbidsdriver.sys
product: Avast
company: AVAST Software
description: Avast IDS Application Activity Monitor Driver.
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.

When I searched this forum I found the same problem in Jan 05, 2019 topic=224261.0 “BSOD DUE TO ASWBIDDRIVER.SYS give the fix” and AVAST said fix is included in 19.2 update which will be released 5.2 2019.

It appears to be back. AVAST please advise.

2

Follow instructions: https://support.avast.com/article/33/ and post the File-ID or name of the Support-File here afterwards.

3

When the tool asked for my email and ticket number, I created my own ticket number: dash_05202021 as I have the free version and I didn’t see how the support page would generate one for me. But after the tool created and sent the report, it did generate a File_ID 8DN5R. So now it is uploaded for analysis. Interestingly, just after I finished the report, my computer got a notice that AVAST have been advanced to the next version.

4

Does it still happen with the latest version (21.4)…?

5

Too soon to tell as luckily this isn’t a daily problem, in fact went weeks. But I would like to know what AVAST engineers think of the memory dump.

6

Hi rdasheiff,

I tried to look for your package but I wasn’t able to locate it. Can you pls resubmit it if the problem happens again?

Thanks,
PDI