Is it safe to run prime overnight?

Justintime said:
Anyway, i should keep my mouth shut and carry on, arguing something pointless like this always drives my blood pressure up.
Click to expand...


justin , you have your way of doing things and others have theres :)
are you telling me you have never had a bsod? and needed to tweak
are these customer machines your talking about because if moneys involved then that would shed a different light on this for me.....i would be annoyed if i built a rig sent it of only to get an email saying it kept failing which ment havng to ship it back at my time and cost. from that point of view i agree with your 24 regime as you put it but for my own rig 'nah' if i did that everytime i tweaked an overclock id never be on it...just constantly in a loop of prime 95 and burn test.
 
Its not like you need to do it every day... Just an initial overclock followed by a stability check. Another thing I do is run a prime check while stressing my gpu. As heat is a cause of downfall. And prime alone won't give realistic inner case temperatures without the gpu being in full swing as well. cutting corners is what causes crashes. And personally I haven't seen a blue screen in years. I've never seen one in windows 7. And the only CTD I've had is skyrim. And that was caused by an audio bit rate issue. I can imagine a few windows haters could actually put their issues down to rushed overclocks.
 
I do that, not on the first go mind only when prime stops failing and I have it nearly setup to be stable that way it won't fail and stop 15 mins after I've fallen asleep :D

My friends used to think what a waste, if it's in windows and there are no bsod's after stressing it with games/rendering programs it's stable. Only when they came to do some proper long video rendering it was bsod mania for them.

Sometimes I carry on using the PC during the Prime tests just to watch a bit of video or browse forums, don't know how that affects the stability but surely it'd help bring out the flaws within Prime instead of hinder it.
 
cammy5477 said:
justin , you have your way of doing things and others have theres :)
are you telling me you have never had a bsod? and needed to tweak
are these customer machines your talking about because if moneys involved then that would shed a different light on this for me.....i would be annoyed if i built a rig sent it of only to get an email saying it kept failing which ment havng to ship it back at my time and cost. from that point of view i agree with your 24 regime as you put it but for my own rig 'nah' if i did that everytime i tweaked an overclock id never be on it...just constantly in a loop of prime 95 and burn test.
Click to expand...

I have customers yes, however i like my own pcs stable too. I've not had an overclocking related BSOD, Agility 3 drives especially in their earlier firmwares is what caused 99% of mine this year, another was driver related (keeping my audigy 2 ZS may not be such a brill idea).
 
I have to agree with the need for testing, and with a few programmes/methods. It can work out those awkward niggles that you otherwise miss, which could cause a whole lot of seemingly random bugs and crashes.

Case in point - my 4.5Ghz settings were running fine, ten passes of IBT maximum (at about 15GB memory size, so about 10 mins a run), 100 passes of standard 1GB, linpack temperatures were reasonable (peaking at mid 70s, gaming was in the 50s). Ran Prime 95 x64 blend mode, about 13 hours in I started using internet in the background whilst Prime was still going and after a while I got a BSOD (uncorrectable hardware error) :)

If I'd left it with IBT then I'd never have realised the system wasn't quite there, but might have been subject to a lot more wierd glitches etc, as it seems the system must have been a little on the edge.

As it is, the RAM's XMP required it to go 1.65v for 1600Mhz (which I hadn't realised at first) so I've stepped that back to 1.5v JEDEC settings and 1333 rather than XMP as per Intel's recommendations on memory voltage, I'm running 4 sticks so that might have been the issue, also stepped it back with the same voltage to 44 multi rather than 45 to reduce the load slightly, and will need to do the full retest again.

Slow, but at least once I get the pass criteria right, I'll be confident my system is 99% solid afterwards, I intend to encode, so whilst it won't be as hard as prime/linpack, I do need a system that can hold up to high load for long periods.
 
Last edited:
Folding at home or SETI are other pretty strenous tasks that require a rock solid stable system, and theyll work a cpu as hard as prime.
 
Nope, but theyre very strenous programs that will soon expose any instabilities. Even some games will throw up hissy fits with supposedly stable oc's. Bfbc2 was notorious for this, quite a few people with supposedly stable clocks had issues in this game as it's pretty cpu dependent.
 
Exactly, this is why although I'd like to rush, I'd rather take some time.
I'd rather run completely at stock and forsake the extra 20% than run unstably, as it's only my encodes and hair colour if I start getting crashes, glitches and the likes (well, the ones you don't expect when overclocking and testing things haha)

It should run nicely cool and quiet with the tranquillo if I opt for the stock option, the intel stock cooler is terrible, it went straight into the 80s when I tested the chip with linpack and the board at default/auto settings. :)
 
Last edited:
setter said:
It's fine to let it run overnight. If your cooling is good you dont have to worry. LinX or intel burn test are other stress testers which work well. Besides, any modern cpu will shut down when it hits its limit. Ive had cpu's that were 8 hours+ prime stable, yet failed LinX/ibt in minutes.
Click to expand...

+1 this. And like WJA96 said, if yo overnightur not comfortable with prime running over night then back off the overclock :)
 
You must log in or register to reply here.
Back
Top Bottom