IRQL_NOT_LESS_OR_EQUAL

[darkwing]

After I installed VirtualBox 2.1.4 on my Windows XP Tablet PC, every time I tried to start VirtualBox, I get the blue screen of death. Under Technical information, I have * STOP: 0x0000000A (0x00000016, 0x0000001C, 0x00000000, 0x80502392).

I plan on installing Red Hat for a virtual machine but I never got that far because VirtualBox would not run.

[misha]

Does it happen on VirtualBox 2.1.4 only? I.e. did you see this issue with 2.1.2 or 2.1?
Could you also attach a ​minidump here please.

[darkwing]

I had the same issue when I tried 2.1.2. I reinstalled the system and 2.1.4 is running right now. I saw on one of the track items that the graphic driver might be the cause of the problem so I did not install the graphic driver this time. I had it working before on a previous occasion but it randomly decided to die and not come back up. If I run into the issue again, I will post a minidump. Thanks.

[darkwing]

Vbox Crashed Minidump

[darkwing]

I opened the minidump file using WinDbg and got the followings (I don't think it's working correctly though). I've attached the minidump file above.

---

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini040609-02.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 Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 Debug session time: Mon Apr 6 14:58:04.609 2009 (GMT-4) System Uptime: 0 days 0:00:57.298 *

• 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 Kernel Symbols ............................................................... ................................................................ .. Loading User Symbols Loading unloaded module list ......................... *

• *
• Bugcheck Analysis *
• *

*

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {16, 1c, 0, 80502392}

* Kernel symbols are WRONG. Please fix symbols to do analysis.

* WARNING: Unable to verify timestamp for VBoxUSBMon.sys * ERROR: Module load completed but symbols could not be loaded for VBoxUSBMon.sys * WARNING: Unable to verify timestamp for wdf01000.sys * ERROR: Module load completed but symbols could not be loaded for wdf01000.sys * * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * * * * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!KPRCB * * * * * * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * * * * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!KPRCB * * * * * * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * * * WARNING: Unable to verify timestamp for umpusbvista.sys * ERROR: Module load completed but symbols could not be loaded for umpusbvista.sys * WARNING: Unable to verify timestamp for usbhub.sys * ERROR: Module load completed but symbols could not be loaded for usbhub.sys * * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * * * * * * * * Your debugger is not using the correct symbols * * * * In order for this command to work properly, your symbol path * * must point to .pdb files that have full type information. * * * * Certain .pdb files (such as the public OS symbols) do not * * contain the required information. Contact the group that * * provided you with these symbols if you need this command to * * work. * * * * Type referenced: nt!_KPRCB * * * * *

• 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+ *

* *

• 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+ *

* Probably caused by : VBoxUSBMon.sys ( VBoxUSBMon+750 )

Followup: MachineOwner

---

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.