Best Stability test software for Core 2 Duo ... orthos or ...!?

[HamidFULL]

whats best Stability test software for Core 2 duo and how I should run it for Dual Cores? (Core 2 duo)

any reply can help me
Tanx in advanced

 

[cmdrdredd]

just run Orthos on small FFT for about 12+ hours. If it doesn't error or freeze or crash in any way the CPU will be fine for any general usage/gaming you can do. To check memory run memtest86 from a Floppy or CD.

 

[HamidFULL]

Originally posted by: cmdrdredd
just run Orthos on small FFT for about 12+ hours. If it doesn't error or freeze or crash in any way the CPU will be fine for any general usage/gaming you can do. To check memory run memtest86 from a Floppy or CD.

PLZ give me latest Orthos for download for my Dual Core!!

 

[myocardia]

Run this on blend. Small fft only checks the processor. Blend checks nearly the entire system: Orthos download link.

 

[lopri]

http://sp2004.fre3.com/beta/beta2.htm

Or better,
http://forums.anandtech.com/messageview.aspx?catid=28&threadid=1901991

I'd actually suggest LargeFFT over SmallFFT with C2D, because the OC'ing is so much dependent on MCH unlike A64 OC where you can divide/conquer.

 

[cmdrdredd]

Originally posted by: lopri
http://sp2004.fre3.com/beta/beta2.htm

Or better,
http://forums.anandtech.com/messageview.aspx?catid=28&threadid=1901991

I'd actually suggest LargeFFT over SmallFFT with C2D, because the OC'ing is so much dependent on MCH unlike A64 OC where you can divide/conquer.

SmallFFT produces the most heat and removes the memory from the equation. What you want to do with Orthos is tell if your CPU can run at that speed/voltage without fail. You don't want to error out and have no idea if your memory or your CPU caused the error. So I say run CPU on small FFT and run memtest to check memory.

 

[HamidFULL]

Orthos automatically check with 2 thread for Dual cores or I need 2 Orthos in same time??
Tanx a lot guys

 

[Baked]

Originally posted by: HamidFULL
Orthos automatically check with 2 thread for Dual cores or I need 2 Orthos in same time??
Tanx a lot guys

Just download it, install it, and hit the Start button already. Jesus Christ, you sound like a woman.

 

[Madellga]

Originally posted by: lopri
http://sp2004.fre3.com/beta/beta2.htm

Or better,
http://forums.anandtech.com/messageview.aspx?catid=28&threadid=1901991

I'd actually suggest LargeFFT over SmallFFT with C2D, because the OC'ing is so much dependent on MCH unlike A64 OC where you can divide/conquer.

I agree. With C2D you have to test the complete set.

 

[Dexion]

If your old school, use Prime95 LOL

Again, Orthos with Small FFTs & Memtest86 is probably the easiest to get running and most complete level of testing.

 

[TraumaRN]

Dont laugh.

But the new game released, Company of Heroes.


Definitely showed me that my system was unstable. Better than any stress test. I was primed stable for 12+ hours...and yet Company of Heroes would freeze me after 20 minutes. Turned my CPU down 20mhz and it worked just fine.

 

[cmdrdredd]

Originally posted by: Madellga

Originally posted by: lopri
http://sp2004.fre3.com/beta/beta2.htm

Or better,
http://forums.anandtech.com/messageview.aspx?catid=28&threadid=1901991

I'd actually suggest LargeFFT over SmallFFT with C2D, because the OC'ing is so much dependent on MCH unlike A64 OC where you can divide/conquer.

I agree. With C2D you have to test the complete set.

Again if it does give an error you don't know if it's memory or CPU. You can eliminate either possibility by testing CPU with smallfft and the memory with memtest.

 

[cmdrdredd]

Originally posted by: DeathBUA
Dont laugh.

But the new game released, Company of Heroes.


Definitely showed me that my system was unstable. Better than any stress test. I was primed stable for 12+ hours...and yet Company of Heroes would freeze me after 20 minutes. Turned my CPU down 20mhz and it worked just fine.

Um...sounds like bad code more than anything...

 

[TraumaRN]

Originally posted by: cmdrdredd

Originally posted by: DeathBUA
Dont laugh.

But the new game released, Company of Heroes.


Definitely showed me that my system was unstable. Better than any stress test. I was primed stable for 12+ hours...and yet Company of Heroes would freeze me after 20 minutes. Turned my CPU down 20mhz and it worked just fine.

Um...sounds like bad code more than anything...

Actually I wasnt the only case. So maybe that is bad code. Maybe it isnt. But the game is definitely CPU and GPU intensive. Lots of physics, lots of animations etc.

 

[jzinckgra]

Weird, I can't run the test. I get the alarm with this message:

Type: Small FFTs - stress CPU Min: 8 Max: 64 InPlace: Yes Mem: 8 Time: 15
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
9/19/2006 10:26 PM
Launching 2 threads...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 0 minutes 4 seconds - 1 errors, 0 warnings.
Execution halted.

Type: Small FFTs - stress CPU Min: 8 Max: 64 InPlace: Yes Mem: 8 Time: 15
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
9/19/2006 10:27 PM
Launching 2 threads...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 0 minutes 2 seconds - 1 errors, 0 warnings.
Execution halted.

