Question PC randomly getting BSODs, possibly due to Hypervisor ?

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
I just read back here and see that Prime95 has failed on this build. Which test failed? If it was the large FFTs then it's most likely to be the CPU, if it was the small FFTs then it's most likely to be RAM - in which case Memtest86 is a MUST. I've seen brand new RAM fail.

How do you know that disabling C-States did nothing? Do you mean that the BSODs continued? You can also try modifying the Processor Power Management setting in the Windows power options so that BOTH the maximum, and minimum processor power states is 99%. That will stop the processors dropping into low-power states.

Until you do the RAM test however we may be barking up the wrong tree.
 
ubuysa said:
I just read back here and see that Prime95 has failed on this build. Which test failed? If it was the large FFTs then it's most likely to be the CPU, if it was the small FFTs then it's most likely to be RAM - in which case Memtest86 is a MUST. I've seen brand new RAM fail.
Click to expand...
I forgot which test failed. All that happened was as soon as I started the Prime95 test, I instantly got a BSOD.
ubuysa said:
How do you know that disabling C-States did nothing? Do you mean that the BSODs continued? You can also try modifying the Processor Power Management setting in the Windows power options so that BOTH the maximum, and minimum processor power states is 99%. That will stop the processors dropping into low-power states.
Click to expand...
The BSODs continued after disabling that C-state setting in my BIOS. Anyway, I've decided to change my power plan to "High Performance" and in the advanced settings, I set the "Processor Power Management" setting to 99% for both the maximum and minimum processor power states.

EDIT

Five minutes after changing my power plan and posting this message, my computer got an "IRQL_NOT_LESS_OR_EQUAL" BSOD so I decided to change my power plan, again. Now, it's set to "AMD Ryzen High Performance" and I set the "Processor Power Management" setting to 100% for both the maximum and minimum processor power states.
 
Last edited:
@ConorDuey2000

You are not helping yourself much.

For recent example: "I forgot which test failed."

You must pay attention, take notes, screenshots, be methodical, and careful.

Likewise - you decided: "Now, it's set to "AMD Ryzen High Performance" and I set the "Processor Power Management" setting to 100% for both the maximum and minimum processor power states."

Why? Reasons - expectations?

Okay: fair enough to simply give that a try. However, were you careful not to change anything else?

My suggestion is that you simply stop for a bit and do some review and focused "discovery".

The described problems are, for the most part "Critical Events".

What I suggest that you do is to use Reliability History/Monitor and Event Viewer to look for as many critical events (Red circles) as you can find. Make a list of them including Event IDs.

Likely you will find many other things: warnings (Yellow triangles) and informational entries.

Focus on the critical errors first.

Start with the proverbial big picture.

Open Event Viewer with Admin rights.

Select Windows Logs.

A pop up window should appear listing the five major logs: Application, Security, Setup, System, and Forwarded Events along with Name, Number of Events, and Size.

Take a screenshot so all can be seen and post the screen here via imgur (www.imgur.com)

Then open each individual Windows log and do the same. Sometimes windows may be a bit slow especially if the logs are very big. Possibly thousands of entries......

You do not need to rush and do not let yourself get distracted by any given discovery.

The objective is simply make a concentrated effort to learn more about what Windows is "seeing".

If you see lots of Red Circles somewhere (Reliabiity History/Monitor for example) again take some screenshots of the full screen and post.

Then the next step is to look at the critical errors (individually and collectively) that you find and troubleshoot accordingly.

It may be possible to do some filtering simply to narrow down the search results. Keep that in mind.

My sense of it all is that the system is very much amiss and that the end result will be the need for a clean install. Like it or not. Plan accordingly.

Have you been backing up everything that is important? You need multiple backups to locations away from the computer in question. Verify that the backups are recoverable and readable.

Help yourself.
 
Ralston18 said:
@ConorDuey2000

You are not helping yourself much.

For recent example: "I forgot which test failed."

You must pay attention, take notes, screenshots, be methodical, and careful.

Likewise - you decided: "Now, it's set to "AMD Ryzen High Performance" and I set the "Processor Power Management" setting to 100% for both the maximum and minimum processor power states."

