• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Hack into the AMIbios or VIA KT-133 (686a) "other functions"?

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

gwballs

Registered
Joined
May 8, 2001
hi, I really would like to OC my T-900 above 1000mhz but I do not have ANY mutiplier support on my Gigabyte 7-ZX rev.1.0 what do ever :( When I OC clock the FBS to arould 110 FBS my system is unstable; no blue deaths but it just locks up. I'm Think there got to be ways to tap into the AMIbios or VIA bios to disable the "autodetect" feature that is blocking me from speed. Any suggestions??

Antec SX830 workstation case, T-900 socket, 448 PC133 ram(mixed brands), WD7200rpm 30 gig HD on a Maxtor ATA100 controler card, SB-live X-gamer +5.1, TDK12X10X32, Hercules GFII MX
 
The reaseon why you cannot oc your FSB more lies in the chipset. The KT133 cannot usually take higher FSB's than 110. A friend of mine cannot even get that, he's absolute maximum is 107. I've read about people getting 118MHz, but that's just pure luck.

You could try to cut&connect the other bridges to change the default multiplier, but I don't know much about that. Tom's Hardware should have an article about cutting the bridges, if I remember correctly. You could also check the frontpage here at overclockers.com for those articles.
 
What I was trying to say was; Anyway to disable the "autodetect" AMIbios or VIAbios functions that controls the CPU core votage and mutipliers. (maby I didn't make that clear, sorry) My mother MoBo does NOT have ANY mutiplier jumpers and in the Bioses not settings for mutiplier, votage ether. I have connected the L1 brige using some conductive poxy(got it from work); its made of Platunim, silver and some sticky stuff.
anyway, when i put the CPU back in the socket, my system does not boot at all!! and I did make sure there was not "shorts" with the L1 connection. what is going on with that?
thanks
 
Sadly I have no idea what is causing the no-boot problem. :(
The only way I know of changing the initial multiplier, the one that is "hardcoded" on the chip, is connecting and breaking those L7 brigdes.

Hopefully someone else will reply in this topic too.
 
Back