Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\MEMORY.DMP] Kernel Complete Dump File: Full address space is available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612 Machine Name: Kernel base = 0x8200b000 PsLoadedModuleList = 0x82122c70 Debug session time: Sat Mar 14 17:51:42.625 2009 (GMT+0) System Uptime: 0 days 0:04:50.540 Loading Kernel Symbols ............................................................... ................................................................ .......................................................... Loading User Symbols ............................................................... Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D9, {1, 8f610d08, b2ed3ee0, 40} *** ERROR: Module load completed but symbols could not be loaded for vmx86.sys *** ERROR: Module load completed but symbols could not be loaded for vmware-vmx.exe ************************************************************************* *** *** *** *** *** 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: kernel32!pNlsUserInfo *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: kernel32!pNlsUserInfo *** *** *** ************************************************************************* Probably caused by : vmx86.sys ( vmx86+3ca8 ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* LOCKED_PAGES_TRACKER_CORRUPTION (d9) Arguments: Arg1: 00000001, The MDL is being inserted twice on the same process list. Arg2: 8f610d08, Address of internal lock tracking structure. Arg3: b2ed3ee0, Address of memory descriptor list. Arg4: 00000040, Number of pages locked for the current process. Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** 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: kernel32!pNlsUserInfo *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: kernel32!pNlsUserInfo *** *** *** ************************************************************************* DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD9 PROCESS_NAME: vmware-vmx.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 8207d5a3 to 820d80e3 STACK_TEXT: ba1f89d0 8207d5a3 000000d9 00000001 8f610d08 nt!KeBugCheckEx+0x1e ba1f8a04 8207d455 822f92d7 b66e1ca8 00000040 nt!MiAddMdlTracker+0xd4 ba1f8ad8 822f92d7 b2ed3ee0 00000001 00000002 nt!MmProbeAndLockPages+0x168b ba1f8af8 b66e1ca8 b2ed3ee0 00000001 00000002 nt!VerifierMmProbeAndLockPages+0x79 WARNING: Stack unwind information not available. Following frames may be wrong. ba1f8b40 b66e636b 00040000 c2fb5100 00000040 vmx86+0x3ca8 ba1f8b64 b66e67c2 babb9008 c2fb5100 00000040 vmx86+0x836b ba1f8b9c b66de977 babb9008 8f7c6648 baa9f9b6 vmx86+0x87c2 ba1f8be4 b66df650 89da17f0 babb9008 000000f0 vmx86+0x977 ba1f8c0c 822ed6be 81bbaa70 acdeef68 8f7d5c40 vmx86+0x1650 ba1f8c30 820c6f8a acdeefd8 acdeef68 81bbaa70 nt!IovCallDriver+0x23f ba1f8c44 82257615 8f7d5c40 acdeef68 acdeefd8 nt!IofCallDriver+0x1b ba1f8c64 82257dba 81bbaa70 8f7d5c40 0012ef00 nt!IopSynchronousServiceTail+0x1d9 ba1f8d00 82241a8d 81bbaa70 acdeef68 00000000 nt!IopXxxControlFile+0x6b7 ba1f8d34 82062a1a 00000320 00000000 00000000 nt!NtDeviceIoControlFile+0x2a ba1f8d34 77059a94 00000320 00000000 00000000 nt!KiFastCallEntry+0x12a 0012eee0 77058444 76b6c2a3 00000320 00000000 ntdll!KiFastSystemCallRet 0012eee4 76b6c2a3 00000320 00000000 00000000 ntdll!ZwDeviceIoControlFile+0xc 0012ef44 00462c4c 00000320 81013f84 0012efa4 kernel32!DeviceIoControl+0x14a 0012ef74 00579dab 0012efa4 009c3330 0001851e vmware_vmx+0x62c4c 0012fe80 0045944a 6fdd4b6c 034113e0 00000000 vmware_vmx+0x179dab 0012fe98 00405cec 6fdd4b6c 0394fb88 00000000 vmware_vmx+0x5944a 0012feb0 004062f6 00000000 6fdd4b6c 0394fb88 vmware_vmx+0x5cec 0012fee4 00405048 00000008 017f3060 0012ff88 vmware_vmx+0x62f6 0012fef4 0040193a 00400000 00000000 00241ba6 vmware_vmx+0x5048 0012ff88 76b84911 7ffdf000 0012ffd4 7703e4b6 vmware_vmx+0x193a 0012ff94 7703e4b6 7ffdf000 771ade2c 00000000 kernel32!BaseThreadInitThunk+0xe 0012ffd4 7703e489 00401aaa 7ffdf000 00000000 ntdll!__RtlUserThreadStart+0x23 0012ffec 00000000 00401aaa 7ffdf000 00000000 ntdll!_RtlUserThreadStart+0x1b STACK_COMMAND: kb FOLLOWUP_IP: vmx86+3ca8 b66e1ca8 c745fcfeffffff mov dword ptr [ebp-4],0FFFFFFFEh SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: vmx86+3ca8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: vmx86 IMAGE_NAME: vmx86.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4907d282 FAILURE_BUCKET_ID: 0xD9_VRF_vmx86+3ca8 BUCKET_ID: 0xD9_VRF_vmx86+3ca8 Followup: MachineOwner --------- kd> !deadlock Locks: 0 Nodes: 0 Threads: 0 Nodes trimmed based on age 35. Nodes trimmed based on count 80. Analyze calls 11195. Maximum nodes searched 11. No deadlock verifier issues. kd> !deadlock 1 Locks: 0 Nodes: 0 Threads: 0 Nodes trimmed based on age 35. Nodes trimmed based on count 80. Analyze calls 11195. Maximum nodes searched 11. No deadlock verifier issues.