Why? Reasons - expectations?

Okay: fair enough to simply give that a try. However, were you careful not to change anything else?

My suggestion is that you simply stop for a bit and do some review and focused "discovery".

The described problems are, for the most part "Critical Events".

What I suggest that you do is to use Reliability History/Monitor and Event Viewer to look for as many critical events (Red circles) as you can find. Make a list of them including Event IDs.

Likely you will find many other things: warnings (Yellow triangles) and informational entries.

Focus on the critical errors first.

Start with the proverbial big picture.

Open Event Viewer with Admin rights.

Select Windows Logs.

A pop up window should appear listing the five major logs: Application, Security, Setup, System, and Forwarded Events along with Name, Number of Events, and Size.

Take a screenshot so all can be seen and post the screen here via imgur (www.imgur.com)

Then open each individual Windows log and do the same. Sometimes windows may be a bit slow especially if the logs are very big. Possibly thousands of entries......

You do not need to rush and do not let yourself get distracted by any given discovery.

The objective is simply make a concentrated effort to learn more about what Windows is "seeing".

If you see lots of Red Circles somewhere (Reliabiity History/Monitor for example) again take some screenshots of the full screen and post.

Then the next step is to look at the critical errors (individually and collectively) that you find and troubleshoot accordingly.

It may be possible to do some filtering simply to narrow down the search results. Keep that in mind.

My sense of it all is that the system is very much amiss and that the end result will be the need for a clean install. Like it or not. Plan accordingly.

Have you been backing up everything that is important? You need multiple backups to locations away from the computer in question. Verify that the backups are recoverable and readable.

Help yourself.
Click to expand...
https://imgur.com/a/Z7AjFif
View: https://imgur.com/a/Z7AjFif

Here are the screenshots that I've taken. Hopefully, this helps you out.
 
Nicely done.

However the objective is to help you help yourself.

When you look at the logs what do you see and note?

With respect to both the big picture and re-occuring details.

Thousands of entries (approximately 90,000). Many routine and informational. [At some point it may be worthwhile to clear out the logs - but not yet. The history may be needed.]

Some of what I noted:

Those critical errors are interesting as are all of of the warnings.

For example (I cannot quite read the dates, but according to Reliability History/Monitor something happened on 1/5/2025) . "Application crashing events" and other errors began. Any problem or failed updates in Update History?

Lots of CertificateServicesClient-AutoEnrollment entries. Applications error entries.

Some Security-SPP errors.

"The Security-SPP event IDs 16384 and 16394 are related to the Software Protection Platform (SPP), which handles Windows licensing and activation. Seeing them repeatedly in the Event Viewer suggests that the Software Protection service (sppsvc) is unnecessarily restarting or re-triggering."

Lots of EventID 1000's

At face value - as if this thread was just starting with the posted screens - my first thought would be to run "dism" and "sfc /scannow".

Reference:

https://learn.microsoft.com/en-us/t...leshoot-application-service-crashing-behavior

I believe that "dism" was run at some time, maybe both tools were.

Overall, what the logs are telling me is that the OS and likely a few apps have become corrupted. Circular: you fix A which breaks B. Fix B and C breaks, fix C and D breaks, fix D and break A again.

Around and around..... Gets worse and worse. Even more so if attempted fixes are not calculated, careful, and methodical.

The fix being a clean windows install which has been continuously recommended in one way or another.
There are a few experts here when it comes to Clean Windows installs.

Of course you do not want to reinstall Windows, your apps, your games, associated files etc.. Unfortunately there may be no choice about it.

= = = =

How to proceed. My thoughts. (There may be other suggestions.)

Google a few more of the errors, read carefully, look at the details. You might find the "one ring" to resolve the issues. I would not be optimistic.

Nor am I sure that there is not some underlying hardware issue yet to discovered. That is a matter of continuing concern.

I would be very sure, that important data is backed up. Have you done that?

Read back through the entire thread. Take a step back and think about how you want to proceed.

Plan out your next steps. Lots of possibilities. Trade-offs. Priorities. Return on Investment.

Post accordingly. There may be other ideas and suggestions - especially if something else comes to light.
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom