Let me rephrase and add unto my statement as that was not entirely what I wanted to say.
The best stability 'test' in my opinion is to just use your PC as you do normally after you've run Prime or whatever for at least 30 minutes or so as you will usually BSOD in the first couple minutes. No more is necessary. I haven't found any application that stresses the CPU as hard as Prime or any other stress application so calibrating your CPU to be a 100% stable with it is meaningless as you'll have to compensate for the vdroop that happens under load. People with crappier motherboards have this issue more often and it generally isn't fixable via the BIOS. Stressing doesn't guarantee it's stable either as I've seen cases where people would get BSODs anywhere but under stress which could mean two things: fix the vcore or it might be a power state issue. But not everyone wants to run their clocks at 4.5GHz all the time. Back to tinkering with the OC then.
So why would you, after you OC, run Prime for hours upon hours only to find out your system is unstable after you try to use your PC for normal usage?
I find running Prime (or eqv) for hours a complete waste of time and energy as well. Why not simply test it the 'fun' way? You're obviously not meant to work with 'sensitive' data straight away as you might BSOD etc. You can do that when you feel it's stable. I do know it's not for everyone, I'm just putting out there how I do it.
Edit: Oh and moved to DP.
The best stability 'test' in my opinion is to just use your PC as you do normally after you've run Prime or whatever for at least 30 minutes or so as you will usually BSOD in the first couple minutes. No more is necessary. I haven't found any application that stresses the CPU as hard as Prime or any other stress application so calibrating your CPU to be a 100% stable with it is meaningless as you'll have to compensate for the vdroop that happens under load. People with crappier motherboards have this issue more often and it generally isn't fixable via the BIOS. Stressing doesn't guarantee it's stable either as I've seen cases where people would get BSODs anywhere but under stress which could mean two things: fix the vcore or it might be a power state issue. But not everyone wants to run their clocks at 4.5GHz all the time. Back to tinkering with the OC then.
So why would you, after you OC, run Prime for hours upon hours only to find out your system is unstable after you try to use your PC for normal usage?
I find running Prime (or eqv) for hours a complete waste of time and energy as well. Why not simply test it the 'fun' way? You're obviously not meant to work with 'sensitive' data straight away as you might BSOD etc. You can do that when you feel it's stable. I do know it's not for everyone, I'm just putting out there how I do it.
Edit: Oh and moved to DP.
