Sorry in advance

sticks · 2012-01-03, 22:36

I would like to apologise in advance if this has been answered before (I'm sure it has) but I have had the worse day at work ever only to come home from m y almost 20hour shift to find mutiple errors in my prime test.

I have a pre bundle overclocked system that I bought from OC'ers its 2500k chip

I have run memtest and all is fine

this is the errors I get , wall of text inc sorry :(

WINDOW 1

[Jan 2 20:53] Worker starting
[Jan 2 20:53] Setting affinity to run worker on logical CPU #1
[Jan 2 20:53] No work to do at the present time. Waiting.
[Jan 2 20:58] Resuming.
[Jan 2 20:58] Worker stopped.
[Jan 2 20:58] Worker starting
[Jan 2 20:58] Setting affinity to run worker on logical CPU #1
[Jan 2 20:58] Beginning a continuous self-test to check your computer.
[Jan 2 20:58] Please read stress.txt. Choose Test/Stop to end this test.
[Jan 2 20:58] Test 1, 6500 Lucas-Lehmer iterations of M12451841 using Pentium4 type-2 FFT length 640K, Pass1=640, Pass2=1K.

[Jan 3 04:12] Test 6, 1200 Lucas-Lehmer iterations of M53477375 using Core2 type-3 FFT length 3M, Pass1=1K, Pass2=3K.
[Jan 3 04:12] FATAL ERROR: Rounding was 0.4921875, expected less than 0.4
[Jan 3 04:12] Hardware failure detected, consult stress.txt file.
[Jan 3 04:12] Torture Test completed 601 tests in 7 hours, 14 minutes - 1 errors, 0 warnings.
[Jan 3 04:12] Worker stopped.

WINDOW 2

[Jan 2 20:53] Waiting 5 seconds to stagger worker starts.
[Jan 2 20:53] Worker starting
[Jan 2 20:53] Setting affinity to run worker on logical CPU #2
[Jan 2 20:53] No work to do at the present time. Waiting.
[Jan 2 20:58] Resuming.
[Jan 2 20:58] Worker stopped.
[Jan 2 20:58] Worker starting
[Jan 2 20:58] Setting affinity to run worker on logical CPU #2
[Jan 2 20:58] Beginning a continuous self-test to check your computer.
[Jan 2 20:58] Please read stress.txt. Choose Test/Stop to end this test.
[Jan 2 20:58] Test 1, 6500 Lucas-Lehmer iterations of M12451841 using Pentium4 type-2 FFT length 640K, Pass1=640, Pass2=1K.
[Jan 2 20:59] Test 2, 6500 Lucas-Lehmer iterations of M12451839 using Pentium4 type-3 FFT length 640K, Pass1=640, Pass2=1K.

[Jan 2 22:43] Test 18, 5300 Lucas-Lehmer iterations of M14155775 using Core2 type-3 FFT length 960K, Pass1=256, Pass2=3840.
[Jan 2 22:43] FATAL ERROR: Rounding was 0.4998989105, expected less than 0.4
[Jan 2 22:43] Hardware failure detected, consult stress.txt file.
[Jan 2 22:43] Torture Test completed 139 tests in 1 hour, 45 minutes - 1 errors, 0 warnings.
[Jan 2 22:43] Worker stopped.

WINDOW 3

[Jan 3 02:06] Test 3, 1900 Lucas-Lehmer iterations of M38251583 using Core2 type-2 FFT length 2M, Pass1=1K, Pass2=2K.
[Jan 3 02:07] Test 4, 1900 Lucas-Lehmer iterations of M37748737 using Core2 type-3 FFT length 2M, Pass1=1K, Pass2=2K.

[Jan 3 13:12] Test 7, 1200 Lucas-Lehmer iterations of M52331647 using Core2 type-2 FFT length 3200K, Pass1=640, Pass2=5K.
[Jan 3 13:13] FATAL ERROR: Rounding was 0.4993286133, expected less than 0.4
[Jan 3 13:13] Hardware failure detected, consult stress.txt file.
[Jan 3 13:13] Torture Test completed 1381 tests in 16 hours, 14 minutes - 1 errors, 0 warnings.
[Jan 3 13:13] Worker stopped.

the last window 4 is fine

OC'er have asked me to remove a battery? on the MB that I am reluctant to do.

I'm new to these kind of test so if anyone could point me in the correct position I would be very greatful.

Batalov · 2012-01-04, 00:23

memtest at its hardest only behaves like that last alive 4th thread that you still have running - it bangs on the memory using 1 core. So the result is consistent with memtest: a 1-threaded application survives long in both. However, the 4-threaded test overstresses and after the errors the threads shut down one by one. So, it is over-optimistically OC'd: sort of works but then fails under real load. You are right to try to wind it down.

Re: battery. Depending on the motherboard, there's usually a pair of naked pins not far from the battery; if they are there, you can (first, power off system and only then) short these pins with a key or a knife for a second - the effect will be the same as removing the battery. Try "Load Default Settings" in BIOS as well. (Enter BIOS settings by using DEL or F1, you know. Find the m/b manual on the web by googling its exact name - it's a good thing to have at hand.)

Dubslow · 2012-01-04, 00:30

Well, I personally can't tell you what exactly might cause the errors, but others are probably going to ask what frequency is it OC'd to, what temperatures does it reach while running the stress tests (if you don't have a monitoring program, try Googling HWMonitor), and what cooling solution came with it. A link to the page on the seller's site should have this info. (On a 2500K, temps above 80-85C are worrisome. Above 70C is definitely very hot, but not as prone to errors.)

davieddy · 2012-01-04, 06:01

Landlady's looking for front rent.
She'll be lucky to get any back rent
David

sticks · 2012-01-04, 06:49

thanks all for the fast reponse, my voltage through the test was 1.352 not sure of core temp what would be a good program for me so see core temps as I do not remember seeing it listed on cpu-z

thanks again

Dubslow · 2012-01-04, 06:55

HWMonitor (as I already said)
http://www.cpuid.com/softwares/hwmonitor.html

sticks · 2012-01-04, 06:58

Quote:

Originally Posted by Dubslow

HWMonitor (as I already said)
http://www.cpuid.com/softwares/hwmonitor.html

sorry Dubslow just opened me eyes :)

EDIT: And thank you :)

