Bypassing Intel's Overclock Limit Reveals DDR2-667
BatonRogue writes "Slashdot posted a Tomshardware article talking about Intel's 10% overclock limit on their new chipsets not too long ago. The situation has just become even more interesting. AnandTech just posted a roundup of DDR2 memory that sheds some light as to why Intel may have implemented the lock. It seems that on the Abit board they tested, which supposedly bypasses the overclock limit, the first generation of DDR2-533 memory modules had no problems working at 667MHz. Could it be that Intel is keeping DDR2-667 support for yet another revision of their new chipsets even though the memory support is clearly here today?"
Incidentally, my brother also says that Intel would be at a great advantage over its competitors if it could offer the 667 mhz, so it is clearly not hiding an existing feature to milk the market. The spikes are the reason.
How can you jump to that conclusion? There is a whole lot more to a new technology level being "here today" than a few chips being able to run at that level. Yield, reliability, availability of memory at reasonable price points and reliability, reliability of motherboard support, etc. all play a part. The famous Pentium floating point bug had rare effect except on scientific applications, but clearly that version of the Pentium wasn't even "here" when it shipped.
I currently have an ASUS based AMD64 system at home that I made the mistake of buying in the second month of availability. I can tell you from firsthand experience that it wasn't "here" when it shipped. Almost everything of any meaning has been replaced and the system still freezes solid twice a day. Only a hard reset brings it around. Pretty soon, I'll go another round of replace the processor... does it work... replace the motherboard... does it work... replace the memory... does it work. I'm betting this time I'll finally get there because someone has figured out a problem and fixed it in the latest releases of these 'stable' products.
From the article the numbers actually represent clock cycles not nanoseconds. 1 clock cycle on 450 is 2.2ns, while 1 clock cycle on 667 is 1.5ns. 2-2-2-6 @ 450 is ~30% faster than 4-4-4-12 @ 667. :)
The hard drive analogy is a good one since geeks have been debating SCSI vs ATA for decades
D6 63 0D 70 89 81 BB 8E 7B 7C 5F 5D 54 EA AB 73
Because they're making and selling as many $1000 chips as the market will support. Now, they can either sell the $1000 chips for less money and sell more of them, or they can sell a slower chip for $500 and keep the $1000 top-end CPU.
As it happens, the math works out in Intel's favor selling a 3.4GHz chip for your eldest son and a 3.2GHz chip for your right arm and a 3.0Ghz chip for a pretty penny. In the begining this is great. Then for a while the 3.4GHz chips get too easy to make and so they sell some of them as 3.2GHz chips and maybe even some as 3.0GHz chips. But until they can make enough 3.6GHz chips to satisfy current demand for 3.4GHz chips, they can't introduce a new speed grade. When the 3.6GHz parts come out, demand increases for the now-cheaper 3.4Ghz parts, and the now-cheaper 3.2GHz parts and the now-low-end 3.0GHz parts. And the cycle repeats.
Intel and AMD don't sell CPUs to consumers. They don't respond to market pressures except at predetermined times, so when demand for high-end parts is less than supply, they sell the high-end parts for less money, and when demand exceeds supply there's a shortage. These are not spot prices as would be paid by a consumer, these are contract prices as would be paid by someone ordering 20,000 chips a month for the next 3 months: there is no other way to respond to surplus or shortage within the current system. Intel would much rather sell a potentially-high-end P4 as a mid-range P4 and make $100 than force the customer to source mid-range parts from AMD.
High-speed Road Trip (18.000KPH)
I'm one of the original overclockers. I had a 486DX36, back when overclocking required replacing the clock module on the motherboard. I'm also an occasional chip designer.
The trick to overclocking is to know what your limit is. Until recently, thermal load was not the limiting factor. The real limiting factor was a condition called "metastability", where a digital transition fails to finish before being latched in the next register (usually due to violations of the setup and hold time restrictions of those registers). The smallest case of metastability can flip a bit.
A larger case can cascade through multiple stages, flipping lots of bits or even pushing the state tables into illegal states. This is where the first real danger lies: a processor that uses one-hot encoding to improve the speed of the controlling state machine can be pushed into illegal states that may cause several circuits to drive the internal busses at once. This leads to large current dissipation, and in some cases it can burn holes in the thin metal layers of the IC.
A less common hazard appears in cases when the CPU is massively overclocked. The CPU in such a case will never exit the metastable state. This causes each clocked circuit on large areas of the chip to dissipate maximum current during those metastable states. This can also lead to high current dissipation, although it is less dangerous than the abovementioned one. It's also worth mentioning that a chip in this state will not function normally.
Generally speaking, you have a wide margin between the onset of metastability and the onset of serious damage. Unfortunately, there is now *another* danger of overclocking processors. High thermal load can cause ion migration. In fact, most processors are now designed to only last 5 years (!) before ion migration renders them useless. (This is also why I personally don't overclock anymore).
It's frightening to notice that mainstream CPU's are less and less overclockable and have higher and higher thermal loads with smaller and smaller featuresizes, though. The manufacturers are simply not leaving as much margin as they once did.
Hardware, software, and blinking lights!
Think about it. If they invent a 5GHz CPU now, and release it now, and it takes them 2 years to develop the 10GHz CPU, then they will spend 18 months (thanks to the roughly 6-month CPU lifecycle) with no "cutting-edge" product. If they release that CPU as a 3.5GHz CPU now, a 4.0GHz CPU in 6 months, a 4.5GHz CPU 6 months after that, and a 5GHz CPU 6 months after that, suddenly they've filled in their entire product line for that time. And since the CPU market is an oligopoly, they only have to make it look like they're fighting the good fight against AMD. The next "competitors" (via, transmeta, and the like) don't have the resources to compete on pure performance.
I'm not saying that I honestly think they're doing exactly this. I do suspect something on a much smaller scale, though. Remember, this is the company that gave you the 487SX.
Hardware, software, and blinking lights!