My computer got crashed randomly .

Question

Not sure if my headphone cause the crashing issue , below is the dump analysis detail :

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.047 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29547.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\xtng\Desktop\060626-20890-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff801`bfa00000 PsLoadedModuleList = 0xfffff801`c08f51f0
Debug session time: Sat Jun  6 17:20:20.661 2026 (UTC + 8:00)
System Uptime: 0 days 16:39:31.886
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................................................
Loading User Symbols

Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`bfef7e30 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff918c`d9b871f0=000000000000000a
11: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................................................
Loading User Symbols

Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffecf47d6392a8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff801c05be791, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1921

    Key  : Analysis.Elapsed.mSec
    Value: 35029

    Key  : Analysis.IO.Other.Mb
    Value: 5

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 13

    Key  : Analysis.Init.CPU.mSec
    Value: 468

    Key  : Analysis.Init.Elapsed.mSec
    Value: 9860

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 102

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_mshidkmdf!HidKmdfPassThrough

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff801c05be791

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0xbbe791

    Key  : Failure.Hash
    Value: {c63ae10c-d392-7b1f-e683-ac2021dc9d4d}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : Stack.Pointer
    Value: NMI

    Key  : WER.System.BIOSRevision
    Value: 7.18.0.0


BUGCHECK_CODE:  a

BUGCHECK_P1: ffffecf47d6392a8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff801c05be791

FILE_IN_CAB:  060626-20890-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc68ec7d75040

READ_ADDRESS: fffff801c09c44d8: Unable to get MiVisibleState
 ffffecf47d6392a8 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

DPC_STACK_BASE:  FFFF918CD9B87FB0

