Prime95 help

[mrwil]

Hi well i just oc my cpu to 4ghz i was wondering how can i tell if its stable ? i got a asrock z68 extreme4 gen 3 i5 2500k cpu amd 6850 im using a evo 212 cpu cooler i did a fast test on prime95 and this is what i got
[Tue Feb 07 00:01:57 2012]
Compare your results to other computers at http://www.mersenne.org/report_benchmarks
Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
CPU speed: 3937.99 MHz, 4 cores
CPU features: Prefetch, MMX, SSE, SSE2, SSE4, AVX
L1 cache size: 32 KB
L2 cache size: 256 KB, L3 cache size: 6 MB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
TLBS: 64
Prime95 64-bit version 26.6, RdtscTiming=1
Best time for 768K FFT length: 6.590 ms., avg: 6.897 ms.
Best time for 896K FFT length: 9.515 ms., avg: 9.870 ms.
Best time for 1024K FFT length: 8.872 ms., avg: 9.341 ms.
Best time for 1280K FFT length: 11.401 ms., avg: 11.762 ms.
Best time for 1536K FFT length: 13.941 ms., avg: 14.322 ms.
Best time for 1792K FFT length: 17.048 ms., avg: 17.356 ms.
Best time for 2048K FFT length: 18.787 ms., avg: 19.387 ms.
Best time for 2560K FFT length: 23.926 ms., avg: 25.428 ms.
Best time for 3072K FFT length: 29.283 ms., avg: 29.800 ms.
Best time for 3584K FFT length: 35.677 ms., avg: 36.166 ms.
Best time for 4096K FFT length: 39.651 ms., avg: 39.824 ms.
Best time for 5120K FFT length: 51.154 ms., avg: 51.482 ms.
Best time for 6144K FFT length: 63.296 ms., avg: 63.850 ms.
Best time for 7168K FFT length: 79.193 ms., avg: 79.978 ms.
Best time for 8192K FFT length: 85.472 ms., avg: 85.945 ms.
Timing FFTs using 2 threads.
Best time for 768K FFT length: 3.469 ms., avg: 3.555 ms.
Best time for 896K FFT length: 4.937 ms., avg: 5.350 ms.
Best time for 1024K FFT length: 4.676 ms., avg: 4.786 ms.
Best time for 1280K FFT length: 5.996 ms., avg: 6.177 ms.
Best time for 1536K FFT length: 7.175 ms., avg: 7.850 ms.
Best time for 1792K FFT length: 8.806 ms., avg: 9.026 ms.
Best time for 2048K FFT length: 9.663 ms., avg: 9.919 ms.
Best time for 2560K FFT length: 12.331 ms., avg: 12.572 ms.
Best time for 3072K FFT length: 15.001 ms., avg: 15.315 ms.
Best time for 3584K FFT length: 18.327 ms., avg: 18.563 ms.
Best time for 4096K FFT length: 20.060 ms., avg: 21.020 ms.
Best time for 5120K FFT length: 25.962 ms., avg: 26.317 ms.
Best time for 6144K FFT length: 32.008 ms., avg: 32.511 ms.
Best time for 7168K FFT length: 41.148 ms., avg: 41.367 ms.
Best time for 8192K FFT length: 43.230 ms., avg: 43.829 ms.
Timing FFTs using 3 threads.
Best time for 768K FFT length: 2.388 ms., avg: 2.456 ms.
Best time for 896K FFT length: 3.450 ms., avg: 3.605 ms.
Best time for 1024K FFT length: 3.233 ms., avg: 3.301 ms.
Best time for 1280K FFT length: 4.107 ms., avg: 4.592 ms.
Best time for 1536K FFT length: 4.922 ms., avg: 5.027 ms.
Best time for 1792K FFT length: 6.038 ms., avg: 6.185 ms.
Best time for 2048K FFT length: 6.669 ms., avg: 6.865 ms.
Best time for 2560K FFT length: 8.433 ms., avg: 8.611 ms.
Best time for 3072K FFT length: 10.242 ms., avg: 10.430 ms.
Best time for 3584K FFT length: 12.471 ms., avg: 12.804 ms.
Best time for 4096K FFT length: 13.756 ms., avg: 14.118 ms.
Best time for 5120K FFT length: 17.710 ms., avg: 17.936 ms.
Best time for 6144K FFT length: 21.694 ms., avg: 22.041 ms.
Best time for 7168K FFT length: 29.306 ms., avg: 29.985 ms.
Best time for 8192K FFT length: 29.413 ms., avg: 29.826 ms.
Timing FFTs using 4 threads.
Best time for 768K FFT length: 2.022 ms., avg: 2.098 ms.
Best time for 896K FFT length: 2.700 ms., avg: 2.776 ms.
Best time for 1024K FFT length: 2.742 ms., avg: 2.840 ms.
Best time for 1280K FFT length: 3.178 ms., avg: 3.783 ms.
Best time for 1536K FFT length: 3.818 ms., avg: 3.967 ms.
Best time for 1792K FFT length: 4.689 ms., avg: 4.823 ms.
Best time for 2048K FFT length: 5.180 ms., avg: 5.285 ms.
Best time for 2560K FFT length: 6.498 ms., avg: 6.718 ms.
Best time for 3072K FFT length: 7.973 ms., avg: 8.222 ms.
Best time for 3584K FFT length: 9.580 ms., avg: 9.858 ms.
Best time for 4096K FFT length: 10.612 ms., avg: 10.860 ms.
Best time for 5120K FFT length: 13.810 ms., avg: 14.019 ms.
Best time for 6144K FFT length: 16.817 ms., avg: 17.164 ms.
Best time for 7168K FFT length: 25.217 ms., avg: 25.662 ms.
Best time for 8192K FFT length: 22.626 ms., avg: 23.020 ms.
Best time for 61 bit trial factors: 1.932 ms.
Best time for 62 bit trial factors: 1.955 ms.
Best time for 63 bit trial factors: 2.202 ms.
Best time for 64 bit trial factors: 2.277 ms.
Best time for 65 bit trial factors: 2.685 ms.
Best time for 66 bit trial factors: 3.161 ms.
Best time for 67 bit trial factors: 3.127 ms.
Best time for 75 bit trial factors: 3.042 ms.
Best time for 76 bit trial factors: 3.040 ms.
Best time for 77 bit trial factors: 3.042 ms.

 

