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

Associate
Joined
7 Mar 2007
Posts
996
Location
Birmingham, UK
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.
1:Press 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.
2:Press 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?

screeniewg2.jpg

Cheers,
Jay
 
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 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
 
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)
 
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.
2:Press Stop to end this test.
1:Beginning a continuous self-test to check your computer.
1:Press 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 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?
 
MoodyB said:
Put a fan on it if you're trying to get 3ghz+ out of your cpu. The Ninja is a good heatsink, but running it passively cooled with an overclocked cpu is not the best idea.

Not sure how to actually attempt to put it in a DS3.. Everything gets in the way of the huge thing. Ram sockets etc. I'll try now and see what i can do.
 
Ive got the Scythe Ninja fan on now.
Lower temps :D

Upping my vcore still isnt working though, do i need to up any other of the other voltages or keep them at normal?
Ive tried 3.2Ghz (410) @ 1.45v i think it is, well the highest 1.45 setting.
Still wont pass or even boot if i change the voltages.
Running 3.2Ghz now with all voltages on AUTO it boots, but i dont think its stable.
 
Big.Wayne said:
Hi Jay™

surely 3.2GHz is 8x400, you wrote 210? In your boots I would start again, and I would 'manually' set most the of the voltages to a low value and off you go, slowly crank it up.

You need to find out how fast your motherboard can run, how fast your memory can run and finally how fast your processor can run, its not a good idea to try to find this out all at the same time! :)

It's easy to get the impression that overclocking is a doodle and I guess it is when you know how, but when your starting it isn't easy, best to read up what other people are doing and take lots of notes.

[edit] oh btw don't worry about the details when Orthos Prime fails (I noticed you were pasting lines and lines of results from that program). If it errors you just know something is wrong deep down!

Thanks for replying.

I think im stable at 3.279Ghz (410x8.0) and 1.3250v. Been running Orthos for an hour now.
 
Back
Top Bottom