Need Help!!! I am running a fully patched Hyper-V Server 2016 with 6 VMs. 3 of them are (bug checks -- crashing multiple times daily. They are all fully patched.

Question

The VMS are 4 x Windows 10 Pro, 2 x Server 2022 Standard. I have run DISM restore health | sfc /scannow | chkdsk /r /f with no issues found!

2 of the Win10 and 1 of the server VMs are crashing. The mini-dumps point to bad driver (ntoskrnl.exe) from bad address (ntoskrnl.exe+42xxx)

In the Hyper V server logs: 'xxxx' has encountered a fatal error.  The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x109, ErrorCode1: 0xA39FD5DE01C8D62E, ErrorCode2: 0xB3B6E264544B62C5, ErrorCode3: 0x3000001A0, ErrorCode4: 0x7.  If the problem persists, contact Product Support for the guest operating system.  (Virtual machine ID 9A66162B-856C-4BEC-B121-4F4C4AB5E94F)

moved from Windows / Windows 10 / Performance and system failures

Answer 1

Hello

Thank you for posting in Microsoft Community forum.

ntoskrnl.exe+42xxx error: This error is often associated with memory corruption or a problematic driver. Here are some steps you can take to troubleshoot this issue:

Check your computer’s RAM: Use a tool like Windows Memory Diagnostic or MemTest86 to check for any issues.

Reinstall important drivers: If the RAM checks out, there might be a software issue causing the problem. Drivers are often the culprit for software-based system crashes.

Disable overclocking: If you’re overclocking your system, it’s recommended to disable it as it can cause BSOD and make troubleshooting difficult.

Check the Event Viewer: Look for any related error logs about the VM startup failure in Applications and Services > Microsoft > Windows > Hyper V VMMS and Hyper V worker.

If you have the ability to use the Windows debugger to solve this problem, you can refer to the following documents for debugging:

Bug Check 0x109 CRITICAL_STRUCTURE_CORRUPTION - Windows drivers | Microsoft Learn

Best Regards,

Wesley Li