HYPERVISOR_ERROR 0x20001 at nt!HalProcessorIdle on Ryzen 9 5900X (Canary Build 26200)

Question

HYPERVISOR_ERROR 0x20001 at nt!HalProcessorIdle on Ryzen 9 5900X (Canary Build 26200)

JRam 0

System Configuration

OS: Windows 11 Canary Insider Preview (Build 26200.9168)

CPU: AMD Ryzen 9 5900X

Motherboard: ASUS ROG STRIX X570-E GAMING WIFI II

GPU: NVIDIA GeForce RTX 3060 12GB

Active Virtualization Environment: Docker and SQL Server running in the background

Crash Description The system experiences unrecoverable Bugcheck 0x00020001 (HYPERVISOR_ERROR) crashes. The stack trace consistently points to a failure at nt!HalProcessorIdle during a power state transition. While these crashes trigger randomly during standard desktop tasks, they most frequently occur during gaming when the CPU rapidly shifts between heavy loads and idle moments.

Troubleshooting Steps Completed

Verified core system files using DISM and SFC (no integrity violations found).

Disabled Memory Integrity within Windows Security.

Updated to the latest AMD X570 chipset drivers.

Applied a +0.050V VDDCR CPU Voltage offset in the ASUS BIOS to cushion low-voltage states.

Disabled Global C-States in the BIOS.

Disabled the Precision Boost Overdrive (PBO) Curve Optimizer to remove any potential core undervolting.

(Administrator note: remove duplicate)

0 comments

2 answers

Your answer

Answer 1

Carl-L 21,995 Microsoft External Staff Moderator

Hello JRam,

Welcome to Microsoft Q&A forum.

It seems like you have already tried the basic troubleshooting steps. Based on the description here, I suspect that this is a firmware issue Hyper-V. Before we proceed further, please help me check this.

Type "Command Prompt" in the search bar and select "Run as administrator"
Type bcdedit /set hypervisorlaunchtype off and press Enter.
Restart your computer and monitor if the issue persists.

I'm waiting for your reply.

Carl-L 21,995 Reputation points Microsoft External Staff Moderator

2026-08-29T10:03:12.7433333+00:00

Hello JRam,

Just checking in to make sure that you have received my reply. Please let me know if you have any updates.
JRam 0 Reputation points

2026-09-13T19:30:08.7466667+00:00

Hey sorry fo the time I took to reply, I genuinly just got the mail informing me of your answer. What I did to solve the issue was simply reinstall my W11. That did the trick
Adam Holmes 0 Reputation points

2026-09-14T11:15:05.1966667+00:00

@JRam You did exactly those steps to solve the problem? Settings → System → Recovery → Fix problems using Windows Update → Reinstall now
Carl-L 21,995 Reputation points Microsoft External Staff Moderator

2026-09-15T13:37:31.4466667+00:00

Hello JRam,

IT's good to hear that you have found a way to fix it.

Hello Adam Holmes

I'm not sure if this is exactly what the OP did, but that is a way to do so. Can you please try it and let me know the results?
JRam 0 Reputation points

2026-09-15T13:42:01.7366667+00:00

@Adam Holmes No, complete new install with a USB. I did this bc it got to a point where I couldn’t enter my recovery environment window.

Answer 2

I am experiencing recurring HYPERVISOR_ERROR (0x00020001) BSODs on Windows 11 with an AMD Ryzen 5 3600 and ASRock B450M-HDV R4.0.

The crashes occur intermittently during normal use and have now occurred repeatedly over several weeks.

Importantly, disabling Global C-State Control did not prevent the crash, and the crash also persisted after AMDRyzenMasterDriver.sys was removed.

System:

AMD Ryzen 5 3600
ASRock B450M-HDV R4.0
32? GB DDR4-3200 [tu wpisz ilość RAM]
Windows 11 24H2
SVM enabled
VBS active

Troubleshooting already performed:

Updated motherboard BIOS to the latest stable version.
Installed the latest AMD B450 chipset drivers.
Verified that SVM/AMD virtualization is enabled.
Removed ASRock A-Tuning and its AMDRyzenMasterDriver.sys driver.
Tested Global C-State Control = Disabled; the same HYPERVISOR_ERROR still occurred.
DISM/SFC and Windows Update checked.
The system continues to generate HYPERVISOR_ERROR 0x20001 minidumps.

Several crashes show the same general HYPERVISOR_ERROR pattern. The issue resembles this recently reported Ryzen/Hyper-V problem.

I have multiple minidump files available, including crashes from August 26, August 27, August 31, September 3, September 5, September 6, September 9, September 12 and September 13.

Since the issue persists after BIOS, chipset and power-state troubleshooting, could this be a Windows Hyper-V/VBS regression affecting AMD Ryzen systems?