burn-in before overclocking? How long? What tools?

x509

2[H]4U
Joined
Sep 20, 2009
Messages
2,630
I assume that watercooling the CPU and GPU, plus remounting the IOH/SB/MOSFET heatsink, will void the warranties. Especially if I lap the CPU. The system will include the ASUS P6T Deluxe 2, i7-920, ATI 5770 (vendor tbd), and 1 12 GB kit of Corsair memory. All in a Corsair 800D case.

So once I get this system put together, I want to do a burnin at stock settings to make sure that I don't have any defective components, with the stock air cooling on the 800D.

How long? A day? A week? More?

What tools? The same ones used to test stability at OC settings? I'm not trying to push the CPU or GPU to the max, just "exercise" them long enough to flush out bad parts. I'll probably run the latest version of memtest, regardless of what other tools I use.

I also want to benchmark my system at stock settings so that I can measure the improvement with overclocking the CPU, the GPU, and possibly the RAM.

Thanks.

x509
 
burn in... what does that mean? LOL

I waited about 3 hours maybe(basically after getting Win7 install and everything running smoothly), then went to 3.6, then just wanted more so went to 4.15... that is my current clock

i7 920 @ 4.15Ghz :D

oh and you could speed up burn in by running Prim95 or IntelBurnTest at stock speeds but I really dont think it is that big of deal.

WHY?

Because the new tech in the thermal pastes makes it unneeded, Personally would use MX2 or MX3 and just start overclocking

I personally use Intel Burn Test for stability checks because I have ran Prim95 and not had it fail when IBT made it fail, so now I use IBT.

RealTEMP to check temps

CPUZ for a good system overview

Used all the different PC marks/3d marks and only noticed a few hundred point spread difference from stock to 4.15Ghz... lol.. I dont OC for the points or the FPS
 
you dont need to burn in modern processors.. that is all done in the factory for you.. now if you just want to test the processor.. do 10-15 passes on intel burn test and your done..
 
There is really no reason to wait at all.

You are very unlikely to end up in a situation where your chip won't clock past a certain level at first, but magically will once the paste sets in or whatever. Chances are the only difference you will notice is 1-3C if anything.
 
Never heard of burning in the processor. I've only heard about letting the thermal compound set in, as GotNoRice mentioned.
 
I kick em off in the morning for a couple of hours stock speed idle in windows (test the sound, browse the web to check the nic, defrag the HD, then do some casual OCing while checking temps and using OCCT as it lets me set the % of cpu utilization which I set at 80%. Finger heat test/check all the aux cooling/heatpipes etc. If all looks good I let it run overnight and in the morning if all is still OK, mount it in the case and really go to work on whatever .
 
I kick em off in the morning for a couple of hours stock speed idle in windows (test the sound, browse the web to check the nic, defrag the HD, then do some casual OCing while checking temps and using OCCT as it lets me set the % of cpu utilization which I set at 80%. Finger heat test/check all the aux cooling/heatpipes etc. If all looks good I let it run overnight and in the morning if all is still OK, mount it in the case and really go to work on whatever .

+1

I run through the "normal" things and do an over night run of IBT and memtest to check that nothing is bad before I lap anything, once it's lapped your not going to get an RMA. After I have found the chip is good I then lap it and have fun. :D

Also, watercooling a cpu should not void the warranty, lapping sure will. And some video card mfg's don't like you messing with the cooler, some don't care so long as the card it self has no mod's/tampering which includes things as simple as using thermal adhesive to attach RAM HS's etc etc, same goes for mobo HS's.
 
I'm the OP. Big thanks to everyone who replied. :D

Sounds like I need to just "run" the system for a few hours before Iap the CPU, and then install the watercooling and then OC'ing. Of course, with watercooling, there is that big "soak in" period. ;) LOL!

x509
 
The only "burn in" time you ever need is the time it takes to install the OS. No sense in taking the chance of messing up the install, especially when the install time is limited by other things, not the CPU.
 
I forgot you mentioned WCing.

My "process" there is to assemble/mount the WCing in the case and let it leak test while I am making sure the board/cpu/etc. is ok.
 
I forgot you mentioned WCing.

My "process" there is to assemble/mount the WCing in the case and let it leak test while I am making sure the board/cpu/etc. is ok.

Bill,

I had thought that the "best practice" is to do the leak-test while the motherboard is not powered up. That way, if there is a leak, you don't run the risk of a short circuit.

Thanks,

x509
 
Bill,

I had thought that the "best practice" is to do the leak-test while the motherboard is not powered up. That way, if there is a leak, you don't run the risk of a short circuit.

Thanks,

x509
He didn't say to turn on the PC anywhere in his post.
 
He didn't say to turn on the PC anywhere in his post.

Well, if you read his post, he does say:

let it leak test while I am making sure the board/cpu/etc. is ok.

To me, "making sure ..." means the board, etc is powered on. If I'm wrong, then, OK, I'm wrong.

x509
 
To me, "making sure" means making sure that you don't have a shit-ton of water leaking out of the loop and pouring down onto your components. It doesn't necessarily imply that the computer is powered on.
 
Well, if you read his post, he does say:

let it leak test while I am making sure the board/cpu/etc. is ok.

To me, "making sure ..." means the board, etc is powered on. If I'm wrong, then, OK, I'm wrong.

x509

He also said he does his "making sure" with the motherboard, etc. out of the case.
 
Back
Top