: Why does my computer keep giving me a random HYPERVISOR_ERROR error?
: Why does my computer keep giving me a random HYPERVISOR_ERROR error?
Hello. I'm back, again. I still have a big problem with HYPERVISOR_ERROR BSODs. Every time I start up my computer with all of the VMWare services disabled, everything seems to be going fine, but after I turn on a VMWare service, open VMWare, or open WSL, that's when the problems start. After using the computer for a while after I've opened VMWare or WSL, at complete random, I get a HYPERVISOR_ERROR BSOD. I thought that it was because my RAM was faulty so I replaced my RAM, but I still get those HYPERVISOR_ERROR BSODs. In fact, I've got one a few hours ago. I've tried debugging the minidump and the kernel dump files using WinDBG and that program just told me that the process that caused the BSOD was "System". Therefore, I don't know the cause of that HYPERVISOR_ERROR BSOD. I've been all over the internet looking for a fix, but I wasn't successful. The only three known things that I can try to do in order to stop getting these HYPERVISOR_ERROR BSODs is to either buy a new CPU, buy a new computer, or use another computer that I have if I wanna run virtual machines. I don't have that kind of money just to fix that problem. There's also a program called Driver Verifier that I can use and I'll use it once I have the time to do so. Anyway, can you please help me stop getting these HYPERVISOR_ERROR BSODs? By the way, here is the minidump and here is the kernel dump.
Have you, just to remove all doubt, run memtest on the new ram? As so far, every single person who knows anything about checking dumps has looked at your PC and come up blank. So to save time, that would be a nice first step. I think Ubuysa is on a break (Just a guess based on him not being here recently, I don't really know). Driver verifer will cause BSOD... that is its job after all. It puts drivers into positions they not meant to be in, just to see their reactions. So if the problem is a driver, then has evaded us for 2 years, its doing a really good job at hiding. I assume you have clean installed in the time - I didn't read the last 3+ threads we have on this to check... Haven't we checked all the hardware already? File: 122523-49390-01.dmp (Dec 26 2023 - 09:40:33) BugCheck: [ HYPERVISOR_ERROR (20001) ] Probably caused by: memory_corruption (Process: System ) Uptime: 0 Day(s), 2 Hour(s), 57 Min(s), and 37 Sec(s) report Your bios isn't reporting any info to the report, which can be a sign of an outdated BIOS or part of your problem. I mean, if its not ram its only going to be the motherboard or CPU at this point... its been the same error for a year or more now. Update your BIOS, there is one from October 23 - https://www.asus.com/au/motherboard...sk...PLUS-WI-FI Page 50 shows you how - https://dlcdnets.asus.com/pub/ASUS/mb/So...?model=TUF GAMING X570-PLUS (WI-FI) if you had it already, it may not have flashed right the first time. Try running this on CPU - https://www.guru3d.com/files-details/pri...nload.html Prime 95 Instructions - https://appuals.com/how-to-run-a-cpu-str...g-prime95/ it is the only real software test we have for Ryzen. It will run hot and long... memory controller in CPU so if you getting same error on two different ram sticks, it could be CPU.
I don't think running memtest is useful right now because these RAM sticks are new. How could they break? I didn't change my computer's software settings, so I'm sure this isn't a problem with the operating system. My laptop works fine when I run VMWare and WSL sometimes. I will update my BIOS anyway. If that fixes things or gives me better info about my BSOD dumps, then so be it. I'll start Prime95 right away after turning on the computer to check if my CPU is okay. I need to make sure it boots straight to the desktop when I press power, and other programs won't get in the way.
It probably isn't the RAM ... errors in general don't happen over time like yours has done before a year ago. They just seem random now, so it's unlikely new RAM would make this exact same mistake, which means the RAM is likely not the issue. The controller on the CPU or motherboard could also be to blame since those parts aren't showing their details. But there are no official tests for motherboards here. You should test or replace everything else first and then see if it's just one thing left behind.