New PC has hypervisor error with seemingly no fix.

Question

I recently bought and built a new pc and when setting up windows my first boot went fine for about 30 minutes until i installed all the drivers for it and i immediately started having constant freezes and hypervisor_error pop up, i eventually got a critical process died error, took it to a friend who said he reinstalled windows and had it working like normal, i took it back home and instantly had the same error as soon as it booted to windows sign in, i dont think it is a hardware issue as he told me it was a corrupted file. I again reinstalled windows myself and had it running fine for a little while, i boot it up again and immediately get the same error AGAIN. I have tried absolutely everything online that has to do with the error and nothing works, i have reinstalled windows 4 times already and it is still the same, my buddy downloaded all the drivers for the computer while he had it and said they were working fine? Im really at a loss and I dont have a clue what it could be anymore ive tried everything. Ive updated my bios and ive installed the drivers, i reinstalled windows, i tried to turn on hyper v both in windows and on my bios, ive turned it off, ive removed the ram and the cmos battery, everything is seemingly fine whilst on my home screen but as soon as i do anything it crashes and gives me the same error, i dont have anything installed on the computer currently besides the gigabyte control center but my buddy had it installed and he said it was working fine for the 2 ish hours he was messing with it.

Answer 1

Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Please do not upload a very large Memory.dmp file.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.

Answer 2

The HYPERVISOR_ERROR stop code (bug check 0x00020001) indicates that the Windows hypervisor has encountered a fatal error. On a new PC where clean installs of Windows work briefly and then blue-screen again, the most effective path is to treat this as a low‑level driver/firmware/virtualization issue and isolate it step by step.

Use the following structured approach:

1. Disable all virtualization features temporarily
   • In UEFI/BIOS, turn off:
     • SVM/AMD‑V or Intel VT‑x
     • IOMMU/VT‑d
     • Any “SVM Mode”, “Virtualization Support”, or similar options.
   • In Windows (once it boots):
     • Open Windows Features and ensure Hyper‑V, Virtual Machine Platform, Windows Hypervisor Platform, and Windows Sandbox are all unchecked.
   • Test the system under load (web browsing, installing apps, copying files). If crashes stop with virtualization disabled, the issue is almost certainly with the hypervisor path (firmware or a driver that uses virtualization).
2. Boot with minimal drivers and software
   • Boot into Safe Mode (minimal) and see if the system remains stable while doing basic tasks.
   • If Safe Mode is stable but normal mode is not, the cause is typically a third‑party driver or utility that hooks into virtualization or low‑level kernel features (e.g., some anti‑cheat, overclocking, monitoring, or security tools).
3. Remove or avoid vendor utilities and non‑essential drivers
   • Uninstall Gigabyte Control Center and any other motherboard vendor utilities, RGB/OC tools, or “system tuning” apps.
   • Use only:
     • Chipset drivers from Windows Update or the motherboard support page.
     • GPU driver from the GPU vendor.
   • Do not install any additional utilities until the system is proven stable.
4. Apply all Windows updates and firmware updates
   • Install all pending Windows 11 updates. For blue screens and stop codes, current updates and drivers are a primary mitigation path.
   • Ensure the motherboard BIOS/UEFI is on the latest stable version (already updated, but confirm you are not on a beta build).
5. Check for known hypervisor‑related stop codes
   • Hypervisor‑related bug checks (like 0x00020001 HYPERVISOR_ERROR) are typically debugged by analyzing the memory dump with the !analyze debugger extension. If comfortable, collect the memory dump from C:\Windows\Minidump and analyze it using the Windows Debugging Tools to identify the exact driver or module causing the crash.
6. Rule out hardware instability even if it appears fine
   • Run extended memory tests (e.g., multiple passes) and verify RAM is running at JEDEC defaults (disable XMP/EXPO for testing).
   • Ensure no CPU or GPU overclocking is enabled, including automatic “boost” or “game” profiles in the BIOS.
7. If crashes persist with virtualization fully disabled
   • If the PC still shows HYPERVISOR_ERROR even when all virtualization features and Hyper‑V components are disabled, and with only basic drivers installed, collect the dump and event logs and escalate via official support channels, as the hypervisor is encountering a fatal condition that requires detailed dump analysis.

For general blue screen troubleshooting (including repeated stop codes and unexpected restarts), follow the basic steps: remove new hardware, start in Safe Mode, check Device Manager for driver issues, ensure sufficient free disk space, install the latest Windows updates, and if needed, use System Restore or recovery options.

---

References:

• Bug Check 0x20001: HYPERVISOR_ERROR
• Troubleshooting Windows unexpected restarts and stop code errors