This content was originally featured on Amdmb.com and has been converted to PC Perspective’s website. Some color changes and flaws may appear.

With such a fast processor in my hands, you could imagine the racing my mind was doing about overclocking this puppy. Just recently, I saw some reports of a person reaching 2.1 GHz with one of these 1.33 GHz AXIA part number CPUs, but I am hesitant to believe it. There weren’t any details on cooling and only said that they used a modified A7M266 motherboard, running at 2.0v. I’d like to believe that it was not faked, but without further evidence…

AMD Athlon 1.33 GHz 266 MHz FSB Review - Processors 26   AMD Athlon 1.33 GHz 266 MHz FSB Review - Processors 27
(Click to Enlarge – Amazing what different lighting does)

On to my experience with this chip: I tried both of the major ways of overclocking this processor. I first used the multipliers solely, then used the FSB solely and finally used both to reach the highest clock speed.

Using the multipliers, I was easily able to push the 1.33 GHz processor to the 1463 MHz by merely pushing the multiplier up to 11x. This was using the standard air-cooling and the Foxconn heatsink/fan. With FSB-only modification, I was able to reach a speed of 1550 MHz, running at 155 x 10. Pretty nice, passing up the 1.5 GHz mark! Using both the FSB and multipliers, the maximum overclock I was able to reach was 150 MHz x 11 for a total 1.65 GHz. I was simply amazed by this processor and motherboard able to reach such high speeds with air-cooling and only slight voltage modifications (over the 1.85v range).

An interesting note here is the processor had its L1 bridges already closed, meaning it was ready to be overclocked by motherboards. There have been lots of reports of the new 1.2 GHz processors being sold that are version ‘C’ (266 MHz FSB) with their L1 bridges closed as well. I am not sure what AMD’s stance is on the overclocking community and I am not sure what other reason they would have to re-implement this feature from a technical standpoint. Hopefully we will hear from AMD on the issue soon.

« PreviousNext »