I'm getting a BSOD on WinXP SP3 when I try to start a Ubuntu 10.10 guest in VMware Player. I was able to create the Virtual machine by installing from the ISO file. After the install, I upgraded the Ubuntu packages and starting using the OS. It ran fine up until I closed the VMware player and suspended the virtual machine. Now I get the BSOD whenever I try to start the virtual machine back up. The crash dump keeps showing the exact same backtrace with the crash happening at a call to KeQueryActiveProcessors.
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 805a13f8, memory referenced
Arg2: 0000001d, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 805a13f8, address which referenced memory
Debugging Details:
------------------
OVERLAPPED_MODULE: rdbss
WRITE_ADDRESS: 805a13f8
CURRENT_IRQL: 1d
FAULTING_IP:
nt!KeQueryActiveProcessors+0
805a13f8 a1505a5580 mov eax,[nt!KeActiveProcessors (80555a50)]
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from af0697bd to 805a13f8
TRAP_FRAME: ae31cacc -- (.trap ffffffffae31cacc)
ErrCode = 00000010
eax=00000001 ebx=8c026f01 ecx=000000e1 edx=0000001d esi=00000001 edi=00000004
eip=805a13f8 esp=ae31cb40 ebp=ae31cb70 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010217
nt!KeQueryActiveProcessors:
805a13f8 a1505a5580 mov eax,[nt!KeActiveProcessors (80555a50)] ds:0023:80555a50=0000000f
Resetting default scope
STACK_TEXT:
ae31cb3c af0697bd 00000002 8c026f80 89c3c540 nt!KeQueryActiveProcessors
WARNING: Stack unwind information not available. Following frames may be wrong.
ae31cb70 af0666d6 89c3c540 0136d0a8 891adea8 vmx86+0x37bd
ae31cbb4 af0673d5 8891fc10 8947d770 00000002 vmx86+0x6d6
ae31cbdc 804ef19f 899a3a70 8c026f68 806e6428 vmx86+0x13d5
ae31cbec 80658128 891adea8 806e6410 8c026f68 nt!IopfCallDriver+0x31
ae31cc10 8057f982 8c026fd8 891adea8 8c026f68 nt!IovCallDriver+0xa0
ae31cc24 805807f7 899a3a70 8c026f68 891adea8 nt!IopSynchronousServiceTail+0x70
ae31ccc0 80579274 0000029c 00000000 00000000 nt!IopXxxControlFile+0x5c5
ae31ccf4 b0659652 0000029c 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
ae31cd34 8054164c 0000029c 00000000 00000000 klif+0x21652
ae31cd34 7c90e514 0000029c 00000000 00000000 nt!KiFastCallEntry+0xfc
0012fd78 00000000 00000000 00000000 00000000 0x7c90e514
FOLLOWUP_IP:
vmx86+37bd
af0697bd 33d2 xor edx,edx
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: vmx86+37bd
MODULE_NAME: vmx86
IMAGE_NAME: vmx86.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4cdc5e9c
STACK_COMMAND: .trap ffffffffae31cacc ; kb
FAILURE_BUCKET_ID: 0xA_W_VRF_vmx86+37bd
BUCKET_ID: 0xA_W_VRF_vmx86+37bd
Followup: MachineOwner
---------
