VMware Communities
PandaGorl
Contributor
Contributor

BSOD (PAGE_FAULT_IN_NONPAGED_AREA) with VMware Player on XP SP2 x64

I get BSOD in host OS when I try to start VMWare Player (downloaded yesterday) on my system (2 core, 6 Gb, windows XP sp2 x64 etc). It doesn't matter wich guest OS i try i still get BSOD.

In Windows XP SP2 x86 everything is ok.

what m i doin wrong?

Crash details:

-


BugCheck 50, {fffffadf5e1ff0ba, 0, fffff80001034eea, 0}

Unable to load image vmx86.sys, Win32 error 0n2

      • WARNING: Unable to verify timestamp for vmx86.sys

      • ERROR: Module load completed but symbols could not be loaded for vmx86.sys

Could not read faulting driver name

Probably caused by : vmx86.sys

Followup: MachineOwner

-


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

  • *

  • Bugcheck Analysis *

  • *

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

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except,

it must be protected by a Probe. Typically the address is just plain bad or it

is pointing at freed memory.

Arguments:

Arg1: fffffadf5e1ff0ba, memory referenced.

Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

Arg3: fffff80001034eea, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000000, (reserved)

Debugging Details:

-


Could not read faulting driver name

READ_ADDRESS: fffffadf5e1ff0ba

FAULTING_IP:

nt!MmMapLockedPagesSpecifyCache+666

fffff800`01034eea 66418b4a1a mov cx,word ptr

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: vmware-vmx.exe

CURRENT_IRQL: 1

TRAP_FRAME: fffffadf5bf656b0 -- (.trap 0xfffffadf5bf656b0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=fffffadf693d7b18 rcx=00000000000000a6

rdx=000000000007ffae rsi=0000000000000000 rdi=0000000000000001

rip=fffff80001034eea rsp=fffffadf5bf65840 rbp=fffffadf5c89f000

r8=000000fffffff000 r9=0000000000000863 r10=fffffadf5e1ff0a0

r11=fffffadf5bf6580f r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na po nc

nt!MmMapLockedPagesSpecifyCache+0x666:

fffff800`01034eea 66418b4a1a mov cx,word ptr ds:fffffadf`5e1ff0ba=????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800010a6072 to fffff8000102e890

0 Kudos
6 Replies
poliwoda
Contributor
Contributor

Absolutely the same for me. Absolutely reproducable.

0 Kudos
philosopher_sam
Contributor
Contributor

I'm seeing the same page fault when opening a VMWare guest on Windows XP S2 x64. I'm running VMWare PLayer 2.0.3 build-80004. Does anyone know if this impacts the recent previous versions? I may try it and let you know.

Thanks,

Sam

0 Kudos
wroemer
Contributor
Contributor

I used vmware workstation 6.0.3 build-80004 as well with absolutely the same failure.

0 Kudos
philosopher_sam
Contributor
Contributor

FYI to everyone on this thread...if you can use it, I got the VMWare Server beta to install on XP SP2 x64. All appears to be working well. I've spun up an guest a few times already....updated VMWare tools. Obviously, this is not very scientific. Smiley Happy I will let everyone know if anything changes. Is anyone on VMWare support or QA watching this thread? This is easy to reproduce on XP SP2 x64.

Regards,

Sam

0 Kudos
wilhil
Contributor
Contributor

Same for me with workstation (latest) on Vista Ultimate x64

It happens 100% of the time if I right click and do run as administrator, if I run without it, it works.... it always happens and no idea why.

If I turn UAC off, the system crashes at boot and I can trace it back to Workstation so I am guessing that it is some sort of privilaged operation that crashes it on Vista and XP 64bit however it is containted with UAC turned on.

0 Kudos
wroemer
Contributor
Contributor

Switching to the latest version of VMware Player (2.0.4 build 93057) SOLVED the problem for me.

0 Kudos