View Full Version : KT400 + 9700 Pro = No chance of FSB OCing?
krarg
04-17-2003, 06:29 PM
I've got an AT7-MAX2, a 9700 Pro, and a 2500+ on watercooling. The highest I've been able to get the 2500 is 13.5x166 (unlocked), and I'm pretty sure I won't be able to hit 14x. However, a problem I've always noticed with this motherboard is its inability to lock the AGP bus freq...is there any way around this? I know the 9700s are really niggly when it comes to overclocked agp buses - mine doesn't even allow a POST past an AGP bus that's out of spec by 2-3mhz - but I see a lot of people on these forums hitting insane FSB speeds without nForce 2s. Is the only way around this to just not have a 9700?
mike.elmes
04-17-2003, 07:00 PM
krarg, I don't have your particular board, mine is an abit KD7....
KT400 board though, and mine was totally compatable with the radeon 9700 pro. And many around here are getting great results with the kt400 boards....mine was doing 195 fsb in the prometeia....However, I was after 200+ fsb.
Have you tried another video card in there with better results??
Perhaps someone around here will chirp in who has your config.
good luck
Hmm.. Try adding some major cooling to your northbridge.. A duron hsf should work nicely if it will fit. If not, get the hsf off a k6-2 500 or something. If your southbridge is warm, put a heatsink on that too. Same with clock gen and mosfets.
On that board, can you adjust your vagp? If so, give it a little more voltage and see if that helps. Turn up your VIO too. Make sure your voltages are not drasticaly high or low in BIOS (not sandra or the like).
The other thing you can try is turning off all those nice goodies in the board has in BIOS. One or more of those may be limiting your overclock. Good luck
-RuKK
krarg
04-28-2003, 10:46 AM
mike, if you don't mind my asking, what onboard features are you using? I'm thinking the instability might be caused by one of the onboard components on my motherboard, such as the networking or sound. Instead of trying to figure out which onboard device might be causing the problems, I figure it would be better if I narrow it down a bit first, since there are a -lot- of onboard devices on this motherboard.