VMware Communities
LeonardAchanya
Contributor
Contributor
‎05-07-2021 10:08 AM

My HOST PC a Windows 10 Home crashes when opening a vm in VMware workstation 15

Hi,

I was using the VMware Workstation Pro 15 and could run several VM's on my machine.

I am now trying to use those same VMs now for school work but all of a sudden, they seem to crash my Windows 10 Home PC with a blue screen displaying. I have tried various solutions found on the web but not successful. I even went on to reset my pc so as to update my windows but still no success. I need help pls

Also, pls note that I am using an ASUS ROG STRIX GT531 with an Nvidia Geforce Gtx and intel core i7 and the intel virtualization technology is enabled.

Please help,

Kind regards,

0 Kudos
2 Replies
LeonardAchanya
Contributor
Contributor
‎05-07-2021 10:10 AM

attached is the error displayy

Preview file
529 KB
0 Kudos
LeonardAchanya
Contributor
Contributor
‎05-07-2021 10:14 AM

and this is from the memory dump


Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`49800000 PsLoadedModuleList = 0xfffff806`4a42a130
Debug session time: Fri May 7 12:38:18.214 2021 (UTC - 4:00)
System Uptime: 0 days 0:50:57.012
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000070`bc384018). Type ".hh dbgerr001" for details
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`49bf6cf0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff810a`0761ec50=0000000000000050
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: 000001f8154ab6cd, memory referenced.
Arg2: 0000000000000003, value 0 = read operation, 1 = write operation.
Arg3: fffff80649c09c67, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 000000000000000f, (reserved)

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4171

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 8525

Key : Analysis.Init.CPU.mSec
Value: 592

Key : Analysis.Init.Elapsed.mSec
Value: 12305

Key : Analysis.Memory.CommitPeak.Mb
Value: 77

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 50

BUGCHECK_P1: 1f8154ab6cd

BUGCHECK_P2: 3

BUGCHECK_P3: fffff80649c09c67

BUGCHECK_P4: f

WRITE_ADDRESS: 000001f8154ab6cd

MM_INTERNAL_CODE: f

PROCESS_NAME: vmware-vmx.exe

IRP_ADDRESS: ffffffffffffff88

TRAP_FRAME: ffff810a0761eef0 -- (.trap 0xffff810a0761eef0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000001f8154ab6cd rbx=0000000000000000 rcx=000001f8154ab6d0
rdx=ffffbb8d64353003 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80649c09c67 rsp=ffff810a0761f088 rbp=ffff810a0761f1d0
r8=0000000000000181 r9=ffff810a0761f1a0 r10=fffff80649b0ee40
r11=ffffbd85797fe851 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!memcpy+0xa7:
fffff806`49c09c67 0f1100 movups xmmword ptr [rax],xmm0 ds:000001f8`154ab6cd=????????????????????????????????
Resetting default scope

STACK_TEXT:
ffff810a`0761ec48 fffff806`49a909dc : 00000000`00000050 000001f8`154ab6cd 00000000`00000003 ffff810a`0761eef0 : nt!KeBugCheckEx
ffff810a`0761ec50 fffff806`49b28c92 : 00000000`00000000 80000002`b3fa7867 ffffdb80`fc0aa558 ffffbd85`8138f080 : nt!MiValidFault+0x68c
ffff810a`0761ecc0 fffff806`49b27f7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUserFault+0x7a2
ffff810a`0761ed50 fffff806`49c04e5e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x16a
ffff810a`0761eef0 fffff806`49c09c67 : fffff806`49b0f331 00000000`00000000 ffffbd85`81347080 ffffbd85`822f9040 : nt!KiPageFault+0x35e
ffff810a`0761f088 fffff806`49b0f331 : 00000000`00000000 ffffbd85`81347080 ffffbd85`822f9040 ffff810a`0761f201 : nt!memcpy+0xa7
ffff810a`0761f090 fffff806`49a0ee00 : 00000000`00000000 00000000`00000000 ffffbd85`85b94890 ffffbd85`85b94880 : nt!IopCompleteRequest+0x4f1
ffff810a`0761f150 fffff806`49bfb050 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`00000000 : nt!KiDeliverApc+0x1b0
ffff810a`0761f200 fffff806`62bf107e : fffff806`62bf86f4 00000000`00000000 fffff806`49b12172 ffffbd85`74002340 : nt!KiApcInterrupt+0x2f0
ffff810a`0761f398 fffff806`62bf86f4 : 00000000`00000000 fffff806`49b12172 ffffbd85`74002340 fffff806`49df5e31 : vmx86+0x107e
ffff810a`0761f3a0 fffff806`62bfaf60 : ffffbd85`85693660 00000000`00000000 ffff9500`db723000 ffffbd85`85db3050 : vmx86+0x86f4
ffff810a`0761f4e0 fffff806`62bf1f27 : ffff810a`0761f5c0 00000000`00000000 ffff810a`0761f868 fffff806`49b15841 : vmx86+0xaf60
ffff810a`0761f5a0 fffff806`62bf295e : 00000000`81013f63 ffff8484`7fb22c40 00000000`00000000 fffff806`49a0afca : vmx86+0x1f27
ffff810a`0761f780 fffff806`49ee1d82 : 00000000`81013f63 ffff810a`0761fa80 00000000`00000005 ffffbd85`861a43f0 : vmx86+0x295e
ffff810a`0761f7e0 fffff806`49ee19e6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x382
ffff810a`0761f920 fffff806`49c086b5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
ffff810a`0761f990 00007ffb`bea6cf04 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000070`bd8ffce8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`bea6cf04


SYMBOL_NAME: vmx86+107e

MODULE_NAME: vmx86

IMAGE_NAME: vmx86.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 107e

FAILURE_BUCKET_ID: AV_INVALID_vmx86!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {dbd33a08-5c1a-0339-8617-7037c47e0cf0}

Followup: MachineOwner
---------

 

 

0 Kudos