Windows SP 3 Guest OS Blue Screens everytime an iPod is plugged in. Host OS is Win 7 x64. Running Workstation 7. Here's the dump from the guest OS:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRVC:\Symbolshttp://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Apr 22 18:31:12.629 2010 (UTC - 7:00)
System Uptime: 0 days 1:08:37.127
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*
Bugcheck Analysis *
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {8, 2, 0, babd35af}
Probably caused by : usbuhci.sys ( usbuhci!UhciAbortAsyncTransfer+4f )
Followup: MachineOwner
-
0: kd> !analyze -v
*******************************************************************************
*
Bugcheck Analysis *
*
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000008, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: babd35af, address which referenced memory
Debugging Details:
-
READ_ADDRESS: 00000008
CURRENT_IRQL: 2
FAULTING_IP:
usbuhci!UhciAbortAsyncTransfer+4f
babd35af 8b4e08 mov ecx,dword ptr
CUSTOMER_CRASH_COUNT: 8
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from babd11fb to babd35af
STACK_TEXT:
ba5a9c74 babd11fb 89aef9dc 89520588 895ce690 usbuhci!UhciAbortAsyncTransfer+0x4f
ba5a9c98 ba52948b 89aef9dc 89520588 895ce690 usbuhci!UhciAbortTransfer+0x3d
ba5a9ce4 ba529753 89aef028 89520410 80546afc USBPORT!USBPORT_DmaEndpointPaused+0x263
ba5a9d10 ba52bb7c 89aef028 80546afc 89520410 USBPORT!USBPORT_DmaEndpointWorker+0x149
ba5a9d38 ba52f5ea 89aef028 00000002 89aef028 USBPORT!USBPORT_CoreEndpointWorker+0x6d2
ba5a9d7c ba5281b0 89aef028 00000000 899fa020 USBPORT!USBPORT_Worker+0x212
ba5a9dac 805cff62 89aef028 00000000 00000000 USBPORT!USBPORT_WorkerThread+0x12a
ba5a9ddc 8054611e ba528086 89aef028 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
usbuhci!UhciAbortAsyncTransfer+4f
babd35af 8b4e08 mov ecx,dword ptr
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: usbuhci!UhciAbortAsyncTransfer+4f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbuhci
IMAGE_NAME: usbuhci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 480254ce
FAILURE_BUCKET_ID: 0xD1_usbuhci!UhciAbortAsyncTransfer+4f
BUCKET_ID: 0xD1_usbuhci!UhciAbortAsyncTransfer+4f
Followup: MachineOwner
-
Hi,
Do you still see the problem if you select "Enable high-speed support for USB 2.0 devices" in the GUI?
Thanks,
Doug
Hi,
Do you still see the problem if you select "Enable high-speed support for USB 2.0 devices" in the GUI?
Thanks,
Doug
That did the trick! I had to upgrade the virtual hardware from version 5 to version 6.5. Once I did that, high speed USB 2.0 was enabled and the problem went away.
Thanks,
Mike.