*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {4, ffffe001fb0f0b10, ffffe001fb634520, ffffe001ff31401c}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_ProcessURB+1049b )
Followup: MachineOwner
---------
3: kd> !analyze -v;r;kv;lmtsmn;.bugcheck;!peb;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {4, ffffe001fb0f0b10, ffffe001fb634520, ffffe001ff31401c}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_ProcessURB+1049b )
Followup: MachineOwner
---------
3: kd> !analyze -v;r;kv;lmtsmn;.bugcheck;!peb;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000004, IRP_URB_DOUBLE_SUBMIT The caller has submitted an irp
that is already pending in the USB bus driver.
Arg2: ffffe001fb0f0b10, Address of IRP
Arg3: ffffe001fb634520, Address of URB
Arg4: ffffe001ff31401c
did you see it anywhere else other than the driver stack?I agree, but it is there for some reason.