BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: ffffa7899dba41a0, Device extension pointer of the host controller
Arg3: 0000000010024396, PCI Vendor,Product id for the controller
Arg4: ffffa7899d9c7a68, Pointer to Endpoint data structure
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4171
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-MNQ5K5I
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 29614
Key : Analysis.Memory.CommitPeak.Mb
Value: 79
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: fe
BUGCHECK_P1: 5
BUGCHECK_P2: ffffa7899dba41a0
BUGCHECK_P3: 10024396
BUGCHECK_P4: ffffa7899d9c7a68
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffbe8f`83029598 fffff807`4ff8de94 : 00000000`000000fe 00000000`00000005 ffffa789`9dba41a0 00000000`10024396 : nt!KeBugCheckEx
ffffbe8f`830295a0 fffff807`4ffe8c05 : 00000000`bec2cb00 ffff9701`c93c9080 ffffa789`9d9c7be8 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x17354
ffffbe8f`830295f0 fffff807`4ffe8b5b : ffffa789`9d9c7a68 00000000`00000018 ffffa789`9d9c7be8 fffff807`4d931101 : usbehci!EHCI_sMode_PollEndpointSlot+0x79
ffffbe8f`830296a0 fffff807`4ffed5de : ffffa789`9dba41a0 ffffa789`9dba4050 fffff780`00000320 00000000`ffffffff : usbehci!EHCI_sMode_PollEndpoint+0x5f
ffffbe8f`830296f0 fffff807`4ff70ed3 : ffffa789`9dba4050 ffffa789`9dba41a0 00000000`00000000 ffffa789`9dba41a0 : usbehci!EHCI_PollEndpoint+0x2e
ffffbe8f`83029720 fffff807`4ff70b58 : 00000000`ffffffff ffffa789`9dba4050 ffffa789`9dba4b90 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x1b3
ffffbe8f`83029780 fffff807`4ff76e1b : ffffa789`9dba4b90 00000000`ff9ff19c 00000000`00000002 ffffa789`968e7040 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x218
ffffbe8f`830297e0 fffff807`48ee9a3e : ffffbe8f`83029960 ffffa789`969ca000 ffffbe8f`83029b30 ffff9701`c8866180 : USBPORT!USBPORT_Xdpc_Worker_HcIntDpc+0x18b
ffffbe8f`83029860 fffff807`48ee8d24 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffffbe8f`830299d0 fffff807`48ff7a0e : ffffffff`00000000 ffff9701`c8866180 ffff9701`c8871240 ffffa789`a2e4e080 : nt!KiRetireDpcList+0x1f4
ffffbe8f`83029c60 00000000`00000000 : ffffbe8f`8302a000 ffffbe8f`83024000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: usbehci!EHCI_sMode_PollEndpointSlot+79
MODULE_NAME: usbehci
IMAGE_NAME: usbehci.sys
IMAGE_VERSION: 10.0.19041.1030
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 79
FAILURE_BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5539ea26-939a-447a-4fd6-8b5926f84092}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffff98044f6c3960
Arg4: ffffb38f62d74ad0
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for dxgmms2.sys
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3578
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-MNQ5K5I
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 40392
Key : Analysis.Memory.CommitPeak.Mb
Value: 76
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffff98044f6c3960
BUGCHECK_P4: ffffb38f62d74ad0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9804`4f6c3888 fffff805`365b3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff9804`4f6c3960 : nt!KeBugCheckEx
ffff9804`4f6c3890 fffff805`3941bc61 : 00000000`00000000 ffffb38f`62d71000 ffff9804`4f6c3999 ffffb38f`62d71000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff9804`4f6c38d0 00000000`00000000 : ffffb38f`62d71000 ffff9804`4f6c3999 ffffb38f`62d71000 00000000`00000000 : dxgmms2+0x1bc61
SYMBOL_NAME: dxgmms2+1bc61
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1bc61
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a94318af-dd13-4d43-2ae8-8f2dd0117694}
Followup: MachineOwner
---------