IP_IN_PAGED_CODE: 
nt!KscpCfgDispatchUserCallTargetEsSmep+11
fffff801`c05be791 4f8b1cd3        mov     r11,qword ptr [r11+r10*8]

STACK_TEXT:  
ffff918c`d9b871e8 fffff801`c00bcee9     : 00000000`0000000a ffffecf4`7d6392a8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff918c`d9b871f0 fffff801`c00b81a8     : ffffc68e`fe8fbb00 ffffc68e`ef387c50 ffffc68e`d0da0730 ffffc68e`fe8fbbe0 : nt!KiBugCheckDispatch+0x69
ffff918c`d9b87330 fffff801`c05be791     : fffff801`bfcd7b8b 00000000`00000056 fffff801`5531343d ffffc68e`ce1111d0 : nt!KiPageFault+0x468
ffff918c`d9b874c8 fffff801`bfcd7b8b     : 00000000`00000056 fffff801`5531343d ffffc68e`ce1111d0 00000000`0000000a : nt!KscpCfgDispatchUserCallTargetEsSmep+0x11
ffff918c`d9b874d0 fffff801`bfcd7b03     : 00000000`00000019 00000002`00000000 ffffc68e`ce111060 00000000`00000002 : nt!IopfCallDriver+0x5b
ffff918c`d9b87510 fffff801`553010b4     : 01dcf595`b26bde24 01dcf595`5912455e ffffc68e`ce1111d0 ffffc68e`ceee86f0 : nt!IofCallDriver+0x13
ffff918c`d9b87540 fffff801`55313f69     : fffff801`553420d8 fffff801`553420d8 00000000`00000000 00000000`00000000 : mshidkmdf!HidKmdfPassThrough+0x44
ffff918c`d9b87570 fffff801`553124a7     : ffffc68e`ce1111d0 00000000`00000000 ffffc68e`d0da0730 fffff801`0000000a : HIDCLASS!HidpSubmitInterruptRead+0x149
ffff918c`d9b87600 fffff801`bfdc6cc4     : ffffc68e`d0da0730 fffff801`bfdb6a2f 00000000`00000001 ffff918c`d9b87820 : HIDCLASS!HidpInterruptReadComplete+0x197
ffff918c`d9b87740 fffff801`bfdc6923     : 00000000`00000000 00000000`00000000 ffffc68e`ec148530 ffffc68e`cdf3abc0 : nt!IopfCompleteRequest+0x374
ffff918c`d9b878c0 fffff801`51f946fe     : ffffc68e`ec148692 00000000`00000000 ffffc68e`d0da0730 ffffc68e`ec148530 : nt!IofCompleteRequest+0x13
(Inline Function) --------`--------     : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxIrp::CompleteRequest+0x13
ffff918c`d9b878f0 fffff801`51fc61b7     : ffffc68e`cecec702 00003971`320c5438 ffffc68e`d0da0730 ffffc68e`ec148530 : Wdf01000!FxRequest::CompleteInternal+0x13e
(Inline Function) --------`--------     : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxRequest::Complete+0x35
ffff918c`d9b87980 fffff801`5557adaf     : ffffc68e`ce10fbb0 ffffc68e`ec148530 fffff801`55583100 ffffc68e`ec148530 : Wdf01000!imp_WdfRequestComplete+0xa7
ffff918c`d9b87a00 fffff801`51fb3d71     : ffffb6d1`371ddb93 00003971`31e2b598 ffffc68e`ce1d4b58 00000000`00000015 : hidi2c!OnInterruptDpc+0x1df
(Inline Function) --------`--------     : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxInterrupt::DpcHandler+0x69
ffff918c`d9b87a90 fffff801`bfc16512     : ffff918c`d9b87e20 ffff9301`93fa2180 00000000`00000000 00000000`00000002 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xb1
ffff918c`d9b87ae0 fffff801`bfc12e9e     : ffff9301`93fa2180 ffff918c`d9b87e20 ffffc68e`c7d75040 00000000`00000008 : nt!KiExecuteAllDpcs+0x692
ffff918c`d9b87d20 fffff801`c00b0c45     : cccccccc`cccccccc ffff9301`93fa2180 ffffc68e`c7d75040 ffff9301`93fa2180 : nt!KiRetireDpcList+0x43e
ffff918c`d9b87fb0 fffff801`c00b0bef     : ffff918c`da07f450 fffff801`bfc338b5 00000000`00000000 00000000`00000000 : nt!KxSwapStacksAndRetireDpcList+0x5
ffff918c`da07f390 fffff801`bfc338b5     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPlatformSwapStacksAndCallReturn
ffff918c`da07f3a0 fffff801`c00b007f     : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KiDispatchInterrupt+0x65
ffff918c`da07f3d0 fffff801`bfc15076     : 00000000`00000001 ffffc68e`ceceb498 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x39f
ffff918c`da07f560 fffff801`bfc14eb1     : 0000ffff`f80151fb ffffc68e`ce1d4a60 00000000`00000000 00000000`00000000 : nt!KiInsertQueueDpc+0x1b6
ffff918c`da07f650 fffff801`51fc5b64     : ffffc68e`ec148530 ffffc68e`cbb70940 ffffffff`ff676980 ffff73b9`28b86ea3 : nt!KeInsertQueueDpc+0x11
(Inline Function) --------`--------     : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxInterrupt::QueueDpcForIsr+0x19
(Inline Function) --------`--------     : --------`-------- --------`-------- --------`-------- --------`-------- : Wdf01000!FxInterrupt::QueueDeferredRoutineForIsr+0x19
ffff918c`da07f690 fffff801`5557b40b     : ffffc68e`ce10fbb0 ffffc68e`ce1d4a60 ffff918c`da07f780 00000000`0000000a : Wdf01000!imp_WdfInterruptQueueDpcForIsr+0x64
ffff918c`da07f700 fffff801`51f75560     : 00000000`00000000 ffffc68e`ce1d4a60 00000000`00000000 ffffc68e`ce1d4ba8 : hidi2c!OnInterruptIsr+0x59b
ffff918c`da07f7b0 fffff801`bfd30c39     : ffff9301`94507200 fffff801`c0815980 00000000`00000000 fffff801`bfee1b92 : Wdf01000!FxInterrupt::_InterruptThunk+0xe0
ffff918c`da07f7f0 fffff801`bfdbb3d6     : ffff9301`94507280 00000000`00000000 00000000`00000000 fffff801`bfd2ee00 : nt!KiCallInterruptServiceRoutine+0x109
ffff918c`da07f860 fffff801`bfdbafa1     : 00000000`00000000 ffff918c`da07fa18 00000000`00000000 ffff9301`94507280 : nt!KiInvokeInterruptServiceRoutine+0xfe
ffff918c`da07f9b0 fffff801`bfe4bbfd     : ffffc68e`fbd48030 fffff801`bffa1dc0 00000000`00000080 fffff801`bffa1dc0 : nt!KiInterruptDispatchCommon+0x1f9
ffff918c`da07fa80 fffff801`bffa1e0c     : fffff801`c098c000 fffff801`bfe16000 ffffb6d1`34a25500 00000000`00000000 : nt!IopPassiveInterruptWorker+0x7d
ffff918c`da07faf0 fffff801`bfe8173a     : ffffc68e`c7d75040 ffffc68e`fbd48078 ffff9301`94136180 066fe47f`b19bbdff : nt!IopPassiveInterruptRealtimeWorker+0x4c
ffff918c`da07fb30 fffff801`c00a9ff4     : ffff9301`94136180 ffffc68e`c7d75040 fffff801`bfe816e0 4800076d`21058b48 : nt!PspSystemThreadStartup+0x5a
ffff918c`da07fb80 00000000`00000000     : ffff918c`da080000 ffff918c`da079000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  mshidkmdf!HidKmdfPassThrough+44

