Overclocking AMD 900 Tbird using FIC AZ11E, couldn't change ratio!

tomkwc

Junior Member
Mar 6, 2001
3
0
0
Hi, I just bought an AMD 900 TBird with a FIC AZ11E Motherboard. I am trying to OC my processor but only able to do it through FSB through software. I wanted to change the ratio above 9x through the dip switch like the manuel said, but unfortunately no matter how I set the dip switch the ratio stays at 9. I have disabled the ADR (Auto Detect Ratio) pin for auto detection of the ratio already. But the ratio still stays at 9. What can I do Help!!!!!
 

Hammbone

Senior member
Aug 8, 2000
214
0
0
hey man, i have a tbird 900 and the same motherboard as you do, i am having problems even getting the thing to boot, wont click the screen on. i tried the norms (video, cmos, memory, processor seating) do you have any suggestions, wondering if you hit any problems while getting it up and running. sorry that this isnt a reply that you were looking for but i really could use the help if you have anything, thanks!!!
 

BCYL

Diamond Member
Jun 7, 2000
7,803
0
71
You cannot change the multipler because your processor is locked... most multipliers on the processors come locked, and you have to unlock it yourself if you wanna overclock...

Luckily AMD make it very easy to unlock the processor... all you need to do is connect the L1 bridges on the face of the processor... There are some very good articles on anandtech.com on how to do this... Just do a search for Overclocking in CPU reviews...
 

tomkwc

Junior Member
Mar 6, 2001
3
0
0
Hammbone, I am sorry to say that I didn't run into any trouble booting up my new motherboard and CPU. The only time I had trouble booting up is when I tried to set my FSB pin from 100 to 133 on the jumper (which was a bad idea ofcourse). But that was the only time I had trouble booting. In the past, incompatible RAM and loose AGP card on your slot can also cause your PC from booting. Sometimes, the CPU fan wouldn't even start. But it'll take a little trial and error to figure it out. Good luck. Cheap incompatible RAM can be a good cause.