Hypervisor error 0x20001 occurs during a BSOD when two monitors are used.
Hypervisor error 0x20001 occurs during a BSOD when two monitors are used.
Hello, I'm attempting to configure a sensor panel for my PC with a 7-inch display. AIDA64 is handling the sensors, and everything functions properly when connected via HDMI and powered through USB. My GPU is an RTX 5070Ti, and I also have a 4K monitor connected using DP. Initially, it worked well, but since the screen is 1080p, I don't want to overload my main GPU with rendering tasks—preferably let the 4K monitor handle that.
My CPU is an AMD 7600X, which includes its own integrated graphics. While not a high-end card, it should be sufficient for running the sensor panel. I'm considering letting the built-in GPU manage the panel while the main CPU focuses on other tasks. The system reports the GPU and driver are active in Task Manager and MSI Afterburner, but no Radeon software is installed.
After connecting the HDMI to the motherboard, it worked briefly for about five seconds before a hypervisor error (BSOD) appeared, freezing the PC at 0%. I had to manually shut it down. After restarting, everything functioned normally—no issues during operation. I spent several hours customizing gauges and visuals on the panel, using the screen as a preview. Eventually, I unplugged the HDMI and the problem disappeared.
Now, when the desktop loads, the BSOD returns repeatedly, freezing at 0% and forcing a manual shutdown. This happened five times in a row. After that, I removed the screen and everything worked again. It seems the display or the integrated GPU is causing this issue. Additionally, the monitor is showing my desktop background even when the main screen is displaying the BSOD.
I haven't experienced this exact error before, though I did face "low virtual memory" warnings a few months ago, which were resolved by reinstalling Windows 11. I've never used the integrated GPU on my system since switching to discrete GPUs after the 7600X. I'm hesitant about installing full drivers or Radeon software, fearing compatibility issues.
Could anyone share similar experiences? Specifically, how did you resolve this problem? Any tips would be greatly appreciated.
Specs: AMD RYZEN 7600X (no overclocking, all limits set), Corsair Vengeance RGB 2x16GB, 6000MHz, H150i AIO with BeQuiet fans, case with 7LianLi AL120 fans and MSI B650 power supply.
Thanks, I'll try turning off PBO. It seems it's not helping much, even at high loads where limits are removed. Temperatures are fluctuating between 88-90°C, staying below 95°C, which suggests it isn't slowing down to avoid overheating. Regarding stress tests, CPU and RAM performance are normal; I've run them multiple times recently, especially after other issues arose, which made me suspect a problem—but it wasn't there. Update: It worked for hours before again triggering the BSOD today. This time it didn’t freeze, went to 100%, and restarted automatically. I have the minidump file now, so I can attach it. Minidump.zip
This case highlights an issue with the Nvidia driver causing a Hypervisor_Error crash. It's not typical, but we should attempt using DDU. Please share any additional dump files if available. Having just one example isn't much help at the moment.
You're using an HDMI to HDMI cable for the signal and USB-A to USB-C for power. The device came from AliExpress, and you're comparing it to Torzx or similar options that use their own software instead of AIDA64. You chose the HDMI route or AIDA64 route because you wanted full customization and confidence that the software would offer the features and sensor data you needed. It's possible the issue might be a driver or firmware problem, but you're unsure how to resolve it at this stage.
I’ll handle it in the same way, mainly to rule out an improbable scenario. I installed Malwarebytes just to check the system, and it detected some items—though I didn’t mark them as critical from my list. Right now it’s only this one issue. If more BSODs occur and a minidump appears, I’ll share it here.
Well, it's been a couple of days without any problems until recently. While playing a game, my main monitor—connected to the RTX 5070ti—would suddenly go dark, as if losing GPU input. This began yesterday, and checking the Event Viewer didn’t show anything. It only occurred during gameplay, especially when running demanding tasks. It would happen roughly every minute or so, with a brief "blackout" lasting about five seconds. To confirm the DP cable wasn't loose, I reconnected it on the monitor side, which triggered a BSOD with the same hypervisor error. The PC would freeze again, forcing me to manually shut it down. Unfortunately, no minidump was recorded. After rebooting, I entered safe mode and checked DDU for AMD and nVidia. I downloaded new drivers a few days ago but hadn’t reinstalled yet. Once I restarted, I thought installing the latest AMD driver first, then nVidia, would help—since I suspect the nVidia driver was installed before the GPU driver. After the update, the hypervisor BSOD returned, and the PC rebooted on its own. Before logging in, another hypervisor error appeared, and after rebooting, I couldn’t access Windows. Just before login, I encountered yet another BSOD, which I now believe stems from a conflict between the two GPUs. After two failed attempts to launch Windows, it tried to fix itself but didn’t work. Eventually, I managed to enter safe mode using advanced recovery options. I reverted the AMD driver and prevented automatic driver updates, then installed just the nVidia driver. Now things seem stable, though using the iGPU isn’t working. Without a driver, it’s not detected at all. I’m hoping the connected sensor panel on my RTX 5070ti won’t trigger another BSOD or affect performance. I don’t think the new minidumps differ much from the previous ones, but they might help clarify what caused the issue. I’ll share these updated ones and ask for any insights, as I can’t view their details or understand them fully. By the way, I disabled PBO—it didn’t help, since I experienced the same BSOD that evening. It froze, no minidump was saved, so I didn’t mention it, especially since there were no issues in the following three days. Minidump.zip — edited September 5, 2025 by kiki4431
Recent crashes consistently trigger an NMI to the CPU. NMI stands for Non-Maskable Interrupt, a critical signal that forces the processor to halt and address the issue right away. It bypasses normal command queues, making it ideal for severe problems such as hardware faults. While any component can generate an NMI, in consumer devices it's typically the CPU that initiates it. The involvement of the Nvidia driver in this particular Hypervisor_Error crash is noteworthy and raises some questions about its implications.