| Author |
Message |
Sythro
384Mb of RAM
Age: 26
Joined: 08 Dec 2003
Posts: 464
|
|
I put this article in the Overclocking section because this topic does pertain to overclocking in one or more ways.
I in no way take credit for the methodology explained in this guide. I mostly took the methodology from
Guide on How to Burn in Your CPU and ammended it with my own thoughts.
Introduction
If you've ever wanted to improve your CPU's temperature while at stock speeds or have hit a wall while overclocking, burning your CPU may help you. Though this guide is based around an AMD chip, I'm sure you can use the same methodology for an Intel chip.
What is burning in your CPU?
Burning in your CPU is the process of slowly pushing your processor to either (a) it's maximum stable clock rate or (b) minimum stable voltage and then running it, with a full workload, at that speed or voltage for a decent amount of time (2 days --> whenever your heart is content).
Why Burn-in in the first place?
Subjective reviews of burning in a CPU have found that overclocking potential increases due to the process. This is two fold:
1) You'll be able to push the processor to a higher speed while maintaining stock voltage (which is important for processor longevity. Increasing core voltage can be detrimental to the processor).
2) You'll be able to run the processor at stock speeds with a lower core voltage (meaning the processor will use less electricity and run cooler as well).
As an example, let's take an Athlon X2 4600+, which runs at 2.4 Ghz stock (12x multiplier * FSB speed). Let's say that your maximum overclock was 230 Mhz on the FSB (230 * 12 = 2760). After the Burn-in process, you may be able to squeeze more out of that processor.
What kind of results can I expect?
Some CPU burn-ins will result in an appreciable gain while others net virtually nothing. I'm currently working on an Athlon X2 3600+ (Brisbane) and I hope to push it further (details below).
As far as I know, no scientific evidence has been found to support the idea that burning in your CPU will increase its overclocking potential. However, enough people have been experiencing positive results that there must be some merit to the claims.
Burning in your CPU apparently nets better results when it's brand new and not 2 months+ old. You can try to burn it in afterwards, but your results may not be as good as they could have been had you burned the CPU in when it was new.
Da Process
Here are some tools that you'll need (depending on if your motherboard supports it):
1) Prime95 or Orthos (to Stress CPU. I like Orthos' interface better. Plus it has built-in dual core support) - Prime95, Orthos
2) Super PI (another stress tester) - Super PI
3) CPU-Z (to read your voltage / speed / ram timings) - CPU-Z
4) CrystalCPUID (may be needed if your motherboard doesn't support voltage lowering) - CrystalCPUID
5) SpeedFan (just to measure temperatures) - SpeedFan
There are 2 methods I've found to burning in your CPU. Both apparently work - though I've only used method 1.
Method 1 - Undervolting your CPU
Step 1: Set your CPU and ram to stock speeds and timing
Step 2: Using either your BIOS or CrystalCPUID, lower the voltage to your CPU by 0.025v. (e.g. 1.275 from 1.30 volts)
Step 3: After you lower the voltage, run either Prime95 (1 instance per core) or Orthos (automatically creates 1 thread per core) for a half hour or so (more or repeatedly if you want to be anal). For Orthos use the "Blended" test. Run SuperPI 1M too for good measure (2M+ if you want to be anal again).
Step 4: Repeat steps 2 and 3 until Prime95/Orthos/SuperPI generates errors (Orthos flashes red, SuperPI will give you an alert box).
Step 5: Once you get those errors, raise the volts to your CPU to the last 100% successful amount (e.g. if your voltage is 0.975 and your last stable was 1.00, raise it to 1.00).
Step 6: After you've run the stress program of your choice for a few days, try lowering the voltage again by repeating steps 2 and 3 until you get errors, then run the stress test for another few days.
Step 7: Once you've hit your "lowest" point and you have no errors on your testing program after a few days, you've successfully burnt in your CPU. If you want, you can keep the volts as they are (since you know that they're stable) or raise the volts back up to stock and start overclocking.
Method 2 - Overclocking Your CPU
I originally started with this method, then discovered CrystalCPUID and went back to Method 1. Use this Method if you want to.
Step 1: Make sure your CPU Voltage is at stock
Step 2: Raise your FSB by 5 Mhz at a time till you get errors in a 1M Super PI (Do 2M or 4M once you start getting to those "higher" clock ranges). Once you start getting errors, lower the FSB 1 Mhz at a time until you stop getting errors.
Step 3: Run a stress test program (Prime/Orthos... use either CPU testing option for Orthos (gromacs or small in-place FFTs or Blended if you really, really want to) for 4+ hours at a time over the course of a week.
Step 4: Return to Step 2 except raise the FSB by 2-3mhz at a time.
Step 5: Repeat this whole process until you get no more increase in clock speeds.
My Current Progress
On my X2 4600, I wasn't able to get a high overclock out of it due to limitations of the board (the Nforce 570 chipset SUCKS for overclocking). However, my Nforce 6150 (410/430) seems to overclock a lot better... and for 50 bucks cheaper. Thanks Abit.
Current Burn-in Setup:
AMD Athlon X2 3600+ (Brisbane)
Abit NF-M2 nView
2 GB Corsair TWINXMS26400 (DDR2 800 (PC6400) Cas 5)
Windows Vista Ultimate (Screenshots will show it - it's just a test system, so don't get your panties in a bunch)
The stock speed for the Athlon X2 3600+ is 1.9 ghz (200 FSB * 9.5 multiplier). Stock voltage range is anywhere between 1.25 - 1.35 volts.
*I'll Post Pics Once I Resize Them*
Currently running at 1.032 - 1.040 volts (CrystalCPUID setting of 1.00) volts. This has been burning in for about 3 days, so I'm going to try lowering it soon and seeing if I can go lower.
As an aside, I was originally able to get this chip up to around 2755 (290 * 9.5) with stock cooling and voltage. I should probably invest in an aftermarket heatsink, but... yeah, I'll cross that bridge when I actually need it.
|
|
|
|
_________________
Remember, it's a matter of fully upgraded vs. non-fully upgraded.
|
|
   |
     |
|
Sythro
384Mb of RAM
Age: 26
Joined: 08 Dec 2003
Posts: 464
|
|
| Apparently I didn't log into Vista for a while and it locked me out... So... I lost those screenshots. I'll eventually get them back up.
|
|
|
|
_________________
Remember, it's a matter of fully upgraded vs. non-fully upgraded.
|
|
| |
|
|
thecybrwlf
1.5Gb of RAM
Age: 34
Joined: 05 Dec 2003
Posts: 1795
Location: Folsom, PA
|
|
| Aroo? Vista did what to your screenshots?
|
|
|
|
_________________
I knew it. I'm surrounded by coke drinkers. Keep posting, cokesuckers!
A howl in the distance marks the arrival of the CybrWlf...
|
|
  |
     |
|
Sythro
384Mb of RAM
Age: 26
Joined: 08 Dec 2003
Posts: 464
|
|
| Essentially it locked me out because I didn't activate it (forgot to apply something)... So I had to reformat and I didn't feel like mounting the drive in another machine just for screenshots. When I get around to it, I'll take new ones.
|
|
|
|
_________________
Remember, it's a matter of fully upgraded vs. non-fully upgraded.
|
|
| |
|
|
Vile
384Mb of RAM
Age: 26
Joined: 28 Sep 2005
Posts: 427
Location: Browns Mills, NJ
|
|
My laptop ran out of activation time, too. I managed to get a command window up and ran the rearm thing and rebooted and got it back.
If anyone wants more detail on this process, let me know.
|
|
|
|
_________________
-- Lazy
|
|
 |
 |
|
Sythro
384Mb of RAM
Age: 26
Joined: 08 Dec 2003
Posts: 464
|
|
| I just didn't feel like going through the hassle. It was late and reformatting was quicker.
|
|
|
|
_________________
Remember, it's a matter of fully upgraded vs. non-fully upgraded.
|
|
| |
|
|
Vile
384Mb of RAM
Age: 26
Joined: 28 Sep 2005
Posts: 427
Location: Browns Mills, NJ
|
|
| it took me like, 30 seconds...
|
|
|
|
_________________
-- Lazy
|
|
| |
|
|
Hysteric
192Mb of RAM
Age: 23
Joined: 04 Jul 2005
Posts: 197
Location: Millville, NJ
|
|
yea there is some like slmgr -rearm thing that will let you use vista for like another 30 days or whatever, buty ou can only do it like 3 times.
good guide though! i had never heard of the lowering the voltage method
|
|
|
|
_________________
Intel DX58SO
Intel Core i7-930
6.0GB DDR3-1600 (2x2048)
2x250 raid 0
8800GTS
|
|
 |
|
|
Vile
384Mb of RAM
Age: 26
Joined: 28 Sep 2005
Posts: 427
Location: Browns Mills, NJ
|
|
It's useable 4 times.
BUT... there's a registry key where you can change the value to 1, and it resets that count. And you can do that like 8 times or maybe more.
so 3x8x30 = 720 days, or 2 years-ish
-------------------------------------
my bad, it's 3 times
total comes to like 1 year
|
|
|
|
_________________
-- Lazy
Last edited by Vile on Fri Jun 08, 2007 5:41 pm; edited 1 time in total
|
|
| |
|
|
Sythro
384Mb of RAM
Age: 26
Joined: 08 Dec 2003
Posts: 464
|
|
| Who honestly keeps an install for more than 2 years? lol
|
|
|
|
_________________
Remember, it's a matter of fully upgraded vs. non-fully upgraded.
|
|
| |
|
|
Vile
384Mb of RAM
Age: 26
Joined: 28 Sep 2005
Posts: 427
Location: Browns Mills, NJ
|
|
| |
|
|
|
|
Calendar 