2012-01-04, 06:01	#4
davieddy "Lucan" Dec 2006 England 2×3×13×83 Posts	Sorry in arrears. Landlady's looking for front rent. She'll be lucky to get any back rent David Last fiddled with by davieddy on 2012-01-04 at 06:08

2012-01-04, 06:55	#6
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3·29·83 Posts	HWMonitor (as I already said) http://www.cpuid.com/softwares/hwmonitor.html Last fiddled with by Dubslow on 2012-01-04 at 06:55

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Reserving numbers in advance	Raman	Cunningham Tables	32	2010-02-17 20:13

2012-01-03, 22:36	#1
sticks Jan 2012 3₁₆ Posts	Sorry in advance I would like to apologise in advance if this has been answered before (I'm sure it has) but I have had the worse day at work ever only to come home from m y almost 20hour shift to find mutiple errors in my prime test. I have a pre bundle overclocked system that I bought from OC'ers its 2500k chip I have run memtest and all is fine this is the errors I get , wall of text inc sorry :( WINDOW 1 [Jan 2 20:53] Worker starting [Jan 2 20:53] Setting affinity to run worker on logical CPU #1 [Jan 2 20:53] No work to do at the present time. Waiting. [Jan 2 20:58] Resuming. [Jan 2 20:58] Worker stopped. [Jan 2 20:58] Worker starting [Jan 2 20:58] Setting affinity to run worker on logical CPU #1 [Jan 2 20:58] Beginning a continuous self-test to check your computer. [Jan 2 20:58] Please read stress.txt. Choose Test/Stop to end this test. [Jan 2 20:58] Test 1, 6500 Lucas-Lehmer iterations of M12451841 using Pentium4 type-2 FFT length 640K, Pass1=640, Pass2=1K. [Jan 3 04:12] Test 6, 1200 Lucas-Lehmer iterations of M53477375 using Core2 type-3 FFT length 3M, Pass1=1K, Pass2=3K. [Jan 3 04:12] FATAL ERROR: Rounding was 0.4921875, expected less than 0.4 [Jan 3 04:12] Hardware failure detected, consult stress.txt file. [Jan 3 04:12] Torture Test completed 601 tests in 7 hours, 14 minutes - 1 errors, 0 warnings. [Jan 3 04:12] Worker stopped. WINDOW 2 [Jan 2 20:53] Waiting 5 seconds to stagger worker starts. [Jan 2 20:53] Worker starting [Jan 2 20:53] Setting affinity to run worker on logical CPU #2 [Jan 2 20:53] No work to do at the present time. Waiting. [Jan 2 20:58] Resuming. [Jan 2 20:58] Worker stopped. [Jan 2 20:58] Worker starting [Jan 2 20:58] Setting affinity to run worker on logical CPU #2 [Jan 2 20:58] Beginning a continuous self-test to check your computer. [Jan 2 20:58] Please read stress.txt. Choose Test/Stop to end this test. [Jan 2 20:58] Test 1, 6500 Lucas-Lehmer iterations of M12451841 using Pentium4 type-2 FFT length 640K, Pass1=640, Pass2=1K. [Jan 2 20:59] Test 2, 6500 Lucas-Lehmer iterations of M12451839 using Pentium4 type-3 FFT length 640K, Pass1=640, Pass2=1K. [Jan 2 22:43] Test 18, 5300 Lucas-Lehmer iterations of M14155775 using Core2 type-3 FFT length 960K, Pass1=256, Pass2=3840. [Jan 2 22:43] FATAL ERROR: Rounding was 0.4998989105, expected less than 0.4 [Jan 2 22:43] Hardware failure detected, consult stress.txt file. [Jan 2 22:43] Torture Test completed 139 tests in 1 hour, 45 minutes - 1 errors, 0 warnings. [Jan 2 22:43] Worker stopped. WINDOW 3 [Jan 3 02:06] Test 3, 1900 Lucas-Lehmer iterations of M38251583 using Core2 type-2 FFT length 2M, Pass1=1K, Pass2=2K. [Jan 3 02:07] Test 4, 1900 Lucas-Lehmer iterations of M37748737 using Core2 type-3 FFT length 2M, Pass1=1K, Pass2=2K. [Jan 3 13:12] Test 7, 1200 Lucas-Lehmer iterations of M52331647 using Core2 type-2 FFT length 3200K, Pass1=640, Pass2=5K. [Jan 3 13:13] FATAL ERROR: Rounding was 0.4993286133, expected less than 0.4 [Jan 3 13:13] Hardware failure detected, consult stress.txt file. [Jan 3 13:13] Torture Test completed 1381 tests in 16 hours, 14 minutes - 1 errors, 0 warnings. [Jan 3 13:13] Worker stopped. the last window 4 is fine OC'er have asked me to remove a battery? on the MB that I am reluctant to do. I'm new to these kind of test so if anyone could point me in the correct position I would be very greatful.

2012-01-04, 00:23	#2
Batalov "Serge" Mar 2008 Phi(4,2^7658614+1)/2 9488₁₀ Posts	memtest at its hardest only behaves like that last alive 4th thread that you still have running - it bangs on the memory using 1 core. So the result is consistent with memtest: a 1-threaded application survives long in both. However, the 4-threaded test overstresses and after the errors the threads shut down one by one. So, it is over-optimistically OC'd: sort of works but then fails under real load. You are right to try to wind it down. Re: battery. Depending on the motherboard, there's usually a pair of naked pins not far from the battery; if they are there, you can (first, power off system and only then) short these pins with a key or a knife for a second - the effect will be the same as removing the battery. Try "Load Default Settings" in BIOS as well. (Enter BIOS settings by using DEL or F1, you know. Find the m/b manual on the web by googling its exact name - it's a good thing to have at hand.) Last fiddled with by Batalov on 2012-01-04 at 00:30

2012-01-04, 00:30	#3
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3·29·83 Posts	Well, I personally can't tell you what exactly might cause the errors, but others are probably going to ask what frequency is it OC'd to, what temperatures does it reach while running the stress tests (if you don't have a monitoring program, try Googling HWMonitor), and what cooling solution came with it. A link to the page on the seller's site should have this info. (On a 2500K, temps above 80-85C are worrisome. Above 70C is definitely very hot, but not as prone to errors.)

2012-01-04, 06:49	#5
sticks Jan 2012 11₂ Posts	thanks all for the fast reponse, my voltage through the test was 1.352 not sure of core temp what would be a good program for me so see core temps as I do not remember seeing it listed on cpu-z thanks again