Windows 10: Windows 10 USBXHCI.sys BSOD

I have for the last few months been having issues with BSODs with USBXHCI.sys

I thought I solved them buy disconnecting a couple USB extension cable, went 2 weeks without a crash and then crashed again. this is getting extremely frustrating and having me reconsider my decision to use Windows, the compatibility of Windows isn't worth it if its this unreliable, I have had more crashes in the last 6 months than the last 15 years. I just can't for the life of me figure out WHAT device is causing it to crash. the most common thing I am doing when it crashes is using Chrome and moving my mouse, i will be running driver verifier to try to identify if there is a driver that doesn't work properly.

When I look in my device manager I see multiple HID-compliant mouse, multiple HID Keyboard Devices, and multiple HID-compliant consumer control devices, and multiple HID-compliant vendor-defined devices.

Motherboard is Crosshair VIII Hero Wifi

Here are the currently connected USB devices
NZXT Kraken X73 AIO Liquid Cooler and NZXT Cam Software
Corsair K95 RGB and Corsair iCUE software
HP Wired mouse
Logitech Desktop Mic

also an Aura LED controller built into motherboard

Here is what is connected, but drivers still showing up

Logitech Virtual device Software for a G502 that was connected to K95 before the left mouse button died

Focusrite Audio Usb software root Focusrite Scarlett Solo 2nd gen that is unplugged


Here is what was connected prior to disconnecting 2 extension cables

Razer Kiyo Webcam connected via USB extension cable
Connected to USB Hub which is connected to USB extension cable
Logitech Extreme 3D Pro
Saitek Flight Rudder Pedals drivers were updated after failing driver verifier


here is a link to the latest full memory dump from 11/8/2020: https://1drv.ms/u/s!AreYLbFUtxfggVVH0w3er_OilW9w?e=RMRRn5
here is a link to minidumps of crashes since september: https://1drv.ms/u/s!AreYLbFUtxfggVQ0yQwBlHn49si3?e=1vOax9

here is what i get from the win debugger tool


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


