Computer experiences frequent random HYPERVISOR_ERROR BSODs?
Computer experiences frequent random HYPERVISOR_ERROR BSODs?
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 decided to perform a memtest on the new RAM? To be certain, all those who are familiar with checking dumps have examined your PC and found nothing. This would be a good initial action.
I believe Ubuysa is currently offline (just a guess based on his absence lately, I’m not sure).
Driver verifier can trigger BSOD... that’s its intended purpose. It forces drivers into unexpected states to observe their behavior. Therefore, if the issue stems from a driver, it has likely been overlooked for two years and is effectively concealing itself.
I assume you installed it correctly recently—didn’t I review the last three or more threads we discussed? Have we already verified all hardware components?
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 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.
I'll update my BIOS once again. Hopefully, the update will fix my problems and/or give you more information on my BSOD dumps.
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.
It's unlikely the RAM is the issue, as the problems have persisted for over a year and are not consistent. The new RAM seems less likely to be the cause, making it more probable that another component is responsible. The CPU controller may also be involved, but there are no available tests for motherboards. It might help to check other parts first.