WHEA Error - Please Help

[GamerGuy89]

Everything on my computer has been running flawlessly since building it a few months ago. For the last week, I've been getting random WHEA errors. I assumed they would go away on their own since it was a generic error every time. Today, I got fed up and reinstalled windows. About 15 minutes into the new installation, I get another WHEA error. I googled it and decided to get blue screen viewer to determine the root of the problem. I have no clue how to read this error log though and need help in a big way. Can someone please direct me on how to fix this crap? Let me know what other information is needed. I'm going crazy over here.

 

[Kursah]

Have you tried backing off from overclocking and running stock? Could be a hardware issue/failure at your overclocked settings that is causing the issue.

 

[GamerGuy89]

Have you tried backing off from overclocking and running stock? Could be a hardware issue/failure at your overclocked settings that is causing the issue.

I am running stock and have been since finishing the build. I wanted to overclock a little, but have just been too busy with work. Everything was running great up until a few days ago when these errors randomly started.

edit: Nothing has changed with my build. I haven't installed or removed any new hardware since finishing the build. My temps don't ever go higher than 60-61 degrees when gaming. I'm at a loss right now.

 

[Hood]

Possible memory problem - try running Memtest86+ to check for a bad stick. These usually show up right away with a new build, but I built a Z68 system that ran fine for a year before the bad RAM stick showed errors...

 

[Kursah]

When I see 0X124 BSOD codes, it's usually from a CPU issue and usually from an OC'd CPU.

Is it the PC in your system specs?

How are temps?

What are you doing most often when it crashes?

Maybe try resetting BIOS to make sure it's all stock, RAM included. Try setting XMP profiles to run at rated speed and see if that makes it unstable. Maybe try 1 stick of RAM as well. Or try a more relaxed config for DDR4.

I'd run some tests. Check temps. I like to use OCCT, Memtest and Asus ROG for stress/stability testing. There's others as well...but that's where I'd start.

 

[GamerGuy89]

Possible memory problem - try running Memtest86+ to check for a bad stick.

I will download that and try now.

When I see 0X124 BSOD codes, it's usually from a CPU issue and usually from an OC'd CPU.

Is it the PC in your system specs?

How are temps?

What are you doing most often when it crashes?

Maybe try resetting BIOS to make sure it's all stock, RAM included. Try setting XMP profiles to run at rated speed and see if that makes it unstable. Maybe try 1 stick of RAM as well. Or try a more relaxed config for DDR4.

I'd run some tests. Check temps. I like to use OCCT, Memtest and Asus ROG for stress/stability testing. There's others as well...but that's where I'd start.

Yes it is. My temps before the Windows reinstall were fine. They never reached higher than 60-61 degrees. I'm doing anything when it crashes. It has done it playing WoW, surfing the web, idling at the desktop and it just did it when replying to this quote. How do I reset BIOS? I'm trying to download the memtest now. Everything is new and was working a few days ago without an error ever. How can this error just happen out of the blue? I'm literally going crazy.

 

[GamerGuy89]

Add another BSOD to the list.

 

[Caring1]

https://answers.microsoft.com/en-us...ll-error/bff7bb96-4b9d-4448-ac4b-6b21dcea8cd7
Scroll down to the most helpful answer towards the bottom of the screen.

 

[GamerGuy89]

https://answers.microsoft.com/en-us...ll-error/bff7bb96-4b9d-4448-ac4b-6b21dcea8cd7
Scroll down to the most helpful answer towards the bottom of the screen.

I'll try to do some of those things. I've gotten a BSOD about 5 times since creating this post. It's becoming impossible to do anything remotely productive in terms of troubleshooting.

 

[Hood]

I notice that your RAM is clocked at 3000 MHz, and while this is within the specs of your board, that speed is not guaranteed. Are you using the XMP setting in your BIOS? I don't really trust MSI boards since the Z87 board I had only wanted to run my 2400 RAM at 1333, no matter what settings I used, so I ended up selling that system. You could try manually clocking the RAM at 2400 or 1866 to see if the errors persist.

 

[GamerGuy89]

I notice that your RAM is clocked at 3000 MHz, and while this is within the specs of your board, that speed is not guaranteed. Are you using the XMP setting in your BIOS? I don't really trust MSI boards since the Z87 board I had only wanted to run my 2400 RAM at 1333, no matter what settings I used, so I ended up selling that system. You could try manually clocking the RAM at 2400 or 1866 to see if the errors persist.

Yes I was using XMP. Here's what I've done so far since opening this thread:

Turned XMP off
Downloaded Ccleaner and fixed registry issues that it noticed
Memtest is running now (not sure how intense the testing is but I'm at 51C on the CPU during test)
Installed updated chipset drivers

Edit: memtest is 66% done with pass 1 of 4. No errors as of yet.

 

[Final_Fighter]

WHEA Errors 90% of the time are a result of an unstable overclock. sense you said that you are not overclocking than it might be a power supply/delivery issue. i would try and find out what your 3.3v, 5v, and 12v rail reading are. most of the time you can find these in the bios under the hardware monitoring tab. there are other ways to test a power supply but i am not skilled in advanced methods.

if the psu seems alright try giving the cpu a slight overvolt. you may have just got a really bad chip or its just hungry.

edit, why i bring up the power supply is because i had a similar situation were i was getting WHEA errors and just ignored them. after a while the computer would just randomly lock up and i would have to shut it down. ended up being the psu.

 

[GamerGuy89]

WHEA Errors 90% of the time are a result of an unstable overclock. sense you said that you are not overclocking than it might be a power supply/delivery issue. i would try and find out what your 3.3v, 5v, and 12v rail reading are. most of the time you can find these in the bios under the hardware monitoring tab. there are other ways to test a power supply but i am not skilled in advanced methods.

if the psu seems alright try giving the cpu a slight overvolt. you may have just got a really bad chip or its just hungry.

Test 1 of 4 on memtest just finished with 0 errors. Should I cancel the test now and try to get my psu readings?

 

[Final_Fighter]

Test 1 of 4 on memtest just finished with 0 errors. Should I cancel the test now and try to get my psu readings?

i would let memtest run when you go to bed. go ahead and get those readings.

also see what your cpu temp is inside the bios.

 

[GamerGuy89]

i would let memtest run when you go to bed. go ahead and get those readings.

also see what your cpu temp is inside the bios.

I'm not finding anything for psu in bios. Under hardware monitoring is just fan speeds etc. I tried the bios search bar for psu, power, rail, 3.3 and nothing there either. Any other ideas to check psu?

 

[Final_Fighter]

let me look around.

edit: just looked up a video on your bios and did not see anything either. do you have a spare psu that you could put in and test?

 

[GamerGuy89]

let me look around.

edit: just looked up a video on your bios and did not see anything either. do you have a spare psu that you could put in and test?

I do not have any extra pieces of hardware at all other than 2 SP120 fans. Since doing the things mentioned above, I have not had a BSOD in about 15 minutes. I was getting them every 5 minutes or so previously. I'm running burnin test on a friend's recommendation right now too. 8 minutes in and CPU temps maxed out at 70C and the 1080 maxed at 55C with no errors found anywhere yet either. I have no way of knowing when/if things are fixed for sure until I get a BSOD.

 

[eidairaman1]

I found most bsods that would pop even on clean os installs were memory related, pull your cpu, chevk for bent or burnt pins, swap in known good ram and see if it stabilizes, next to worst case is a fresh OS install.

 

[DRDNA]

I notice that your RAM is clocked at 3000 MHz, and while this is within the specs of your board, that speed is not guaranteed. Are you using the XMP setting in your BIOS? I don't really trust MSI boards since the Z87 board I had only wanted to run my 2400 RAM at 1333, no matter what settings I used, so I ended up selling that system. You could try manually clocking the RAM at 2400 or 1866 to see if the errors persist.

I think Hood hit a bulls-eye here with XMP on that MSI board. Manually set it to 2400 or 1866 and retest and I bet no more BSOD.

 

[RejZoR]

WHEA is usually CPU related.

Check your CPU OC stability using ASUS RealBench and running H.264 test in 10 loops. If it passes all 10, it's not CPU.

 

[GamerGuy89]

I think Hood hit a bulls-eye here with XMP on that MSI board. Manually set it to 2400 or 1866 and retest and I bet no more BSOD.

I just turned XMP off. Is that sufficient?

WHEA is usually CPU related.

Check your CPU OC stability using ASUS RealBench and running H.264 test in 10 loops. If it passes all 10, it's not CPU.

I'm downloading and doing that now.

WHEA is usually CPU related.

Check your CPU OC stability using ASUS RealBench and running H.264 test in 10 loops. If it passes all 10, it's not CPU.

All 10 H.264 loops went just fine. My max temp was 69C.

Just got 2 BSOD in the last few minutes. Memtest went fine, Burnin test went fine, Realbench loops went fine, I turned off XMP, I reinstalled windows 10, I used a registry cleaner...Now what?

 

[Hood]

I just turned XMP off. Is that sufficient?

Maybe, but I would set BIOS to optimized defaults, then set memory clock manually, or leave it at 1333 for now, and see how long it runs without errors or bluescreens. If no problems then, raise the memory clock to 1600, 1866, 2400, and finally 2800 (to see when errors start to occur). If errors start showing, drop back to the next slower clock and redo stability testing to confirm that it's stable. Have you tried clearing the CMOS? Also, do you have the latest BIOS installed? A BIOS update will often improve hardware compatibility.

 

[sneekypeet]

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?

 

[DeathtoGnomes]

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?

If there are no BSOD's while running all these tests, then ^^This^^, the "auto" settings in the BIOS are inadequate. Get HWIfno64 post a screen of everything there along with the CPUZ screenshot.

If your BIOS is flash is current, then try a previous one, or update to the latest.

Being a new build can we assume everything is still under warranty?

 

[GamerGuy89]

http://i.imgur.com/AeGm79G.png

It won't let me insert it for some reason. BIOS hasn't been touched since I built the computer. Everything should be under warranty still since it was all purchased in Feb/March.