Loading Dump File [C:\Users\Chandler Henson\Desktop\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 = 0xfffff806`4d800000 PsLoadedModuleList = 0xfffff806`4e42a310
Debug session time: Sun Nov 8 12:57:09.585 2020 UTC - 5:00
System Uptime: 0 days 1:01:47.221
Loading Kernel Symbols
...............................................................
..................Page ffe556 not present in the dump file. Type ".hh dbgerr004" for details
..............................................
................................................................
..........................................................
Loading User Symbols

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: fffff8064dad4ba4, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: ffffc8899f98cd90, 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: 90

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8064dad4ba4

BUGCHECK_P3: 1

BUGCHECK_P4: ffffc8899f98cd90

WRITE_ADDRESS: ffffc8899f98cd90 Nonpaged pool

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: ffffc8899f98cd90

BLACKBOXBSD: 1 !blackboxbsd


BLACKBOXNTFS: 1 !blackboxntfs


BLACKBOXPNP: 1 !blackboxpnp


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

TRAP_FRAME: fffff8065366b140 -- .trap 0xfffff8065366b140
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8065366b338 rbx=0000000000000000 rcx=ffffc8899f98cdc0
rdx=0000000070436f49 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8064dad4ba4 rsp=fffff8065366b2d0 rbp=ffffc88a9fa515e0
r8=ffffc88aba6ef3c0 r9=000000000000000c r10=0000fffff8064daa
r11=ffff80f82b800000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ObfReferenceObjectWithTag+0x24:
fffff806`4dad4ba4 f0480fc15ed0 lock xadd qword ptr [rsi-30h],rbx ds:ffffffff`ffffffd0=????????????????
Resetting default scope

BAD_STACK_POINTER: fffff80653680158

STACK_TEXT:
fffff806`53680158 fffff806`4dcf465e : 00000000`0000001e ffffffff`c0000005 fffff806`4dad4ba4 00000000`00000001 : nt!KeBugCheckEx
fffff806`53680160 fffff806`4dbfd462 : fffff806`4dcf463c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff806`536801a0 fffff806`4da52d97 : fffff806`53680710 00000000`00000000 fffff806`5366bc60 fffff806`4dbf810e : nt!RtlpExecuteHandlerForException+0x12
fffff806`536801d0 fffff806`4da519a6 : fffff806`5366b098 fffff806`53680e20 fffff806`5366b098 00000000`00000000 : nt!RtlDispatchException+0x297
fffff806`536808f0 fffff806`4dbf5432 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff806`53680fb0 fffff806`4dbf5400 : fffff806`4dc066a5 ffffc889`9f98cd90 fffff806`5366b060 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff806`5366af58 fffff806`4dc066a5 : ffffc889`9f98cd90 fffff806`5366b060 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff806`5366af60 fffff806`4dc02843 : 00000000`00000000 00000000`00000000 ffffc88a`9fee5000 00000000`00000002 : nt!KiExceptionDispatch+0x125
fffff806`5366b140 fffff806`4dad4ba4 : ffffc88a`a02f1970 fffff806`4e1b1019 00000000`00000000 fffff806`4ca0818a : nt!KiPageFault+0x443
fffff806`5366b2d0 fffff806`4daa1c03 : ffffc889`9f98cdc0 ffffc88a`ba6ef3c0 ffffc88a`a02f1970 00000000`00000000 : nt!ObfReferenceObjectWithTag+0x24
fffff806`5366b310 fffff806`4dac310e : ffffc88a`9fa515e0 fffff806`5366b3c9 ffffc88a`9f98cdc0 ffffc88a`9fa519cb : nt!IopUnloadSafeCompletion+0x43
fffff806`5366b340 fffff806`4dac2fd7 : 00000000`00000001 00000000`00000000 ffffc88a`9fa550e0 00000000`00000002 : nt!IopfCompleteRequest+0x11e
fffff806`5366b430 fffff806`51db811a : 00000000`00000000 ffffc88a`a0219bf0 ffffc88a`9fa515e0 fffff806`5366b510 : nt!IofCompleteRequest+0x17
fffff806`5366b460 fffff806`51db5bbf : ffffc88a`9fa6b702 ffffc88a`9fa1a0d0 ffffc88a`9fa515e0 00000000`00000000 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
fffff806`5366b4f0 fffff806`5f09b91c : 00000000`ffffff02 ffffc88a`9fa6b5f0 ffffc88a`9fa554c0 ffffc88a`9fa554c0 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
fffff806`5366b550 fffff806`5f09b7e1 : ffffc88a`9fa6b790 00000000`00000005 ffffc88a`9fa6b820 fffff806`5366b768 : USBXHCI!Bulk_Transfer_CompleteCancelable+0xc8
fffff806`5366b5b0 fffff806`5f09b5d0 : 00000000`00000004 fffff806`5366b720 00000000`00000000 ffffc88a`9fa405f0 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x1fd
fffff806`5366b660 fffff806`5f096570 : 00000000`00000004 fffff806`5366b738 00000000`00000008 fffff806`5366b740 : USBXHCI!Bulk_EP_TransferEventHandler+0x10
fffff806`5366b690 fffff806`5f0960a5 : 00000000`00000780 00003775`5fd15f00 ffffc88a`a0682d20 ffffc88a`9f82b0d0 : USBXHCI!Endpoint_TransferEventHandler+0xb0
fffff806`5366b6f0 fffff806`5f095d7c : 00000000`00000002 00000000`00000000 00003775`5f99a728 00000000`00000001 : USBXHCI!Interrupter_DeferredWorkProcessor+0x315
fffff806`5366b7f0 fffff806`51db38f5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc
fffff806`5366b820 fffff806`4dae549e : fffff806`4a56b240 00000000`00000000 fffff806`5366bb20 00000000`00000000 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa5 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 404]
fffff806`5366b860 fffff806`4dae4784 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff806`5366b9d0 fffff806`4dbf810e : 00000000`00000000 fffff806`4a568180 fffff806`4e527600 ffffc88a`ad37a080 : nt!KiRetireDpcList+0x1f4
fffff806`5366bc60 00000000`00000000 : fffff806`5366c000 fffff806`53666000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: USBXHCI!Bulk_Transfer_CompleteCancelable+c8

MODULE_NAME: USBXHCI

IMAGE_NAME: USBXHCI.SYS

IMAGE_VERSION: 10.0.19041.488

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: c8

FAILURE_BUCKET_ID: 0x1E_c0000005_W_STACKPTR_ERROR_USBXHCI!Bulk_Transfer_CompleteCancelable

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {11db9b30-7bb1-197f-15bc-9999f424c0f6}

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

:)

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

wdf01000.sys and ntoskrnl.exe BSOD

I'm on Windows 10, 64bit

Basically, whenever I try to update my LPC controller through Device Manager, BSOD with WDF_VIOLATION occurs (culprit being wdf01000.sys)

So I try to use the driver verifier to see which driver is causing the BSOD, but then it causes BSOD (cultprit being ntoskrnl.exe)

Have no idea which driver is causing them

Please help!

Here are my list of drivers and system info: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

dxgmms2.sys BSOD

Hello,

A while back, my computer lost power while it was installing windows updates. Since then, I've had BSODs every couple days, with various errors pointing to a driver error. These were annoying, but manageable. I tried a few basic troubleshooting steps, like
using a removal tool for my graphics card drivers and reinstalling, but I didn't do much else.

The last couple days, the BSOD rate has ramped up, and I started seeing "dxgmms2.sys" get listed in the BSODs, which is relatively new.

I followed the instructions
here.

And here are my dmp files resulting from that:
https://1drv.ms/u/s!Au4wk9mJt6sJgcFgkEXA4rOFod4-cg?e=wIzEMq

Thanks.