Windows 10: Constant BSOD Kmode_exception_not_handled and USBXHCI.sys

I have been having constant BSODs that I can't track down the cause of. I spent an hour or so on the phone with Microsoft and tracked down an issue with a USB cable, but even fixing that still having issues, it happens randomly with no known way to "repeat" it

Here is a an analysis of a dump with WinDbgX64


Microsoft R Windows Debugger Version 10.0.19041.1 AMD64
Copyright c Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP 16 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`08600000 PsLoadedModuleList = 0xfffff802`0922a310
Debug session time: Thu Sep 24 21:13:18.991 2020 UTC - 4:00
System Uptime: 7 days 4:42:41.612
Loading Kernel Symbols
...............................................................
..................Page 589a6e not present in the dump file. Type ".hh dbgerr004" for details
..............................................
................................................................
................................................................
..........
Loading User Symbols
PEB is paged out Peb.Ldr = 0000005c`4d518018. Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED 1e
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff802088d9284, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: ffff900cc5d47d10, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on CHANDLERPC

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 2

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff802088d9284

BUGCHECK_P3: 1

BUGCHECK_P4: ffff900cc5d47d10

WRITE_ADDRESS: ffff900cc5d47d10 Nonpaged pool

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: ffff900cc5d47d10

BLACKBOXBSD: 1 !blackboxbsd


BLACKBOXNTFS: 1 !blackboxntfs


BLACKBOXPNP: 1 !blackboxpnp


BLACKBOXWINLOGON: 1

PROCESS_NAME: chrome.exe

TRAP_FRAME: fffff8020b472400 -- .trap 0xfffff8020b472400
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8020b4725f8 rbx=0000000000000000 rcx=ffff900cc5d47d40
rdx=0000000070436f49 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802088d9284 rsp=fffff8020b472590 rbp=ffff900e001c5a60
r8=ffff900e2a9d9fa0 r9=0000000000000008 r10=0000fffff8020886
r11=ffff8ffbaa600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ObfReferenceObjectWithTag+0x24:
fffff802`088d9284 f0480fc15ed0 lock xadd qword ptr [rsi-30h],rbx ds:ffffffff`ffffffd0=????????????????
Resetting default scope

DPC_STACK_BASE: FFFFF8020B472FB0

BAD_STACK_POINTER: fffff8020b480158

STACK_TEXT:
fffff802`0b480158 fffff802`08af4d4e : 00000000`0000001e ffffffff`c0000005 fffff802`088d9284 00000000`00000001 : nt!KeBugCheckEx
fffff802`0b480160 fffff802`089fcd62 : fffff802`08af4d2c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff802`0b4801a0 fffff802`08885027 : fffff802`0b480710 00000000`00000000 fffff802`0b472fb0 fffff802`089faee5 : nt!RtlpExecuteHandlerForException+0x12
fffff802`0b4801d0 fffff802`08883ce6 : fffff802`0b472358 fffff802`0b480e20 fffff802`0b472358 00000000`00000000 : nt!RtlDispatchException+0x297
fffff802`0b4808f0 fffff802`089f4d32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff802`0b480fb0 fffff802`089f4d00 : fffff802`08a05fa5 ffff900c`c5d47d10 fffff802`0b472320 fffff802`0b472380 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff802`0b472218 fffff802`08a05fa5 : ffff900c`c5d47d10 fffff802`0b472320 fffff802`0b472380 fffff802`088d1f35 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff802`0b472220 fffff802`08a02143 : ffff900e`00fd09b0 fffff802`08fb2019 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125
fffff802`0b472400 fffff802`088d9284 : ffff900d`c56d9ba0 fffff802`08fb2019 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x443
fffff802`0b472590 fffff802`08866883 : ffff900c`c5d47d40 ffff900e`2a9d9fa0 ffff900d`c56d9ba0 00001c21`01800000 : nt!ObfReferenceObjectWithTag+0x24
fffff802`0b4725d0 fffff802`088c782e : ffff900e`001c5a60 fffff802`0b472689 ffff900d`c5d47d40 ffff900e`001c5e4b : nt!IopUnloadSafeCompletion+0x43
fffff802`0b472600 fffff802`088c76f7 : 00000000`00000001 00000000`00000000 ffff900d`cf1f3a30 00000000`00000002 : nt!IopfCompleteRequest+0x11e
fffff802`0b4726f0 fffff802`09db811a : 00000000`00000000 ffff900d`bc6f2530 ffff900e`001c5a60 ffff900d`d91d3010 : nt!IofCompleteRequest+0x17
fffff802`0b472720 fffff802`09db5bbf : 00000000`00000002 fffff802`0b472858 ffff900e`001c5a60 00000000`00000000 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
fffff802`0b4727b0 fffff802`16fb265e : ffff900e`145d29f0 ffff900e`145d2850 00000000`00000002 ffff900d`cf1f3e10 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
fffff802`0b472810 fffff802`16fb20e6 : fffff802`0b472ab8 ffff900d`cf1f3e10 fffff802`00000030 00000000`00000001 : USBXHCI!Isoch_Stage_CompleteTD+0x47e
fffff802`0b4728d0 fffff802`16fb1ef0 : fffff802`0b472a00 fffff802`0b472a00 00000000`00000000 fffff802`00000000 : USBXHCI!Isoch_ProcessTransferEventWithED1+0x1d6
fffff802`0b4729b0 fffff802`16fb6570 : 00000000`00000004 fffff802`0b472a88 00000000`00000008 fffff802`0b472a90 : USBXHCI!Isoch_EP_TransferEventHandler+0x10
fffff802`0b4729e0 fffff802`16fb60a5 : 00000000`00000780 00006ff2`3a8b6800 ffff900d`c53cf000 ffff900d`c5c63c10 : USBXHCI!Endpoint_TransferEventHandler+0xb0
fffff802`0b472a40 fffff802`16fb5d7c : ffff900d`bc9fcbf8 ffff900d`bc589040 00006ff2`3a8d3fd8 ffff900d`bc9fc000 : USBXHCI!Interrupter_DeferredWorkProcessor+0x315
fffff802`0b472b40 fffff802`09db38f5 : 00000000`00000f44 00000000`00400a02 00000000`00000000 00054e4d`24b05d40 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
fffff802`0b472b70 fffff802`088e9a3e : fffff802`02986240 ffff900d`bc642000 fffff802`0b472e70 fffff802`00000002 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa5 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 404]
fffff802`0b472bb0 fffff802`088e8d24 : fffff7ef`00001158 00000000`00000000 00000000`00000008 00000000`0169e951 : nt!KiExecuteAllDpcs+0x30e
fffff802`0b472d20 fffff802`089faee5 : 00000000`00000000 fffff802`02983180 ffffa001`9cd8a8c0 0000005c`4ddfd1b0 : nt!KiRetireDpcList+0x1f4
fffff802`0b472fb0 fffff802`089facd0 : fffff802`089eff90 fffff802`0883f03a 0000005c`4ddfcbf0 00006a1a`00000000 : nt!KxRetireDpcList+0x5
ffffdc0a`622b8ac0 fffff802`089fa585 : 0000005c`4ddfd1b0 fffff802`089f5a11 00000000`00000013 0000019d`1d330000 : nt!KiDispatchInterruptContinue
ffffdc0a`622b8af0 fffff802`089f5a11 : 00000000`00000013 0000019d`1d330000 ffffdc0a`00000000 ffff900d`00000000 : nt!KiDpcInterruptBypass+0x25
ffffdc0a`622b8b00 00007fff`f24792e7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb1
0000005c`4ddfd0c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`f24792e7


