Free Weekly Tech Newsletter

Captn · 04-01-2007, 06:11 PM

I ran Prime95 ver. 24.14 on my E6400 & after 2hours 8min's i get this error

Test 1, 7800 Lucas-Lehmer iterations of M9961473 using 512k FFT Length
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 2 hours 8 minutes - 1 errors, 0 warnings.
Execution halted.

My system Specs are:

E6400 @ 2.6 with Arctic Freezer 7 Pro
EVGA 8800GTX
EVGA 680i Motherboard
Corsair XMS2 2gig
SeaSonic M-12 700W PSU
Antec 900 Case
WD 320 x2

I play games everything runs great with CoreTemp & TAT my temps never get above 37 while running Prime95 Torture Test, my pc never crashed or anything it runs stable. I don't understand the error, maybe someone could shed some light for me? Thank you in advance.

Mr.Ferrari · 04-01-2007, 06:25 PM

Run Orthos instead of prime ----> http://sp2004.fre3.com/beta/beta2.htm

When you get this error, does the computer freeze or shutdown? I would try running it at stock speed and see what happens.

Captn · 04-01-2007, 06:30 PM

Quote:

Originally Posted by Mr.Ferrari

Run Orthos instead of prime ----> http://sp2004.fre3.com/beta/beta2.htm

When you get this error, does the computer freeze or shutdown? I would try running it at stock speed and see what happens.

No it doesnt freeze or crash or shutdown at all, just Prime95 Halts. It runs really good thats what i dont get about the Prime95 error.

Mr.Ferrari · 04-01-2007, 06:35 PM

I would put the CPU back at stock speed and try stress testing again.

And double check with Orthos as that is a more efficient prime stress test.

Captn · 04-01-2007, 07:29 PM

Running Orthos now with it overclocked see what happens.

Captn · 04-01-2007, 08:00 PM

Well i ran Orthos & for test i selected Blend and after 22min this is what i got:

Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1790 Time: 15
CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.]
CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.]
4/1/2007 8:27 PM
Launching 2 threads...
2:Using CPU #1
1:Using CPU #0
2:Beginning a continuous self-test to check your computer.
1:Beginning a continuous self-test to check your computer.
2:Press Stop to end this test.
1:Press 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:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
1:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
2:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
1:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
2:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
1:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
1:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
2:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
2:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
1:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
1:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length.
2:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length.
1:Self-test 1024K passed!
1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Self-test 1024K passed!
2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
1:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
2:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Maximum number of warnings exceeded.
2:Torture Test ran 22 minutes 11 seconds - 0 errors, 100 warnings.
2:Execution halted.

1:Torture Test ran 22 minutes 11 seconds - 0 errors, 0 warnings.
1:Execution halted.

System never crashed or lockedup or shutdown Orthos started beeping. Gonna set my cpu to default & run Orthos again.

Captn · 04-01-2007, 09:08 PM

I set my bios back to default & ran Orthos again:

Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1790 Time: 15
CPU: 2133MHz FSB: 266MHz [266MHz x 8.0 est.]
CPU: 2133MHz FSB: 266MHz [266MHz x 8.0 est.]
4/1/2007 9:17 PM
Launching 2 threads...
2:Using CPU #1
1:Using CPU #0
2:Beginning a continuous self-test to check your computer.
1:Beginning a continuous self-test to check your computer.
2:Press Stop to end this test.
1:Press 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:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
1:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
2:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
1:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
2:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
1:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
2:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
1:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
2:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
1:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
2:Self-test 1024K passed!
2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Self-test 1024K passed!
1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2: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:Self-test 8K passed!
2:Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length.
1:Self-test 8K passed!
1:Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length.
2:Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length.
1:Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length.
2:Test 3, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT length.
1:Test 3, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT length.
2:Test 4, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT length.
1:Test 4, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT length.
2:Test 5, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT length.
1:Test 5, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT length.
2:Test 6, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT length.
1:Test 6, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT length.
2:Test 7, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT length.
1:Test 7, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT length.
2:Test 8, 560000 Lucas-Lehmer iterations of M188415 using 10K FFT length.
1:Test 8, 560000 Lucas-Lehmer iterations of M188415 using 10K FFT length.
2:Self-test 10K passed!
2:Test 1, 4500 Lucas-Lehmer iterations of M17432577 using 896K FFT length.
1:Self-test 10K passed!
1:Test 1, 4500 Lucas-Lehmer iterations of M17432577 using 896K FFT length.
2:Torture Test ran 49 minutes 16 seconds - 0 errors, 0 warnings.
2:Execution halted.

1:Torture Test ran 49 minutes 16 seconds - 0 errors, 0 warnings.
1:Execution halted.

I stopped Orthos after 49min.

Mr.Ferrari · 04-01-2007, 09:57 PM

Cool, atleast we know that theres nothing wrong with your CPU.

Now before you push the clocks again, make sure you have your pci-e and pci bus's locked at 100mhz and 33mhz respectively if you already have not.

From here, you might've needed some more Vcore voltage. So raise it just a bit and see what happens. You can check your vcore via CPU-Z. And keep an eye on temperatures.