[festerovic]

Do the blend or the "memory intensive" test (not sure what its named) You want it to be 24 hour stable if you want it to actually be 24 hour stable when you use it. FYI, prime will tell you when it fails per core. I dont think the numbers really mean ish unless you are concerned about crunching prime numbers.

 

[mrwil]

so i will let prime95 run about 8hrs so i can sleep how will i know if it fails?

 

[mrwil]

and does it matter if temp goes two high when i'm using prime95 some times it gets to 70-9xC? so does it matter if i run it for 8hrs

 

[slicedtoad]

If it crashed (read: bsod or freezes) or gives you an error message, it failed. Otherwise it's stable.

As festerovic said, blend for 24 hours if you want to make sure it's 100% stable. If you don't care that there's a small chance it might crash, run it for less time (it's debatable how healthy long prime95 sessions are).

Also do 20 minutes of small ffts to get max temperature. If its over 80C after 20 min of small ffts, it's too hot. Though at 4ghz and that cooler, you should have no problem keeping it under 70C.

edit: what's your voltage? those temps are too high for a 4GHz oc. Prime won't kill it overnight though.

 

[festerovic]

You shouldnt have to use voltage higher than 1.30 volts most of the time.

 

[mrwil]

Clock BCLk/pcie frequen 100.00mhz, cpu ration x40.0, gt frequency 1100mhz voltage for all of the valtage of w.e this are
Cpu voltage offset +0V
Dram valtage 1.500v
pch valtage 1.059
vtt valtage 1.051v
cpu pll valtage 1.832v
vccsa vaktage 0.925v
igpu valtage offset 0 mV
thats what it shows on my asrock extreme tuning utility didn't want to restart pc and yea the ram i'm using is a cosair vengeance 4x2* stick

 

