Stable in orthos for only 25-26hrs w/ E8400

[err]

CPU: Intel E8400
Overclock: 9 x 423 = 3.8Ghz
CPU-Z reported Voltage: 1.265V
CPU @ 100% temp varies between 49-56C (Yes my room temperature fluctuates)

I was able to run Orthos stable for more than 24 hours.
Dual instance of Prime95 also ran stable for at least 6 hours.

However Orthos died when I was asleep and my guess is that is between 24-30 hrs of run time. The system itself never crashes and vista is rock solid for at least 72 hrs.

The big million $ question... If I'd like to run at 3.8Ghz on this speed? would it make sense to give it more voltage juice to my Proc? Should I leave this on the current settings? I'd really hate to increase voltages unecessarily.

Thought?

 

[RussianSensation]

Originally posted by: err
The system itself never crashes and vista is rock solid for at least 72 hrs.

The statement is contradictory. Does the system crash after 72 hours or it never crashes unless you run Orthos?

You can safely increase voltage since 1.265 is very low to say 1.2875.

 

[err]

The system never crashes once....

Orthos does crash, but it did not affect the OS... Basically orthos just stopped processing the cpu stress test...

OK maybe I am being stupid here.. but is it a correct assumption that Orthos will NEVER stop running by default unless you stop the process? Does it only run for24 hours or something by default?

Thanks!

 

[MarcVenice]

24 hour orthos stable ? I'd say your good to go. Just leave it at 3.8ghz, in fact, I never run orthos for more then 8 hours. IF you ever encounter a bsod or instability issues, it's time to start tweaking again. But if you don't, I'd ignore it. Orthos isn't the be all and end all of overclocking stability.

 

[GundamF91]

Orthos never stops without a fault unless you tell it to stop. Orthos will stop when a checksum fault is detected, and it means there's instability in the system. It does not need to be a full BSOD type crash to call a system unstable. So in your case, the system instability occured after 24 hours or so.

Is this your primary system? I wouldn't want to run on a system that I don't trust. I would say you back off on the OC, or up the vCore by 0.02. It's probably needed to make it completely stable at 3.8Ghz. Your vCore's pretty low. What's the default Intel vCore setting when you dont' OC? You can safely go 10% beyond factory setting. 20% or more is pushing it. Or you can back off on OC, fact is 50-100mhz is nothing in grand scheme of things these days.

 

[Anubis]

im willing to bet if you up the CPU voltage a notch itll fix your orthos issue, however a 16+ hour orthos is generally fine, i ran mine for ~20 and figured good enough 440x9 on my 8400

 

[taltamir]

it should be stable forever... if it isn't that means it makes errors without BSOD... so what happens when it makes an error during windows update a month from now? corrupt OS files that's what...
Just give it sometime and your system will be jacked.
Either up the voltage or scale it back.

EDIT: did you have anything else on that isn't set to run at boot? in vista when it BSOD's I have seen it do a memory dump and restarts the computer by itself...
I find it odd that orthos just shut itself down...

Makes more sense to me that the computer BSODed and you didn't realise it due to the auto restart.

 

[Anubis]

Originally posted by: taltamir
it should be stable forever... if it isn't that means it makes errors without BSOD... so what happens when it makes an error during windows update a month from now? corrupt OS files that's what...
Just give it sometime and your system will be jacked.
Either up the voltage or scale it back.

EDIT: did you have anything else on that isn't set to run at boot? in vista when it BSOD's I have seen it do a memory dump and restarts the computer by itself...
I find it odd that orthos just shut itself down...

Makes more sense to me that the computer BSODed and you didn't realise it due to the auto restart.

vista lets you see uptime right from the system properties doesnt it, really easy to see if it was orthos quitting or a reboot

 

[aigomorla]

Use Prime95 25.4 or higher.

And use that. I noticed Orthos is kinda buggy and sometimes will pass on a lot of occations where prime95 wouldn't.

Or you can ask the people in DC on how to load up 2 instances of F@H and see if it fails there. If thats the case, yeah, your voltage will need a bit tweeking. Maybe 1-2 set higher then where its at.

 

[err]

Originally posted by: GundamF91
Orthos never stops without a fault unless you tell it to stop. Orthos will stop when a checksum fault is detected, and it means there's instability in the system. It does not need to be a full BSOD type crash to call a system unstable. So in your case, the system instability occured after 24 hours or so.

Is this your primary system? I wouldn't want to run on a system that I don't trust. I would say you back off on the OC, or up the vCore by 0.02. It's probably needed to make it completely stable at 3.8Ghz. Your vCore's pretty low. What's the default Intel vCore setting when you dont' OC? You can safely go 10% beyond factory setting. 20% or more is pushing it. Or you can back off on OC, fact is 50-100mhz is nothing in grand scheme of things these days.

