"Whea_Uncorrectable_Error" Bsod Message after CPU OC.

[TheNaitsyrk]

I overclocked my 4790K in BIOS to 4.6Ghz with 1.2V.

 

I run Prime95 test to see if it's stable. 

 

For a minute it works perfectly, temperatures are well within reason (70 degrees).

 

But then I get "Whea_Uncorrectable_Error" BSOD. I tried running the test twice to see if that's just a random error, and well... It wasn't.

 

Any idea why it happens? I tried overclocking my CPU through software before I overclocked through BIOS and then I played some games and it was all stable but temperatures were slightly too high so I decided to overclock through BIOS.

[Fluxx]

BIOS is safer, the blue screen just means it was unstable, give it more voltage if you can or back down the clock speed.

[TheNaitsyrk]

I'll try 4.5Ghz maybe it will work.

[daniellearmouth]

Yeah, either dial back the overclock or increase the voltage slightly.

[TheNaitsyrk]

Now the test works for longer and no crashes after altering the clock speed. 4.5Ghz seems to be stable for now. By how much should I increase the voltage to achieve 4.6Ghz in this case?

[TheNaitsyrk]

Actually after 5 minutes the temperatures were fine, and then they started to skyrocket up. I started getting 87 then 90 then 92 ao I turned the test off. Any idea what happened?

[ApolloX75]

Actually after 5 minutes the temperatures were fine, and then they started to skyrocket up. I started getting 87 then 90 then 92 ao I turned the test off. Any idea what happened?

Prime95 plays havoc with Haswell in certain tests. Use Intel XTU or Aida64 for trouble-free and worry free stress testing.

[Cheddle]

I overclocked my 4790K in BIOS to 4.6Ghz with 1.2V.

I run Prime95 test to see if it's stable.

For a minute it works perfectly, temperatures are well within reason (70 degrees).

But then I get "Whea_Uncorrectable_Error" BSOD. I tried running the test twice to see if that's just a random error, and well... It wasn't.

Any idea why it happens? I tried overclocking my CPU through software before I overclocked through BIOS and then I played some games and it was all stable but temperatures were slightly too high so I decided to overclock through BIOS.

http://www.hardwareluxx.com/index.php/reviews/hardware/cpu/33127-oc-guide-bringing-haswell-e-to-its-limits.html?start=5

There is some info on BSOD and their relevant causes

[Fetzie]

You shouldn't be using Prime95 anymore. All it does is generate a butt ton of heat, and at some point it'll crash. A bit like Furmark did before AMD and nVidia put in detection for it and throttle the GPU when that program is running. Use Aida64 or OCCT instead.

[TheNaitsyrk]

I tested using IntelBurnTest, Intel Extreme Tuning Utility and results are very different...

IntelBurnTest = 80c under full load on 4.2Ghz (I reverted back to original settings in BIOS, all on auto so it's stock)

Extreme Utility = 63c under full load on 4.0Ghz I believe.

OCCT = 63c, same as Extreme Utility.

[Cheddle]

I personally use Cinebench R15 (three runs), XTU (bench + 5 min test) then AIDA64 (10 min test) - in that order... to test a CPU clock/voltage.

 

depending on how far along my failure is will give me an idea of how "unstable" the clock is.

 

Cinebench is light and I have run it on entirely unstable clocks, but if it crashes I know that my clock is very very unstable. 

 

XTU is fairly heafty and will usually either crash in the bench or it will pass the 5 min test.

 

AIDA64 is just to make sure everything is hunkydory. AIDA64 is so intense I cant use the computer for browsing while its running without slowdowns... XTU is taking it easy.

 

I then do normal use/game for a few days to make sure it is what I consider "stable" before I start to push any other component to its limits - I won't touch RAM until I know my CPU is stable af. TBH I never really touch RAM given its low returns for effort spent.

 

--

 

I never use prime95 and I have stopped using Linx - I have had Linx crash my rig or report errors where NOTHING ELSE will show any signs of being sad.

[TheNaitsyrk]

I personally use Cinebench R15 (three runs), XTU (bench + 5 min test) then AIDA64 (10 min test) - in that order... to test a CPU clock/voltage.

 

depending on how far along my failure is will give me an idea of how "unstable" the clock is.

 

Cinebench is light and I have run it on entirely unstable clocks, but if it crashes I know that my clock is very very unstable. 

 

XTU is fairly heafty and will usually either crash in the bench or it will pass the 5 min test.

 

AIDA64 is just to make sure everything is hunkydory. AIDA64 is so intense I cant use the computer for browsing while its running without slowdowns... XTU is taking it easy.

 

I then do normal use/game for a few days to make sure it is what I consider "stable" before I start to push any other component to its limits - I won't touch RAM until I know my CPU is stable af. TBH I never really touch RAM given its low returns for effort spent.

 

--

 

I never use prime95 and I have stopped using Linx - I have had Linx crash my rig or report errors where NOTHING ELSE will show any signs of being sad.

Well, that's what I did. Tested couple of times and temperatures are still not so great, even though the CPU is only at 4.2Ghz.

[runit3]

Well, that's what I did. Tested couple of times and temperatures are still not so great, even though the CPU is only at 4.2Ghz.

63C at full load is great. Your clock is meaningless when it comes to temps, only voltage matters. If you were at 4.2 with 1.1-1.15v you have plenty of overhead, just stop using IBT and Prime.

 

They offer nothing that XTU and AIDA don't, besides the ability to stress test your cooling setup more than any other bench/stress software suite.