Orthos - FATAL ERROR: Rounding was 0.5, expected less than 0.4

Jaaay · 20 Mar 2007 at 17:59

Hi, im running my E6400 at 3.42Ghz, it seems ok, no crashing etc. but the problem comes in Orthos: It gives me a fatal error after only 14 seconds =/

ORTHOS said:
Type: Small FFTs - stress CPU Min: 8 Max: 64 InPlace: Yes Mem: 8 Time: 15
CPU: 3424MHz FSB: 428MHz [428MHz x 8.0 est.]
20/03/2007 17:49
Launching 2 threads...
1:Using CPU #0
2:Using CPU #1
1:Beginning a continuous self-test to check your computer.
1ress Stop to end this test.
1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Beginning a continuous self-test to check your computer.
2ress Stop to end this test.
2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:FATAL ERROR: Rounding was 0.5, expected less than 0.4
1:Hardware failure detected, consult stress.txt file.
1:Torture Test ran 0 minutes 14 seconds - 1 errors, 0 warnings.
1:Execution halted.

2:Torture Test ran 0 minutes 14 seconds - 0 errors, 0 warnings.
2:Execution halted.

Im not sure what im doing wrong.. :confused:

Can someone point me in the right direction?

Cheers,
Jay

JeffyB · 20 Mar 2007 at 18:03

This is due to system insability, although you may not have encountered any problems with general usage programs like orthos are designed to stress your pc to the limit to ensure stability. Either up the vcore a smidge if your temps are ok under full load or lower the overclock down a bit till you can pass orthos. 12 hours orthos is the general rule of thumb for stability, just leave it going over night.

joeyjojo · 20 Mar 2007 at 18:06

JeffyB said:
This is due to system insability, although you may not have encountered any problems with general usage programs like orthos are designed to stress your pc to the limit to ensure stability. Either up the vcore a smidge if your temps are ok under full load or lower the overclock down a bit till you can pass orthos. 12 hours orthos is the general rule of thumb for stability, just leave it going over night.

Spot on

I can't see how people are happy to run unstable systems. Aren't they concerned for their data at all?

Jaaay · 20 Mar 2007 at 18:08

JeffyB said:
This is due to system insability, although you may not have encountered any problems with general usage programs like orthos are designed to stress your pc to the limit to ensure stability. Either up the vcore a smidge if your temps are ok under full load or lower the overclock down a bit till you can pass orthos. 12 hours orthos is the general rule of thumb for stability, just leave it going over night.

Errrrm, n00b question, i followed a guide to overclock my pc, what is the vcore, im supposing its got something to do with voltage, ive got all my voltage on auto..

joeyjojo · 20 Mar 2007 at 18:11

It's the voltage through the cpu. With a higher voltage the chip is able to run faster without failing, but also runs hotter.

Jaaay · 20 Mar 2007 at 18:13

joeyjojo said:
It's the voltage through the cpu. With a higher voltage the chip is able to run faster without failing, but also runs hotter.

Hmm, ok.
How much should i up it to?
Its currently running on 1.392v according to CPU-Z

simonnance · 20 Mar 2007 at 18:15

mine needs about 1.43ish to hit 3.3Ghz stabaly, varies. That's BIOS tough, not "rea" voltage.

overcl0cker · 20 Mar 2007 at 18:49

Jay™ said:
Hmm, ok.
How much should i up it to?
Its currently running on 1.392v according to CPU-Z

1.392v is stock core for an E6400 I think. As a previous poster wrote, upping the Vcore makes your CPU hotter so if you're going to increase that make sure you have decent cooling installed.

My E6300 runs @ 1.325v stock @ 1.86Ghz, and is currently running at 1.425v @ 3.1Ghz. This 0.1v has upped my 100% load temps by about 10 degrees so it does make a difference.

oc.

Jaaay · 20 Mar 2007 at 19:25

overcl0cker said:
1.392v is stock core for an E6400 I think. As a previous poster wrote, upping the Vcore makes your CPU hotter so if you're going to increase that make sure you have decent cooling installed.

My E6300 runs @ 1.325v stock @ 1.86Ghz, and is currently running at 1.425v @ 3.1Ghz. This 0.1v has upped my 100% load temps by about 10 degrees so it does make a difference.

oc.

overcl0cker, could you do me a massive favour and take a pic of your MN Intelligent Tweaker? Cos im not sure which voltage thingies to increase.

