Contributor
Contributor

hyper-v crashing

Jump to solution

Hello, I'm attempting to run Windows 2019 with Hyper-V on ESXI 6.7 with the latest build but having an issue with Hyper-V crashing every 28-29 mins of running.

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
Enthusiast
Enthusiast

I had the same issue but I figured out that crashing is because of Exploit protection in Windows Security.

I change setting for vmcompute.exe and disable Control flow guard (CFG). After this settings, I have no crash of vmcompute.exe.

Pic01.jpg

Pic02.jpg

View solution in original post

0 Kudos
13 Replies
VMware Employee
VMware Employee

Can you provide more details on the crash?  Also could attach the vmware.log file from the Win2019 VM?

0 Kudos
Contributor
Contributor

I have Windows 10 VMs running on top of an ESXI 2019 VM are crashing very 28-29 mins. The windows 2019 logs show that "the Hyper-V host Compute service terminated unexpectedly. and Corrective action was to restart the service."

0 Kudos
Contributor
Contributor

Hello,

I am seeing the same issue on both Windows 10 1904 and 2004 running on ESX v6.7U3.  Every 30 minutes, Hyper-V will crash and restart.  I originally thought the problem had something to do with power management since the errors occur with such precise frequency, so I checked all of the power settings inside Windows and made sure all settings were set for maximum performance but it had no effect.  Is there something to check for in ESX that may be causing the issue?  This is also the only VM in the environment that has VT extensions exposed.  Thanks.

0 Kudos
Contributor
Contributor

Hi, I have the same issue.

Windows Docker container stopped working properly after en 6.5 to 6.7U3 upgrade.

We use the "process isolation", not Hyper-V hypervisor, even if the HyperV branding is used for "Hyper-V Host Compute Service" which is crashing.

We made 2 VM with Windows Server 2019 Std will all the latest updates running on different ESX hosts: same problem.

We then installed the Windows Server 2019 Std on a bare metal, same version, same hotfixes... → no problem.

Enabling "Expose hardware assisted virtualization to the guest OS" and "I/O MMU" doesn't help.

0 Kudos
Contributor
Contributor

I have the same issue.  I saw some blogs about downgrading VMWare tools, but it didn't solve the problem.

0 Kudos
Enthusiast
Enthusiast

I had the same issue but I figured out that crashing is because of Exploit protection in Windows Security.

I change setting for vmcompute.exe and disable Control flow guard (CFG). After this settings, I have no crash of vmcompute.exe.

Pic01.jpg

Pic02.jpg

View solution in original post

0 Kudos
Contributor
Contributor

It seems to partly solve the problem as I don't have crashing vmcompute and zombie containers anymore.

But yet, the containers still end with an error:

pastedImage_1.png

First "Filter Manager failed to attach to volume".

Then "An error was detected on device \Device\Harddisk3\DR11 during paging operation"

Furthermore, we were able to reproduce this problem on all 3 VMs we installed from scratch.

We installed 2 bare metal servers and they don't exhibit such problem, IT IS VMWare related !

0 Kudos
Enthusiast
Enthusiast

Anybody opened vmware SR?

0 Kudos
Enthusiast
Enthusiast

So reply from support is that Microsoft need to investigate. This is weird, cause on ESXi 6.5 it works..

0 Kudos
Contributor
Contributor

I have the same problem, running vSphere 6.7 and Windows Server 2019 Standard 1809 build 17763.1369

The VMs running on the server crashes every 15~30 minutes.

I tried the solution above (set I/O MMU, Update Windows Defender settings) but that did not help.

This is what I found in the event log

Faulting application name: vmwp.exe, version: 10.0.17763.1369, time stamp: 0x58bd4f69

Faulting module name: ntdll.dll, version: 10.0.17763.1192, time stamp: 0x5854f5da

Exception code: 0xc0000409

Fault offset: 0x00000000000a4740

Faulting process id: 0x1d34

Faulting application start time: 0x01d65fb4c52eee5e

Faulting application path: C:\Windows\System32\vmwp.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report Id: f2134e52-e2ae-4470-a242-a66a45a4db83

Faulting package full name:

Faulting package-relative application ID:

0 Kudos
Contributor
Contributor

Windows Defender fix worked for me. Thank you very much !  Windows VMs have been operating without any issues.

0 Kudos
Enthusiast
Enthusiast

Do you have just Hyper-V crashing or also BSOD? We have various problems, including BSOD:

vmware-5.log:2020-07-03T04:48:50.370Z| vcpu-0| W115: WinBSOD: Synthetic MSR[0x40000100] 0x1a

but vmware support will not investigate. They claim MS should do it.

0 Kudos
Contributor
Contributor

Just a quick update.

The windows defender settings works for me finally.

I set as below:

wmwp.exe.png

wmcomputer.exe.png

0 Kudos