[slicedtoad]

There are some excellent ocing guides here, use them to get the lowest voltage possible.
basically, reduce the voltage in small steps while testing in prime for 5 minutes until the voltage is too low and it crashes. then up the voltage a bit and test overnight.

 

[slicedtoad]

does that say 1.832v??? download cpuz and send the voltage from that.

First though, restart the computer and make sure the core cpu voltage is not above 1.4 at the most. if it is at 1.8, u could be seriously (likely are) damaging the cpu.

edit: nvm, cpu pll valtage is not core voltage. give us your cpuz reading with and wihtout furmark running.

 

[mrwil]

k downloaded its shows
technology 32mm core valtage 1.176v ran prime95 really fast so the cpu to go to 4hz and the valtage went to 1.2v max

 

[mrwil]

and no the temps are not going over 5xC now its stable at 5x before it went to 8x but i did a few changes

 

[mrwil]

btw idk wat's furmark nvm i download it o,owhat you want me to do with it i ran it 1min i think it was and the gpu didn't go over 70C it got score 5690 o3marks,fps min 81,fps max 95,time60000ms,res 1290x1024/msaa ox rendere:amd redeon hd 6800 series aka 6850 ,active gpu1 and cpu speed 3.3mhz but its really 4mhz in cpuz

 

[jsc]

Do the blend or the "memory intensive" test (not sure what its named) You want it to be 24 hour stable if you want it to actually be 24 hour stable when you use it. FYI, prime will tell you when it fails per core. I dont think the numbers really mean ish unless you are concerned about crunching prime numbers.

Either the blend or large fft's test will do that. I prefer the large fft's test.

and does it matter if temp goes two high when i'm using prime95 some times it gets to 70-9xC? so does it matter if i run it for 8hrs

20 minutes of P95 small fft's will drive CPU temps to max. If you exceed 70 C, your are running too hot.

Learn to use the BIOS for overclocking. Windows utilities tend to unnecessarily overvolt which drives the temps too high.

We have had all sorts of discussions about how long to run P95 - 2, 3, 4, 6, 8, 12, or 24 hours. It is up to you to decide, "OK. It is stable enough."

I am one of relatively few who has decided that 24 hours is enough.

 

[mrwil]

k its bin running for about 20min and im using cpuz and speedfan and it shows on cpuz well nothing much just core speed 4000.5 mhz core valtage is 1.2 and yea i did use bios for this so it wont go over 1.2v i just did what this guy said on bios http://www.tomshardware.com/forum/266189-29-sandy-bridge-series-ocing-cores-guide, all those setting i have atm and yea in those 2xmin running it the cpu is at 45C the core 0 is at 56C hasnt gone to 60 and idk why but the gpu is always 4x-50 and im not even playing games i have'nt even touched gpu settings.

 

[slicedtoad]

btw idk wat's furmark nvm i download it o,owhat you want me to do with it i ran it 1min i think it was and the gpu didn't go over 70C it got score 5690 o3marks,fps min 81,fps max 95,time60000ms,res 1290x1024/msaa ox rendere:amd redeon hd 6800 series aka 6850 ,active gpu1 and cpu speed 3.3mhz but its really 4mhz in cpuz

i meant prime, not furmark, sorry bout that. furmark is equivalent (kinda) to prime95 but for gpus.
Glad you cpu temps are down.

Don't worry too much about the gpu if you're not over clocking it. But if you want the temps to go down, improve airflow to your case. To see how restricted your case is, remove the side panel and compare those gpu temps to having the side panel on.