Btw. Im running a silent Scythe Ninja Rev. B (No Fan on)

Jaaay · 20 Mar 2007 at 21:30

Just lowered my overclock to 3.295Ghz, and its coming up with a different error, 16 odd minutes in.

ORTHOS said:
Type: Small FFTs - stress CPU Min: 8 Max: 64 InPlace: Yes Mem: 8 Time: 15
CPU: 3295MHz FSB: 412MHz [411MHz x 8.0 est.]
20/03/2007 21:03
Launching 2 threads...
2:Using CPU #1
1:Using CPU #0
2:Beginning a continuous self-test to check your computer.
2ress Stop to end this test.
1:Beginning a continuous self-test to check your computer.
1ress Stop to end this test.
2:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
1:Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
1:Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
2:Test 4, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
1:Test 4, 800000 Lucas-Lehmer iterations of M157695 using 8K FFT length.
2:Test 5, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
1:Test 5, 800000 Lucas-Lehmer iterations of M155649 using 8K FFT length.
2:Test 6, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
1:Test 6, 800000 Lucas-Lehmer iterations of M153599 using 8K FFT length.
2:Test 7, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
1:Test 7, 800000 Lucas-Lehmer iterations of M147455 using 8K FFT length.
2:Test 8, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
1:Test 8, 800000 Lucas-Lehmer iterations of M143361 using 8K FFT length.
2:Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
1:Test 9, 800000 Lucas-Lehmer iterations of M141311 using 8K FFT length.
2:Test 10, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
1:Test 10, 800000 Lucas-Lehmer iterations of M135169 using 8K FFT length.
2:Test 11, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
1:Test 11, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
2:Test 12, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
1:Test 12, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
2:Self-test 8K passed!
2:Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length.
1:Self-test 8K passed!
1:Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length.
2:Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length.
1:FATAL ERROR: Final result was 35EF0055, expected: 0555250D.
1:Hardware failure detected, consult stress.txt file.
1:Torture Test ran 16 minutes 48 seconds - 1 errors, 0 warnings.
1:Execution halted.

2:Torture Test ran 16 minutes 48 seconds - 0 errors, 0 warnings.
2:Execution halted.

Can anyone shed any light onto this one?

spb251272 · 20 Mar 2007 at 22:04

Your system is still unstable, which is why it's failing orthos. Are you not using the bios to change your voltage? This is the best way to alter your settings - better than windows based tweaking programs. Just try upping your vcore a step at a time until orthos becomes stable. Make sure you keep an eye on temps with coretemp. You don't want them to exceed 60c.

Jaaay · 20 Mar 2007 at 22:11

spb251272 said:
Your system is still unstable, which is why it's failing orthos. Are you not using the bios to change your voltage? This is the best way to alter your settings - better than windows based tweaking programs. Just try upping your vcore a step at a time until orthos becomes stable. Make sure you keep an eye on temps with coretemp. You don't want them to exceed 60c.

Ok, ive tried setting the vcore manually, but it just keeps and restarting, doesnt even post. Normally i have to short circuit the CMOS.

If i do increase the vcore, what about the other voltages, keep them at normal?

spb251272 · 20 Mar 2007 at 22:24

I would take a step back, start with stock speeds, and manually set the vcore to 1.325. Make sure your memory is on a divider so that it is not being overclocked (just until you know the limit of your cpu). Then start to raise the fsb a little at a time until it becomes unstable. Then you can increase vcore a step at a time until it is stable. Repeat this until your temps are hitting mid 50's when running orthos - I wouldn't raise the vcore any higher than about 1.55 personally. Key to this is use the bios and take it slowly. It takes a while to get a stable overclock, so try to be patient with it

benktlottie · 20 Mar 2007 at 22:26

Jay™ said:
Ok, ive tried setting the vcore manually, but it just keeps and restarting, doesnt even post. Normally i have to short circuit the CMOS.

If i do increase the vcore, what about the other voltages, keep them at normal?

Man, i aint being funny, but youre scaring me with your approach! LOL

Set the Vcore to 1.425 in the BIOS. Then try and run Orthos @ 3.2ghz. If Orthos is OK for a few hours, try 3.25ghz. Then 3.3ghz. If Orthos fails, @ any of those speeds the change the BIOS voltage to 1.45, then repeat Orthos tests. Stop worrying about what all the different Orthos errors mean, they all mean UNSTABLE and risking your hardware! Only tinker with what you can afford to replace mate. Keep an eye on the temps, try to keep under 60 degrees LOAD.

