Sign in with
Sign up | Sign in
Your question
Solved

Prime95 Errors

Last response: in Overclocking
Share
April 26, 2012 10:29:49 PM

I seem to get several Prime95 errors when I run the In-Place Large FFT's Test. I have an Intel Core i7 2600k. These are two errors that sprung up within 15 minutes:


[Apr 26 17:45] Worker starting
[Apr 26 17:45] Setting affinity to run worker on logical CPU #4
[Apr 26 17:45] Beginning a continuous self-test to check your computer.
[Apr 26 17:45] Please read stress.txt. Choose Test/Stop to end this test.
[Apr 26 17:45] Test 1, 4000 Lucas-Lehmer iterations of M19922945 using FFT length 1024K.
[Apr 26 17:46] Test 2, 4000 Lucas-Lehmer iterations of M19922943 using FFT length 1024K.
[Apr 26 17:48] Test 3, 4000 Lucas-Lehmer iterations of M19374367 using FFT length 1024K.
[Apr 26 17:49] Test 4, 4000 Lucas-Lehmer iterations of M19174369 using FFT length 1024K.
[Apr 26 17:51] Test 5, 4000 Lucas-Lehmer iterations of M18874369 using FFT length 1024K.
[Apr 26 17:52] Test 6, 4000 Lucas-Lehmer iterations of M18874367 using FFT length 1024K.
[Apr 26 17:54] Test 7, 4000 Lucas-Lehmer iterations of M18474367 using FFT length 1024K.
[Apr 26 17:55] Test 8, 4000 Lucas-Lehmer iterations of M18274367 using FFT length 1024K.
[Apr 26 17:57] Test 9, 4000 Lucas-Lehmer iterations of M18274369 using FFT length 1024K.
[Apr 26 17:58] Test 10, 4000 Lucas-Lehmer iterations of M18074369 using FFT length 1024K.
[Apr 26 18:00] Self-test 1024K passed!
[Apr 26 18:00] Test 1, 4500 Lucas-Lehmer iterations of M17432577 using FFT length 896K.
[Apr 26 18:00] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Apr 26 18:00] Hardware failure detected, consult stress.txt file.
[Apr 26 18:00] Torture Test completed 10 tests in 15 minutes - 1 errors, 0 warnings.
[Apr 26 18:00] Worker stopped.

and:


[Apr 26 17:45] Worker starting
[Apr 26 17:45] Setting affinity to run worker on logical CPU #6
[Apr 26 17:45] Beginning a continuous self-test to check your computer.
[Apr 26 17:45] Please read stress.txt. Choose Test/Stop to end this test.
[Apr 26 17:45] Test 1, 4000 Lucas-Lehmer iterations of M19922945 using FFT length 1024K.
[Apr 26 17:46] Test 2, 4000 Lucas-Lehmer iterations of M19922943 using FFT length 1024K.
[Apr 26 17:48] Test 3, 4000 Lucas-Lehmer iterations of M19374367 using FFT length 1024K.
[Apr 26 17:49] Test 4, 4000 Lucas-Lehmer iterations of M19174369 using FFT length 1024K.
[Apr 26 17:51] Test 5, 4000 Lucas-Lehmer iterations of M18874369 using FFT length 1024K.
[Apr 26 17:52] Test 6, 4000 Lucas-Lehmer iterations of M18874367 using FFT length 1024K.
[Apr 26 17:54] Test 7, 4000 Lucas-Lehmer iterations of M18474367 using FFT length 1024K.
[Apr 26 17:55] Test 8, 4000 Lucas-Lehmer iterations of M18274367 using FFT length 1024K.
[Apr 26 17:57] Test 9, 4000 Lucas-Lehmer iterations of M18274369 using FFT length 1024K.
[Apr 26 17:58] Test 10, 4000 Lucas-Lehmer iterations of M18074369 using FFT length 1024K.
[Apr 26 18:00] Self-test 1024K passed!
[Apr 26 18:00] Test 1, 4500 Lucas-Lehmer iterations of M17432577 using FFT length 896K.
[Apr 26 18:00] FATAL ERROR: Rounding was 0.5, expected less than 0.4
[Apr 26 18:00] Hardware failure detected, consult stress.txt file.
[Apr 26 18:00] Torture Test completed 10 tests in 15 minutes - 1 errors, 0 warnings.
[Apr 26 18:00] Worker stopped.

If any of you could help me solve this problem, it would be appreciated! Also, I am VERY new to overclocking so I'm not experienced with voltages and such. Thanks in advance!

More about : prime95 errors

April 27, 2012 3:34:32 AM

Sounds like a RAM error. Run memtest86.
m
0
l
April 28, 2012 12:43:23 AM

When I run memtest86 I get a crapload of errors. I tried switching out each ram stick and still get hundreds of errors
m
0
l
Related resources

Best solution

a b à CPUs
April 28, 2012 12:54:27 AM

Can you replace the memory sticks you have? If they're the same brand, you might have stumbled upon a bad batch.
Share
a b à CPUs
a b K Overclocking
April 28, 2012 1:10:30 AM

Run a baseline (stock) prime95 test to make sure it is not just a unstable OC..If the baseline errors on you then run memtest at stock settings if your getting errors at stock settings then the RAM modules are bad...If no errors then its a bad OC
m
0
l
April 28, 2012 1:13:00 AM

lowjack989 said:
Run a baseline (stock) prime95 test to make sure it is not just a unstable OC..If the baseline errors on you then run memtest at stock settings if your getting errors at stock settings then the RAM modules are bad...If no errors then its a bad OC

Stock Prime95 test? Which setting would that be?
m
0
l
a b à CPUs
a b K Overclocking
April 28, 2012 1:19:59 AM

Stock settings you know default settings in BIOS for the CPU, Memory, etc.....

BTW...When using prime 95 ...start off with small FFT's for at least 2 hours, then run Blend for at least 2 hours, and then run the hardcore Large FFT's for at least 2 hours.
m
0
l
a c 172 à CPUs
a c 197 K Overclocking
April 28, 2012 5:47:25 PM

Yep. Small fft's primarily stresses the CPU.

As you work through the tests in the order that lowjack suggests, you are increasingly stressing the memory.

That is one of the things that I like about P95. Any test that fails gives you an indication of what is wrong.

Something else to try:
If your stock settings test good, leave your memory at DDR3-1333 speeds when you overclock the CPU and see what happens.
m
0
l
May 14, 2012 11:34:20 PM

Best answer selected by MoltenCore7.
m
0
l
!