This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Yesterday my pc was running fine. Today at startup, I can log into windows. While waiting and seeing the desktop, within 1 minute the BSOD crash happens. Only the SYSTEM THREAD EXCEPTION NOT HANDLED is displayed. It loads and then restarts.
I have searched online for solutions and I expect one of my Drivers is Faulty. But I have not experience in reading the dump file and figuring out what the issue is.
Anyone had experience and is able to help me?
Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\122821-12484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff80571405000 PsLoadedModuleList = 0xfffff8057202f1b0
Debug session time: Tue Dec 28 15:03:34.145 2021 (UTC + 1:00)
System Uptime: 0 days 0:01:07.816
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80571dc7b19, The address that the exception occurred at
Arg3: ffffb2031ff57068, Exception Record Address
Arg4: ffffb2031ff568a0, Context Record Address
Debugging Details:
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 3046
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 10633
Key : Analysis.Init.CPU.mSec
Value: 4468
Key : Analysis.Init.Elapsed.mSec
Value: 200165
Key : Analysis.Memory.CommitPeak.Mb
Value: 92
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff80571dc7b19
BUGCHECK_P3: ffffb2031ff57068
BUGCHECK_P4: ffffb2031ff568a0
EXCEPTION_RECORD: ffffb2031ff57068 -- (.exr 0xffffb2031ff57068)
ExceptionAddress: fffff80571dc7b19 (nt!IovpValidateDeviceObject+0x0000000000000005)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000046dc232
Attempt to read from address 00000000046dc232
CONTEXT: ffffb2031ff568a0 -- (.cxr 0xffffb2031ff568a0)
rax=ffff800be8666e10 rbx=ffff800be8666e10 rcx=00000000046dc232
rdx=0000000000000000 rsi=00000000046dc232 rdi=ffff800bf04fe470
rip=fffff80571dc7b19 rsp=ffffb2031ff572a8 rbp=fffff80571772197
r8=0000000000000000 r9=0000000000000000 r10=fffff8057214ea00
r11=0000000000000000 r12=ffff800bfc57d000 r13=fffff80548127008
r14=0000000000400000 r15=fffff80548120188
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
nt!IovpValidateDeviceObject+0x5:
fffff80571dc7b19 66833903 cmp word ptr [rcx],3 ds:002b:00000000046dc232=????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: fffff80572100390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
00000000046dc232
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000046dc232
EXCEPTION_STR: 0xc0000005
LOCK_ADDRESS: fffff80572049b80 -- (!locks fffff80572049b80)
Cannot get _ERESOURCE type
Resource @ nt!PiEngineLock (0xfffff80572049b80) Available
1 total locks
PNP_TRIAGE_DATA:
Lock address : 0xfffff80572049b80
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
STACK_TEXT:
ffffb2031ff572a8 fffff80571dc6e03 : ffff800be8666e10 fffff8054810398a ffffb20300000001 ffffb2031ff572d8 : nt!IovpValidateDeviceObject+0x5
ffffb2031ff572b0 fffff80571843cb1 : ffff800be8666e10 0000000000000000 0000000000400000 ffff800bf04fe470 : nt!IovCallDriver+0x15f
ffffb2031ff572f0 fffff80571772197 : ffff800be8666f70 fffff80571dd319e ffff800b00000000 ffff800b00000001 : nt!IofCallDriver+0x1af531
ffffb2031ff57330 fffff80571dc6f0a : ffff800be8666e10 ffff800bffc52a90 0000000000000000 ffff800c014911b0 : nt!IopfCallDriver+0x53
ffffb2031ff57370 fffff80571843cb1 : ffff800be8666e10 0000000000000017 003300320043005f ffff800bf1ec0960 : nt!IovCallDriver+0x266
ffffb2031ff573b0 fffff8054810398a : fffff805729f6010 00260031005c0032 0035006600390037 0026003700380064 : nt!IofCallDriver+0x1af531
ffffb2031ff573f0 fffff805481155a5 : 0000000000000000 ffff800c014911d0 ffff800be8666e10 0000000000000000 : HIDCLASS!HidpCallDriver+0xba
ffffb2031ff57460 fffff8054813458a : ffff800c014911b0 0000000000050282 ffffb2031ff574e8 ffffb2031ff574f0 : HIDCLASS!HidpIrpMajorDefault+0x129
ffffb2031ff574c0 fffff80548102737 : ffffb20300000002 ffff800c014911b0 0000000000000017 fffff80571dd3615 : HIDCLASS!HidpIrpMajorSystemControl+0x4e2
ffffb2031ff574f0 fffff80571772197 : 0000000000000000 ffff800be8666e10 ffff800c01491060 ffff800b00000001 : HIDCLASS!HidpMajorHandler+0x267
ffffb2031ff57580 fffff80571dc6f0a : ffff800be8666e10 ffff800c01491060 0000000000000000 fffff80571dd36b9 : nt!IopfCallDriver+0x53
ffffb2031ff575c0 fffff80571843cb1 : ffff800be8666e10 ffff800c01491060 ffff800bffc52a90 ffff800bf04fcb40 : nt!IovCallDriver+0x266
ffffb2031ff57600 fffff80571dd3615 : ffff800bffc52a90 ffffb2031ff57829 0000000000000000 0000000000000000 : nt!IofCallDriver+0x1af531
ffffb2031ff57640 fffff80571de557a : ffff800bffc52a90 ffffb2031ff57829 0000000000000001 ffff800bffc52a90 : nt!VfIrpSendSynchronousIrp+0x115
ffffb2031ff576b0 fffff80571dd9c3c : 0000000000000000 ffffb2031ff57829 0000000000000001 ffff800bffc52a90 : nt!VfWmiTestStartedPdoStack+0x5a
ffffb2031ff57750 fffff80571770b30 : 0000000000000000 ffffb2031ff57829 0000000000000001 ffff800bd474c680 : nt!VfMajorTestStartedPdoStack+0x58
ffffb2031ff57780 fffff80571b2fd83 : 0000000000000000 ffffb2031ff57829 0000000000000001 ffffb2031ff57829 : nt!PpvUtilTestStartedPdoStack+0x18
ffffb2031ff577b0 fffff80571b2c29d : ffff800bffc54a20 ffffb20300000001 0000000000000000 0000000000000000 : nt!PipProcessStartPhase3+0xc3
ffffb2031ff57890 fffff80571b3ce88 : ffff800bd46fd100 ffffb2031ff57a01 ffffb2031ff579b0 fffff80500000002 : nt!PipProcessDevNodeTree+0x2dd
ffffb2031ff57960 fffff805717730c6 : 0000000100000003 ffff800bd474c680 ffff800bd46fd140 ffff800bd46fd140 : nt!PiProcessReenumeration+0x88
ffffb2031ff579b0 fffff805716bd5f5 : ffff800bf9713040 ffff800bd46e4b10 fffff80572048360 ffff800b00000000 : nt!PnpDeviceActionWorker+0x206
ffffb2031ff57a70 fffff8057175a935 : ffff800bf9713040 0000000000000080 ffff800bd46b5040 fffff80571804c70 : nt!ExpWorkerThread+0x105
ffffb2031ff57b10 fffff80571803728 : ffff9f8091de0180 ffff800bf9713040 fffff8057175a8e0 1d1d1d1d1d1d1d1d : nt!PspSystemThreadStartup+0x55
ffffb2031ff57b60 0000000000000000 : ffffb2031ff58000 ffffb2031ff51000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: HIDCLASS!HidpCallDriver+ba
MODULE_NAME: HIDCLASS
IMAGE_NAME: HIDCLASS.SYS
IMAGE_VERSION: 10.0.19041.1110
STACK_COMMAND: .cxr 0xffffb2031ff568a0 ; kb
BUCKET_ID_FUNC_OFFSET: ba
FAILURE_BUCKET_ID: AV_HIDCLASS!HidpCallDriver
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {09223f76-66f9-c8bc-7ce8-d669ecd11026}
Followup: MachineOwner
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi RVD2 ,
I'm Paul and I'm here to help you with your concern.
The minidump file indicates "HIDCLASS.SYS". It is a Human Interface Device driver that supports Keyboards, Mouse and other input devices.
May I know what HID devices are plugged in your PC when you encountered the BSOD?
Thanks.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 93%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
It shows that the Human Interface Driver (aka HID) is the fault, I don't precisely know which hardware caused it. You can try updating the drivers of keyboard, mouse, and other such devices from Device Manager (accessible by right-clicking Start button in taskbar and choosing the app).