What is the brand/model of your ram sticks?

Captn · 04-01-2007, 10:02 PM

Corsair XMS2, PCI-E x16_1, MHz Auto 125. Are you familiar with the 680i Bios at all?

Burn · 04-01-2007, 10:36 PM

Corsair XMS2 5 5 5 12 ?

if its the same as me .. my mobo on auto mode put 1.8V on it. Stock voltage of this memory is 1.9V. I run them at 425Mhz at 1.9V. Check the voltage on your own sticks ...

Captn · 04-01-2007, 10:40 PM

Quote:

Originally Posted by Burn

Corsair XMS2 5 5 5 12 ?

if its the same as me .. my mobo on auto mode put 1.8V on it. Stock voltage of this memory is 1.9V. I run them at 425Mhz at 1.9V. Check the voltage on your own sticks ...

ok

Captn · 04-01-2007, 10:44 PM

Quote:

Originally Posted by Burn

Corsair XMS2 5 5 5 12 ?

if its the same as me .. my mobo on auto mode put 1.8V on it. Stock voltage of this memory is 1.9V. I run them at 425Mhz at 1.9V. Check the voltage on your own sticks ...

CPU-Z says Cas# Latency 5.0 Clocks
RAS# to CAS# Delay 5 clocks
RAS# Precharge 5 clocks
Cycle Time 18 Clocks
Bank Cycle time 22 Clocks
Command Rate 2T

Captn · 04-01-2007, 10:48 PM

THis is my memory http://www.newegg.com/Product/Produc...82E16820145590

Burn · 04-01-2007, 10:54 PM

yup , same as me...

You should see 12 as the cycle time instead of 18 to get what you paid for. You will have to put it manualy in the BIOS. Just make sure the voltage is 1.9V. Leave it there until you reach stability with your overclocking and then adjust the memory timing. Play it safe for now.

Captn · 04-01-2007, 10:54 PM

Ok cool, thank you.

Mr.Ferrari · 04-01-2007, 10:59 PM

Quote:

Originally Posted by Captn

Corsair XMS2, PCI-E x16_1, MHz Auto 125. Are you familiar with the 680i Bios at all?

Somewhat, i've been around Asus 680i bioses.

Alright set that manually to 100mhz and turn off linkboost if thats an option.

Your ram is definately not the weak point. I would however concentrate on your cpu overclock before tweaking memory timings.

Start raising the fsb slowly and add a bit of voltage. I.E .025v at a time until it becomes stable with that Prime/Orthos test.

Captn · 04-01-2007, 11:02 PM

Quote:

Originally Posted by Mr.Ferrari

Somewhat, i've been around Asus 680i bioses.

Alright set that manually to 100mhz and turn off linkboost if thats an option.

Your ram is definately not the weak point. I would however concentrate on your cpu overclock before tweaking memory timings.

Start raising the fsb slowly and add a bit of voltage. I.E .025v at a time until it becomes stable with that Prime/Orthos test.

Yea linkboost is on.

Captn · 04-02-2007, 12:15 AM

Is there an issue with the NEWEST CPU-Z? Its reading my Core speed @ 1953.1 MHz & my multipier @ x6 which is wrong in my bios its set at x8. Its telling me my Bus speed is 325.5 & FSB is 1302(Which is what i have it set at). But my multiplier is set at x8, odd. TAT says my CPU speed is 2.6...lol

I did set my memory @ 1.9v & its now reading my memory settings as 5,5,5, 12.

Is there another program other then CPU-Z that does the same thing?

Captn · 04-02-2007, 12:40 AM

Nevermind i figured it out here. http://forum.x86-secret.com/showthread.php?t=6806

