Hi Guys
I am just about to oc my cpu and was wondering how long should I run Orthos for, each time I increase the oc
To be honest i still stand by the fact tah stability should be judged by your needs.
Your cpu will never be taxed out as much as orthos and there is allthese people saying dont get quad ull onyl use 2 cores. Then its definitly never going to be taxed that much or get taht hot.
Judge it on your needs. Play your games, if they crash ok its an inconveniance so you make sure you save regularly while testing. if it does crash take the overclock down a bit.
4 hours orthos stable is the longest id run it then do the rest with testing on games and my own needs.
If you need to build a bridge for just you to cross something. Why make it so it can be used by a lorry when it only needs to be stable for your body weight ?
To be honest i still stand by the fact tah stability should be judged by your needs.
Your cpu will never be taxed out as much as orthos and there is allthese people saying dont get quad ull onyl use 2 cores. Then its definitly never going to be taxed that much or get taht hot.
Judge it on your needs. Play your games, if they crash ok its an inconveniance so you make sure you save regularly while testing. if it does crash take the overclock down a bit.
4 hours orthos stable is the longest id run it then do the rest with testing on games and my own needs.
If you need to build a bridge for just you to cross something. Why make it so it can be used by a lorry when it only needs to be stable for your body weight ?
Totally agree mate!
The only way I test to see if my overclock is stable is by just doing all the things my pc will be doing. If I can game for hours and do everything I need to then thats good enough for me.
My last setup, in which I had a Pentium D950 at 4.25GHz, couldn't run Orthos for more than 30 mins without an error. But I never had a single problem with it in the 13-14 months I used it.
But if it makes you feel better about your overclock then theirs no harm. I just think it's excessive to stress your processors at 100% for hours and hours when in reality your pc will never have to do that anyway.
I don't usually say this as i hate confronatation, but these two posts are absolutely rubbish advice.
Running prime etc... DOES NOT only involve stressing components 100%, it also tests how accurate the hardware is at its speed. A voltage starved cpu or chipset might not overheat, but the lack of volts make everything it does inaccurate. The stability of the system in general is tested, just not under heat. The RAM is tested as well to an extent and undervolted or too tightly overclocked/timed RAM will produce errors. Some say 'well it folds for hours', well it might be folding but its producing garbage, it 'games' for hours.. well one day it might well lockup or cause some save game corruption cause a few bytes got lost in the instability blackhole. Your OS might be fine for weeks and one day cause your RAM or cpu was unstable it totally blows its partition table. As for testing two cores on a quad only... seriously.. like i said, its not only about load and heat. However even that plays a big part, you test two cores and one day you use a nice encoder that cranks everything 100% and things get toasty.. opps why did the rig crash??
I've been overclocking longer than most, not showing off but i've done everything under the sun, water, phase, Peltiers.. only thing i never really done much was LN, you name it and can tell ya, a system might be stable for weeks and suddenly cave in. Testing gives a good scope on how stable you are. Simply put, if your PC can't pass a test at 4Ghz but can do it for hours at 3.6Ghz then it ain't stable. In most reasonable peoples minds, a stable overclock is a PC, that while overclocked, can do everything it can at stock speeds.
I don't usually say this as i hate confronatation, but these two posts are absolutely rubbish advice.
Running prime etc... DOES NOT only involve stressing components 100%, it also tests how accurate the hardware is at its speed. A voltage starved cpu or chipset might not overheat, but the lack of volts make everything it does inaccurate. The stability of the system in general is tested, just not under heat. The RAM is tested as well to an extent and undervolted or too tightly overclocked/timed RAM will produce errors. Some say 'well it folds for hours', well it might be folding but its producing garbage, it 'games' for hours.. well one day it might well lockup or cause some save game corruption cause a few bytes got lost in the instability blackhole. Your OS might be fine for weeks and one day cause your RAM or cpu was unstable it totally blows its partition table. As for testing two cores on a quad only... seriously.. like i said, its not only about load and heat. However even that plays a big part, you test two cores and one day you use a nice encoder that cranks everything 100% and things get toasty.. opps why did the rig crash??
I've been overclocking longer than most, not showing off but i've done everything under the sun, water, phase, Peltiers.. only thing i never really done much was LN, you name it and can tell ya, a system might be stable for weeks and suddenly cave in. Testing gives a good scope on how stable you are. Simply put, if your PC can't pass a test at 4Ghz but can do it for hours at 3.6Ghz then it ain't stable. In most reasonable peoples minds, a stable overclock is a PC, that while overclocked, can do everything it can at stock speeds.
Your cpu will never be taxed out as much as orthos and there is allthese people saying dont get quad ull onyl use 2 cores. Then its definitly never going to be taxed that much or get taht hot.
4 hours orthos stable is the longest id run it then do the rest with testing on games and my own needs.
Apologies, i thought you were the same guy that said he'd only test 2 cores on a quad. Vcore starvation might show earlier or later. I go for a full 24 hr cycle as i've seen it fail as much as 17+ hours into a test. However, that late in the game for a fail usually means its just about on the verge of the right vcore and one notch up usually sorts it.