PC Crash product: VMware kernel driver

[JJoli]

Hello, 

I've been getting PC crashes ( I think since flash update for windows, not sure ), here is memory dump

On Mon 3/8/2021 8:11:14 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: vmx86.sys (vmx86+0x200A)
Bugcheck code: 0x80 (0x4F4454, 0x0, 0x0, 0x0)
Error: NMI_HARDWARE_FAILURE
product: VMware kernel driver
company: VMware, Inc.
description: VMware kernel driver
Bug check description: This bug check indicates that a hardware malfunction has occurred.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: vmx86.sys (VMware kernel driver, VMware, Inc.).
Google query: vmx86.sys VMware, Inc. NMI_HARDWARE_FAILURE

Workstation 16 player
Windows 20H2 OS build 19042.844

Ryzen 1600
32GB ram
GTX 1050

Can some one advise how to fix it? If there is more data needed, please let me know.

[XavierMalory]

Adding my plea for help to the OP.

I too have been getting this same error since March 2nd.  There were no changes that day on my VMWare Workstation Pro installation or my Windows 10 x64 host, except for the removal of Adobe Flash and the Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10, version 1909, and Windows Server, version 1909.

[JJoli]

Hello,

Thank you for you reply.

Atleast I am not alone. Can you elaborate a bit more, do you mean if you remove this Flash update (from host or VM?) the host should no longer crash? Or if I upgrade VMs to 20H2, same version as host, should it somehow solve the issue itself?

[XavierMalory]

My updates were on the host box (which is running an older version of Windows 10 due to incompatibility issues with sound hardware).  I had in fact tried (just for laughs) upgrading the guest OS (VM) to 20H2 with little success.  However my use case may be a bit beyond the average individual. I've no idea if removing the Flash update from the host OS would help (said update was only supposed to remove the Adobe Flash program so I highly doubt that's the problem, but I suppose you could try).

In this particular situation, I'm using VMWare Workstation Pro to host some game servers (which require access to the graphics card).  The host box is also my gaming PC, which has more than enough horsepower to perform both functions (it has done so without issue for the last six months).  Of course once this started happening, my first thought was some of the hardware was going bad, so I ran it through stress tests (memtestx86, CPUZ, PassMark) but had no crashes if I did not run VMWare Workstation Pro.  As soon as I launched it and began running the guest OS game servers, it would start having problems (said game servers did NOT get updates on March 2nd either, so I highly doubt they're the cause).

Long and short of it is I've no idea what could've changed or what you could try. After running stress tests, updating my host box's BIOS and ensuring all drivers are up to the latest stable version, I even reduced the number of cores and RAM on the guest OS.  None of this helped.

[Kautism]

I crash too after windows update.😥

NMI_HARDWARE_FAILURE (80)
This is typically due to a hardware malfunction. The hardware supplier should
be called.
Arguments:
Arg1: 00000000004f4454
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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

Page 82ea12 not present in the dump file. Type ".hh dbgerr004" for details
Page 82ea12 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on KAUTISMPC

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 33

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

Key : Analysis.System
Value: CreateObject

BUGCHECK_CODE: 80

BUGCHECK_P1: 4f4454

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: vmware-vmx.exe

STACK_TEXT:
ffffe680`1c96eb38 fffff804`2d2b395a : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffe680`1c96eb40 fffff804`29c115b0 : 00000000`00000000 ffffbf0e`280df8c8 fffff804`2da507e0 ffffbf0e`280df8c8 : nt!HalBugCheckSystem+0x7a
ffffe680`1c96eb80 fffff804`2d3b552e : 00000000`00000000 ffffe680`1c96ec29 ffffbf0e`280df8c8 fffff804`2da507e0 : PSHED!PshedBugCheckSystem+0x10
ffffe680`1c96ebb0 fffff804`2d2b8012 : 00000000`00000030 00000000`00000030 fffff804`2da507e0 00000000`0000005c : nt!WheaReportHwError+0x46e
ffffe680`1c96ec90 fffff804`2d30cdf2 : 00000000`00000001 ffffe680`1c96ed10 00000000`00000000 fffff804`2d31f6a0 : nt!HalHandleNMI+0x142
ffffe680`1c96ecc0 fffff804`2d201182 : ffffe680`1c90ffb0 ffffe680`1c96eed0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x132
ffffe680`1c96ed10 fffff804`2d200f52 : ffffe680`1c90ffb0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffffe680`1c96ee50 fffff804`3356200a : fffff804`335693c4 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x212
fffff887`1b5af388 fffff804`335693c4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vmx86+0x200a
fffff887`1b5af390 fffff804`3356c055 : 00000a42`00000a42 00000000`00006001 fffff887`1b5af801 00000000`00000000 : vmx86+0x93c4
fffff887`1b5af4d0 fffff804`33562f7e : 00000000`00020000 000002b0`7d1d31a0 fffff887`1b5af868 00000000`00000000 : vmx86+0xc055
fffff887`1b5af5a0 fffff804`33563992 : 00000000`81013f67 ffffad83`6115bd00 00000000`00000000 fffff804`2d063eea : vmx86+0x2f7e
fffff887`1b5af780 fffff804`2d3fcee2 : 00000000`81013f67 00000000`00000000 00000000`00000000 ffffbf0e`31b87700 : vmx86+0x3992
fffff887`1b5af7e0 fffff804`2d3fcb46 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x382
fffff887`1b5af920 fffff804`2d2074b5 : 00000000`00000000 00000000`00000000 00000000`00000474 fffff804`2d4ba180 : nt!NtDeviceIoControlFile+0x56
fffff887`1b5af990 00007ffa`3deac704 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000cc`c5fffb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`3deac704

[e2489]

I've been experiencing the same issue for the past month or so. Hopefully we can get some help with this.

[JJoli]

Hello, I wonder if someone was able to get this fixed? This is really frustrating

[allusory]

I am also experiencing this issue. I am using an AMD Zen 2 Threadripper. Could everyone on this thread please comment with their CPU/chipset?

[XavierMalory]

Intel i9-9900K Coffee Lake
Intel 300 Series Chipset (Asus Prime Z390-A)

[e2489]

Tried updating to see if that would fix it. Nope. Just got a MEMORY_MANAGEMENT crash.

Is VMware aware of this issue? Is anything being done? All my VMs are completely unusable right now because of this issue, and I depend on them for work.

Edit: Intel i7-8700K

[JJoli]

I dont understand how VMware does not acknowledge that.

All my pcs experience this issue. First msi b350 arctic/Ryzen 1600 and now Fx8350 m5a97 r2.

[steve44]

HELLLLLLLOOO? VMWARE? Are you going to acknowledge this problem, or do you plan to just leave your product broken?

[scott28tt]

Has anyone in this thread reported the problem to support?

VMTN is a user community forum, not a channel of communication to the support team.

[e2489]

---

@scott28tt wrote:

Has anyone in this thread reported the problem to support?

VMTN is a user community forum, not a channel of communication to the support team.

---

As an employee, can you maybe pass this along to someone? This issue has been ongoing for 5+ months, no one has acknowledged it or even seems to know it exists, and I've been completely unable to find where it can be reported.

[e2489]

Just a quick update, Windows 11 appears to solve this problem. I've been using it since November, and haven't had a VM-related crash since then. Buggy as hell otherwise, but for those that rely on VMs, at least this is fixed. Hopefully it doesn't show up again, because VMWare certainly doesn't seem to care.