• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

4ghz...finally!!!

I think it's silly to not stability check with a long orthos session. Even if everything seems to be running fine, your video encoding might be making little mistakes. Or when you defragment, things might slowly become corrupted. Nobody wants that to happen.

Seems especially foolish as you only have to go without the machine for one evening if you start and finish at bed time for example.
 
Agreed any clock that is not tested orthos or prime stable for a long period of time is a useless clock.

There is no excuse not to test whether your cpu can calculate data effectively.

Just because it doesn't crash or it can encode video does not make a clock valid.

Unless it completes caclulations error free can it be deemed to be doing its job.
 
tastyweat said:
I can never be bothered with orthos - as long as it doesn't crash in games/when encoding video - that's stable.


Nope sorry its not.

If the pc errors after a few hours of orthos its not doing its job correctly.
 
Well it still won't stabilise with 1.57, managed 4 hours so its getting there. Up to 1.6v now but heat is starting to creep in - 59c load :(. We'll see how it goes.

BTW anyone wanting to start a donation thread for a replacement conroe for me after this one dies please feel free to do so :D
 
joeyjojo said:
I think it's silly to not stability check with a long orthos session. Even if everything seems to be running fine, your video encoding might be making little mistakes. Or when you defragment, things might slowly become corrupted. Nobody wants that to happen.

Seems especially foolish as you only have to go without the machine for one evening if you start and finish at bed time for example.


Not foolish when you change your components & overclock/change settings frequently - I'd be running orthos almost every night by your standings.

And I never defragment - waste of time! I tend to perform a fresh windows install every 2-3 months (tops)... I just do a full format and start a fresh.

If it's ever made mistakes while encoding video - I've never noticed. And I've encoded on a machine that is unstable enough not to be able to run 3d (and that's memory causing the reboot - bot cpu/graphics - which is what would be most likely to affect encoding).

If I get a blue screen/lock up - I find out why and adjust - it doesn't happen often.
 
easyrider said:
Agreed any clock that is not tested orthos or prime stable for a long period of time is a useless clock.

There is no excuse not to test whether your cpu can calculate data effectively.

Just because it doesn't crash or it can encode video does not make a clock valid.

Unless it completes caclulations error free can it be deemed to be doing its job.


No matter what you say - I'll never waste my time testing with orthos.



If it can do what I want it to do without crashing - then it makes it valid for me and that's what counts! Not whether you think it's stable or not.
 
trojan698 said:
lol yeah I'd be wary about putting any more than 1.6v through it personally


Damn - with my Tuniq I had to use 1.75V to reach 4.1GHz lol

Temps never broke 60 under load (special circumstances of course)

I'd never do that in my case though - the temps would skyrocket!

I tend to not go over 3.9GHz with the chip in my case & that's stable @ 1.55V (set in bios - not sure of actual V)
 
tastyweat said:
If it does everything I want it to - then yes it is.


OH no it isnt!

there is no excuse not to run orthos overnight....
I think you may be scared that it will fail and your clock is BS TBH.
Us hardcore enthusuiasts like me and w3bbo will deem it a failed clock.
 
easyrider said:
OH no it isnt!

there is no excuse not to run orthos overnight....
I think you may be scared that it will fail and your clock is BS TBH.
Us hardcore enthusuiasts like me and w3bbo will deem it a failed clock.


Deam it what you want - works fine for me. And like i said - that's what counts, it's end user preference.

Heh... the 4.1 would've failed without a doubt lol - that clock wouldn't even run through '06 - just got a nice 12.6s Super Pi 1m
 
Personally I don't think any Orthos run proves TOTAL stability as a 12hr run could fail at 12hrs 1 min. However an 8hr or 12hr run is usually what is expected as a minimum before any serious overclocker declares his/her overclock stable.

If you regard your overclock stable then good luck to ya, I don't have a problem with that and sure, posting a 4ghz overclock does come with it a large amount of bragging rights, but if you can also post with it a decent orthos run then there can be little doubt of a 'successfull' overclock. Orthos/P95 isn't the be all and end all as it only gives an indication of stability, but for now it is the most accepted method of stability testing imo.
 
Little update before I turn in for the night.

2hrs.jpg


6 hours to go but I'll leave it running overnight and see if it passes, should be 12hrs by then....hopefully :cool:
 
tastyweat said:
That's not 4GHz... you're off by 0.4GHz!!!

lol... only kidding mate -gl in your quest :)

0.4mhz, 0.4ghz would be 400mhz(3.6ghz) ;)

Nice overclock, if it passes move on to large FFTs and small FFTs. My experience is that large FFTs will put most strain on your cpu.
 
I had to run 1.75v just to get 4mins 24seconds on orthos :o (@ 4ghz)

and temps went waaaaay up.. to like 80degrees :P
 
Back
Top Bottom