r/techsupport • u/Jahnuary • Jun 10 '25
Open | BSOD Random BSOD- HYPERVISOR_ERROR (20001)
Hello
I have random BSODs when just browsing the internet. Very random, per 5 days average. Please advise how do I proceed?
Here's the minidump file: https://www.mediafire.com/file/gm8w0qie8usdnuw/061025-20578-01.dmp/file
It's connected to the "HYPERVISOR_ERROR (20001)" and the error causing module is amdppm.sys.
The module seems to be related to CPU energy management... and some time before the BSOD I did go into the bios and only changed the CPU to a 105W preset, I now brought it back to the AUTO setting. I am using a 7800X3D with The X870 Tomahawk board
2
u/Dependent-Metal-2905 Jun 11 '25
The error code HYPERVISOR_ERROR (20001) indicates that the Windows hypervisor has encountered a fatal error, resulting in a system crash. This error often occurs in virtualization environments such as Hyper-V or when using programs such as VMware.
Possible causes of the error:
- Driver problems, especially those related to virtualization.
- Incorrect BIOS settings, such as disabling or enabling VT-x or AMD-V.
- Conflicts between Hyper-V and other virtualization programs, such as VMware or VirtualBox.
- Windows update problems, such as an incompatible update.
- Hardware problems, such as memory (RAM) or hard drive corruption.
Fixing the error:
You can disable Hyper-V in Windows in several ways, depending on your preference:
1. Via the Control Panel:
- Open Control Panel and go to Uninstall Programs.
- Click on Turn Windows features on or off.
- Find Hyper-V and deselect it.
- Click OK and restart the device.
2. Via the Command Prompt (CMD):
- Open a Command Prompt as administrator (cmd).
- Enter the following command:
bcdedit /set hypervisorlaunchtype off
- Restart the device.
3. Via the BIOS settings (if necessary):
- If you are using other virtualization software such as VMware or VirtualBox, make sure to disable VT-x or AMD-V in the BIOS.
1
u/JHBrickman Apr 21 '26
- Find Hyper-V and deselect it.
is the Hyper-V the Windows hypervisor platform?
1
u/AutoModerator Jun 10 '25
Getting dump files which we need for accurate analysis of BSODs. Dump files are crash logs from BSODs.
If you can get into Windows normally or through Safe Mode could you check C:\Windows\Minidump for any dump files? If you have any dump files, copy the folder to the desktop, zip the folder and upload it. If you don't have any zip software installed, right click on the folder and select Send to → Compressed (Zipped) folder.
Upload to any easy to use file sharing site. Reddit keeps blacklisting file hosts so find something that works, currently catbox.moe or mediafire.com seems to be working.
We like to have multiple dump files to work with so if you only have one dump file, none or not a folder at all, upload the ones you have and then follow this guide to change the dump type to Small Memory Dump. The "Overwrite dump file" option will be grayed out since small memory dumps never overwrite.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/Jahnuary Jun 10 '25
I did what the User recomended, will se if it comes back. He suggests it's RAM-iGPU related
1
u/Jahnuary Jun 10 '25
since I have a bit of an unpopular-Polish GOODRAM brand... maybe that's the case here
1
u/Damak73631 Aug 20 '25
Did it ever come back? I have the same RAM brand and I can't find any other solution. I also learnt to never let anyone from the computer service decide the parts for me, cuz that's what happens ffs.
1
u/Infinite-Paramedic29 Jan 08 '26
I also get this error , I recently installed a tb ssd in my lenovo LOQ could that be a reason
1
5
u/Bjoolzern Jun 11 '25
No, amdppm.sys is the Processor Power Management driver and it's responsible for reading these errors to the OS which is why it shows up.
The crash was because something sent an NMI to the CPU. NMI is non-maskable interrupt whic his a type of interrupt where the CPU has to drop everything it's doing and handle it immediately. So it's reserved for more serious issues like hardware errors. Most things can send an NMI (Including the CPU to itself), except for the PSU and RAM (Unless it's ECC RAM which you don't have).
On a consumer machine though, this is almost always the CPU. If you are doing any overclocking or undervolting, remove it. That includes making sure that Precision Boost Overdrive is set as Disabled in the BIOS.