MODULE_NAME: mshidkmdf

IMAGE_NAME:  mshidkmdf.sys

IMAGE_VERSION:  10.0.26100.1150

STACK_COMMAND: .process /r /p 0xffffc68ec451e040; .thread /r /p 0xffffc68ec7d75040 ; kb

BUCKET_ID_FUNC_OFFSET:  44

FAILURE_BUCKET_ID:  AV_mshidkmdf!HidKmdfPassThrough

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c63ae10c-d392-7b1f-e683-ac2021dc9d4d}

Followup:     MachineOwner
---------

Answer 1

Hi Fallson Cheung,

The analyze logs indicate the problem with mshidkmdf.sys - a Windows system driver known as the Pass-through HID (Human Interface Device) to KMDF (Kernel-Mode Driver Framework) Filter Driver.

Please run the following commands on Command Prompt (Run as administrator) to scan and fix your system files:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

After done successfully, please restart your computer and see if the problem can be resolved.

If you have further information, please feel free to let me know.

Answer 2

Hi, I'm Jan. Please share the latest dmp files for us to further diagnose the cause of the computer crash. Thank you

Please find this folder.

C:\Windows\Minidump

Put the files in a zip

upload files to OneDrive

Share the link here.

Thank you

Answer 3

The dump shows a classic driver‑level crash in the HID (Human Interface Device) stack, not a general hardware failure.

Key points from the analysis:

• Bugcheck: IRQL_NOT_LESS_OR_EQUAL (0xA) – typically caused by a kernel‑mode driver accessing invalid or paged memory at too high an IRQL.
• Failure bucket: AV_mshidkmdf!HidKmdfPassThrough
• Call stack around the fault:
  • mshidkmdf!HidKmdfPassThrough
  • HIDCLASS!HidpSubmitInterruptRead
  • hidi2c!OnInterruptDpc / hidi2c!OnInterruptIsr

This shows the crash occurred while processing an interrupt from a HID device (via hidi2c and mshidkmdf.sys). That is consistent with a USB or I2C‑based HID peripheral such as a mouse, keyboard, touchpad, or headset with HID controls (volume, mute, etc.). So the headset (or another HID device) can be involved indirectly via its driver path.

Actionable steps:

1. Update HID‑related drivers and chipset
   • Install the latest drivers from the PC/motherboard or laptop vendor, especially:
     • Chipset drivers
     • USB controller drivers
     • Touchpad / input device drivers
   • Ensure Windows Update is fully applied, as mshidkmdf.sys is a Microsoft HID driver.
2. Check and update or remove third‑party HID devices
   • Temporarily disconnect non‑essential USB/I2C HID devices (USB headset, gamepad, extra mouse/keyboard, etc.).
   • Use the system normally and see if crashes stop.
   • Reconnect devices one by one to identify which one triggers the issue.
   • For the suspect device, install the latest vendor driver or firmware if available.
3. Roll back or reinstall recent device software
   • If any HID‑related software (headset control app, RGB/keyboard software, etc.) was recently installed or updated, uninstall it and test.
4. Check for additional dumps
   • If more BSODs occur, confirm they show the same bucket (AV_mshidkmdf!HidKmdfPassThrough) or HID stack involvement. Consistency strengthens the case for a specific HID device/driver.
5. If crashes persist
   • Use Driver Verifier targeting non‑Microsoft HID and USB drivers only, and be prepared to boot into recovery to disable it if it causes boot loops.

In summary, the crash is in the Microsoft HID driver path (mshidkmdf.sys) while handling an interrupt from a HID device. A connected HID peripheral (including the headphone if it exposes HID controls) or its associated driver is the most likely trigger, so focus on updating, testing, or temporarily removing those devices and their software.

---

References:

• Bug Check 0xD4: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
• Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
• Bug Check 0x1A5: USB_DRIPS_BLOCKER_SURPRISE_REMOVAL_LIVEDUMP
• Kernel_Security_Error BSOD. Driver Verifier causing bootloop. - Microsoft Q&A
• Issue with Driver_Power_State_Failure 0x9F Windows 11 - Microsoft Q&A
• Please check my minidumps, BSOD and shutdowns - Microsoft Q&A
• BSODs caused by ntkrnlmp.exe - Microsoft Q&A