Not really a question but noting it here and planning to open a bug report about this (*Edit* opened as SR# 1134437591). I was in my XP SP3 VM, no USB devices attached to host or guest. I was connected to a remote machine over VPN+RDP. All of a sudden I got a Windows BSOD for no apparent reason. This is an XP SP3 VM not upgraded to the latest virtual hardware. The error message was USB_BugCheck in usbport.sys
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File C:\WINDOWS\Minidump\Mini090108-01.dmp
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
Executable search path is:
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Sep 1 07:42:49.838 2008 (GMT-5)
System Uptime: 1 days 4:00:43.609
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image USBPORT.SYS, Win32 error 0n2
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, 82ac00e0, 80867112, 82c83e08}
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File C:\WINDOWS\Minidump\Mini090108-01.dmp
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
- Symbol loading may be unreliable without a symbol search path. *
- Use .symfix to have the debugger choose a symbol path. *
- After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
*********************************************************************
- Symbols can not be loaded because symbol path is not initialized. *
- *
- The Symbol Path can be set by: *
- using the _NT_SYMBOL_PATH environment variable. *
- using the -y <symbol_path> argument when starting the debugger. *
- using .sympath and .sympath+ *
Unable to load image ntoskrnl.exe, Win32 error 0n2
- WARNING: Unable to verify timestamp for ntoskrnl.exe
- ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Sep 1 07:42:49.838 2008 (GMT-5)
System Uptime: 1 days 4:00:43.609
*********************************************************************
- Symbols can not be loaded because symbol path is not initialized. *
- *
- The Symbol Path can be set by: *
- using the _NT_SYMBOL_PATH environment variable. *
- using the -y <symbol_path> argument when starting the debugger. *
- using .sympath and .sympath+ *
Unable to load image ntoskrnl.exe, Win32 error 0n2
- WARNING: Unable to verify timestamp for ntoskrnl.exe
- ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image USBPORT.SYS, Win32 error 0n2
- WARNING: Unable to verify timestamp for USBPORT.SYS
- ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
- *
- Bugcheck Analysis *
- *
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, 82ac00e0, 80867112, 82c83e08}