Athlon 64 In-depth Overclocking Guide
jmke writes "Everything you ever wanted to know about Athlon 64 overclocking, and then some. If you are confused about HTT, LDT, memory dividers and relationship between these settings, then read on. This in-depth overclocking guide will show you how to get the maximum from your brand new Athlon 64 system"
Is $150 for a lower end Athlon 64 really THAT EXPENSIVE?
No, of course most wouldn't try to overclock an IBM server or clustered 20 4-way xeons. Why? Most people DO NOT OWN THOSE. That's corporate equipment. People can afford to play with $150 chips at home, and will.
I've already overclocked my 64 to a 96. W00T!
keep on because of a rumor that after the 4GHz barrier you can create a tear in the time-space continium... :)
As someone who does real-time generative audio/video processing, I have to say that oftentimes what a 2GHz machine cannot run comfortably, a 2.5GHz machine can do satisfactorily. 12FPS may not be good enough, but 15FPS may be passible. People often dismiss overclocking as something just for gamers, but in reality, it can be useful to anyone doing processor-intensive, real-time processing. I feel that some of the anti-overclocking opinions here are a bit unjustified, and more of a knee-jerk response to a loosely correlated l33t culture. The only games I play are Clan Lord and Civilization III... hardly a reason to overclock. However, for video processing, I need all the power I can get despite my modest budget.
I was just happy that I could plonk a NEC V20 in my IBM XT - going from a 4.77 MHz 8088 to a whopping 8 MHz!
I don't see why this is so fantastically irritating to you. Does it bother you when someone has a ferrari that they just drive to work or an SUV that they just drive to soccer practice? You know, it really bothers me that you have a kitchen and don't bother to cook up gourmet 5 star meals.
MacroHard - Boning you in a big way! (TM)
The likelyhood of frying parts is not very high. Before that happens you will get restarts, BSODs etc, telling you that you've messed up the settings. If you do it properly, and test your systems stability with Memtest86, Prime95 and the like, then there is no harm.
I have my Athlon 64 3000+ running at 2.2 gHz up from the stock of 1.8. That's the speed of a 3500+ which at the time of purchase cost $170AU more. Do I need that extra speed? No. Is it handy? Yes. Games run smoother. Compilation is quicker. More research for folding@home is acheived.
Give it a go. It's plain old geeky fun.
Yet another blogger begging for an audience.