Ok I fixed my voltage on my ram and set it at 1.9(which is default for my memory) & set my timings correct on my ram @ 5, 5, 5, 12 and re-ran Orthos heres what i got:

Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1790 Time: 15
CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.]
CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.]
4/2/2007 8:27 AM
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.
1:Press Stop to end this test.
2:Press 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:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
1:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
2:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
1:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
2:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
1:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
2:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
1:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
2:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
1:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
1:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length.
2:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length.
2:Self-test 1024K passed!
2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Self-test 1024K passed!
1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2: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, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length.
1:Self-test 8K passed!
1:Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length.
2:Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length.
1:Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length.
2:Test 3, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT length.
1:Test 3, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT length.
2:Test 4, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT length.
1:Test 4, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT length.
2:Test 5, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT length.
1:Test 5, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT length.
2:Test 6, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT length.
1:Test 6, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT length.
2:Test 7, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT length.
1:Test 7, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT length.
2:Test 8, 560000 Lucas-Lehmer iterations of M188415 using 10K FFT length.
1:Test 8, 560000 Lucas-Lehmer iterations of M188415 using 10K FFT length.
2:Test 9, 560000 Lucas-Lehmer iterations of M186369 using 10K FFT length.
1:Test 9, 560000 Lucas-Lehmer iterations of M186369 using 10K FFT length.
2:Self-test 10K passed!
2:Test 1, 4500 Lucas-Lehmer iterations of M17432577 using 896K FFT length.
1:Self-test 10K passed!
1:Test 1, 4500 Lucas-Lehmer iterations of M17432577 using 896K FFT length.
2:Test 2, 4500 Lucas-Lehmer iterations of M17432575 using 896K FFT length.
1:Test 2, 4500 Lucas-Lehmer iterations of M17432575 using 896K FFT length.
2:Test 3, 4500 Lucas-Lehmer iterations of M17115073 using 896K FFT length.
1:Test 3, 4500 Lucas-Lehmer iterations of M17115073 using 896K FFT length.
2:Test 4, 4500 Lucas-Lehmer iterations of M16815071 using 896K FFT length.
1:Test 4, 4500 Lucas-Lehmer iterations of M16815071 using 896K FFT length.
2:Test 5, 4500 Lucas-Lehmer iterations of M16515073 using 896K FFT length.
1:Test 5, 4500 Lucas-Lehmer iterations of M16515073 using 896K FFT length.
2:Test 6, 4500 Lucas-Lehmer iterations of M16515071 using 896K FFT length.
1:Test 6, 4500 Lucas-Lehmer iterations of M16515071 using 896K FFT length.
2:Test 7, 4500 Lucas-Lehmer iterations of M16297569 using 896K FFT length.
1:Test 7, 4500 Lucas-Lehmer iterations of M16297569 using 896K FFT length.
2:Self-test 896K passed!
2:Test 1, 5300 Lucas-Lehmer iterations of M14942209 using 768K FFT length.
1:Self-test 896K passed!
1:Test 1, 5300 Lucas-Lehmer iterations of M14942209 using 768K FFT length.
2:Test 2, 5300 Lucas-Lehmer iterations of M14942207 using 768K FFT length.
1:Test 2, 5300 Lucas-Lehmer iterations of M14942207 using 768K FFT length.
2:Test 3, 5300 Lucas-Lehmer iterations of M14155777 using 768K FFT length.
1:Test 3, 5300 Lucas-Lehmer iterations of M14155777 using 768K FFT length.
2:Test 4, 5300 Lucas-Lehmer iterations of M14155775 using 768K FFT length.
1:Test 4, 5300 Lucas-Lehmer iterations of M14155775 using 768K FFT length.
2:Test 5, 5300 Lucas-Lehmer iterations of M13969343 using 768K FFT length.
1:Test 5, 5300 Lucas-Lehmer iterations of M13969343 using 768K FFT length.
2:Test 6, 5300 Lucas-Lehmer iterations of M13669345 using 768K FFT length.
1:Test 6, 5300 Lucas-Lehmer iterations of M13669345 using 768K FFT length.
2:Test 7, 5300 Lucas-Lehmer iterations of M13369345 using 768K FFT length.
1:Test 7, 5300 Lucas-Lehmer iterations of M13369345 using 768K FFT length.
2:Self-test 768K passed!
2:Test 1, 460000 Lucas-Lehmer iterations of M250519 using 12K FFT length.
1:Self-test 768K passed!
1:Test 1, 460000 Lucas-Lehmer iterations of M250519 using 12K FFT length.
2:Test 2, 460000 Lucas-Lehmer iterations of M245759 using 12K FFT length.
1:Test 2, 460000 Lucas-Lehmer iterations of M245759 using 12K FFT length.
2:Test 3, 460000 Lucas-Lehmer iterations of M245281 using 12K FFT length.
1:Test 3, 460000 Lucas-Lehmer iterations of M245281 using 12K FFT length.
2:Test 4, 460000 Lucas-Lehmer iterations of M243713 using 12K FFT length.
1:Test 4, 460000 Lucas-Lehmer iterations of M243713 using 12K FFT length.
2:Test 5, 460000 Lucas-Lehmer iterations of M235519 using 12K FFT length.
1:Test 5, 460000 Lucas-Lehmer iterations of M235519 using 12K FFT length.
2:Torture Test ran 1 hours, 31 minutes 7 seconds - 0 errors, 0 warnings.
1:Torture Test ran 1 hours, 31 minutes 7 seconds - 0 errors, 0 warnings.
2:Execution halted.

1:Execution halted.

***glc*** · 04-02-2007, 01:54 AM

Please use the Edit button instead of making multiple posts. Thank you.

Burn · 04-02-2007, 12:54 PM

Quote:

Your ram is definately not the weak point. I would however concentrate on your cpu overclock before tweaking memory timings.
.

well , well ... it do seem it was the case .. he fixed the voltage and timing and now Orthos is happy.... i knew it. i had the same problem.

Mr.Ferrari · 04-02-2007, 03:29 PM

Aha good point, didn't really think of that, I referred to it as not being the weak point only in that he would not be limited in future overclocks.

I thought he might of had DDR2 667 ram

.

Glad to see it worked.

Captn · 04-09-2007, 12:16 PM