What does this mean?

 

[cmdrdredd]

Originally posted by: jzinckgra
Weird, I can't run the test. I get the alarm with this message:

Type: Small FFTs - stress CPU Min: 8 Max: 64 InPlace: Yes Mem: 8 Time: 15
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
9/19/2006 10:26 PM
Launching 2 threads...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 0 minutes 4 seconds - 1 errors, 0 warnings.
Execution halted.

Type: Small FFTs - stress CPU Min: 8 Max: 64 InPlace: Yes Mem: 8 Time: 15
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
9/19/2006 10:27 PM
Launching 2 threads...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 0 minutes 2 seconds - 1 errors, 0 warnings.
Execution halted.

What does this mean?

That means your CPU returned a result that isn't right and basically failed the test. You need to add more voltage and try again. Until it can run for about 12 hours it's not stable.

 

[Madellga]

Originally posted by: cmdrdredd

Originally posted by: Madellga

Originally posted by: lopri
http://sp2004.fre3.com/beta/beta2.htm

Or better,
http://forums.anandtech.com/messageview.aspx?catid=28&threadid=1901991

I'd actually suggest LargeFFT over SmallFFT with C2D, because the OC'ing is so much dependent on MCH unlike A64 OC where you can divide/conquer.

I agree. With C2D you have to test the complete set.

Again if it does give an error you don't know if it's memory or CPU. You can eliminate either possibility by testing CPU with smallfft and the memory with memtest.

No, you can't that easy. The issue with this C2D platform is that you have more things to set. When everything but VCore and VDim is at auto and it fails, I learned that the MCH and FSB voltages needed some bump also. After that, everything runs fine.

Using your methodology, I would have set for a lower clock.

 

[jzinckgra]

cmdrdredd,
it looks like we have almost the same setup. At least the same MB, ram and chip. I am also running at 3.2Ghz, but never adjusted the cpu voltage. Should I put that at 1.4V? I've only adjusted my Vcore to 2.1V.

 

[TheSlamma]

Originally posted by: cmdrdredd

Originally posted by: jzinckgra
Weird, I can't run the test. I get the alarm with this message:

Type: Small FFTs - stress CPU Min: 8 Max: 64 InPlace: Yes Mem: 8 Time: 15
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
9/19/2006 10:26 PM
Launching 2 threads...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 0 minutes 4 seconds - 1 errors, 0 warnings.
Execution halted.

Type: Small FFTs - stress CPU Min: 8 Max: 64 InPlace: Yes Mem: 8 Time: 15
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
CPU: 3200MHz FSB: 400MHz [400MHz x 8.0 est.]
9/19/2006 10:27 PM
Launching 2 threads...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 0 minutes 2 seconds - 1 errors, 0 warnings.
Execution halted.

What does this mean?

That means your CPU returned a result that isn't right and basically failed the test. You need to add more voltage and try again. Until it can run for about 12 hours it's not stable.

I am getting this same thing with everything at stock on a E6600 with a DS3 mobo. maybe a defective CPU or RAM? (2GB of the corsair XMS-6400 running at the 1.9v)

 

[n7]

I find it remarkable how many threads ppl have Corsair RAM & their system isn't stable.

In fact, i'm starting to wonder about it...

I'd bet RAM is the issue.

Likely needs some tweaking.

 

[MADMAX23]

SmallFFT produces the most heat and removes the memory from the equation. What you want to do with Orthos is tell if your CPU can run at that speed/voltage without fail. You don't want to error out and have no idea if your memory or your CPU caused the error. So I say run CPU on small FFT and run memtest to check memory.

How many times do I have to tell you that Memtest is not enough for testing Ram memory??
Once you are 100% sure your Cpu is running 100% stable (previously tested under ORTHOS Small FFTs test), you have to run ORTHOS BLEND TEST to test the whole Memory system...to test if communication between Cpu and Ram is working properly on Windows...What do you not understand?? myocardia is also telling you the same thing....Small FFts is only for Cpu testing, that's all, and we all know that's not enough before stating "My system is stable", even if your Ram passes 24 hours trough Memtest error free....Memtest86 is not enough.

 

[TheForce81]

Large FFT tests something extra on the CPU front as well. I had a E6300 running at 3Ghz, failed within 5 minutes no matter what Vcore I gave it. Now I have another E6300, passes it fine at 3Ghz with 1,24Vcore even for more than 9 hours. So I say if Large FFT fails after small FFT passes, it still could be your CPU!

 

[imported_Buckster]

I did a Blend test last night at a new overclock speed and it failed after 8 hours - I'm still counting it as stable though.

Anything could have interacted with Orthos after 8 hours - and even when video encoding etc - very very rare to go 8 hours with both cores fully loaded ...

Mark.

 

[myocardia]

Buckster, you can call your overclock stable if you want. You can call it George Bush, if you want. But, if it won't run any software that will run without "failing" at stock speed, then your overclock is not stable.

 

[imported_Buckster]

True - but Orthos/Prime is a bit of a picky beast ....

I had an overclocked Northwood - ran 24/7 no problems, games, encoding etc, ran Prime and it lasted 2 minutes !