• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How should I interpret Orthos errors?

Fireye0

Member
So, I'm running pretty happy with my current overclock. It's not too extreme, temps are acceptable. E4300 running at 340x9, 1.375v, DDR667@816 4-4-4-12, 2.0v (I think, can't see it in cpu-z), on a Gigabyte P35-DS3L.

However, after approximately 9 hours, Orthos failed. How should I figure out what caused the failure, and what to change?


Test 7, 1200 Lucas-Lehmer iterations of M52331647 using 3072K FFT length.
FATAL ERROR: Final result was 89B6A890, expected: A1EAE85D.
Hardware failure detected, consult stress.txt file.
Torture Test ran 9 hours, 18 minutes 51 seconds - 1 errors, 0 warnings.
Execution halted.
 
An error in Orthos means CPU instability. You need to increase voltage slightly, or lower your overclock until you can pass all stability tests.

Or, you can call it 8 hr stable and leave it alone and pray that you never hit that weak spot during normal usage.
 
Ahh, terrific. So, an increase to the mem voltage is in order, or loosening up the timings if that doesn't solve it?
 
Terrific, thanks a ton for the advice. An extra .1v on the memory has allowed my system to run stable on Orthos for about 16 hours now.
 
Back
Top