I upped my overclock a little [img=http://img240.imageshack.us/img240/2561/overclockns6.th.jpg] I was at 2.8 & Orthos failed after like 6min so i backed it down to 2.7. Will i have to up my CPU voltage now that Orthos failed at 2.8? My temps at idle(@ 2.7) are TAT = 33/34 & CoreTemp = 32/33

Mr.Ferrari · 04-09-2007, 01:02 PM

Yeah, you definitely need more voltage. 2.7ghz is still very good at stock voltages.

Ed989 · 04-09-2007, 02:06 PM

Hey, just wondering if anybody has any advice.....

I have my E6400 overclocked to 3.2 Ghz (400 x 8) on a DS3 board. There are some occasional system crashes and lockups, and when I run Prime95, it gets a fatal error anywhere from 2 minutes to 2 hours into the test. I don't think my RAM is the problem because it's running at stock voltage and speed. I have been increasing the CPU voltage, and it's currently at 1.28V. Should I keep increasing the CPU voltage, or maybe try increasing the FSB voltage? Thanks.

**Alaron** · 04-09-2007, 03:02 PM

__Moderator Note__

Ed, please start your own thread. Thanks.

Burn · 04-10-2007, 03:14 AM

Quote:

I upped my overclock a little [img=http://img240.imageshack.us/img240/2561/overclockns6.th.jpg] I was at 2.8 & Orthos failed after like 6min so i backed it down to 2.7. Will i have to up my CPU voltage now that Orthos failed at 2.8? My temps at idle(@ 2.7) are TAT = 33/34 & CoreTemp = 32/33

You are now to the point where you need more voltage to your CPU. I don't know the BIOS of your board but do you know if it use EIST ? its the intel speedstep technology that allow the mobo to control the CPU voltage and multiplier. So when your comp is idling you will run at lower voltage and lower frequency so it run cooler and quiet. If you adjust the voltage yourself you will need to disable this feature. You can tell if its enabled buy looking at CPUZ and see if the voltage and CPU frequency change will you do thing ...

i suggest that you add only +0.1V on yout CPU im sure you will hit a 2.8 GHZ stable...

Note that if EIST is disabled , your cpu will always run at full speed , so ALWAYS check you temp.I know someone at 3.20 Ghz on a E6400 , he added 0.15V. air cooled ....

i personally stopped at 3.4 Ghz .. because i dont need more power ..yet .. haha

Captn · 04-10-2007, 01:59 PM

Quote:

Originally Posted by Burn

You are now to the point where you need more voltage to your CPU. I don't know the BIOS of your board but do you know if it use EIST ? its the intel speedstep technology that allow the mobo to control the CPU voltage and multiplier. So when your comp is idling you will run at lower voltage and lower frequency so it run cooler and quiet. If you adjust the voltage yourself you will need to disable this feature. You can tell if its enabled buy looking at CPUZ and see if the voltage and CPU frequency change will you do thing ...

i suggest that you add only +0.1V on yout CPU im sure you will hit a 2.8 GHZ stable...

Note that if EIST is disabled , your cpu will always run at full speed , so ALWAYS check you temp.I know someone at 3.20 Ghz on a E6400 , he added 0.15V. air cooled ....

i personally stopped at 3.4 Ghz .. because i dont need more power ..yet .. haha

I have Intel Speedstep disabled. CPUID reads voltages wrong, i have my voltage set manualy at 1.20625 in the bios & CPUID read it @ 1.176. My overclock is now at 2.9Ghz. Look here

At Idle im at TAT =23/24 & CoreTemp = 21/23

Good so far...hehe

Burn · 04-10-2007, 02:22 PM

the CPUID voltage reading is not very accurate ... my own voltage is 1.41V and it show 1.38

congrat overclocking your E6400

Faith972 · 04-12-2007, 11:07 AM

Well i ran Orthos & for test i selected Blend and after 22min this is what i got:

Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1790 Time: 15
CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.]
CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.]
4/1/2007 8:27 PM
Launching 2 threads...
2:Using CPU #1
1:Using CPU #0
2:Beginning a continuous self-test to check your computer.
1:Beginning a continuous self-test to check your computer.
2:Press Stop to end this test.
1:Press 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:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
1:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
2:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
1:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
2:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
1:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
1:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
2:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
2:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
1:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
1:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length.
2:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length.
1:Self-test 1024K passed!
1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Self-test 1024K passed!
2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
1:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
2:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Possible hardware failure, consult readme.txt file, restarting test.
2:ERROR: ILLEGAL SUMOUT
2:Maximum number of warnings exceeded.
2:Torture Test ran 22 minutes 11 seconds - 0 errors, 100 warnings.
2:Execution halted.

1:Torture Test ran 22 minutes 11 seconds - 0 errors, 0 warnings.
1:Execution halted.

System never crashed or lockedup or shutdown Orthos started beeping. Gonna set my cpu to default & run Orthos again.

04-01-2007, 06:25 PM	#2
Mr.Ferrari V12 Join Date: Dec 2005 Location: Houston, T.E.X.A.S Posts: 3,488	Run Orthos instead of prime ----> http://sp2004.fre3.com/beta/beta2.htm When you get this error, does the computer freeze or shutdown? I would try running it at stock speed and see what happens. Share Share this post on Digg Del.icio.us Technorati Twitter