SYMBOL_NAME: USBXHCI!Isoch_Stage_CompleteTD+47e

MODULE_NAME: USBXHCI

IMAGE_NAME: USBXHCI.SYS

IMAGE_VERSION: 10.0.19041.488

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 47e

FAILURE_BUCKET_ID: 0x1E_c0000005_W_STACKPTR_ERROR_USBXHCI!Isoch_Stage_CompleteTD

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3430c514-fb6f-22bf-2de7-6cd205f3999e}

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

:)

 

KMODE_EXCEPTION_NOT_HANDLED (wdf01000.sys)

Please run driver verifier again using the settings from the driver verifier tutorial in post KMODE_EXCEPTION_NOT_HANDLED (wdf01000.sys) - Windows 10 Forums

 

Constant BSODs (system_service_exception, kmode_exception_not_handled)

Dealing with near daily BSODs when running intensive software or games. It usually doesn't crash until its under decent load (newer games, rendering, etc.) I have not overclocked my GPU or my CPU. The BSODs I most often get are system_service_exception,
kmode_exception_not_handled, and kernel_security_check_failure.

Another post insisted I ran "Driver verifier." I was able to get the DRIVER_VERIFIED_DETECTED_VIOLATION bsod almost instantly (twice), but neither time did it list the bad driver.

I've provided a link with the downloaded to the dmps, along with msinfo32 and my specs.

ws_4319.zip

 

KMODE_EXCEPTION_NOT_HANDLED on igdkmd64.sys

My computer keeps giving me the blue screen of death and giving me error code

KMODE_EXCEPTION_NOT_HANDLED on igdkmd64.sys

How can this be fixed?