AMOCO

Ok,I'm working on my Opteron 170(2.0) & (2.80).And I was wondering how long do I let Orthos run?At now I'm at (11 hours,37 mins.)[Rounds:1/1]

__________________

nckid4u

You're probably good. Some go for 24 hours, but I have only had one cpu error out after 12 hours and I am one of those who run it for 24 hours.

__________________
FOLDINFISH - a rocketfish WC mod...

OCN Water Cooling Club

780i q6600 tx650 and more for sale

When all men think alike, nobody thinks very much.
-Walter Lippman

Syrillian

As Nckid4u stated, 24 hrs is the general threshold that most abide by.

Additionally, you may want to do some gaming and run a variety of benchmarking programs as I have experienced stability in one element and instability in others.

__________________
WIP: Scarab
Custom Cases:
Silentium, Halcyon, Indigo, Gemini, Prometheus, Anvil
Case Mods:
Liquid Chameleon, VF1000 LAN box

Semper Fidelis

TwoCables

It's not really about how long to let it run for, but more that the goal is to get the overclock stable enough to be able to do the recommended amount of hours for each test.

So, for finalizing an overclock so that you can get on with your life, here's what I recommend: make the overclock stable enough to do at least the following (not necessarily in this order tho):

• 12 hours of the Small FFTs test in the 64-bit version of Prime95 (because you have a 64-bit OS).
• 8 hours of the Blend test in the 64-bit version of Prime95.
• 6-8 hours of the Large, in-place FFTs in the 64-bit version.
• 50-100 linpack runs using LinX. The more the better. Most importantly, click the "All" button next to where it says "Memory to use", and then manually adjust it down by 5-10 MB at a time until the test runs. This is important!
• 7-10 passes in Memtest.

I guarantee you that if the overclock can do all of this, then it is rock-solid stable. But real-world performance is also a good way to gauge the stability, and so are benchmarks. But ignoring any one thing/test could be a mistake.

Most importantly, try to avoid doing anything on the computer while any of these tests are running. For example: I can get any of these stress tests to last longer by simply doing light browsing in Firefox, or checking for e-mail. This is because the system is forced to share the CPU cycles with whatever it is that you're doing (or with whatever is automatically running due to a schedule) instead of being able to give the stress test its undivided attention.

So that's my answer and I'm sticking to it.

__________________

AMOCO

well thanks guy's,gonna let it run to 24 hours,i'm going to post everything i've done to this oc,because there are some twist to it.

__________________