A few months ago, I had no idea how to begin the process of overclocking my machine. It was painful even trying to figure out what questions to ask. This write-up is aimed at those just starting the process. It tries to provide you with the particular steps needed to undertake, investigate further, and produce some level of overclocking.
You should understand that there are various degrees of overclocking;
however, the initial steps associated with running a faster Front-Side Bus (FSB) that will produce the greatest gains. You can continue to tweak almost forever for small gains that are of little value in terms of observable performance, and you may undertake those just because it is fun for you. Nothing wrong with either perspective.
I am most familiar with AMD-based machines and while I’ve
owned and currently use Intel-based machines, I’ve not overclocked them. If you find inconsistencies in regards Intel (PIV) machines, please let me know so others aren’t mislead. And if you feel so moved, please provide verbiage to correct the situation – I’ll acknowledge you as a contributor.
Introduction
To understand overclocking, you need to realize that for the majority of mobos (motherboards), there is a single clock which controls all operations made by the computer. The various operations (for example graphics) are slaved to the clock.
The clock measures time in what is typically called a tick, cycle, period or the clock refresh rate, and reflects a discrete measure (small-fixed unit) of time. The cycle is also commonly converted to an operational frequency, (frequency = 1.0 / period) in many discussions. For example, a clock cycle of 7.5 nanoseconds converts to a 133 Mhz clock speed. (The clock cycle can be viewed as a square wave for those familiar with such representations. The cycle is thus made of a positive half and a negative half.)
A Simple Perspective of Overclocking – The Balance
of Various Component Demands
Because the various computer operations are often slaved
to the single clock, a balance of the various device speeds must be achieved so that each device is stable.
The clock controls the Front-Side Bus (FSB) and the different components use that bus speed to determine their own speed. With a single speed available from the FSB, this creates the need for “multipliers”, a term you often hear.
Some multipliers increase the FSB reference speed for use by their component, for example the CPU multiplier is typically greater than one; for example, an AMD XP 2100+ is set at 13 when the CPU is locked. Others slow it down; the PCI bus, for example, typically uses a multiplier of ¼ on many of today’s motherboards.
If the multiplier slows the speed down, it may also be called a divider. For this discussion multipliers and dividers are viewed as performing the same operation, ie changing the FSB clock speed for use by their particular devices.
One definition of overclocking is the process of balancing the various component speed needs to produce stable operation at different FSB speeds.
When you have the freedom to select the multipliers for the various devices (hard drive, video, memory, etc.), this balance is easier to obtain. That statement may not be obvious to you now but hopefully will be better understood later as we deal with the combination of memory and CPU. Ultimately, what we would really like to do is work with each device independently. Motherboards are available that allow this separation are becoming more widely available.
A Simple Overview of Memory
There are far too many characteristics associated with memory and its operation to include in this simple guide. Thus, I will try (with the help of other contributors) to provide a brief perspective that will hopefully help you better understand memory itself. This perspective will look at major Dynamic Random Access Memory (DRAM) types in use today and a few of their characteristics that directly influence our initial efforts in overclocking.
{mospagebreak}
A reference discussing much more completely the various memory types can be found at pctechguide.com. Here I will provide some detail related to the three main types of memory in use today – SDRAM, DDR SDRAM and RDRAM.
SDRAM – Synchronous DRAM
(SDRAM) employs the fact that most PC memory accesses are sequential, ie the information need has been stored sequentially. Thus, all the bits can be retrieved in a burst. The SDRAM uses a memory controller to determine the location and size of the block of memory required and then supplies the bits as fast as the CPU can take them, using a clock to synchronize the timing of the memory chip to the CPU’s system clock.
This feature of SDRAM allows it to deliver data at burst rates of up to 100 Mhz while using a FSB of 66 Mhz.
PC133 SDRAM is an advancement of SDRAM allowing a doubling of the burst data rate and is compatible with a 133 Mhz FSB.
(This information related to SDRAM was taken from pctechguide.com.)
DDR SDRAM – Often just called DDR (Double Date Rate). DDR works on both "sides" of the clock cycle (positive portion and negative portion), so its data transfer rate (frequently noted as bandwidth) is doubled, hence the name.
DDR memory is the most common, cost effective, and arguably best RAM option currently available. Also, it is the most overclockable RAM, with some high-end sticks allowing FSB speeds in the 200s. It is rated by both speed and bandwidth. For example,
PC 1600 = DDR200 = 1.6 GB/s
PC 2100 = DDR266 = 2.1 GB/s
PC 2700 = DDR 333 = 2.7 GB/s
PC 3200 = DDR 400 = 3.2 GB/s
How these specifications, for example PC 1600, are obtained
is discussed in more detail in an O/C forum thread.
Note, however, that to achieve these ratings the memory needs to be driven at its rated speed. If you put some PC 3200 in an Athlon stock mobo with a 266 Mhz FSB, it would just run at PC 2100. Doesn’t hurt it, but you have wasted your money because you are not running it at its rated speed. You would need to overclock the FSB to 200 Mhz to fully use the PC 3200 at its rated capacity.
RDRAM – A slightly more expensive, yet top performing memory, exclusive to the Intel P4. RDRAM uses a clock generator of its own to run at fast speeds, which achieves the high rate (bandwidth). However, it can get quite hot, and is not a good OR easy overclocker. If the RDRAM multiplier is lowered, decent FSB speeds might be reached. For example, stock PC800 is 100 * 4, but that’s equivalent to 133 * 3. Speed is given in Mhz * 2, since it is on a dual-channel architecture.
PC800 = 4*100 = 3*133 = 3.2 GB/s
PC1066 = 4*133 = 4.2 GB/s
Note that conventional RDRAM boards don’t give options beyond low 150’s for FSB.
Some RAM Characteristics and Their Effect on Overclocking
Today’s memory may operate as either synchronous or asynchronous.
Synchronous memory is synchronous with the FSB. DDR generally operates asynchronously but many mobos (motherboards) can switch memory operation to a synchronous mode, either manually in the BIOS or automatically based on a particular FSB speed being reached.
Asynchronous memory responds to input signals whenever they occur, as long as the signals are applied in the proper sequence, with signal durations and delays between signals that meet the specified limits.
The multipliers used by memory also frequently change at a particular FSB speed. For an Epox (the board I currently have), the FSB speed at which the multiplier behavior changes is 166 Mhz. This change occurs as follows:
Below 166 Mhz, the multiplier is 1.25. Another factor of 2 results from DDR. Thus for a FSB of 133 Mhz, the memory speed will be 1.25 * 2 * 133 Mhz, which produces the 333 Mhz memory speed you commonly hear today. And the memory is operating in an asynchronous mode.
At and above a FSB of 166 Mhz, the multiplier is 1.0. Thus for a FSB of 166 Mhz, the memory speed would be 1.0 * 2 * 166 Mhz, which also produces the 333 Mhz memory speed. In this case, the memory is operating in a synchronous mode.
You should now have noted that an FSB of 133 Mhz and one of 166 Mhz both produce the same memory speed of 333 Mhz for DDR memory, as a result of the multiplier change in value at 166 Mhz. The difference between the two cases being the first is in an asynchronous mode of operation while the second is in a synchronous mode.
I summarize this behavior in the following table:
If others will provide information related to other boards, I will add it to the table. Corrections too, please.
{mospagebreak}
The Mechanics of Overclocking the Motherboard: FSB
and Memory
I mentioned earlier that we would really like to work with each device independently. The combination of memory and CPU is an example of two components that can represent an independence or an interdependence. If the CPU is unlocked, we can deal with the memory and CPU independently of one another. If the CPU is locked, they are interdependent, and this dependence does remove some flexibility. We will briefly look at both cases here.
Overclocking with an Unlocked CPU
1) Go into your BIOS and set the most aggressive memory timings available to you. I’m running 2-2-5-2 on my Corsair 3000 CAS 2. See LostCircuits.com or Rojakpot.com or Radiativenz.com (my favorite) should you need help with the meaning of such things as 2-2-5-2. We’ll investigate the influence of the settings a little bit more below.
2) Start at a stock FSB speed (133 should be stock on new
mobos) and also make sure Vcore and Vdimm are set to default voltages.
3) While in the BIOS, also set the multiplier on your CPU
down, maybe to 8. Yes, this is low, but you want the CPU to be stable as you increase the FSB, so make sure it is running slow. This step is aimed at keeping any CPU stability problems from occuring, ie making the memory behavior independent of the CPU behavior. (By the way, CPU speed is FSB * multiplier. You probably know that, but just making sure.) You’ll reset the CPU multiplier higher later.
4) Run an application that really exercises the memory at each FSB speed to see if you’re stable (see Testing below). Sandra doesn’t cut it for this test. After you know this initial setup is stable, start increasing the FSB speed and retest each time. Yes, this takes a lot of time!
You may wish to jump to 166 FSB once you’ve tested stock. (I believe that is the point at which one or more multipliers change and you’ll want them at FSB higher levels anyway.)
5) When the test results are unstable, increase the Vdimm and try again. Continue increasing the Vdimm till stable or you don’t want to go any higher in voltage.
6) Using this process of increasing the FSB speed, testing and increasing the Vdimm as needed, work your way up to the highest FSB you can reach for the max Vdimm voltage you’re willing to run.
Be careful to keep the CPU near stock speed, or lower, by adjusting the CPU multiplier down should FSB speeds reach high levels. This will keep the CPU stable without having to increase its voltage {Vcore), an operation that we wish to delay and keep independent from the memory overclock.
There are various strategies about how to minimize the time you spend reaching a maximum FSB, but I’ll not take up space to suggest those — I’m sure you can figure several others out.
7) You can reduce your aggressive memory setting (2-2-5-2) to get higher FSB speeds, but it has been noted several times by others that “In general, you can get better memory performance out of a lower clock speed and better timings than out of a faster clock speed but worse timings.”
Often, your memory performance is more important to overall performance than your overclock, so a good approach is to overclock as far as your memory can operate at its most aggressive settings.
8) You can have problems (unstable behavior) with video, networking and other cards as the FSB gets high. The FSB speed at which the multipliers change is critical to these problems. Surf those forums/threads for help.
9) You would work next on the CPU speed, but that isn’t part of this guide – at least not for now. Basically, you start increasing the CPU multiplier and increase the Vcore as needed for stability in this case. And test, test, test… always watching your CPU temperatures!!! The CPU you save maybe your own.
Overclocking with a Locked CPU
1) Go into BIOS and set the most aggressive memory timings available to you. I’m running 2-2-5-2 on my Corsair 3000 CAS 2. See LostCircuits.com or Rojakpot.com or Radiativenz.com (my favorite) should you need help with the meaning of such things as 2-2-5-2. We’ll investigate the influence of the settings a little bit more below.
2) Start at a stock FSB speed (133 should be stock on new
mobos) and also make sure Vcore and Vdimm are set to default voltages.
3) Run an application that really exercises the memory at each FSB speed to see if you’re stable (see Testing below). Sandra doesn’t cut it for this test. After you know this initial setup is stable, start increasing the FSB speed and retest each time. Yes, this takes a lot of time!
4) When the test results are unstable, increase both Vcore and Vdimm one level above their default settings and try again. Continue increasing them till stable or you don’t want to go any higher in voltage.
5) Using this process of increasing the FSB speed, testing and increasing the voltages as needed, work your way up to the highest FSB you can reach for the max voltages you’re willing to run.
There are various strategies about how to minimize the time you spend reaching a maximum FSB but I’ll not take up space to suggest those — I’m sure you can figure several others out.
6) You can reduce your aggressive memory setting (2-2-5-2) to get higher FSB speeds but it has been noted several times by others that “In general, you can get better memory performance out of a lower clock speed and better timings than out of a faster clock speed but worse timings.”
Often, your memory performance is more important to overall performance than your overclock, so a good approach is to overclock as far as your memory can operate at its most aggressive settings.
7) You can have problems (unstable behavior) with video, networking and other cards, as the FSB gets high. These problems don’t occur too frequently with a locked CPU because the FSB speeds don’t reach as high a level as those for an unlocked CPU. Surf those forums/threads for help should problems occur.
As you approach a FSB speed of around 200 Mhz, you may experience problems with devices that operate from either the PCI or AGP buses. For example, hard drives operate at the PCI speed while video cards often use the AGP bus (there are PCI video cards also). Problems around 200 Mhz are not uncommon for boards built with either the Via KT400 chipset or KT 333, or earlier.
As you should realize from our efforts dealing with memory and CPU above, we would really like to work with each device independently. This is not possible for the majority of mobos in use today as regards the speed of the PCI and AGP buses. The dividers associated with PCI and AGP buses are built into the mobo with little or no freedom available to you the user.
The PCI bus typically uses a multiplier of 1/4. The AGP bus typically has a multiplier of 1/2. (These may differ for your particular board, so realize that you may need to find the info for your mobo.) Thus for a stock FSB speed of 133 Mhz, the memory runs at a speed of 133 Mhz * (5/4)*2 = 333 Mhz while the PCI runs at 133 Mhz/4 = 33 Mhz and the AGP runs at 133 Mhz/2 = 66 Mhz.
And of course as you raise the FSB speed, the PCI and AGP speeds also increase; consequently, at some point your devices operating from these buses will experience problems. Determining which device is the problem is not always easy and I know of no solution except to run at the limiting speed.
New mobos are beginning to appear which allow locking of the PCI and AGP buses (for example, Intel’s 845 chipset and Nvidia’s nForce2 chipset). Of course, locking a bus is different from using a multiplier, in that the frequency doesn’t change and is independent of the FSB. In theory, these mobos remove limitations placed on the overclocker by the PCI and AGP.
Testing
A number of the steps above involve testing of your memory overclock, so we should try to understand this part of the process a little better.
You can find a very large number of tests at BenchmarkHQ available to download, but which ones should you run and what do they produce? In using any test, it is extremely important to understand what the test is measuring and how to interpret the results. Does it test a component alone or does it involve the overall system?
For memory, a good stress test is Memtest86 (Memtest86). It runs an array of tests of memory reads, writes, copies, and moves in different patterns and block sizes, and it runs in the first small segment of memory and tests the whole range independently of the OS, HDD, PCI devices, etc.
Prime95 (Mersenne.org) is an excellent application to do ongoing testing of your system stability. My experience thus far says if Prime95 will run stable, your system is stable. I’ve found that using the benchmark within Prime95 (under Options) provides the best testing for my CPU-memory combination, but I will use the cycle time results sometimes.
The cycle time seems to vary depending upon what part of solution Prime95 is doing, so be careful with those numbers. You must be very careful to have the correct CPU speed input into Prime95 (under Options, in CPU). If the CPU speed isn’t correct, your results will not be valid.
The Prime95 benchmark provides output for the fastest time of several different length FFT (Fast Fourier Transforms). You don’t have to know what an FFT is to use this tool, just realize that it provides a measure of your CPU/memory interaction and that smaller times are better.
Here is a sample output for my system:
FFT length
Best time
256K
19.912 ms.
320K
25.756 ms.
384K
32.704 ms.
448K
36.950 ms.
512K
40.705 ms.
640K
52.767 ms.
768K
64.735 ms.
892K
75.638 ms.
1024K
85.891 ms.
1280K
114.064 ms.
1536K
137.621 ms.
1792K
165.509 ms.
There may be various ways to use this data, but I tend to use the output for the 256K length FFT just to keep things simple. I’ll repeat the test several times (typically 6 to 10) and average the results.
{mospagebreak}
To investigate an initial overclock, we will look at changing the FSB, then separately we will consider the memory settings.
Overclocking The FSB
So what do you accomplish by overclocking memory?
Here are 2 results from my machine with an unlocked CPU. Results were obtained with a Vdimm=2.9 volts. Also realize that these are intermediate results (obtained during step-4 above) and aren’t the final overclock reached:
FSB
CPU mult.
CPU
Arithmetic
CPU
MultiMedia
Memory
Bandwidth
Prime95
(ms/cycle)
143
13
5130/2584
10240/11355
2171/2071
40
168
9
4135/2090
8282/9181
2401/2201
37
Three results are shown from SiSandra Software: CPU Arithmetic, CPU MultiMedia, and Memory Bandwidth. Higher is better. Within these results, which is better? The results indicate the CPU performs better at a FSB of 143 Mhz using a multiplier of 13. It should, because the CPU speed is 143 Mhz * 13 = 1859 Mhz, compared to 168 Mhz * 9 = 1512 Mhz. Yet, the memory did perform better at 168 Mhz. Does this matter?
As noted earlier, Prime95 exercises the complete computing part of your machine. Most importantly, it did show my system to be stable at the FSB speed of 168. In addition, a look at the results from running Prime95 shows the time to run a cycle of Prime95 has decreased by about 10% for the higher FSB.
Thus while the CPU performance has decreased at the higher FSB speed due to the multiplier I used, the overall performance of the system has improved!
What might a newbie learn from this example?
First, understand what your test is telling you. Sandra is reporting exactly what it said it would, the performance of the CPU. It didn’t claim that was a true measure of my machine’s ability to compute, even though I may have assumed it to be the case.
Prime95 did run stable at the higher 168 FSB and provided me with an indication of my machine’s better performance, even with the CPU multiplier set at 9. Memory performance is very important to the overall performance of your overclock.
Will your machine behave in this manner? Maybe, maybe not. Pentiums will behave differently than my AMD. Various motherboards may also change the results. However, hopefully with these tools you can begin to experiment.
Memory Settings and Their Effect on Overclocking
Memory settings are often discussed related to their importance to overclocking. In the process (steps) discussed above, we started with the most aggressive (lowest) settings. What is the effect should you not do this, or what is the effect if you want to relax the timings to get a higher FSB?
Here are the results that I obtained by testing my memory settings. I have not tested every setting available to me in my BIOS at this time, but these are typical ones that you will often hear quoted. These results were obtained by using the Prime95 benchmark (noted above) and Corsair 512XMS3500c2 at 2.9v.
The memory is different than that used when this writeup started, but the points can be made without reinstalling my original memory. The percent change shown in the table below is the resulting difference in changing from the lowest setting to the highest setting. (You would expect the percentages to be negative.)
DRAM control
Percent Change
CAS
-0.89
TRP
-2.29
TRAS
0.21
TRED
-3.5
Command rate (CR)
-2.68
Change all at once
-5.38
The changes are all in the direction you would expect except for TRAS. But the change due to TRAS is minor. In their order of importance for my system, the setting’s importance is TRED => CR => TRP => CAS => TRAS. Also, the total effect of changing all settings at once is not the sum of the individual settings and is on the order of 5.5%.
Thus I see a 5.5% improvement in my system’s performance between the less aggressive memory settings to the most agressive.
This translate directly to FSB speed. (I’ve tested to insure the validity of that statement.) For example, the most aggressive memory timing settings at a FSB of 190 will provide the same level of performance as the least aggressive settings at a FSB of 200.
Remember, these are results for my machine and its setup. The results you see may vary, but you should be able to use the same basic techniques to find out.
How do you use this information to obtain your best overclock?
What should you do if you raised your FSB to your machine’s highest stable value using one of the two processes above in "The Mechanics of Overclocking" section and you want to see if you can get higher without giving up too much performance? I would suggest the following steps:
1) Be prepared to spend a significant amount of time to gain a few percentage points improvement in performance. Ask yourself “Do I REALLY want to do this?”
2) Test you memory settings as I did above to determine their order of importance to improve performance of your machine.
3) Relax your timings setting to their least aggressive settings and find you max stable FSB. (If your CPU is locked, it may create stability problems as your try to increase the FSB. But your max FSB is just that, no matter whether it be the CPU or memory that creates the limit.)
At this point, you have two values for your FSB. The lower FSB (FSBlow) is the result of the most aggressive memory timings. The other (FSBhigh) is the result of the least aggressive memory timings.
4) Having found your FSBhigh, change the most important memory setting to its agressive timing. Test for stability if you can boot. If you can’t boot, drop the FSB half way between FSBlow and FSBhigh. Continue moving the FSB down till you can boot and then test. Find your stable FSB for this timing.
5) Now repeat this procedure for each of your memory settings in their order of importance.
Summary
If you’ve gotten to this section, I must say Congratulations! If you’ve done all the testing above to reach this point, then you know more about your machine than anyone else, and your knowledge of overclocking is well beyond that of a newbie. As motherboards and CPUs continue to change and improve, the process will change.
Caution!
Monitor CPU temperatures! A program like MBM 5 (mbm.livewiredev.com) will give you readouts on your temperatures, voltages and CPU speed.
Have you ever heard “The players may change but the game is the same”? There are a lot more players now but the game is the same. Lurking in the forums, I often find a post cursing one board or
ED NOTE: Sami sent this in and it’s worth sharing with all – Joe. Some info of my LN2 experiments with AXIA TB: I did some LN2 CPU cooling with my week 9 1GHz AXIA TB. Not only did the
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.OkPrivacy policy
Be the first to comment