Windows 10: Windows 10 USBXHCI.sys crash

Discus and support Windows 10 USBXHCI.sys crash in Windows 10 BSOD Crashes and Debugging to solve the problem; After about 2 months a USBXHCI.sys crash has occurred again, I am getting fed up with these crashes, i can't trace down what is causing them I thought... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by ChandlerH1990, Jan 18, 2021.

  1. Windows 10 USBXHCI.sys crash

    After about 2 months a USBXHCI.sys crash has occurred again, I am getting fed up with these crashes, i can't trace down what is causing them I thought it was a USB hub or extension cable

    Motherboard is Asus Crosshair VIII Hero Wifi

    AMD Ryzen 7 5800X

    64GB DDR4

    Radeon HD 7570 untill RTX 2070 super is back from RMA

    Windows and drivers are up to date.

    NZXT Kraken X73 AIO Liquid Cooler and NZXT Cam Software
    Corsair K95 RGB and Corsair iCUE software
    Logitech G502 Hero
    Logitech Desktop Mic

    Razer Kiyo Webcam

    also an Aura LED controller built into motherboard

    ill be uploading a memory dump here in a bit

    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 = 0xfffff807`2d800000 PsLoadedModuleList = 0xfffff807`2e42a2f0

    Debug session time: Mon Jan 18 13:36:01.230 2021 UTC - 5:00

    System Uptime: 0 days 3:54:44.818

    Loading Kernel Symbols


    ..................Page c347bc not present in the dump file. Type ".hh dbgerr004" for details

    ........Page 555a4 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 *

    * *



    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.


    Arg1: ffffffffc0000005, The exception code that was not handled

    Arg2: fffff8072da5a2f4, The address that the exception occurred at

    Arg3: 0000000000000001, Parameter 0 of the exception

    Arg4: ffffd7057e8a2b50, Parameter 1 of the exception

    Debugging Details:



    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: 5

    Key : Analysis.Memory.CommitPeak.Mb

    Value: 87

    Key : Analysis.System

    Value: CreateObject


    BUGCHECK_P1: ffffffffc0000005

    BUGCHECK_P2: fffff8072da5a2f4

    BUGCHECK_P3: 1

    BUGCHECK_P4: ffffd7057e8a2b50

    WRITE_ADDRESS: ffffd7057e8a2b50 Nonpaged pool

    EXCEPTION_PARAMETER1: 0000000000000001

    EXCEPTION_PARAMETER2: ffffd7057e8a2b50

    BLACKBOXBSD: 1 !blackboxbsd

    BLACKBOXNTFS: 1 !blackboxntfs

    BLACKBOXPNP: 1 !blackboxpnp


    PROCESS_NAME: System

    TRAP_FRAME: fffff8073146d100 -- .trap 0xfffff8073146d100

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=fffff8073146d2f8 rbx=0000000000000000 rcx=ffffd7057e8a2b80

    rdx=0000000070436f49 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8072da5a2f4 rsp=fffff8073146d290 rbp=ffffd7067e9de010

    r8=ffffd706a54c55e0 r9=0000000000000002 r10=0000fffff8072db1

    r11=ffffa07e98600000 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei pl zr na po nc


    fffff807`2da5a2f4 f0480fc15ed0 lock xadd qword ptr [rsi-30h],rbx ds:ffffffff`ffffffd0=????????????????

    Resetting default scope

    BAD_STACK_POINTER: fffff80731483158


    fffff807`31483158 fffff807`2dcf4b0e : 00000000`0000001e ffffffff`c0000005 fffff807`2da5a2f4 00000000`00000001 : nt!KeBugCheckEx

    fffff807`31483160 fffff807`2dbfe642 : fffff807`2dcf4aec 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22

    fffff807`314831a0 fffff807`2db2bf97 : fffff807`31483710 00000000`00000000 fffff807`3146dc20 fffff807`2dbf92ee : nt!RtlpExecuteHandlerForException+0x12

    fffff807`314831d0 fffff807`2db2ab86 : fffff807`3146d058 fffff807`31483e20 fffff807`3146d058 00000000`00000000 : nt!RtlDispatchException+0x297

    fffff807`314838f0 fffff807`2dbf6612 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186

    fffff807`31483fb0 fffff807`2dbf65e0 : fffff807`2dc078a5 ffffd705`7e8a2b50 fffff807`3146d020 ffffd706`7e7f0001 : nt!KxExceptionDispatchOnExceptionStack+0x12

    fffff807`3146cf18 fffff807`2dc078a5 : ffffd705`7e8a2b50 fffff807`3146d020 ffffd706`7e7f0001 ffffd706`7e985a88 : nt!KiExceptionDispatchOnExceptionStackContinue

    fffff807`3146cf20 fffff807`2dc03a43 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd706`7e6fdd28 : nt!KiExceptionDispatch+0x125

    fffff807`3146d100 fffff807`2da5a2f4 : ffffd706`7e246d40 fffff807`2e1b1019 ffffd706`00000000 ffffd706`995fd7a0 : nt!KiPageFault+0x443

    fffff807`3146d290 fffff807`2db16f43 : ffffd705`7e8a2b80 ffffd706`a54c55e0 ffffd706`7e246d40 fffff807`3146d389 : nt!ObfReferenceObjectWithTag+0x24

    fffff807`3146d2d0 fffff807`2da4885e : ffffd706`7e9de010 fffff807`3146d389 ffffd706`7e8a2b80 ffffd706`7e9de63b : nt!IopUnloadSafeCompletion+0x43

    fffff807`3146d300 fffff807`2da48727 : 00000000`00000001 00000000`00000000 ffffd706`7e8a7020 00000000`00000002 : nt!IopfCompleteRequest+0x11e

    fffff807`3146d3f0 fffff807`2fdb811a : 00000000`00000000 ffffd706`7ee30dc0 ffffd706`7e9de010 fffff807`3146d4d0 : nt!IofCompleteRequest+0x17

    fffff807`3146d420 fffff807`2fdb5bbf : ffffd706`7e8d8602 ffffd706`7e8d54e0 ffffd706`7e9de010 00000000`00000000 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]

    fffff807`3146d4b0 fffff807`3cebb91c : 00000000`ffffff02 ffffd706`7e8d84f0 ffffd706`7e8a7400 ffffd706`7e8a7400 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]

    fffff807`3146d510 fffff807`3cebb7e1 : ffffd706`7e8d8690 00000000`00000008 ffffd706`7e8d8720 fffff807`3146d728 : USBXHCI!Bulk_Transfer_CompleteCancelable+0xc8

    fffff807`3146d570 fffff807`3cebb5d0 : 00000000`00000004 fffff807`3146d6e0 00000000`00000000 ffffd706`7e8a7620 : USBXHCI!Bulk_ProcessTransferEventWithED1+0x1fd

    fffff807`3146d620 fffff807`3ceb6570 : 00000000`00000004 fffff807`3146d6f8 00000000`00000008 fffff807`3146d700 : USBXHCI!Bulk_EP_TransferEventHandler+0x10

    fffff807`3146d650 fffff807`3ceb60a5 : 00000000`00000780 000028f9`814b1f00 ffffd706`7f14d220 ffffd706`7e975c60 : USBXHCI!Endpoint_TransferEventHandler+0xb0

    fffff807`3146d6b0 fffff807`3ceb5d7c : ffffd706`7e48d328 fffff807`28644180 000028f9`80ee3638 fffff807`3146d7d0 : USBXHCI!Interrupter_DeferredWorkProcessor+0x315

    fffff807`3146d7b0 fffff807`2fdb38f5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc

    fffff807`3146d7e0 fffff807`2da0781e : fffff807`28647240 00000000`00000000 fffff807`3146dae0 fffff807`28644180 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0xa5 [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 404]

    fffff807`3146d820 fffff807`2da06b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e

    fffff807`3146d990 fffff807`2dbf92ee : 00000000`00000000 fffff807`28644180 fffff807`2e526600 ffffd706`83c03540 : nt!KiRetireDpcList+0x1f4

    fffff807`3146dc20 00000000`00000000 : fffff807`3146e000 fffff807`31467000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

    SYMBOL_NAME: USBXHCI!Bulk_Transfer_CompleteCancelable+c8



    IMAGE_VERSION: 10.0.19041.662

    STACK_COMMAND: .thread ; .cxr ; kb


    FAILURE_BUCKET_ID: 0x1E_c0000005_W_STACKPTR_ERROR_USBXHCI!Bulk_Transfer_CompleteCancelable

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release


    OSNAME: Windows 10

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

    Followup: MachineOwner


    ChandlerH1990, Jan 18, 2021
  2. peach1971 Win User

    all games crash!

    I suggest you run rthdribl >
    Increase the window size step by step and watch your vga temps permanently.
    What happens?
    If it crashes, run at stock speeds as suggested before and retry.

    P.S.: When your system locks, does the display signal turn off after a time?
    Stuttering sound or no sound at all when freezing?
    What X1800XT model do you own exactly?
    peach1971, Jan 18, 2021
  3. AllenAyen Win User
    Windows 10 it crashes the sys

    Windows 10 crashes my sys at the 32% install. After reinstalling Windows 8.1 I have to disable auto new device install or the sys will crash
    AllenAyen, Jan 18, 2021
  4. Ahhzz Win User

    Windows 10 USBXHCI.sys crash

    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.
    Ahhzz, Jan 18, 2021