04-01-2007, 06:35 PM	#4
Mr.Ferrari V12 Join Date: Dec 2005 Location: Houston, T.E.X.A.S Posts: 3,488	I would put the CPU back at stock speed and try stress testing again. And double check with Orthos as that is a more efficient prime stress test. Share Share this post on Digg Del.icio.us Technorati Twitter

04-01-2007, 07:29 PM	#5
Captn Member (9 bit) Join Date: Aug 2001 Location: Maine Posts: 424	Running Orthos now with it overclocked see what happens. Share Share this post on Digg Del.icio.us Technorati Twitter

04-01-2007, 08:00 PM	#6
Captn Member (9 bit) Join Date: Aug 2001 Location: Maine Posts: 424	Well i ran Orthos & for test i selected Blend and after 22min this is what i got: Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1790 Time: 15 CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.] CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.] 4/1/2007 8:27 PM Launching 2 threads... 2:Using CPU #1 1:Using CPU #0 2:Beginning a continuous self-test to check your computer. 1:Beginning a continuous self-test to check your computer. 2:Press Stop to end this test. 1:Press 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:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length. 1:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length. 2:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length. 1:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length. 2:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length. 1:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length. 1:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length. 2:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length. 2:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length. 1:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length. 1:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length. 2:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length. 1:Self-test 1024K passed! 1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length. 2:Self-test 1024K passed! 2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length. 1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length. 2:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length. 1:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length. 2:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Maximum number of warnings exceeded. 2:Torture Test ran 22 minutes 11 seconds - 0 errors, 100 warnings. 2:Execution halted. 1:Torture Test ran 22 minutes 11 seconds - 0 errors, 0 warnings. 1:Execution halted. System never crashed or lockedup or shutdown Orthos started beeping. Gonna set my cpu to default & run Orthos again. Share Share this post on Digg Del.icio.us Technorati Twitter

04-01-2007, 09:08 PM	#7
Captn Member (9 bit) Join Date: Aug 2001 Location: Maine Posts: 424	I set my bios back to default & ran Orthos again: Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1790 Time: 15 CPU: 2133MHz FSB: 266MHz [266MHz x 8.0 est.] CPU: 2133MHz FSB: 266MHz [266MHz x 8.0 est.] 4/1/2007 9:17 PM Launching 2 threads... 2:Using CPU #1 1:Using CPU #0 2:Beginning a continuous self-test to check your computer. 1:Beginning a continuous self-test to check your computer. 2:Press Stop to end this test. 1:Press 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:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length. 1:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length. 2:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length. 1:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length. 2:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length. 1:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length. 2:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length. 1:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length. 2:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length. 1:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length. 2:Self-test 1024K passed! 2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length. 1:Self-test 1024K passed! 1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length. 1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length. 2: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:Self-test 8K passed! 2:Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length. 1:Self-test 8K passed! 1:Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length. 2:Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length. 1:Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length. 2:Test 3, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT length. 1:Test 3, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT length. 2:Test 4, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT length. 1:Test 4, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT length. 2:Test 5, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT length. 1:Test 5, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT length. 2:Test 6, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT length. 1:Test 6, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT length. 2:Test 7, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT length. 1:Test 7, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT length. 2:Test 8, 560000 Lucas-Lehmer iterations of M188415 using 10K FFT length. 1:Test 8, 560000 Lucas-Lehmer iterations of M188415 using 10K FFT length. 2:Self-test 10K passed! 2:Test 1, 4500 Lucas-Lehmer iterations of M17432577 using 896K FFT length. 1:Self-test 10K passed! 1:Test 1, 4500 Lucas-Lehmer iterations of M17432577 using 896K FFT length. 2:Torture Test ran 49 minutes 16 seconds - 0 errors, 0 warnings. 2:Execution halted. 1:Torture Test ran 49 minutes 16 seconds - 0 errors, 0 warnings. 1:Execution halted. I stopped Orthos after 49min. Share Share this post on Digg Del.icio.us Technorati Twitter

Need Some Help? Type Your Keywords Here:

Still Need Help? Type Your Keywords Here:

Free Weekly Tech Newsletter

04-01-2007, 06:11 PM	#1
Captn Member (9 bit) Join Date: Aug 2001 Location: Maine Posts: 424	E6400 overclock & Prime95 question... I ran Prime95 ver. 24.14 on my E6400 & after 2hours 8min's i get this error Test 1, 7800 Lucas-Lehmer iterations of M9961473 using 512k FFT Length FATAL ERROR: Rounding was 0.5, expected less than 0.4 Hardware failure detected, consult stress.txt file. Torture Test ran 2 hours 8 minutes - 1 errors, 0 warnings. Execution halted. My system Specs are: E6400 @ 2.6 with Arctic Freezer 7 Pro EVGA 8800GTX EVGA 680i Motherboard Corsair XMS2 2gig SeaSonic M-12 700W PSU Antec 900 Case WD 320 x2 I play games everything runs great with CoreTemp & TAT my temps never get above 37 while running Prime95 Torture Test, my pc never crashed or anything it runs stable. I don't understand the error, maybe someone could shed some light for me? Thank you in advance. Share Share this post on Digg Del.icio.us Technorati Twitter

