G
Guest
Guest
Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)
I get this message in the debugger, what else can I do?
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini041605-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
SRV*C:\windows\symbols\*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp2.040919-1003
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054fdd0
Debug session time: Sat Apr 16 15:32:20.022 2005 (GMT-4)
System Uptime: 0 days 0:20:53.621
Loading Kernel Symbols
...................................................................................................................................................
Loading unloaded module list
............
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D9, {1, 88c07dc0, 89aff8c0, 273}
Unable to load image vmx86.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for vmx86.sys
*** ERROR: Module load completed but symbols could not be loaded for vmx86.sys
Probably caused by : vmx86.sys ( vmx86+36f7 )
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: 88c07dc0, Address of internal lock tracking structure.
Arg3: 89aff8c0, Address of memory descriptor list.
Arg4: 00000273, Number of pages locked for the current process.
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD9
LAST_CONTROL_TRANSFER: from 8052f52c to 8052de23
STACK_TEXT:
b4e9fa5c 8052f52c 000000d9 00000001 88c07dc0 nt!KeBugCheckEx+0x19
b4e9fa84 8051cb04 01c28020 b57cc6f7 b57d07f4 nt!MiAddMdlTracker+0x11d
b4e9fb24 b57cc6f7 89aff8c0 00000001 00000002 nt!MmProbeAndLockPages+0x64b
WARNING: Stack unwind information not available. Following frames may be
wrong.
b4e9fb74 b57d07f4 88c4e008 e4052900 00000040 vmx86+0x36f7
b4e9fbcc b57c9afb 88c4e008 88ee4600 88c26b40 vmx86+0x77f4
b4e9fc0c b57ca3a7 88c26b40 88ee4600 88ee4600 vmx86+0xafb
00000000 00000000 00000000 00000000 00000000 vmx86+0x13a7
FOLLOWUP_IP:
vmx86+36f7
b57cc6f7 ?? ???
SYMBOL_STACK_INDEX: 3
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: vmx86+36f7
MODULE_NAME: vmx86
IMAGE_NAME: vmx86.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4241495c
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0xD9_vmx86+36f7
BUCKET_ID: 0xD9_vmx86+36f7
Followup: MachineOwner
---------
Expand AllCollapse All
I get this message in the debugger, what else can I do?
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini041605-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
SRV*C:\windows\symbols\*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp2.040919-1003
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054fdd0
Debug session time: Sat Apr 16 15:32:20.022 2005 (GMT-4)
System Uptime: 0 days 0:20:53.621
Loading Kernel Symbols
...................................................................................................................................................
Loading unloaded module list
............
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D9, {1, 88c07dc0, 89aff8c0, 273}
Unable to load image vmx86.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for vmx86.sys
*** ERROR: Module load completed but symbols could not be loaded for vmx86.sys
Probably caused by : vmx86.sys ( vmx86+36f7 )
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: 88c07dc0, Address of internal lock tracking structure.
Arg3: 89aff8c0, Address of memory descriptor list.
Arg4: 00000273, Number of pages locked for the current process.
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD9
LAST_CONTROL_TRANSFER: from 8052f52c to 8052de23
STACK_TEXT:
b4e9fa5c 8052f52c 000000d9 00000001 88c07dc0 nt!KeBugCheckEx+0x19
b4e9fa84 8051cb04 01c28020 b57cc6f7 b57d07f4 nt!MiAddMdlTracker+0x11d
b4e9fb24 b57cc6f7 89aff8c0 00000001 00000002 nt!MmProbeAndLockPages+0x64b
WARNING: Stack unwind information not available. Following frames may be
wrong.
b4e9fb74 b57d07f4 88c4e008 e4052900 00000040 vmx86+0x36f7
b4e9fbcc b57c9afb 88c4e008 88ee4600 88c26b40 vmx86+0x77f4
b4e9fc0c b57ca3a7 88c26b40 88ee4600 88ee4600 vmx86+0xafb
00000000 00000000 00000000 00000000 00000000 vmx86+0x13a7
FOLLOWUP_IP:
vmx86+36f7
b57cc6f7 ?? ???
SYMBOL_STACK_INDEX: 3
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: vmx86+36f7
MODULE_NAME: vmx86
IMAGE_NAME: vmx86.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4241495c
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0xD9_vmx86+36f7
BUCKET_ID: 0xD9_vmx86+36f7
Followup: MachineOwner
---------
Expand AllCollapse All