Orthos Testing - Priority Setting + Length of Testing

[txtmstrjoe]

I'm presently testing an overclock on my Opteron 165 (CCBBE 0616XPMW), running at 2.727GHz (303*9).

Before overclocking, I determined maximum levels for my board's FSB, CPU, and RAM. I also tested the RAM with MemTest86+ (v.1.70), and then used Gogar's AMD OC Optimizer. I've run S&M (at Long Test Length, Full Priority Testing) CPU + RAM test, and passed that. SuperPi on both cores simultaneously also passed. I'm now running Orthos, and have had to raise VCore from 1.3625V to 1.40V (raised systematically and incrementally), after the tests failed at around 3 - 4 1/2 Hrs.

I'm running Orthos at Priority 10, and I'm going for a minimum of 12 Hrs.

Is there a correlation between Priority Setting, the length of the test, and actual functional stability?

Thanks for your thoughts, people!

[nick2crete]

If you run the S&M (100% & Loops) with success ,no reason to test any more..try for higher now..:cool:

[txtmstrjoe]

If you run the S&M (100% & Loops) with success ,no reason to test any more..try for higher now..:cool:

Big thanks to you, sir.

I guess you could say I'm just a bit anal about stability.

Thanks again for your thoughts. Much appreciated.

[nick2crete]

You are welcome sir...any time...:rolleyes: go higher now..

[Sailindawg]

I have always run P-95 at priority 10. At priority 10, all your system resources are given to that one program. It pretty much slaps your rig around compared to running at a lower priority. I always shoot for 10-12 hours stable (dual) P-95 (or orthos) at priority 10 for my 24/7 overclocks.