04-01-2007, 09:57 PM	#8
Mr.Ferrari V12 Join Date: Dec 2005 Location: Houston, T.E.X.A.S Posts: 3,488	Cool, atleast we know that theres nothing wrong with your CPU. Now before you push the clocks again, make sure you have your pci-e and pci bus's locked at 100mhz and 33mhz respectively if you already have not. From here, you might've needed some more Vcore voltage. So raise it just a bit and see what happens. You can check your vcore via CPU-Z. And keep an eye on temperatures. What is the brand/model of your ram sticks? Share Share this post on Digg Del.icio.us Technorati Twitter

04-01-2007, 10:02 PM	#9
Captn Member (9 bit) Join Date: Aug 2001 Location: Maine Posts: 424	Corsair XMS2, PCI-E x16_1, MHz Auto 125. Are you familiar with the 680i Bios at all? Share Share this post on Digg Del.icio.us Technorati Twitter Last edited by Captn; 04-01-2007 at 10:21 PM.

04-01-2007, 10:36 PM	#10
Burn Member (8 bit) Join Date: Jul 2004 Posts: 194	Corsair XMS2 5 5 5 12 ? if its the same as me .. my mobo on auto mode put 1.8V on it. Stock voltage of this memory is 1.9V. I run them at 425Mhz at 1.9V. Check the voltage on your own sticks ... Share Share this post on Digg Del.icio.us Technorati Twitter __________________ Burn Core Duo 2 E6700(2.66Ghz@3.7Ghz) , Mobo Asus PW5 DH , Cosair XMS2 4Gig (425Ghz) ,Single HD2900XT , OCZ 700watts Power supply, SATA 200, 320 and 160 Gig HD , X-Fi XtremeGamer fatality Pro Last edited by Burn; 04-01-2007 at 10:39 PM.

04-01-2007, 10:48 PM	#13
Captn Member (9 bit) Join Date: Aug 2001 Location: Maine Posts: 424	THis is my memory http://www.newegg.com/Product/Produc...82E16820145590 Share Share this post on Digg Del.icio.us Technorati Twitter

04-01-2007, 10:54 PM	#14
Burn Member (8 bit) Join Date: Jul 2004 Posts: 194	yup , same as me... You should see 12 as the cycle time instead of 18 to get what you paid for. You will have to put it manualy in the BIOS. Just make sure the voltage is 1.9V. Leave it there until you reach stability with your overclocking and then adjust the memory timing. Play it safe for now. Share Share this post on Digg Del.icio.us Technorati Twitter Last edited by Burn; 04-01-2007 at 10:57 PM.

04-01-2007, 10:54 PM	#15
Captn Member (9 bit) Join Date: Aug 2001 Location: Maine Posts: 424	Ok cool, thank you. Share Share this post on Digg Del.icio.us Technorati Twitter

04-02-2007, 12:15 AM	#18
Captn Member (9 bit) Join Date: Aug 2001 Location: Maine Posts: 424	Is there an issue with the NEWEST CPU-Z? Its reading my Core speed @ 1953.1 MHz & my multipier @ x6 which is wrong in my bios its set at x8. Its telling me my Bus speed is 325.5 & FSB is 1302(Which is what i have it set at). But my multiplier is set at x8, odd. TAT says my CPU speed is 2.6...lol I did set my memory @ 1.9v & its now reading my memory settings as 5,5,5, 12. Is there another program other then CPU-Z that does the same thing? Share Share this post on Digg Del.icio.us Technorati Twitter

