zooinsky
Contributor
Contributor

vmx86.sys BSOD

Jump to solution

Under 7.1.1 build-282343

The crash analysis using windows debugger is as follows:

3: kd> !analyze -v

*******************************************************************************

  • *

  • Bugcheck Analysis *

  • *

*******************************************************************************

LOCKED_PAGES_TRACKER_CORRUPTION (d9)

Arguments:

Arg1: 0000000000000001, The MDL is being inserted twice on the same process list.

Arg2: fffffadf9c5c9430, Address of internal lock tracking structure.

Arg3: fffffadf986d2330, Address of memory descriptor list.

Arg4: 0000000000000280, Number of pages locked for the current process.

Debugging Details:

-


DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD9

PROCESS_NAME: vmware-vmx.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800010de673 to fffff8000102eb50

STACK_TEXT:

fffffadf`669396d8 fffff800`010de673 : 00000000`000000d9 00000000`00000001 fffffadf`9c5c9430 fffffadf`986d2330 : nt!KeBugCheckEx

fffffadf`669396e0 fffff800`01086922 : 00000000`00000000 fffff800`011d22a0 00000000`00000000 00000000`00000001 : nt!MiAddMdlTracker+0x1a7

fffffadf`66939760 fffffadf`81b2a071 : fffffadf`986d2330 fffffa80`06c24a01 fffffadf`00000002 fffffadf`986d2330 : nt!MmProbeAndLockPages+0x1c37

fffffadf`66939840 fffffadf`81b2f0d2 : 00000000`00040000 00000000`03290000 00000000`00000040 fffffadf`98517601 : vmx86+0x5071

fffffadf`669398b0 fffffadf`81b2f5d4 : fffffadf`986be570 00000000`00005910 00000000`00000280 fffffadf`986be570 : vmx86+0xa0d2

fffffadf`669398e0 fffffadf`81b26aef : 00000000`00000170 fffffadf`66939cf0 fffffadf`97c26af0 00000000`0000b177 : vmx86+0xa5d4

fffffadf`66939930 fffffadf`81b2642f : fffffadf`97c26af0 00000000`20206f49 fffffadf`987dcd20 00000000`00000001 : vmx86+0x1aef

fffffadf`66939a10 fffff800`01283081 : 00000000`00000101 fffffadf`66939cf0 00000000`00000000 fffffadf`987dcd20 : vmx86+0x142f

fffffadf`66939a70 fffff800`01282b86 : 0012019f`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xa79

fffffadf`66939b90 fffff800`0102e5fd : 00000000`00000234 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56

fffffadf`66939c00 00000000`77ef08da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3

00000000`0023e908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ef08da

STACK_COMMAND: kb

FOLLOWUP_IP:

vmx86+5071

fffffadf`81b2a071 90 nop

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: vmx86+5071

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: vmx86

IMAGE_NAME: vmx86.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4c55cb40

FAILURE_BUCKET_ID: X64_0xD9_vmx86+5071

BUCKET_ID: X64_0xD9_vmx86+5071

Followup: MachineOwner

0 Kudos
1 Solution

Accepted Solutions
ksc
VMware Employee
VMware Employee

LOCKED_PAGES_TRACKER_CORRUPTION (d9)

Arguments:

Arg1: 0000000000000001, The MDL is being inserted twice on the same process list.

Arg2: fffffadf9c5c9430, Address of internal lock tracking structure.

Arg3: fffffadf986d2330, Address of memory descriptor list.

Arg4: 0000000000000280, Number of pages locked for the current process.

The vmx86.sys driver isn't compatible with Driver Verifier (or checked kernel builds). Exempt the driver from Driver Verifier.

What the driver does works correctly and is extremely well-tested. Unfortunately, Driver Verifier is quite conservative and flags it as an error.

I gave a more thorough explanation in a different post a few weeks ago; search for "Driver Verifier" for more details. The short version is that to pass Driver Verifier's checks, we would have to restrict VMs to ~10% of total system memory.

View solution in original post

0 Kudos
4 Replies
continuum
Immortal
Immortal

Hi and welcome

such a report is only useful if you have the luck that a VMware engineer sees this post.

For us mere mortal users some more info would help Smiley Wink

Do you run HyperV or Parallels or VirtualBox on the same host ?




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
ksc
VMware Employee
VMware Employee

LOCKED_PAGES_TRACKER_CORRUPTION (d9)

Arguments:

Arg1: 0000000000000001, The MDL is being inserted twice on the same process list.

Arg2: fffffadf9c5c9430, Address of internal lock tracking structure.

Arg3: fffffadf986d2330, Address of memory descriptor list.

Arg4: 0000000000000280, Number of pages locked for the current process.

The vmx86.sys driver isn't compatible with Driver Verifier (or checked kernel builds). Exempt the driver from Driver Verifier.

What the driver does works correctly and is extremely well-tested. Unfortunately, Driver Verifier is quite conservative and flags it as an error.

I gave a more thorough explanation in a different post a few weeks ago; search for "Driver Verifier" for more details. The short version is that to pass Driver Verifier's checks, we would have to restrict VMs to ~10% of total system memory.

View solution in original post

0 Kudos
continuum
Immortal
Immortal

you are lucky Smiley Wink

check this other related post from ksc too

http://communities.vmware.com/message/1596746#1596746




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
zooinsky
Contributor
Contributor

Hi and thanks

I am not running any other virtualisation software on my host.

I should have specified that my host is Windows 2003 64bit

I was running a Ubuntu 10.04 guest and upon creating and stating a Windows 7 VM I got the afformention BSOD

Following KSC's advice and with a little google fu I fount the following Knowledge Base article.

So far everything has been stable but time will tell.

Thanks for the help.

0 Kudos