Chris Beard · 21 Mar 2007 at 00:05

benktlottie said:
Man, i aint being funny, but youre scaring me with your approach! LOL

Set the Vcore to 1.425 in the BIOS. Then try and run Orthos @ 3.2ghz. If Orthos is OK for a few hours, try 3.25ghz. Then 3.3ghz. If Orthos fails, @ any of those speeds the change the BIOS voltage to 1.45, then repeat Orthos tests. Stop worrying about what all the different Orthos errors mean, they all mean UNSTABLE and risking your hardware! Only tinker with what you can afford to replace mate. Keep an eye on the temps, try to keep under 60 degrees LOAD.

How is unstable risking your hardware?

simonnance · 21 Mar 2007 at 00:24

my E6400 does stock 2.1Ghz on 0.95V

3.5Ghz on 1.437V ish.

Stock volts is 1.3V if memory serves, so shove it in at 1.4V, and start upping the FSB. If it craps out, try dropping the multi and try again, if its the NB, not your CPU, you'll still get errors, and you'll need to up the Vnb. Likewise, try and take the ram out of the equation until you have to!

what you want to know is:
Max CPU MHz
Max NB FSB
Max RAM MHz

then combine the three to get an optimal mix.

Posting specific ORTHOS errors i dont think is likely to diagnose the specific error..... not sure the program is advanced enough to do anything other than tell you if its stable or not, rather than detecting WHAT isnt stable (other than which parts in particular you are stressing, RAM, CPU, or mix).

smsmasters · 21 Mar 2007 at 01:20

My e6600 does:

3.0ghz at 1.30V
3.2ghz at 1.325V
3.6ghz at 1.43V

benktlottie · 21 Mar 2007 at 07:39

Chris Beard said:
How is unstable risking your hardware?

You being serious ?

OK, here goes....

OP said in his last post, he played with the voltage and no the PC keeps resetting itself. Well, if he bumped up voltage, the the components could be overvolted, which could cause too much heat, and could make his RAM or processor go pop! Its common knowleage that if you push a processor too hard with inadequate cooling, they can die...MOSFETs can go pop if they get too hot. Its like if you overclock you graphics card too much, you can fry that aswell. Heat is a major factor when overclocking, which is why more than one person in this thread has suggested a overclock with the processor not exceeding 60 degrees. Overclocking can also trash your operating system.

I once blew up a socket 478 Extreme Edition processor and a 3.4ghz 478 through over-volting in my early days of overclocking!

benktlottie · 21 Mar 2007 at 07:39

simonnance said:
my E6400 does stock 2.1Ghz on 0.95V

3.5Ghz on 1.437V ish.

Stock volts is 1.3V if memory serves, so shove it in at 1.4V, and start upping the FSB. If it craps out, try dropping the multi and try again, if its the NB, not your CPU, you'll still get errors, and you'll need to up the Vnb. Likewise, try and take the ram out of the equation until you have to!

what you want to know is:
Max CPU MHz
Max NB FSB
Max RAM MHz

then combine the three to get an optimal mix.

Posting specific ORTHOS errors i dont think is likely to diagnose the specific error..... not sure the program is advanced enough to do anything other than tell you if its stable or not, rather than detecting WHAT isnt stable (other than which parts in particular you are stressing, RAM, CPU, or mix).

Good post!

Chris Beard · 21 Mar 2007 at 11:13

benktlottie said:
You being serious ?

OK, here goes....

OP said in his last post, he played with the voltage and no the PC keeps resetting itself. Well, if he bumped up voltage, the the components could be overvolted, which could cause too much heat, and could make his RAM or processor go pop! Its common knowleage that if you push a processor too hard with inadequate cooling, they can die...MOSFETs can go pop if they get too hot. Its like if you overclock you graphics card too much, you can fry that aswell. Heat is a major factor when overclocking, which is why more than one person in this thread has suggested a overclock with the processor not exceeding 60 degrees. Overclocking can also trash your operating system.

I once blew up a socket 478 Extreme Edition processor and a 3.4ghz 478 through over-volting in my early days of overclocking!

So we're talking about heat, not instability. Ok, sorry, I got confused.