Overclock and running Orthos

[kwack]

Hi,

Furst thread and I printed the spiel on overclocking on this forum. I followed this to the letter and ran Orthos for 9 oddd hours as you can see.

I did the memory timings and upped the FSB to 300

It then came up with the following after a long time - I have put back to 266 for time being. I have an option within the BIOS to put the CPU into a sports mode so that it will auto increase the FSB if put under load which now brings it up to 2160 when running this program is this a better option for teh Mobo to decide teh load it puts the CPU under or to manually set it to a higher figure all the time?


1:Test 1, 900 Lucas-Lehmer iterations of M77497473 using 4096K FFT length.
2:Test 5, 1000 Lucas-Lehmer iterations of M65390273 using 3584K FFT length.
2:FATAL ERROR: Rounding was 0.5, expected less than 0.4
2:Hardware failure detected, consult stress.txt file.
2:Torture Test ran 9 hours, 41 minutes 17 seconds - 1 errors, 0 warnings.
2:Execution halted.

Any ideas what this means

Cheers

Kwack

[kwack]

Anyone

Is it the Orthos program or is it that my CPU doesnt like the Oveclock?

Kwack

[moogle]

Anyone

Is it the Orthos program or is it that my CPU doesnt like the Oveclock?

Kwack

didnt understand what you were saying till i read the error, its your cpu not stable with that overclock, orthos is just telling you the cpu can produce errors due to the overclock thats all.

are you german? just asking.

[iranu]

Welcome to Hexus.

I would always manually set the overclock in the bios. It is best to find your maximum cpu overclock and get that stable before attempting to tighten the memory timings.

What are your stock cpu temps like at idle and load?
What is your maximum stable overclock and temps at idle and load?
What is you cpu voltage for your stable overclock?
What cooler are you using?
What does the stress.txt file say?

It's possible that your cpu doesn't like the overclock, but until we have a bit more info we won't know. Personally I've never been a fan of stress testing I've always been a "if the PC runs everything I use stably then it's fine" sort of guy, but I'm sure there will be a few more along later that are familiar with orthos.

[kwack]

Thanks for the replies - No I am not German?

I set the memory timinfgs as suggested 5,5,5,15 which is supposedly quite lean given the memory I have.

I use TAT analysis for temps

What are your stock cpu temps like at idle and load? Stock 35, load haven't tested
What is your maximum stable overclock and temps at idle and load? at 320fsb stock 44, Load 68
What is you cpu voltage for your stable overclock? from CPUZ it says 1.408v
What cooler are you using? Zalman 7500
What does the stress.txt file say? THis seems to be a generic file that gives some ideas on what to check


Hope this helps, I have upped the fsb to 320 but I guess that I should leave to 300 for now?

Cheers

Kwack

[iranu]

If you can run orthos at 300fsb or 320fsb with the slacker ram timings then it would indicate that it was the tightening of the ram timings that caused orthos to fail.

Aslong as the cpu doesn't get higher 60°C during orthos then you should be ok for running 24/7. Once your cpu is stable at that overclock then you can start to tighten ram timings. Overclocking is a process not to be rushed. Change one thing at a time and test is the best method.

TAT will stress the cpu to the max and 70°C for a C2D is normal.

I'd rerun your orthos test at 300fsb and stock (auto) ram timings to see whether you ahve reached your maximum overclock at those volts and temps.

Do you get any other problems such as lock ups or BSODs during operation with fsb at 300?