This is my primary home workstation. I can afford downtime on this thing with other work pcs, laptop, old pcs, etc ...

I'll try upping the vcore a bit... E8400 default is 1.15... at 1.24 i am a little below 10% increase

 

[err]

Originally posted by: taltamir
it should be stable forever... if it isn't that means it makes errors without BSOD... so what happens when it makes an error during windows update a month from now? corrupt OS files that's what...
Just give it sometime and your system will be jacked.
Either up the voltage or scale it back.

EDIT: did you have anything else on that isn't set to run at boot? in vista when it BSOD's I have seen it do a memory dump and restarts the computer by itself...
I find it odd that orthos just shut itself down...

Makes more sense to me that the computer BSODed and you didn't realise it due to the auto restart.

Nah I am pretty sure this computer did not booted. All my apps, my remote desktop connections, etc are still in tact.

Orthos itself did not shutdown, but it became "IDLE" instead of "GO".

 

[tigersty1e]

Yup...

Did you get a popup saying Vista shutdown Orthos?

Instead of crashing or BSODing in Vista... the OS just shutdown Orthos on my previous attempt to go to 460 x 7 on my system.

 

[lopri]

If you have run Orthos LargeFFT for more than 8 hours successfully, chance of running into a trouble due to CPU instability < chance of running into troubles due to buggy OS/drivers/software. IMHO, of course.

Now, it'd be a different story if you run a same type of work load 24/7. (such as folding machines or servers)

 

[imported_wired247]

I kept getting rounding errors in prime95 after 12 hours or so, until I bumped MCH (northbridge) voltage a tiny bit.

 

[Idontcare]

Originally posted by: wired247
I kept getting rounding errors in prime95 after 12 hours or so, until I bumped MCH (northbridge) voltage a tiny bit.

Was this with small or large FFT's? (or blend?)

My experience has been small FFT -> Vcore while large FFT -> NB/MCH. Is this expected or have I just been lucky guessing?

 

[VirtualLarry]

Originally posted by: MarcVenice
24 hour orthos stable ? I'd say your good to go. Just leave it at 3.8ghz, in fact, I never run orthos for more then 8 hours.

Good to go? When Orthos failed due to instability? That doesn't sound good to go to me.

Originally posted by: MarcVenice
IF you ever encounter a bsod or instability issues, it's time to start tweaking again. But if you don't, I'd ignore it. Orthos isn't the be all and end all of overclocking stability.

But he just did encounter an instability issue - with Orthos. So it is definately time to keep tweaking, to ensure stability.

 

[VirtualLarry]

Originally posted by: err
Orthos itself did not shutdown, but it became "IDLE" instead of "GO".

It didn't give you a red error? That's strange. I wonder if it does have some sort of time limit built in.

I agree with the other poster, use Prime95 25.5.

 

[LOUISSSSS]

Originally posted by: VirtualLarry

Originally posted by: MarcVenice
24 hour orthos stable ? I'd say your good to go. Just leave it at 3.8ghz, in fact, I never run orthos for more then 8 hours.

Good to go? When Orthos failed due to instability? That doesn't sound good to go to me.

Originally posted by: MarcVenice
IF you ever encounter a bsod or instability issues, it's time to start tweaking again. But if you don't, I'd ignore it. Orthos isn't the be all and end all of overclocking stability.

But he just did encounter an instability issue - with Orthos. So it is definately time to keep tweaking, to ensure stability.

he probably means instability such as windows freezing, windows rebooting randomly etc.
if those things (among others) never happen, then who cares if orthos crashes (in this case, stopping by itself and going idle).

orthos going idle or freezing isn't an "instability issue" in itself. if that were the case, my 2nd system would be instable due to the amount of times itunes encounters an error upon closing..

OP: run Prime95 V25.6 on SMALL FFT's (if your ram isn't overclocked and u can ensure that the ram is stable) for 24 hours, after 24 hours with all green lights you're good for normal system usage.

 

[brencat]

Unless you're using the PC for distributed computing or as a server, 24hrs Orthos is more than sufficient stability testing. In fact, for gamers or office apps users, 1/2 that time (12 hrs Orthos stable) is enough, IMO.

 

[VirtualLarry]

Originally posted by: LOUISSSSS
he probably means instability such as windows freezing, windows rebooting randomly etc.
if those things (among others) never happen, then who cares if orthos crashes (in this case, stopping by itself and going idle).

orthos going idle or freezing isn't an "instability issue" in itself. if that were the case, my 2nd system would be instable due to the amount of times itunes encounters an error upon closing..

Sure it is. If your application is causing apps to crash/freeze/exit, then you sure as heck do have an instability problem. Maybe your other system's itunes is crashing because of your overclock, if it normally doesn't crash.