View Full Version : Burn in Question
train22
09-02-01, 11:37 AM
I was wondering how long people run the burn in before advancing to the next level on the multiplier, for instance using a brand new cpu at max mult at lets say 11.5 you burn burn burn, how long would you burn until you can try 12? Days? Weeks?
nolan_3d
09-02-01, 12:00 PM
from what I understand, the burn in is just to test for stability, if it runs long enough at full load for you to consider it stable then you can try for the next step, burning it in does not garuntee any higher clock speeds
TranceBear
09-02-01, 12:14 PM
Well I was able to get a lower v-core after a month of intense benchmarking and gameplay. This was not 24 hour running, but several hours a day. I was able to get higher and higher mhz as the time went on, I do not know if it was the burn-in or my CPU just stop putting up a fight.
I just try to up the MHz or lower the Vcore from time to time, and sometimes it works! Just run some very CPU demanding programs, for some time (2-3 days) and see if it helps.
How long have you been burning now?
train22
09-02-01, 04:11 PM
well Wlater, I've been burning up as much as I could and to it seems to really help. Almost 24 hours of burning as of now and before the burn I was only able to go to the 11.5 mulitplier for the defualt FSB (11.5x133) and now it lets me hit 12. This means my cpu will be able to handle 1600 easy so I can now go and lowr the mult and max my FSB. I was not even able to boot at 1600 before the burn, it would reboot on startup but now it lets me go into windows and survives the SETI for a few minutes but as soon as I get smothing else going at the same time or I bring up the visual of SETI it crashes so it's a matter of time untill it gets used to it, I went back to 11.5x133 and will run that till tomorrow morning, see what the brings me to, as soon as I can stable-run the 12 mult I will start burning then and then who knows maybe I'll hit 12.5. It's a matter of luck really.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.