Blue screen during Prime95 normal?

SkruDe

Distinguished
Dec 30, 2012
189
12
18,685
Hello.

I have a 3930k and I am currently attempting to get up to 4.5GHz with my XSPC custom watercooled desktop. In the past, when I was overclocking to 4.3Ghz, I used Prime95 and when a "worker" (thread) failed it gave me the notification in the Prime95 program and it shut down that thread completely till the stress test was manually stopped. This has always been the case for me when I stress tested and got failures.

Recently, I have been getting the urge to continue and push my CPU farther. I decided I wanted a 4.5Ghz overclock. I set my multiplier to 45 and adjusted my Vcore voltage to a safe starting range of 1.400V. I then booted to desktop and started stress testing with Prime95 my new settings. The stress testing, on Prime95's "Blend" test went well for the first 3 hours with no problem. A little after 3 hours though my computer dumped to a blue screen. Here is a screenshot of my blue screen: http://tinypic.com/r/2layadh/5

My question is this, is blue screening during Prime95 stress testing something that is common and I should not be worried about? 3 Hours is a pretty good test but I was aiming at getting 12. Again, every time I have stress tested in the past Prime95 would simply stop a worker/thread if it failed to meet the requirements. I'd then stop Prime95, up Vcore by .010 and try again. This time, I am just posting to make sure before moving forward again since this never happened to me before.

If anymore information is needed let me know.

Thank you.
 
Solution
My procedure goes something like this:

1) IBT (Intel Burn Test, Prime95+ pseudo competitor) for 10 passes on "Very High" with max threads enabled. Ensure that it yields a maximum temperature >=10°C below thermal throttle limit (eg max temp <=95°C for Haswell, where thermal limit = 105°C). You will get lots of BSOD's during this test initially and get yourself a ballpark voltage.
2) Use the computer and wait for a BSOD. If my OC fails, I increase the voltage again by 0.005 V. It is not uncommon to have smooth sailing for a few months and then randomly get another BSOD. Simply increase the voltage and repeat step #1 again, and then wait for another BSOD.

Download Bluescreenview (http://www.nirsoft.net/utils/blue_screen_view.html). It's...
Dec 20, 2013
8
0
10,520
IMO any BSOD is bad so something is not right have you updated your BIOS and DRIVERS some times helps but i have NEVER had a prime 95 worker fail ever so i dont no whats happening there

this helped me even if you think you know it all there may be somthing u missed
3ed gen
http://www.youtube.com/watch?v=UCIWTX-jy9A
4th gen
http://www.youtube.com/watch?v=0CHs5_TdpXE

good luck hope u get it fixed soon :)

ps i know is a 4th gen vid but all the same thing ish :p
 

md1032

Distinguished
Dec 31, 2007
297
0
18,860
My procedure goes something like this:

1) IBT (Intel Burn Test, Prime95+ pseudo competitor) for 10 passes on "Very High" with max threads enabled. Ensure that it yields a maximum temperature >=10°C below thermal throttle limit (eg max temp <=95°C for Haswell, where thermal limit = 105°C). You will get lots of BSOD's during this test initially and get yourself a ballpark voltage.
2) Use the computer and wait for a BSOD. If my OC fails, I increase the voltage again by 0.005 V. It is not uncommon to have smooth sailing for a few months and then randomly get another BSOD. Simply increase the voltage and repeat step #1 again, and then wait for another BSOD.

Download Bluescreenview (http://www.nirsoft.net/utils/blue_screen_view.html). It's an excellent program that will go into your minidump files for you and place the information into a nice itemized list that is easy to read. If you see consistent errors on things like ntoskrnl.exe and hal.dll, you're OK...it's just your overclock failing. If you see completely random bluescreens on completely random processes, you have a memory problem and need to troubleshoot that using the motherboard's timing and voltage settings and Memtest.

It took me months to get a stable OC with my new system. I initially posted a stable OC at 4.4 Ghz, 1.260 V. A couple months later, I'm at 1.270 V. And by the way, load has almost nothing to do with when you get a BSOD. Most of the time that I got BSOD's during initial testing, it was doing something mundane like opening Chrome. Your CPU's simply not getting enough voltage to prevent errors, that's all.
 
Solution

SkruDe

Distinguished
Dec 30, 2012
189
12
18,685
I failed at 3 Hours of Prime95 Blend at 3 hours with 1.410 Vcore
I tried again with 1.415 Vcore and failed at the exact same time, 3 hours.

Jumped up to 1.420 Vcore now, but haven't ran Prime95.

@md1032: You're voltage at that frequency is making me jealous. Quite low. I feel like I'm pretty high, yet failed twice at 3 hours Prime with 1.410 and 1.415. Using 1.420 right now, doing all kinds of stuff that isn't Prime and been good so far.
 

md1032

Distinguished
Dec 31, 2007
297
0
18,860


Even scarier, I've seen folks on these forums with 4670k's stable at 1.22 V @ 4.4 Ghz. Amazing how variable these CPU's can be! I've seen a lot of these CPU's on ebay. It makes me wonder how many people order three and then sell the two worst performers on ebay.

That said, your voltage sounds high to me. Do you have one of those motherboards that uses "dynamic" or "adaptive" rather than fixed voltages? If so, you may want to look into setting a fixed voltage, which is the only option with my Asrock Z87 motherboard. Theoretically, there is a thermal disadvantage to using fixed versus dynamic, but I would rather have my CPU ready to "take a hit" at all times.