04-02-2007, 12:40 AM	#19
Captn Member (9 bit) Join Date: Aug 2001 Location: Maine Posts: 424	Nevermind i figured it out here. http://forum.x86-secret.com/showthread.php?t=6806 Ok I fixed my voltage on my ram and set it at 1.9(which is default for my memory) & set my timings correct on my ram @ 5, 5, 5, 12 and re-ran Orthos heres what i got: Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1790 Time: 15 CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.] CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.] 4/2/2007 8:27 AM 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. 1:Press Stop to end this test. 2:Press 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:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length. 1:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length. 2:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length. 1:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length. 2:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length. 1:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length. 2:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length. 1:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length. 2:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length. 1:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length. 1:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length. 2:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length. 2:Self-test 1024K passed! 2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length. 1:Self-test 1024K passed! 1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length. 1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length. 2: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, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length. 1:Self-test 8K passed! 1:Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length. 2:Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length. 1:Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length. 2:Test 3, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT length. 1:Test 3, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT length. 2:Test 4, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT length. 1:Test 4, 560000 Lucas-Lehmer iterations of M204799 using 10K FFT length. 2:Test 5, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT length. 1:Test 5, 560000 Lucas-Lehmer iterations of M200705 using 10K FFT length. 2:Test 6, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT length. 1:Test 6, 560000 Lucas-Lehmer iterations of M196607 using 10K FFT length. 2:Test 7, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT length. 1:Test 7, 560000 Lucas-Lehmer iterations of M194561 using 10K FFT length. 2:Test 8, 560000 Lucas-Lehmer iterations of M188415 using 10K FFT length. 1:Test 8, 560000 Lucas-Lehmer iterations of M188415 using 10K FFT length. 2:Test 9, 560000 Lucas-Lehmer iterations of M186369 using 10K FFT length. 1:Test 9, 560000 Lucas-Lehmer iterations of M186369 using 10K FFT length. 2:Self-test 10K passed! 2:Test 1, 4500 Lucas-Lehmer iterations of M17432577 using 896K FFT length. 1:Self-test 10K passed! 1:Test 1, 4500 Lucas-Lehmer iterations of M17432577 using 896K FFT length. 2:Test 2, 4500 Lucas-Lehmer iterations of M17432575 using 896K FFT length. 1:Test 2, 4500 Lucas-Lehmer iterations of M17432575 using 896K FFT length. 2:Test 3, 4500 Lucas-Lehmer iterations of M17115073 using 896K FFT length. 1:Test 3, 4500 Lucas-Lehmer iterations of M17115073 using 896K FFT length. 2:Test 4, 4500 Lucas-Lehmer iterations of M16815071 using 896K FFT length. 1:Test 4, 4500 Lucas-Lehmer iterations of M16815071 using 896K FFT length. 2:Test 5, 4500 Lucas-Lehmer iterations of M16515073 using 896K FFT length. 1:Test 5, 4500 Lucas-Lehmer iterations of M16515073 using 896K FFT length. 2:Test 6, 4500 Lucas-Lehmer iterations of M16515071 using 896K FFT length. 1:Test 6, 4500 Lucas-Lehmer iterations of M16515071 using 896K FFT length. 2:Test 7, 4500 Lucas-Lehmer iterations of M16297569 using 896K FFT length. 1:Test 7, 4500 Lucas-Lehmer iterations of M16297569 using 896K FFT length. 2:Self-test 896K passed! 2:Test 1, 5300 Lucas-Lehmer iterations of M14942209 using 768K FFT length. 1:Self-test 896K passed! 1:Test 1, 5300 Lucas-Lehmer iterations of M14942209 using 768K FFT length. 2:Test 2, 5300 Lucas-Lehmer iterations of M14942207 using 768K FFT length. 1:Test 2, 5300 Lucas-Lehmer iterations of M14942207 using 768K FFT length. 2:Test 3, 5300 Lucas-Lehmer iterations of M14155777 using 768K FFT length. 1:Test 3, 5300 Lucas-Lehmer iterations of M14155777 using 768K FFT length. 2:Test 4, 5300 Lucas-Lehmer iterations of M14155775 using 768K FFT length. 1:Test 4, 5300 Lucas-Lehmer iterations of M14155775 using 768K FFT length. 2:Test 5, 5300 Lucas-Lehmer iterations of M13969343 using 768K FFT length. 1:Test 5, 5300 Lucas-Lehmer iterations of M13969343 using 768K FFT length. 2:Test 6, 5300 Lucas-Lehmer iterations of M13669345 using 768K FFT length. 1:Test 6, 5300 Lucas-Lehmer iterations of M13669345 using 768K FFT length. 2:Test 7, 5300 Lucas-Lehmer iterations of M13369345 using 768K FFT length. 1:Test 7, 5300 Lucas-Lehmer iterations of M13369345 using 768K FFT length. 2:Self-test 768K passed! 2:Test 1, 460000 Lucas-Lehmer iterations of M250519 using 12K FFT length. 1:Self-test 768K passed! 1:Test 1, 460000 Lucas-Lehmer iterations of M250519 using 12K FFT length. 2:Test 2, 460000 Lucas-Lehmer iterations of M245759 using 12K FFT length. 1:Test 2, 460000 Lucas-Lehmer iterations of M245759 using 12K FFT length. 2:Test 3, 460000 Lucas-Lehmer iterations of M245281 using 12K FFT length. 1:Test 3, 460000 Lucas-Lehmer iterations of M245281 using 12K FFT length. 2:Test 4, 460000 Lucas-Lehmer iterations of M243713 using 12K FFT length. 1:Test 4, 460000 Lucas-Lehmer iterations of M243713 using 12K FFT length. 2:Test 5, 460000 Lucas-Lehmer iterations of M235519 using 12K FFT length. 1:Test 5, 460000 Lucas-Lehmer iterations of M235519 using 12K FFT length. 2:Torture Test ran 1 hours, 31 minutes 7 seconds - 0 errors, 0 warnings. 1:Torture Test ran 1 hours, 31 minutes 7 seconds - 0 errors, 0 warnings. 2:Execution halted. 1:Execution halted. Share Share this post on Digg Del.icio.us Technorati Twitter Last edited by Captn; 04-02-2007 at 09:05 AM.

04-02-2007, 01:54 AM	#20
*glc* Forum Administrator Staff Premium Member Join Date: May 2000 Location: Joplin MO Posts: 37,769	Please use the Edit button instead of making multiple posts. Thank you. Share Share this post on Digg Del.icio.us Technorati Twitter

