Question PC randomly getting BSODs, possibly due to Hypervisor ?

ConorDuey2000

Reputable
Dec 21, 2021
174
3
4,585
Hello.

I'm creating another thread because my computer still has this big problem where it randomly BSODs. Here's a link to the prior thread;


I could be normally using my computer and suddenly, I get a random BSOD. Sometimes, I get a BSOD about fifteen minutes after starting my computer. I'm lucky if my computer doesn't get any BSODs for an entire day. After analyzing the BSODs that I've gotten, I'm pretty sure that Hypervisor's the reason why I'm getting these BSODs because my computer used to randomly get HYPERVISOR_ERROR BSODs on a regular basis until I turned off the Windows features for Hypervisor. Now, the BSODs I get are usually "IRQL_NOT_LESS_OR_EQUAL" BSODs. I also saw errors in Event Viewer relating to Hypervisor such as messages saying "A hypervisor feature is not available to the user." and I see Hypervisor being brought up when I debug my BSOD dumps in WinDbg.

As of now, I've tried everything I could to try and disable Hypervisor, but I still get those BSODs. I've used bcdedit, DISM, and Device Guard and Credential Guard hardware readiness tool, but I still get them. The BSODs are very similar to each other and my efforts to remove Hypervisor from my computer only slightly decreased the amount of BSODs that I get. I'm not reformatting my computer because I have lots of important apps installed on my computer and it's gonna take me forever to reinstall all of them. Also, I'm worried that reformatting my computer won't stop these BSODs from happening. I'm also not buying a new computer because my current computer costed me $2000 USD and I'm not spending another $2000 USD.

At this point, as ridiculous as it may sound, I believe that my computer has become self aware and has decided to get BSODs whenever it feels like it. If I can't get those BSODs to stop, then I'm just gonna have to wait until my current computer becomes obsolete so that I have to buy a new computer. Anyway, I ran SysnativeBSODCollectionApp 5.0.3 and here is the ZIP file that it created. Hopefully, you can analyze what's in the ZIP file and see what's causing all of these BSODs to happen.
 
Last edited by a moderator:
I hope I am wrong and the only way these will stop is new PC.

What year is it? I know, its not always Hypervisor but it sure is often enough.

I let Ubuysa try, you might figure it out :)
 
I hope I am wrong and the only way these will stop is new PC.

What year is it? I know, its not always Hypervisor but it sure is often enough.

I let Ubuysa try, you might figure it out :)
My computer is about five years old and I first built it in December 2019.
 
..... I'm not reformatting my computer because I have lots of important apps installed on my computer and it's gonna take me forever to reinstall all of them. ....
You have been at this for at least a couple of years now. At some point you have to accept the fact that you need to format/reinstall in order to get a clean start. The fact that you don't want to reinstall your apps is irrelevant. You could have solved the problem from the outset had you not been so stubborn.
 
  • Like
Reactions: Lutfij
You have been at this for at least a couple of years now. At some point you have to accept the fact that you need to format/reinstall in order to get a clean start. The fact that you don't want to reinstall your apps is irrelevant. You could have solved the problem from the outset had you not been so stubborn.
Did you read this part of my post?
Also, I'm worried that reformatting my computer won't stop these BSODs from happening.
That's what I consider to be a valid reason why I'm not reinstalling Windows. What if I reinstall Windows, but I still keep on getting those BSODs? That'd mean I'd permanently delete all of my applications and settings for no reason.
 
Did you read this part of my post?
Yes, I did. And every other post you've made concerning this issue over the last 2+ years.
That's what I consider to be a valid reason why I'm not reinstalling Windows. What if I reinstall Windows, but I still keep on getting those BSODs? That'd mean I'd permanently delete all of my applications and settings for no reason.
At some point you must accept the fact that a reinstall is indicated if for no other reason that it provides a known, clean starting point for troubleshooting. Your refusal to go this route is, at this point, beginning to sound like you have a collection of "questionable" titles on board and don't want to have to admit it.
 
Yes, I did. And every other post you've made concerning this issue over the last 2+ years.

At some point you must accept the fact that a reinstall is indicated if for no other reason that it provides a known, clean starting point for troubleshooting. Your refusal to go this route is, at this point, beginning to sound like you have a collection of "questionable" titles on board and don't want to have to admit it.
What if the reinstall doesn't solve my problem? Why can't I just find another way to stop the BSODs instead of giving up and losing all of my apps?
 
