F5F Stay Refreshed Software Operating Systems PC experiences frequent BSODs, which may be linked to the hypervisor.

PC experiences frequent BSODs, which may be linked to the hypervisor.

PC experiences frequent BSODs, which may be linked to the hypervisor.

Pages (3): 1 2 3 Next
S
SA_minecraft
Member
203
01-13-2026, 02:18 AM
#1
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; Question - I'm getting random IRQL_NOT_LESS_OR_EQUAL BSODs on a regular basis? Hello. As of recently, my computer is having some big problems. It's been getting IRQL_NOT_LESS_OR_EQUAL BSODs on a regular basis. I've tried debugging the BSODs using WinDbg, but they just told me "Process name: System" so that means I have no idea what's causing these BSODs. I've tried... forums. 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.
S
SA_minecraft
01-13-2026, 02:18 AM #1

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; Question - I'm getting random IRQL_NOT_LESS_OR_EQUAL BSODs on a regular basis? Hello. As of recently, my computer is having some big problems. It's been getting IRQL_NOT_LESS_OR_EQUAL BSODs on a regular basis. I've tried debugging the BSODs using WinDbg, but they just told me "Process name: System" so that means I have no idea what's causing these BSODs. I've tried... forums. 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.

O
ozhi
Junior Member
7
01-13-2026, 02:18 AM
#2
Is the virtualization feature turned off in the BIOS settings?
O
ozhi
01-13-2026, 02:18 AM #2

Is the virtualization feature turned off in the BIOS settings?

M
MegaDisco
Senior Member
352
01-13-2026, 02:18 AM
#3
Yes. I turned it off, or at least I'm certain I did. I disabled "SVM Mode" in my computer's BIOS, which should have turned off virtualization.
M
MegaDisco
01-13-2026, 02:18 AM #3

Yes. I turned it off, or at least I'm certain I did. I disabled "SVM Mode" in my computer's BIOS, which should have turned off virtualization.

E
emanking1
Member
65
01-13-2026, 02:18 AM
#4
I hope my assumption is incorrect and the only solution is a new PC. What year is it? It's not always about Hypervisor, but it's usually enough. I allowed Ubuysa to try, maybe you can figure it out.
E
emanking1
01-13-2026, 02:18 AM #4

I hope my assumption is incorrect and the only solution is a new PC. What year is it? It's not always about Hypervisor, but it's usually enough. I allowed Ubuysa to try, maybe you can figure it out.

S
SpiderMan1962
Member
77
01-13-2026, 02:18 AM
#5
The computer is roughly five years old, and I assembled it in December 2019.
S
SpiderMan1962
01-13-2026, 02:18 AM #5

The computer is roughly five years old, and I assembled it in December 2019.

D
DDotty2
Member
223
01-13-2026, 02:18 AM
#6
You've been working with this for several years now. Eventually, you realize you must reset and reinstall to achieve a fresh start. Whether you're avoiding reinstalling your apps doesn't matter. You might have managed the issue earlier if you hadn't been so determined.
D
DDotty2
01-13-2026, 02:18 AM #6

You've been working with this for several years now. Eventually, you realize you must reset and reinstall to achieve a fresh start. Whether you're avoiding reinstalling your apps doesn't matter. You might have managed the issue earlier if you hadn't been so determined.

G
190
01-13-2026, 02:18 AM
#7
Did you see this section of my message?
I think it's a solid reason why I'm holding off on reinstalling Windows. What if I do, but the BSODs keep happening? That would mean I'd lose everything without any good reason.
G
gustavbengters
01-13-2026, 02:18 AM #7

Did you see this section of my message?
I think it's a solid reason why I'm holding off on reinstalling Windows. What if I do, but the BSODs keep happening? That would mean I'd lose everything without any good reason.

L
louie018
Posting Freak
824
01-13-2026, 02:18 AM
#8
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.
L
louie018
01-13-2026, 02:18 AM #8

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.

B
Badwolf028
Junior Member
28
01-13-2026, 02:18 AM
#9
If the reinstall doesn't work, there might be other solutions available to resolve the BSOD issues rather than abandoning your efforts.
B
Badwolf028
01-13-2026, 02:18 AM #9

If the reinstall doesn't work, there might be other solutions available to resolve the BSOD issues rather than abandoning your efforts.

Q
quadlaser
Member
95
01-13-2026, 02:18 AM
#10
It would be unusual. If you're not ready for thorough troubleshooting, help will likely be scarce.
Q
quadlaser
01-13-2026, 02:18 AM #10

It would be unusual. If you're not ready for thorough troubleshooting, help will likely be scarce.

Pages (3): 1 2 3 Next