Keep Getting BSOD through Win10 & Win11 New Installs

[gnasher155]

I had a Windows 10 install that started to BSOD. I tried a few things and then went to Windows 11 to see if that got rid of them problem. I'm still getting the BSOD and have a few mini dumps here with driver verifier active. One Drive Public Gnasher155

 

[Colif]

Did you clean install win 11 or just update to it? i ask as if both are different installs, there is a chance cause is hardware. If same install, it could just be the same driver. Upgrading windows when you have bsod often just brings the errors along for ride, doesn't fix them.

Conversion of Dump files

Report - click run as fiddle to read


File: 050823-5890-01.dmp (May 9 2023 - 09:09:06)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: HIDCLASS.SYS (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 06 Sec(s)

File: 050823-5578-01.dmp (May 9 2023 - 08:58:06)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
*** WARNING: Unable to verify timestamp for aswbidsdriver.sys
Probably caused by: aswbidsdriver.sys (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 54 Sec(s)

File: 050823-46078-01.dmp (May 9 2023 - 09:05:35)
BugCheck: [DRIVER_VERIFIER_DETECTED_VIOLATION (C4)]
*** WARNING: Unable to verify timestamp for aswbidsdriver.sys
Probably caused by: aswbidsdriver.sys (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 54 Sec(s)

File: 050823-40562-01.dmp (May 9 2023 - 09:03:34)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: HIDCLASS.SYS (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 41 Sec(s)

File: 050823-22062-01.dmp (May 9 2023 - 08:55:33)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: HIDCLASS.SYS (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 40 Sec(s)


disable driver verifer if you haven't already as it will just slow PC down if its not creating more BSOD

Avast caused the driver verifer errors
aswbidsdriver.sys = IDS Application Activity Monitor Driver.

update or remove it.

The other 3 BSOD all mention HIDCLASS.sys which is used by windows to talk to any human interface devices, so keyboard, mouse, touch screen, game controllers, etc.

what have you got that matches that description?

try updating oculus
could be logitech joystick as well.

 

[gnasher155]

I did a clean install of Windows 11.
Verifier has been disabled as it would crash as i loaded into Windows.
Avast is up to date and has been updated numerous times since this started so i will look to alternatives now to check if that works.

Keyboard: Logitech G413 Carbon
Mouse: Logitech G502
Wheel: Logitech G923
Gamepad: PowerA 1422336-01
Oculus Quest 1 that may be the other HID?

Oculus app is up to date and has been updated many times also since these BSODs started happening.

As far as hardware is involved. I have checked the RAM with Windows checker and then I checked it with the free version of memtest86. I have checked with memtest86 on single stick and both sticks and in different ram slots.
I have also got a different power supply installed than the opne the BSODs started with to check that also.

 

[Colif]

so ram is okay?

What are rest of the specs of PC? The report can only tell me so much
CPU - i5-9600K
MB - Asus TUF Z390-PLUS GAMING (WI-FI)
Ram - 16gb Corsair

Driver verifer did point at Avast though... might be up to date but still cause. Try removing it and see if it makes any difference.

I don't think Avast is involved in the other 3 though. It would be strange, so possible you have 2 problems.

Do you use G Hub to run the Logitech devices or Logitech Gaming Software?

Its possible someone else can get more info out of the dumps, I can't tell what caused the HID errors.

Google kept showing me wrong motherboard models when looking for yours. I see you on latest BIOS
https://www.asus.com/supportonly/tuf z390-plus gaming/helpdesk_bios/ (Not exact board but closest I can find)

 

[gnasher155]

I have heard that the paid Memtest86 has more tests than the free version, but as far as the free version goes it passed every time.

Ram : CMK16GX4M2D3600C18
GPU: EVGA GeForce GTX 1070 Ti FTW ULTRA SILENT GAMING
Boot Drive: Samsung SSD 980 PRO with Heatsink 1TB
Storage: MKNSSDCR240GB
Storage: 2x Hitachi HUA723030ALA640 3000.5 GB====Intel RAID 0 Volume
PSU: SF-550F14HG

I have tried this Windows 11 install without LGHub at first but it just kept BSODing so i recently put it back on. Its installed but i don't think it has been running in the foreground while those BSODs happened, however i can see processes that are running in the background from it on task manager.

 

[ubuysa]

Uninstall Avast!. The Driver Verifier dumps clearly show aswbidsdriver.sys as the faulty driver, and this is part of Avast!. You cannot determine whether Avast! is or is not the cause of the other BSODs, but troubleshooting is like peeling an onion. You know (from Driver Verifier) that Avast! is causing BSODs, so it's necessary to remove that first. If there are other BSODs we'll deal with them next.

 

[gnasher155]

I uninstalled Avast in safe mode with the Avast Clear tool. I have more mini dump files.One Drive Public Gnasher155

 

[ubuysa]

I looked only at the dumps from 9th May and they are identical. The problem driver in all is logi_joy_bus_enum.sys, a Logitech HID driver. ..

fffff487`f53de710  1a000004`60edf863
fffff487`f53de718  fffff800`d4878000 logi_joy_bus_enum+0x8000
fffff487`f53de720  00000000`00000000
fffff487`f53de728  00000000`00000000
fffff487`f53de730  00000000`00000000
fffff487`f53de738  00000000`00000000
fffff487`f53de740  ffff359f`57e49fb0
fffff487`f53de748  00000000`00000000
fffff487`f53de750  00000000`00000000
fffff487`f53de758  ffffcb00`039378f0
fffff487`f53de760  00000000`00000000
fffff487`f53de768  00000000`00000001
fffff487`f53de770  00000000`00000015
fffff487`f53de778  00000000`00000004
fffff487`f53de780  fffff487`f53de7f0
fffff487`f53de788  fffff807`81afde09 nt!MiAllocateWsle+0x5f9
fffff487`f53de790  ffffcb00`039378f0
fffff487`f53de798  00000000`00000004
fffff487`f53de7a0  ffffcb01`80023e18
fffff487`f53de7a8  fffff800`d4878000 logi_joy_bus_enum+0x8000
fffff487`f53de7b0  00000000`00000000
fffff487`f53de7b8  fffff807`81a3d2b8 nt!KiExitDispatcher+0xa58
fffff487`f53de7c0  00000000`00000000
fffff487`f53de7c8  00000000`00000000
fffff487`f53de7d0  00000000`00000000
fffff487`f53de7d8  00000000`00000000
fffff487`f53de7e0  00000000`00000000
fffff487`f53de7e8  fffff807`81c2f59b nt!HvlSwitchToVsmVtl1+0xab
fffff487`f53de7f0  00000000`00000000
fffff487`f53de7f8  fffff487`f53dea20
fffff487`f53de800  00000000`00000001
fffff487`f53de808  00000000`00000000
fffff487`f53de810  00000000`00000000
fffff487`f53de818  00000000`00000000
fffff487`f53de820  00000000`00000000
fffff487`f53de828  00000000`00000000
fffff487`f53de830  00000000`00000000
fffff487`f53de838  00000000`00000000
fffff487`f53de840  00000000`00000000
fffff487`f53de848  00000000`00000000
fffff487`f53de850  00000000`00000000
fffff487`f53de858  fffff807`81a88e6c nt!MiUnlockVadTree+0x40

The version you have installed is a tad old and there may well be an update...

1: kd> lmDvmlogi_joy_bus_enum
Browse full module list
start             end                 module name
fffff80c`cffc0000 fffff80c`cffcc000   logi_joy_bus_enum T (no symbols)          
    Loaded symbol image file: logi_joy_bus_enum.sys
    Image path: logi_joy_bus_enum.sys
    Image name: logi_joy_bus_enum.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Sep  2 23:38:46 2022 (631269D6)
    CheckSum:         00013052
    ImageSize:        0000C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

 

[gnasher155]

So far i have moved the driver "logi_joy_bus_enum.sys" to another HDD for backup.
I could only see "Logitech G HUB Virtual Bus Enumerator" using this driver and cant figure out what it is for, but i can see all my keyboard mouse and wheel works without the driver present.

I can currently run driver verifier as i did before and actually load windows with it running which is nice.

I might need some more time to verify I'm not getting BSODs again. They did seem to be a bit random while i was running windows normally(without verifier). I will keep you up to date when i get another BSOD.

 

[Colif]

I could only see "Logitech G HUB Virtual Bus Enumerator" using this driver and cant figure out what it is for,

my guess is it runs the functions of either virtual mouse or virtual keyboard. It could be used to let you use mouse commands on keyboard or visa versa. I seem to recall my G910 let me do it.

autoruns may show more, run as admin - https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

 

[ubuysa]

So far i have moved the driver "logi_joy_bus_enum.sys" to another HDD for backup.
I could only see "Logitech G HUB Virtual Bus Enumerator" using this driver and cant figure out what it is for, but i can see all my keyboard mouse and wheel works without the driver present.

Why? You can always download it from Logitech again if you need it. You did uninstall it didn't you?

What Driver Verifier settings are you using? It's a very useful tool but you have to set it up properly. Use only these tests...

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Select ALL non-Microsoft drivers (ie. all third-party drivers) and ALSO select these Microsoft drivers...

• Wdf01000.sys
• ndis.sys
• fltMgr.sys
• Storport.sys

If you're not using these stting then please disable Driver Verifier and re-enable it with these sttings.

NOTE: Please take a restore point (or an Acronis/Macrium Reflect disk image) before enabling Driver Verifier. If a driver loaded at boot is BSODed by Driver Verifier you'll be stuck in a boot-BSOD loop.

 

[gnasher155]

I have been running those settings you said and i havent seen a BSOD since getting rid of "logi_joy_bus_enum.sys". Thank you so much both of you for your help. I really appreciate it!

 

[ubuysa]

It sounds like that driver was the problem then. Be sure to disable Driver Verifier with the verifier /reset command (and a reboot).