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: 0000000000001020, USB3_WER_BUGCODE_USBXHCI_INVALID_TRANSFER_EVENT_PTR_ED_0_DUPLICATE
	The controller indicated a transfer completion that was not pending on the controller.
	EventData == 0 (logical address in transfer event TRB not matched)
	The Transfer Event TRB may be redundant (points somewhere near a recently completed request).
Arg2: ffff948eeef4d9a0, XHCI_LIVEDUMP_CONTEXT
Arg3: 0000000000000000, 0
Arg4: 0000000000000000, 0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2452

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on ALEX-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 12007

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

BUGCHECK_CODE:  144

BUGCHECK_P1: 1020

BUGCHECK_P2: ffff948eeef4d9a0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

HARDWARE_VENDOR_ID:  VEN_1022

HARDWARE_DEVICE_ID:  DEV_43BB

HARDWARE_REV_ID:  REV_0002

HARDWARE_ID:  VEN_1022&DEV_43BB&REV_0002

PROCESS_NAME:  System

STACK_TEXT:
ffff948e`eef4d420 fffff807`81c82a48     : 00000000`00000005 ffffb28f`29145db0 fffff807`81ca53e8 ffffffff`ffffffff : USBXHCI!TelemetryData_CreateReport+0xcc
ffff948e`eef4d950 fffff807`81c82f1d     : ffffb28f`14e54460 ffff948e`eef4da80 ffffb28f`176caab0 00000000`00000000 : USBXHCI!Controller_TelemetryReport+0x158
ffff948e`eef4da40 fffff807`777bc6a7     : ffffb28f`14e54360 ffffb28f`00000004 00000000`00000004 00000000`00000000 : USBXHCI!Controller_TelemetryReportWorker+0x28d
ffff948e`eef4dac0 fffff807`732d9d75     : ffffb28f`17726e00 00000000`00000000 ffffb28f`177af2c0 fffff807`777bc5c0 : Wdf01000!FxWorkItem::WorkItemThunk+0xe7 [minkernel\wdf\framework\shared\core\fxworkitem.cpp @ 431]
ffff948e`eef4db00 fffff807`73233f45     : ffffb28f`126a15c0 ffffb28f`126a15c0 fffff807`732d9c40 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffff948e`eef4db70 fffff807`73346745     : ffffb28f`126a15c0 00000000`00000080 ffffb28f`126c4080 00000000`00000000 : nt!ExpWorkerThread+0x105
ffff948e`eef4dc10 fffff807`733e5598     : ffffe401`48a80180 ffffb28f`126a15c0 fffff807`733466f0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff948e`eef4dc60 00000000`00000000     : ffff948e`eef4e000 ffff948e`eef48000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  USBXHCI!TelemetryData_CreateReport+cc

MODULE_NAME: USBXHCI

IMAGE_NAME:  USBXHCI.SYS

IMAGE_VERSION:  10.0.19041.423

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  cc

FAILURE_BUCKET_ID:  LKD_0x144_INVALID_TRANSFER_EVENT_PTR_ED_0_DUPLICATE_USBXHCI!TelemetryData_CreateReport

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5cc4d0c0-23fc-a3b2-ae65-4fd9f06428b8}

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