Thats the thing. My OC passed about 4hrs of Real Bench. Both stress test and benchmark. It then did a a run of about 4hrs gaming in the Division and BF1 no issues.
Then after a week, yesterday it wouldn't even load The Division, it was blue screening whilst it was loading.
R15 then xtu bench to find ballpark clock/vcore. 26.6 1344k for an hour, +.02v, play games. If I'm doing gpu also, 3dm for ballpark clock, xtu stress / heaven 1hr, play games.
R15 then xtu bench to find ballpark clock/vcore. 26.6 1344k for an hour, +.02v, play games. If I'm doing gpu also, 3dm for ballpark clock, xtu stress / heaven 1hr, play games.
R15 is Cinebench R15 which is a benchmark. 26.6 1344K is Prime95 26.6 running a custom burn test, in place FFTs with a minimum and maximum size of 1344K.
imo XTU and benchmarks are too easy to pass. I did an overnight run of XTU and crashed very fast in BF1. On the other hand P95 is incredibly demanding and in a not very realistic way. People can pass hours and hours of Prime and then crash opening chrome.
Nothing beats real world usage, but generally I find that if it can take 12 hours of Prime95 (on mixed) then it's unlikely anything else will upset it. That said, I only overclock CPUs these days: overclocking the RAM has no real-world effect and I was never any good at overclocking GFX. But Prime is pretty good on the RAM side as well.
R15 is Cinebench R15 which is a benchmark. 26.6 1344K is Prime95 26.6 running a custom burn test, in place FFTs with a minimum and maximum size of 1344K.
imo XTU and benchmarks are too easy to pass. I did an overnight run of XTU and crashed very fast in BF1. On the other hand P95 is incredibly demanding and in a not very realistic way. People can pass hours and hours of Prime and then crash opening chrome.
I do very similar to Doug2507 and it hasn't let me down yet - I use XTU to get a ballpark - once its passing and hour or two of that I up voltage very slightly (alternatively you could drop multi very slightly) and test cinebench - if its passing that so far its not fallen over on anything else. After all these years though I have almost a sixth sense for where actual stability is at and once I've got a ballpark from XTU can finesse it the rest of the way.
My testing methodology is overclock then play games, I don't see the point in doing endless stress test if you aren't using similar programmes. I don't encode videos etc so doing handbrake test and stuff like cinebench is pointless if I can play bf1 at 5.0ghz but cinibench would crash at 4.9 etc.You can be stable for hours on end in prime but five minutes of bf1 it will crash , as meridian said real world usage is best overall.
That is great if all you do is game and it holds upto gaming - but that doesn't mean the system is 100% stable and corruption could be creeping in somewhere. Even stress testing isn't bullet proof but a much better representation of all around application stability.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.