Windows 10 USBXHCI.sys crash

  1. Windows 10 USBXHCI.sys crash - Similar Threads - USBXHCI sys crash

  2. PC Crashes, no BSOD, usbhub3.sys

    in Windows 10 Gaming
    PC Crashes, no BSOD, usbhub3.sys: Hi! My PC is crashing like 1-3 times a day. Its really weird because now I have this USBHUB3, WATCHDOG and USBXHCI folder, the date on the folder fits with the hour when the PC crashed but no dmp. Heres the pictures of the folders dates date and time when the crash...
  3. USBxHCI Compliant Host Controller code 10

    in Windows 10 Drivers and Hardware
    USBxHCI Compliant Host Controller code 10: Hello i recently got this gaming pc , and ever since i got it none of my USB ports work . When i go to device manager and i expand universal serial bus controllers usbxhci compliant host controller shows up with a yellow triangle with a exclamation mark. i have tried to...
  4. Windows 10 rtwlane02.sys crash with debug info

    in Windows 10 Installation and Upgrade
    Windows 10 rtwlane02.sys crash with debug info: It passed a few months since the BSOD persist.. so I decided to ask for help in order to leave this problem forever. My wifi adapter is TP-Link Wireless N PCI Express TL-WN881ND 300 mbps. [IMG] Minidump info: Microsoft R Windows Debugger Version 10.0.17763.1 AMD64...
  5. Repeated crashes due to Netwtw06.sys failure

    in Windows 10 Drivers and Hardware
    Repeated crashes due to Netwtw06.sys failure: Split from this thread. Hello my name is romeo i have problem with my asus desktop it keeps crashing every 10-15 minutes when u turn it on and its show like this in the pucture what should i do please can you help me[IMG]...
  6. Repeated crashes due to Netwtw06.sys failure

    in Windows 10 Drivers and Hardware
    Repeated crashes due to Netwtw06.sys failure: Split from this thread. hi, i just started having this issue yesterday after i got a new modem on tuesday and put in the new password for modem/ router... ATaT device... followed the stems on the forum gladly the blue screen has the error indicated... any way i seem to...
  7. Repeated crashes due to Netwtw06.sys failure

    in Windows 10 Drivers and Hardware
    Repeated crashes due to Netwtw06.sys failure: Split from this thread. Same problem. Have had Tech people check hardware and replace Windows 10 and update Windows 10 with November updates, but all have failed....
  8. Repeated crashes due to Netwtw06.sys Error Code

    in Windows 10 Drivers and Hardware
    Repeated crashes due to Netwtw06.sys Error Code: I have had Geeks squad look at computer and they said they updated driver. I picked computer up and it crashed again yesterday. I just now updated the Intel WiFi driver as downloaded the Intel Utility device which said there were a few drivers that needed to be updated....
  9. Repeated crashes due to Netwtw06.sys failure

    in Windows 10 Drivers and Hardware
    Repeated crashes due to Netwtw06.sys failure: My ASUS laptop downloaded and installed the latest Windows 10 updates (on August 31) after which my laptop crashes within 5-10 minutes of use. The stop code error message I get is PAGE_FAULT_IN_NONPAGED_AREA. What failed: Netwtw06.sys. I collected my system information and...
  10. Laptop crashes caused by 'rtkvhd64.sys'

    in Windows 10 BSOD Crashes and Debugging
    Laptop crashes caused by 'rtkvhd64.sys': My laptop is crashing . Please check out these minidumps-!ApFhXMFCkw0wgkG1PupSUzd9eHZi Thanks, Regal76 ***Original Title: My laptop crashing.***...