Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
None
Description
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
|
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.
|
Arguments:
|
Arg1: c0000005, The exception code that was not handled
|
Arg2: f7987400, The address that the exception occurred at
|
Arg3: f28f050c, Exception Record Address
|
Arg4: f28f01fc, Context Record Address
|
|
|
f28f065c f79879a6 b4bc1bd0 f28f0714 00000001 usbccgp!USBCCGP_LegacyEnum+0x1d0 [..\..\drivers\usb\usbccgp\function.c @ 647]
|
f28f0678 f7985388 b4bc1bd0 f28f0714 cccccccc usbccgp!USBCCGP_EnumerateFunctions+0xb6 [..\..\drivers\usb\usbccgp\function.c @ 898]
|
f28f069c f798574e b4bc1bd0 b4d0a668 f28f0714 usbccgp!FDO_StartDevice+0x1e8 [..\..\drivers\usb\usbccgp\fdo.c @ 297]
|
f28f06c4 f7985d27 b4bc1bd0 b4d0a668 f28f0714 usbccgp!FDO_HandlePnp+0x13e [..\..\drivers\usb\usbccgp\fdo.c @ 409]
|
f28f06ec f7989ef7 b4bc1bd0 b4d0a668 b4d0a6fc usbccgp!FDO_Dispatch+0xa7 [..\..\drivers\usb\usbccgp\fdo.c @ 626]
|
f28f0704 808898a0 b4bc1bd0 b4d0a668 f28f0814 usbccgp!USBCCGP_Dispatch+0x67 [..\..\drivers\usb\usbccgp\usbccgp.c @ 134]
|
It's crashing on the line
for (Index = 0; Index < FDODeviceExtension->ConfigurationDescriptor->bNumInterfaces; Index++) |
because FDODeviceExtension->ConfigurationDescriptor is NULL. An UHCI error occurred previously which is probably the reason for this:
(..\..\drivers\usb\usbuhci\hardware.cpp:1271) [UHCI] Error interrupt
|
(..\..\drivers\usb\usbuhci\usb_queue.cpp:339) [USBUHCI] Error detected at descriptor F28592A0 Physical 1252a0
|
(..\..\drivers\usb\usbuhci\usb_queue.cpp:354) [USBUHCI] ErrorBuffer 200000 TimeOut 40000 Nak 0 BitStuff 0
|
(..\..\drivers\usb\usbuhci\usb_request.cpp:1233) [USBUHCI] Error detected at descriptor F28592A0 Physical 1252a0
|
(..\..\drivers\usb\usbuhci\usb_request.cpp:1248) [USBUHCI] Buffer Error detected in descriptor F28592A0 Index 3
|
j_anderw, so here's one VMware bug... although not the one we've been trying to catch 