I put together a little chart here to illustrate:
The top shows 800 RAM, the multipliers for each Intel standard FSB, and you can see that, as 2.0 is the
lowest multiplier available, you can't take the FSB much past 1600 (400 system clock) as, for each each 'tick' of the system clock, you are going 2 more past 800 - which the RAM won't like...
The bottom shows 1066 RAM, the multipliers for each Intel standard FSB, and goes into detail for raising the FSB past 1600 (400+ system clock); I made the chart to show what happens when you have 1066 RAM that you know 'tops out' around 1080 or 1090; with the base 2.66 multiplier, you're going to 'run out of headroom' somewhere between 406-410 system clock; if you can get the 2.5 multiplier (which may not work, as it's on the 266 'strap' [more about that later...]) to operate, it will, at the same point where your RAM 'peters out' at 2.66, only be hitting 1025 - and the 2.5 will have you 'covered' till the system clock hits 436 - where, once again, your RAM will be at 1090, its upper limit... Then we have the 2.4 multiplier (which
will work, as its on a high strap), which has you covered up to a 454 system clock. So, you can see how there is a 'step-wise' operation here, ratcheting your RAM speed up and down somewhat as you 'walk up' the system clock to crank your processor...
Now, I'll yack a bit about the 'straps'; much like memory, which requires more bus cycles of latency as the cycles themselves become shorter (faster), the northbridge's connection to the CPU has an inherent need to adjust its latencies as the FSB increases. These are arranged in four sets, to correspond to the four Intel supported FSBs. On the P43/P45 boards, you select these 'straps' explicitly, by setting the "(G)MCH Frequency Latch" in the BIOS - once this is set, you will only 'see' that strap's available multipliers in the next item, "System Memory Multiplier (SPD)"; in the older boards, based on the X38/X48, the strap that applies to each multiplier is expressed as a letter or symbol after the multiplier's decimal expression. If you use AMD, you're an aberrant who deserves whatever particular hell Murphy and his immutable Law assign to you!
So, for the 200 system clock (800 FSB) strap, which is shown by a 'C' or a '+' after the multiplier, you get 2.66 (4:3), 3.33 (5:3), and 4.00 (2:1); for the 266 system clock (1066 FSB) strap, which is shown by an 'A' or a '~' after the multiplier, you get 2.50 (5:4), 3.00 (5:3), and, once again 4.0 (2:1); for the 333 system clock (1333 FSB) strap, which is shown by a 'B' or a '#' after the multiplier, you get 2.00 (1:1), 2.40 (6:5), 3.20 (8:5), and, yet again 4.0 (2:1); and for the 400 system clock (1600 FSB) strap, which is shown by a 'D' after the multiplier,you get 2.00 (1:1), 2.66 (4:3), and, 3.33 (5:3).
People impute a certain 'magical' capability to the fabled 1:1 ratio, which happens only with the 2.0 multipliers on the 333 and 400 straps... For the most part, this is pretty much hogwash. The 'magic' is this: certain memory bus transactions (and they are a limited few) can only occur when the memory and processor busses are 'synch'ed; in other words, with say, an 8:5 ratio (3.2 mult), the memory and CPU insert 'wait states' till one finishes counting cycles to eight, and the other one five (doesn't matter which way you look at it, the time elapsed is, by definition, the same). That means that the average wait for these transactions is half the worst case, or 7/2, three and a half cycles. Obviously, at a 1:1 ratio, these transactions are always available on the 'next count', so for these transactions, it
is faster. However (and it's a
big however), you are
far ahead by running your RAM at a higher speed - and damned the transaction waits! On my system, my system clock is at 450, and I'm running the 2.4 multiplier, for a 1080 RAM speed. To get 1:1 (2.0 mult), I'd have to lower my RAM speed to 900, and the loss of throughput ([1080-900]/900=.2, or 20%) far outweighs the 'immediate transaction' gain (a couple percent, at best)...
Hope this has made these factors in ram speed and overclocking a bit clearer!
Bill