Quote:
Originally Posted by Prong 
If it would cause system crashes then you would know something is wrong and that your system is not stable and would go back to tweaking. You can also have system crashes while prime95, linx, IBT or OCCT is running. I have never heard of a bad oc that cause corrupted files. If it is not stable your daily usage would give the signals for its unstability.
I have ran all these tests day and night then strated to find it pretty funny when I saw couple of chips even failing these tests at stock settings although causing no problems with daily usage for years.
|
It all depends on how quickly you want to find out if there is instability in the system. If it needs playing games, encoding a video while watching a movie, editing a photo or video and writing a doc and browsing the net, it will take me a couple of days to figure if that BLCK jump from 160 to 162 is stable or not. With LinX, typically it dies within 1-2 hours if the system is not stable. Economies of scale!
BTW, if any of these tests fail: there is a problem and the system will die on you randomly even if you have successfully played games for 3 days straight on without a crash. It will die at a very in-opprtune moment (like that special scene in the movie or just before you go to save that doc you were working on). The thing about computers is that they behave in a deterministic fashion: you pass same data, it will give you same results. If the results are different once in a million times, your computer is a fail, and you need to go back and figure which component (cpu, memory, PSU, NB etc.) has failed you.
So, make sure after the final OC is settled on, you pass 100 passes of LinX (which btw is the best cpu and memory tester) with max memory setting on a 64-bit OS.