04-02-2007, 03:29 PM	#22
Mr.Ferrari V12 Join Date: Dec 2005 Location: Houston, T.E.X.A.S Posts: 3,488	Aha good point, didn't really think of that, I referred to it as not being the weak point only in that he would not be limited in future overclocks. I thought he might of had DDR2 667 ram . Glad to see it worked. Share Share this post on Digg Del.icio.us Technorati Twitter Last edited by Mr.Ferrari; 04-02-2007 at 10:33 PM.

04-09-2007, 12:16 PM	#23
Captn Member (9 bit) Join Date: Aug 2001 Location: Maine Posts: 424	I upped my overclock a little [img=http://img240.imageshack.us/img240/2561/overclockns6.th.jpg] I was at 2.8 & Orthos failed after like 6min so i backed it down to 2.7. Will i have to up my CPU voltage now that Orthos failed at 2.8? My temps at idle(@ 2.7) are TAT = 33/34 & CoreTemp = 32/33 Share Share this post on Digg Del.icio.us Technorati Twitter Last edited by Captn; 04-09-2007 at 12:59 PM.

04-09-2007, 01:02 PM	#24
Mr.Ferrari V12 Join Date: Dec 2005 Location: Houston, T.E.X.A.S Posts: 3,488	Yeah, you definitely need more voltage. 2.7ghz is still very good at stock voltages. Share Share this post on Digg Del.icio.us Technorati Twitter

04-09-2007, 02:06 PM	#25
Ed989 Member (7 bit) Join Date: Apr 2007 Posts: 74	E6400 Overclock..... Hey, just wondering if anybody has any advice..... I have my E6400 overclocked to 3.2 Ghz (400 x 8) on a DS3 board. There are some occasional system crashes and lockups, and when I run Prime95, it gets a fatal error anywhere from 2 minutes to 2 hours into the test. I don't think my RAM is the problem because it's running at stock voltage and speed. I have been increasing the CPU voltage, and it's currently at 1.28V. Should I keep increasing the CPU voltage, or maybe try increasing the FSB voltage? Thanks. Share Share this post on Digg Del.icio.us Technorati Twitter

04-09-2007, 03:02 PM	#26
Alaron Kickin' it Staff Premium Member Join Date: Jan 2002 Location: USA Posts: 7,723	__Moderator Note__ Ed, please start your own thread. Thanks. Share Share this post on Digg Del.icio.us Technorati Twitter __________________ Fold for PCMech: Team 13761

04-10-2007, 02:22 PM	#29
Burn Member (8 bit) Join Date: Jul 2004 Posts: 194	the CPUID voltage reading is not very accurate ... my own voltage is 1.41V and it show 1.38 congrat overclocking your E6400 Share Share this post on Digg Del.icio.us Technorati Twitter

04-12-2007, 11:07 AM	#30
Faith972 Banned Join Date: Apr 2007 Posts: 2	Well i ran Orthos & for test i selected Blend and after 22min this is what i got: Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 1790 Time: 15 CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.] CPU: 2604MHz FSB: 325MHz [325MHz x 8.0 est.] 4/1/2007 8:27 PM Launching 2 threads... 2:Using CPU #1 1:Using CPU #0 2:Beginning a continuous self-test to check your computer. 1:Beginning a continuous self-test to check your computer. 2:Press Stop to end this test. 1:Press 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:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length. 1:Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length. 2:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length. 1:Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length. 2:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length. 1:Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length. 1:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length. 2:Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length. 2:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length. 1:Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length. 1:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length. 2:Test 7, 4000 Lucas-Lehmer iterations of M18474367 using 1024K FFT length. 1:Self-test 1024K passed! 1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length. 2:Self-test 1024K passed! 2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length. 1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length. 2:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length. 1:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length. 2:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Possible hardware failure, consult readme.txt file, restarting test. 2:ERROR: ILLEGAL SUMOUT 2:Maximum number of warnings exceeded. 2:Torture Test ran 22 minutes 11 seconds - 0 errors, 100 warnings. 2:Execution halted. 1:Torture Test ran 22 minutes 11 seconds - 0 errors, 0 warnings. 1:Execution halted. System never crashed or lockedup or shutdown Orthos started beeping. Gonna set my cpu to default & run Orthos again. Share Share this post on Digg Del.icio.us Technorati Twitter

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread:

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to effectively get your questions answered	glc	General Discussion	6	03-29-2006 06:18 PM
motherboard question	Zeppelin1432	Computer Hardware	3	06-25-2005 12:37 PM
AMD 64 overclock question.	TpGun2424	Computer Hardware	8	05-23-2004 08:40 PM
Overclock Question	sdkramer	Computer Hardware	11	02-19-2001 10:58 AM
Overclock question on IBM 300GL 6275-B6U	steveh	Computer Hardware	3	02-02-2001 06:51 PM

Subscribe to THE INSIDER

Need Some Help? Type Your Keywords Here:

Still Need Help? Type Your Keywords Here:

Free Weekly Tech Newsletter