G
GhostReaper2043
Guest
Description
A problem with your hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
Code: 144
Parameter 1: 1006
Parameter 2: fffff0088eb95960
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_18363
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.18363.2.0.0.768.101
Locale ID: 1033
Files that help describe the problem
USBXHCI-20200111-1135.dmp
sysdata.xml
WERInternalMetadata.xml
WERInternalRequest.xml
memory.csv
sysinfo.txt
I get this every time im gaming I do have everything up to date Graphics, Windows updates, and drivers, and bios etc. So why does this keep happening. This is what i have so far.
Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\GhostReaper2043\AppData\Local\Temp\WERC4CB.tmp\USBXHCI-20200111-1135.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 18363 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`3e600000 PsLoadedModuleList = 0xfffff803`3ea48130
Debug session time: Sat Jan 11 11:35:42.646 2020 (UTC - 7:00)
System Uptime: 0 days 0:58:55.360
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
USBXHCI!TelemetryData_CreateReport+0xcc:
fffff803`4b2e8c84 488b03 mov rax,qword ptr [rbx] ds:002b:ffffcb88`6b751460=????????????????
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB3_DRIVER (144)
This bugcheck usually happens when the USB3 core stack detects an invalid
operation being performed by a USB client. This bugcheck may also occur
due to hardware failure on a USB Boot Device.
Arguments:
Arg1: 0000000000001006, USB3_WER_BUGCODE_USBXHCI_CONTEXT_ERROR_AFTER_STALL_RESET_EP
Reset EP failed during an attempt to clear stall on control
endpoint.
Arg2: fffff0088eb95960, XHCI_LIVEDUMP_CONTEXT
Arg3: 0000000000000000, 0
Arg4: 0000000000000000, 0
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on GHOSTREAPER2043
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 5
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 144
BUGCHECK_P1: 1006
BUGCHECK_P2: fffff0088eb95960
BUGCHECK_P3: 0
BUGCHECK_P4: 0
HARDWARE_VENDOR_ID: VEN_1022
HARDWARE_DEVICE_ID: DEV_43D0
HARDWARE_REV_ID: REV_0001
HARDWARE_ID: VEN_1022&DEV_43D0&REV_0001
PROCESS_NAME: System
STACK_TEXT:
fffff008`8eb953e0 fffff803`4b2b0bb8 : 00000000`00000005 ffffcb88`6c6bc750 fffff803`4b2ec618 ffffffff`ffffffff : USBXHCI!TelemetryData_CreateReport+0xcc
fffff008`8eb95910 fffff803`4b2b1080 : ffffcb88`651f22e0 fffff008`8eb95a40 00000000`00000000 00000000`00000000 : USBXHCI!Controller_TelemetryReport+0x15c
fffff008`8eb95a00 fffff803`42333fd9 : ffffcb88`651f21e0 00000000`00000008 00000000`00000008 ffffcb88`65968060 : USBXHCI!Controller_TelemetryReportWorker+0x290
fffff008`8eb95a80 fffff803`42333e69 : ffffdf81`e5a00100 ffffcb88`651f21e0 ffffcb88`6df9d040 fffff803`3e6bd54c : Wdf01000!FxWorkItem::WorkItemHandler+0x7d [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 371]
fffff008`8eb95ac0 fffff803`3e667c0f : ffffcb88`6516ac30 00000000`00000000 00000000`00000000 fffff803`4232adc0 : Wdf01000!FxWorkItem::WorkItemThunk+0x29 [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 439]
fffff008`8eb95b00 fffff803`3e6bd095 : ffffcb88`5d698a20 ffffcb88`6df9d040 fffff803`3e667b10 00000000`0000000c : nt!IopProcessWorkItem+0xff
fffff008`8eb95b70 fffff803`3e72a7a5 : ffffcb88`6df9d040 00000000`00000080 ffffcb88`5d67e040 ffffffff`00000001 : nt!ExpWorkerThread+0x105
fffff008`8eb95c10 fffff803`3e7c8b2a : ffffdf81`e5c00180 ffffcb88`6df9d040 fffff803`3e72a750 fffff008`8eb95cd0 : nt!PspSystemThreadStartup+0x55
fffff008`8eb95c60 00000000`00000000 : fffff008`8eb96000 fffff008`8eb90000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
SYMBOL_NAME: USBXHCI!TelemetryData_CreateReport+cc
MODULE_NAME: USBXHCI
IMAGE_NAME: USBXHCI.SYS
IMAGE_VERSION: 10.0.18362.476
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: cc
FAILURE_BUCKET_ID: LKD_0x144_CONTEXT_ERROR_AFTER_STALL_RESET_EP_USBXHCI!TelemetryData_CreateReport
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7f041737-6927-8fbc-f0ba-712e8ab3eb69}
Followup: MachineOwner
---------
Continue reading...
A problem with your hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
Code: 144
Parameter 1: 1006
Parameter 2: fffff0088eb95960
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_18363
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.18363.2.0.0.768.101
Locale ID: 1033
Files that help describe the problem
USBXHCI-20200111-1135.dmp
sysdata.xml
WERInternalMetadata.xml
WERInternalRequest.xml
memory.csv
sysinfo.txt
I get this every time im gaming I do have everything up to date Graphics, Windows updates, and drivers, and bios etc. So why does this keep happening. This is what i have so far.
Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\GhostReaper2043\AppData\Local\Temp\WERC4CB.tmp\USBXHCI-20200111-1135.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 18363 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`3e600000 PsLoadedModuleList = 0xfffff803`3ea48130
Debug session time: Sat Jan 11 11:35:42.646 2020 (UTC - 7:00)
System Uptime: 0 days 0:58:55.360
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
USBXHCI!TelemetryData_CreateReport+0xcc:
fffff803`4b2e8c84 488b03 mov rax,qword ptr [rbx] ds:002b:ffffcb88`6b751460=????????????????
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB3_DRIVER (144)
This bugcheck usually happens when the USB3 core stack detects an invalid
operation being performed by a USB client. This bugcheck may also occur
due to hardware failure on a USB Boot Device.
Arguments:
Arg1: 0000000000001006, USB3_WER_BUGCODE_USBXHCI_CONTEXT_ERROR_AFTER_STALL_RESET_EP
Reset EP failed during an attempt to clear stall on control
endpoint.
Arg2: fffff0088eb95960, XHCI_LIVEDUMP_CONTEXT
Arg3: 0000000000000000, 0
Arg4: 0000000000000000, 0
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on GHOSTREAPER2043
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 5
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 144
BUGCHECK_P1: 1006
BUGCHECK_P2: fffff0088eb95960
BUGCHECK_P3: 0
BUGCHECK_P4: 0
HARDWARE_VENDOR_ID: VEN_1022
HARDWARE_DEVICE_ID: DEV_43D0
HARDWARE_REV_ID: REV_0001
HARDWARE_ID: VEN_1022&DEV_43D0&REV_0001
PROCESS_NAME: System
STACK_TEXT:
fffff008`8eb953e0 fffff803`4b2b0bb8 : 00000000`00000005 ffffcb88`6c6bc750 fffff803`4b2ec618 ffffffff`ffffffff : USBXHCI!TelemetryData_CreateReport+0xcc
fffff008`8eb95910 fffff803`4b2b1080 : ffffcb88`651f22e0 fffff008`8eb95a40 00000000`00000000 00000000`00000000 : USBXHCI!Controller_TelemetryReport+0x15c
fffff008`8eb95a00 fffff803`42333fd9 : ffffcb88`651f21e0 00000000`00000008 00000000`00000008 ffffcb88`65968060 : USBXHCI!Controller_TelemetryReportWorker+0x290
fffff008`8eb95a80 fffff803`42333e69 : ffffdf81`e5a00100 ffffcb88`651f21e0 ffffcb88`6df9d040 fffff803`3e6bd54c : Wdf01000!FxWorkItem::WorkItemHandler+0x7d [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 371]
fffff008`8eb95ac0 fffff803`3e667c0f : ffffcb88`6516ac30 00000000`00000000 00000000`00000000 fffff803`4232adc0 : Wdf01000!FxWorkItem::WorkItemThunk+0x29 [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 439]
fffff008`8eb95b00 fffff803`3e6bd095 : ffffcb88`5d698a20 ffffcb88`6df9d040 fffff803`3e667b10 00000000`0000000c : nt!IopProcessWorkItem+0xff
fffff008`8eb95b70 fffff803`3e72a7a5 : ffffcb88`6df9d040 00000000`00000080 ffffcb88`5d67e040 ffffffff`00000001 : nt!ExpWorkerThread+0x105
fffff008`8eb95c10 fffff803`3e7c8b2a : ffffdf81`e5c00180 ffffcb88`6df9d040 fffff803`3e72a750 fffff008`8eb95cd0 : nt!PspSystemThreadStartup+0x55
fffff008`8eb95c60 00000000`00000000 : fffff008`8eb96000 fffff008`8eb90000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
SYMBOL_NAME: USBXHCI!TelemetryData_CreateReport+cc
MODULE_NAME: USBXHCI
IMAGE_NAME: USBXHCI.SYS
IMAGE_VERSION: 10.0.18362.476
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: cc
FAILURE_BUCKET_ID: LKD_0x144_CONTEXT_ERROR_AFTER_STALL_RESET_EP_USBXHCI!TelemetryData_CreateReport
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7f041737-6927-8fbc-f0ba-712e8ab3eb69}
Followup: MachineOwner
---------
Continue reading...