Sign in with
Sign up | Sign in
Your question

dumb do you 'burn in' a new comp?

Last response: in CPUs
a b à CPUs
May 30, 2002 5:09:50 PM

I am in the process of building a new computer at the moment, and this will be my second. I've read stuff about people "burning in" their new computers for 24, 48, sometimes 72 hours. What does this mean? Running it nonstop? Is it really necessary? How does it help?
May 30, 2002 5:45:15 PM

Most people run CPU intensive things in a loop like 3Dmark2001se or prime95. You can also do things like encode mp3. Just put your CPU to work and keep it busy.

<b><font color=green>Garbage Can?</font color=green></b>
Related resources
a b à CPUs
May 30, 2002 5:51:41 PM

For how long though? I don't really want to NOT use my computer for a day after it's been built :)  Maybe a rigorous routine of Jedi Knight 2 and Return to Castle Wolfenstein with 4x AA @ 1024x768 and all details set to full will work?
May 30, 2002 5:58:31 PM

yeah running JKII on full is a far more enjoyable way of seeing how stable the computer is, i recommend this way.
May 30, 2002 6:18:33 PM

Play RTCW till your eyes crust over. If it doesn't crash, consider your PC "Burnt". If you're burning in to test temps, use Toast.exe (search in Google) and monitor with MBM 5.0. It will push your CPU and stress test you to the max. If you pc runs, it runs, but its not fun to find out you put your HS on backwards AFTER your CPU burnt while playing solitaire.

Life's a hole...dig it. - Joe Dirt
May 30, 2002 6:21:02 PM

If you are checking for stability, longer is generally better. Most of the time, I do it while I am sleeping or at work so I can use my PC when I am at home. Of course, if you are worried about your temps, you might want to be around to check it once in a while.

That is a nice <b><font color=green>Garbage Can</font color=green></b> you have there!
May 30, 2002 6:38:00 PM

computers are just machines. You don't really need to "burn it in" ... on my part i do have a theory about working out the bugs in the software. At first it won't work the way you want it but eventually after playing around with it you get it to the way you want it.

as for the hardware.. it's just silicon ... and you don't need to have it running all the time, but your also not suppose to power it down and up 50 times a day. that'll kill your hardware faster.

what i notice most people do is they power it up in the morning let it run all day then before going to bed the turn it off.

Hope that answered your qestion.

<A HREF="" target="_new"> My Rig </A>
May 31, 2002 7:17:26 AM

Rtcw sucks for overclocking testing, I had my fsb at 153, and sandra would crash it, so would prime95, but rtcw ran fine, now a game which STRESSES a system, MOHAA, that game ass rapes a system, any kind of instability will be found and exposed roughly by that game.

:wink: The Cash Left In My Pocket,The BEST Benchmark :wink: