• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

WHEA Error - Please Help

My guess is that the auto setting for CPU voltage is a bit light. 124 and WHEA screams CPU. Since you are not overclocking, it would be the logical thing to do in my mind to raise the CPU voltage a few ticks and see if the BSOD goes away.

Could you possibly load the CPU with one of your testing programs and grab us a screen shot of CPU-Z so we can see what the loaded voltage for that CPU is in the first place?

I've never messed with voltages. What should I set it to? It's becoming very hard to do anything on this computer. Blue screens are happening every 5 minutes. I'm at a loss right now and feel defeated as hell.
 
go into BIOS and tell us what the auto setting for voltage on the CPU is currently please.
 
MgsmvkJ.jpg
 
Isn't that Ram meant to run at 1.35V?
Edit, SPD voltage is 1.2, carry on.
 
Isn't that Ram meant to run at 1.35V?

I'm truly not sure. I've never touched voltages before. I built the computer, turned on XMP and left everything else alone. Things were running perfect until a few days ago.
 
I would suggest you bump the CPU voltage to 1.250V and see what happens.
 
I would suggest you bump the CPU voltage to 1.250V and see what happens.

Done. And ran 1 loop of H.264 to have you guys check things.

1zqhMeD.png
 
Looks fine. Now just play the waiting game and see if you get a BSOD.
 
Looks fine. Now just play the waiting game and see if you get a BSOD.

No BSOD yet! /fingers crossed

edit: Still no BSOD as of yet!
 
Last edited:
mmmhhhhmmmm:toast:
 
make sure that the WHEA erros go away to.
 
Done. And ran 1 loop of H.264 to have you guys check things.

1zqhMeD.png

One loop often isn't enough. I've had cases when it has done first 2 loops fine and locked up in the beginning of loop 3.

You can use Heavy Multithreading to also involve single core and memory check because it runs multiple things at once. This can reveal potential issues with RAM.

Oh and based on my recent events, it's smart to make a full CMOS clear on such problems and start all over. I've set all my BIOS settings to default, but somehow, some memory timings remained in action regardless somehow and that was causing system crashes/lockups during heavy loads (aka games) even when my system was seemingly set to stock speeds. Could be just bug on my mobo, but now I know for the future just to be sure.
 
I ran 10 loops previously. I was only running 1 loop to get a voltage screenshot etc for everyone. I passed 10 H.264 loops the previous night without a hiccup. So far, so good since the voltage increase yesterday.
 
Back
Top