It wouldn't be the first time. Unless you are prepared to do proper troubleshooting you will soon find no one willing to assist.
I can learn how to do more types of troubleshooting, but if I'm unable to do so, it'd be okay if I could get some help and tutorials on how to troubleshoot and diagnose computer problems, do debugging, and learn about what error codes mean.
 
Over the last 3-4 years you have been given very good advice and refused to consider a great deal of it. Most of those involved may well have more years of experience in the field than you have been alive. It would do you well to listen, learn, and actually follow the advice given. Until you do you will never find the root cause of your problem.
 
  • Like
Reactions: Lutfij
Over the last 3-4 years you have been given very good advice and refused to consider a great deal of it. Most of those involved may well have more years of experience in the field than you have been alive. It would do you well to listen, learn, and actually follow the advice given. Until you do you will never find the root cause of your problem.
I agree with you. I was given lots of good advice which I've followed and there were only a few pieces of advice that I decided not to follow with one of them being to reinstall Windows and another one being to buy a new computer or expensive computer part. How some people treat their personal data isn't how everybody treats their personal data and I wouldn't wanna lose everything that I have on my C drive or spend lots of money just for a way to stop the BSODs from happening, especially when reinstalling Windows or buying something expensive isn't confirmed to solve my problem. I created this new forum post so I could look for any other users on here that can give me more advice and suggestions on how to stop these BSODs from happening.
 
why not buy a cheap ssd and install windows onto it and see if it solves problem, if you not willing to reinstall on current drive.
I do have a spare SSD that I can use, but since installing it into my computer and putting Windows on it could be a pretty big task, I prefer to search for other possible fixes.
 
I do have a spare SSD that I can use, but since installing it into my computer and putting Windows on it could be a pretty big task, I prefer to search for other possible fixes.
It wouldn't take more than 2 minutes to install (replacing the existing drive) the drive and another 15 or so to install Windows & updates, nothing "pretty big" about it. You still haven't revealed what specific software (by title) you are so worried about losing.
 
  • Like
Reactions: drivinfast247
It wouldn't take more than 2 minutes to install (replacing the existing drive) the drive and another 15 or so to install Windows & updates, nothing "pretty big" about it. You still haven't revealed what specific software (by title) you are so worried about losing.
Whatever apps and settings are on my computer doesn't really matter. It's just gonna take forever for me to reapply all of my settings and reinstall all of my apps which I regularly use. Fifteen minutes seems to be a short time. I do have the spare SATA SSD and all that I need a SATA cable and a way to disable my M.2 SSD that I currently have Windows installed on. I'm worried that it might conflict with installing windows onto the SATA SSD.
 
might want to take nvme out when you install onto ssd. Windows will see it and want to use its boot partition. Better to not let it do that.

don't need everything on it, just enough to see if errors return. Its not meant to replace nvme, its just a test.

install time onto ssd on modern pc is about 15 minutes. Its much better than the past. Yes, making it home again takes time.
 
might want to take nvme out when you install onto ssd. Windows will see it and want to use its boot partition. Better to not let it do that.

don't need everything on it, just enough to see if errors return. Its not meant to replace nvme, its just a test.

install time onto ssd on modern pc is about 15 minutes. Its much better than the past. Yes, making it home again takes time.
I'll see if it's possible to take out my M.2 SSD. If it is, then I'll try installing Windows onto the SATA SSD and letting it stay on overnight to see if it gets any BSODs.
 
Whatever apps and settings are on my computer doesn't really matter. It's just gonna take forever for me to reapply all of my settings and reinstall all of my apps which I regularly use. Fifteen minutes seems to be a short time. I do have the spare SATA SSD and all that I need a SATA cable and a way to disable my M.2 SSD that I currently have Windows installed on. I'm worried that it might conflict with installing windows onto the SATA SSD.
And how long would it take to reinstall your apps and reapply settings if the drive failed in the next 15 seconds and you had to reinstall everything from scratch? Sounds like you don't have a backup or recovery plan in place.
 
  • Like
Reactions: Lutfij and COLGeek
My computer is about five years old and I first built it in December 2019.
you might want to remove this driver:
ScpVBus.sys Sun May 5 14:31:26 2013
it has a bug where it will corrupt system memory and crash other drivers.
I think I saw a fixed version that was made in 2016 but I am not sure where to get it.

be sure to update your Realtek hd audio driver. there used to be a bug where it would crash other gpu audio drivers. I do not recall when it was fixed. your version was from 2021.

there were a few other issues with very old drivers but those two drivers should be updated or removed.
oh, i think you have to use Microsoft autoruns64.exe to remove the ScpVBus.sys driver because the installer just leaves in installed. driver is scarlet crush public domain driver. main issue was pooltag was set to NULL. pooltags are now required.
the driver is used for some game adapters.
 
looked at the rest of the mini dumps, you have a few modified files, and some old drivers. looks like all of your problems are due to some stupid driver you have installed that is over writing kernel memory data structures. basically, a driver requests a memory block, windows gives the block to it. the driver writes data to the memory block, then later frees the data block and windows then is free to give it back to the next driver. So windows gives the block to driver 2. The problem happens when driver 1 then writes to the memory block (bug) and corrupts the memory. Later driver 2 uses the memory and crashes or windows checks the released block for corruption and calls a bugcheck if it finds a corruption.

you can use verifier.exe testing to make windows check each memory allocation and it will bugcheck your system at the time of corruption and name the bad driver.
the scarlet crush driver will be flagged and bugcheck the system on bootup if it is installed while verifier flags are turned on.
(2016 version might be ok, never tested it)

most likely one of your other old drivers will also fail.
you also had a few modified windows files but not the files that are generally modified by malware. looked like modified usb files. it might be related to your usb filter driver that is redirecting your usb. (UsbDk.sys)
notes:
WinRing0x64.sys Sat Jul 26 06:29:37 2008
MsIo64.sys Sun Dec 10 22:39:57 2023
C:\Program Files (x86)\UltraISO\drivers\ISODrv64.sys Fri Nov 24 19:44:22 2006
idmwfp.sys Wed Jul 6 07:37:41 2011
GLCKIO2.sys Mon Apr 22 06:44:46 2019
dtlitescsibus.sys Mon Nov 12 19:11:07 2018
dtliteusbbus.sys Mon Jul 26 11:43:47 2021

edit:
idmwfp.sys Wed Jul 6 07:37:41 2011
is some 3rd party internet download manager. You should use autoruns64.exe and remove it.
 
Last edited:
I have just come out of seemingly this exact issue - I ended up concluding that my CPU was failing and replacing it after a lot of messing with verifier and drivers, then a clean reinstall of Windows which did nothing, and the RAM was also okay. Try running prime95 - see how your CPU fares with a stress test.
 
  • Like
Reactions: Colif
And how long would it take to reinstall your apps and reapply settings if the drive failed in the next 15 seconds and you had to reinstall everything from scratch? Sounds like you don't have a backup or recovery plan in place.
About a year.

you might want to remove this driver:
ScpVBus.sys Sun May 5 14:31:26 2013
it has a bug where it will corrupt system memory and crash other drivers.
I think I saw a fixed version that was made in 2016 but I am not sure where to get it.
I've removed that driver. It's supposed to be for DualShock 3 controllers which I rarely use with my computer.
you can use verifier.exe testing to make windows check each memory allocation and it will bugcheck your system at the time of corruption and name the bad driver.
the scarlet crush driver will be flagged and bugcheck the system on bootup if it is installed while verifier flags are turned on.
(2016 version might be ok, never tested it)
Last time I ran Driver Verifier, it got stuck in a boot loop. Luckily, I created a restore point just before I ran Driver Verifier.
idmwfp.sys Wed Jul 6 07:37:41 2011
is some 3rd party internet download manager. You should use autoruns64.exe and remove it.
I've removed idmwfp.sys using autoruns64.exe. That driver's for Internet Download Manager which I never use.
I have just come out of seemingly this exact issue - I ended up concluding that my CPU was failing and replacing it after a lot of messing with verifier and drivers, then a clean reinstall of Windows which did nothing, and the RAM was also okay. Try running prime95 - see how your CPU fares with a stress test.
The last time I ran Prime95, my computer instantly got a BSOD right after I ran it.