Wth... orthos 2mins error already?

[penguin1]

i havent even started ocing.. still stock

anyone knows what error this is?

1st error:

"Using CPU #1
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 2 minutes 38 seconds - 1 errors, 0 warnings.
Execution halted.''

 

[zarooch]

WTF? read stress.txt?

 

[penguin1]

WTF? read stress.txt?

where is it located??

 

[zarooch]

WTF? read stress.txt?

where is it located??

check My Documents, check the installation directory of the program. Also check %temp% . . . if not found then Search in C: Drive!

 

[penguin1]

ya i did. but all i can find is this file called, splog.txt

and in it is,

Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1790 Time: 15
CPU: 2400MHz FSB: 266MHz [266MHz x 9.0 est.]
CPU: 2400MHz FSB: 266MHz [266MHz x 9.0 est.]
5/7/2007 9:27 PM
Launching 2 threads...
1:Using CPU #0
2:Using CPU #1
1:Beginning a continuous self-test to check your computer.
2:Beginning a continuous self-test to check your computer.
1ress Stop to end this test.
2ress Stop to end this test.
1:Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
2:Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
2:FATAL ERROR: Rounding was 0.5, expected less than 0.4
2:Hardware failure detected, consult stress.txt file.
2:Torture Test ran 2 minutes 38 seconds - 1 errors, 0 warnings.
2:Execution halted.

1:Torture Test ran 2 minutes 38 seconds - 0 errors, 0 warnings.
1:Execution halted.

Type: Small FFTs - stress CPU Min: 8 Max: 8 InPlace: Yes Mem: 8 Time: 15
CPU: 2400MHz FSB: 266MHz [266MHz x 9.0 est.]
CPU: 2400MHz FSB: 266MHz [266MHz x 9.0 est.]
5/7/2007 9:35 PM
Launching 2 threads...
1:Using CPU #0
2:Using CPU #1
1:Beginning a continuous self-test to check your computer.
2:Beginning a continuous self-test to check your computer.
1ress Stop to end this test.
2ress Stop to end this test.
1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
1:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
2:Test 4, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
1:Test 4, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
2:Test 5, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
1:Test 5, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
2:Test 6, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
1:Test 6, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
2:Test 7, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
1:Test 7, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
2:Test 8, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
1:Test 8, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
2:Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
1:Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
2:Self-test 8K passed!
2:Test 1, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
1:Self-test 8K passed!
1:Test 1, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
2:Test 2, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.

 

[zarooch]

hmm... weird. Anyways, try changing process affinity to core 1 and run some programs, maybe compile something (gcc).

 

[penguin1]

small FFTs - Stress CPU an hour no cpu errors so far.. u think it could be the rams?

 

[WR]

Yes, RAM most probable cause of crash...

Try Large, in-place FFTs as a diagnostic. I assume you're running a C2D E6600, and large FFTs stress the L2 cache on the CPU, usually the first thing to go when the CPU is unstable.

If that passes 5min, then you need to troubleshoot the RAM sticks.

 

[penguin1]

so what now?

 

[dasickninja]

Run Memtest86 to see for sure if its the RAM or run just a CPU affinity test.

 

[penguin1]

will do

 

[WR]

Run Memtest86 to see for sure if its the RAM or run just a CPU affinity test.

I don't think he needs to worry about affinity because blend took 3 hours to fail last time. Perhaps running CoreTemp after 10+ minutes of blend would help us make sure the CPU isn't on the verge of overheating.

Small FFTs cleared the CPU core from being a likely problem source.

Large FFTs (5-10 min) would rule out the CPU L2, which would otherwise manifest as a memory error.

I agree, memtest has a high chance of finding the error.