Technical Support Request: Random Laptop Restarts (Hypervisor Error 0x20001)

Configure Windows 11 to capture an automatic memory dump, reproduce one restart, and analyze that dump before disabling Hyper-V or changing BIOS power settings, because 0x20001 identifies a fatal hypervisor error but does not identify its underlying cause.^1^

1. Capture the next crash

1. Search for Advanced system settings and open it.
2. Select Advanced → under Startup and Recovery, select Settings.
3. Under Write debugging information, select Automatic memory dump.
4. Confirm that the dump path is %SystemRoot%\MEMORY.DMP.
5. Select OK, then restart the laptop once to apply the setting.
6. Keep the Windows paging file enabled and system-managed; dump creation depends on it.
7. After the next unexpected restart, check:
   • C:\Windows\MEMORY.DMP
   • C:\Windows\Minidump

Microsoft documents those settings and locations for supported Windows clients.^2^

Back up important files now. Repeated system crashes can interrupt writes and risk data loss.

2. Analyze the dump

Open the dump in WinDbg and run:

!analyze -v

Record these fields from the output:

• BUGCHECK_CODE
• MODULE_NAME
• IMAGE_NAME
• FAILURE_BUCKET_ID
• PROCESS_NAME
• The first non-Microsoft driver appearing in STACK_TEXT

Microsoft specifically recommends !analyze for determining the cause of HYPERVISOR_ERROR.^1^ A module named in the dump is evidence for further investigation, but it is not automatically proof that the module itself is defective.

If sharing the dump publicly, use a minidump rather than a full memory dump and review it first because dump files can contain data from memory.

3. Apply the branch supported by the dump

If the dump consistently names a hardware driver

Install the laptop manufacturer’s current driver for that component, together with the manufacturer’s current chipset and firmware packages. If crashes began directly after a driver update, roll that driver back instead.

Microsoft recommends contacting the hardware or software vendor when a stop error identifies a particular driver, and also recommends keeping BIOS and firmware current.^2^

Do not use third-party driver-download utilities; laptop drivers may be customized by the manufacturer.

If crashes started after attaching hardware

Shut down and temporarily remove the newly added device. Also open Start → Device Manager and check for devices marked with an exclamation point. Windows’ consumer troubleshooting guidance recommends removing newly added hardware and updating, disabling, or uninstalling a device flagged in Device Manager.^3^

If the dump is inconsistent, corrupted, or names different components

Treat hardware instability as a possibility rather than assuming Hyper-V itself is defective:

• Run the laptop manufacturer’s memory and hardware diagnostics.
• Test without external peripherals.
• Return any CPU, memory, undervolting, or overclocking settings to manufacturer defaults.
• Confirm that the system drive has approximately 10–15% free space.
• Install all pending updates from Settings → Windows Update → Check for updates.

Microsoft notes that unexpected restarts can originate from hardware, drivers, or software and recommends free-space and update checks.^3^

If no dump is created

After another restart, open Event Viewer → Windows Logs → System and look at events immediately before the reboot.

• A recorded bug check combined with a dump confirms a Windows stop error.
• Repeated restarts with no dump or bug-check record require checking the paging-file configuration first.
• If dump configuration is correct but Windows still records no bug check, contact the laptop manufacturer for power, motherboard, memory, cooling, or firmware diagnostics. A sudden hardware-level reset might not leave Windows enough time to write a dump.

Disabling Hyper-V is not the first diagnostic step here. It can change the symptom while removing evidence, and the stop code alone does not establish that Hyper-V—as opposed to a driver, firmware, memory, or other hardware interaction—is the root cause.

References

1. Bug Check 0x20001: HYPERVISOR_ERROR
2. Advanced troubleshooting for stop code errors
3. [Windows 11](https://support.microsoft.com/windows/experience/performance-optimization/troubleshooting-windows-unexpected-restarts-and-stop-code-errors)