Question BSOD HID COMPLIANT HEADSET

[Chivers]

Hello there,

I've a loooooot of BSOD, in my event viewer, i got hid compliant headseat as a critical error, which that make my PC restart

Here is some WHOCRASHED result :

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Mon 20/04/2020 18:10:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042020-9296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x162 (0xFFFF81047CD8C040, 0xFFFF810475FFBD00, 0xFFFFFFFF, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a lock tracked by AutoBoost was released by a thread that did not own the lock.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 20/04/2020 18:10:57 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x1E7E)
Bugcheck code: 0x162 (0xFFFF81047CD8C040, 0xFFFF810475FFBD00, 0xFFFFFFFF, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a lock tracked by AutoBoost was released by a thread that did not own the lock.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 20/04/2020 18:08:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042020-9218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x162 (0xFFFFBF873E416040, 0xFFFFBF873E416710, 0xFFFFFFFF, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a lock tracked by AutoBoost was released by a thread that did not own the lock.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 20/04/2020 17:33:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042020-5578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x192 (0xFFFFE50D62B93040, 0xFFFFE50D644F5338, 0x0, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

There is my onedrive with minidump files if you can find something.
I've tried to install new W10 4 times, and nothing change.
Already tried chkdsk, and driver update from everywhere, and sfc /scannow etc... etc... etc...

Thanks you.

 

[MuhammadSufyan]

Facing Same. Any Solutions?

 

[Reine Baumann]

Been experiencing the same issue and formatting has not helped at all.
Must be driver related --- most likely a Windows problem.

Disabling and re-enabling the HID Compliant headset device in Device Manager didn't work. Will need to uninstall all related audio drivers and hardware drivers and take it from there I suppose. Been blaming Corsair's iCUE software, but that was not the culprit either...

 

[eak232]

I have had this issue for over a year. I have Hyperx Cloud 2 headset, this issue is acknowledge by the company on their subreddit. They claim its Microsofts issue, really hope this gets corrected sometime soon.