Question Computer keeps on getting random HYPERVISOR_ERROR BSODs ?

[ConorDuey2000]

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.

 

[Colif]

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.

Anyway, my CPU is an AMD Ryzen 7 3800X 8-Core processor, I have 16GB of RAM, I have a 512GB SSD and a 10TB HDD, and I have a power supply by EVGA.

ASUS TUF GAMING X570-PLUS (WI-FI)

Update your BIOS, there is one from October 23 - https://www.asus.com/au/motherboard...sk_bios?model2Name=TUF-GAMING-X570-PLUS-WI-FI

Page 50 shows you how - https://dlcdnets.asus.com/pub/ASUS/mb/SocketAM4/PRIME_X570-P/E15829_PRIME_PRO_TUF_GAMING_X570_Series_BIOS_EM_WEB.pdf?model=TUF GAMING X570-PLUS (WI-FI)

if you had it already, it may not have flashed right the first time.

buy a new CPU,

Try running this on CPU - https://www.guru3d.com/files-details/prime95-download.html
Prime 95 Instructions - https://appuals.com/how-to-run-a-cpu-stress-test-using-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.

 

[ConorDuey2000]

Have you, just to remove all doubt, run memtest on the new ram?

I really do not see the point in running memtest on two brand new sticks of RAM. They're brand new. How could they have problems?

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?

I didn't do a clean install. I wouldn't really see the point since I'm certain that this isn't a software issue. I've have a laptop that I occasionally run VMWare and WSL on and it doesn't have any problems.

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.

I'll update my BIOS once again. Hopefully, the update will fix my problems and/or give you more information on my BSOD dumps.

Try running this on CPU - https://www.guru3d.com/files-details/prime95-download.html

I'll run Prime95 to see if my CPU has problems. I'll make sure to start it as soon as I turn on my computer and it boots to the desktop so other programs won't get in the way.

 

[Colif]

It probably isn't the ram ... ram errors generally don't stick to the same cause like yours has for over a year now. They more random.,.. its doubtful new ram would cause the exact same problem, so its more likely ram isn't the problem.

Controller for ram on CPU
Motherboard not showing its details could also mean its cause... but there are no tests for motherboards. You test or replace everything else to point its the only thing left.