cant get 133 FSB to work on KT7A-RAID

[Nealybird]

I just got a 1.2 tbird (200) and an Abit kt7a-raid. The L1 bridges were already connected and I can clock the thing all kinds of different ways, but can't get close to 133fsb. Tried multipliers as low as 7, but
it won't POST. Using the 100/33 setting and the "plus" setting I can get up to 112 or 115 but anything higher gets me nothing. The best I've gotten is (110 x 12.5). Bumped the voltage up, and back down. It's micron pc133 mem and some globalwin or something fan. Anybody know what's going on?

[NDD]

Got 1 GHz AXHA T-Bird (200 MHz FSB) and KT7A, have no troubles going up to 133/33 setting, with locked multiplier I'm getting 1330 MHz. Check what processor you got (second line under "AMD Athlon"), some of them just can't do higher then yours did.
Also, try HOSTCLK setting in Softmenu, my Micron memory does 157 MHz easily, but maybe it's cause the problem in your case.
Also, o/cing affects PCI bus, you must have good HD/PCI cards/AGP video in order to run PCI > 43 MHz ...

Best Regards ...

[Nealybird]

Thanks for the reply. I don't know the exact markings on the chip, other than that it was a 1.2 and 200 mhz bus. At the 133/33 setting I wouldn't be overclocking any pci or agp devices....I'll mess with it some more tonight... Anybody else got more info for me?

[Nealybird]

... AND It doesn't seem to just be a matter of the chip not being able to handle the speed since it does close to 1.4ghz and I can't even get it to do 7 x 133, which is only 931!
must be something goofy.

[Bovon]

Are you absolutely, without a doubt, certain that the L1 bridges are factory closed...many were not. The 200 generally indicates open bridges. Even some C series 266 cpu's had cut bridges. These are extremely hard to see. I had to finally get a jewlers eye loup to see them. In normal but good lighting, they looked closed to me.

[Nealybird]

bovon,
yea I'm pretty sure. If they weren't closed I wouldn't be able to do different multipliers. And it's working at 12.5 instead of 12 now, and I think I had it on 11 * 115 or so, too. Am I thinking right?

[Atomic Rooster]

Just another silly question. Is the mobo a KT7-RAID or a KT7A-RAID? It almost sounds like you got the KT7 because those rarely go over 115mhz FSB.

[Nealybird]

it's a kt7a raid for sure. says so several places on the mobo.

[Bovon]

Nealybird

'scuse me if I'm wrong here. I'm not familiar with the KT7A myself, but I believe you should have multipliers available in both 100 fsb and 133 fsb mode. If this was not correct, how in the world could you run anything from 600 mhz (6 X 10 @ 100 fsb) to the 1.2 mhz (12 X 100 fsb)?

If the cpu is locked, I don't think you will even have the option to change to 133 fsb from what I have read.

[Nealybird]

yea, it's got 2 different preset settings for 1000 and 1200 (one for 100 and one for 133)as well as 750, 800 etc. Or you can put it on "user define" and it's got 100/33, 133/33, 103/34, etc with an additional box for "cpu fsb plus" which adds whatever # you put there (0-28) to the fsb. And then a field for the multiplier of course.

[Anton Rohan]

Hello,

I have a KT7A-Raid MB with 200 FSB and 266 FSB 1 gig TB. I have not overclocked either computers. But when I build both of them I had trouble in getting 133 MHz (although I could get 100 MHz without difficulty). It will do the memory test and stop. After a whole lot of dinking around I started pulling the RAM. I had 2 PC 133 micron RAM. Once I pulled the first RAM it booted up fine.

Why don't you try different RAM of if you have 2 sticks pull one and see.

Another idea is try to update the Bios and see.

Good luck.

Rohan

[Nealybird]

good idea... thanks I'll try that now.

[Atomic Rooster]

Nealybird -
If you have the K7 CLK CTL option in the Advanced Chipset Features in the bios set it to default. That has helped others use the 133+fsb settings.

[Nealybird]

Anton,
hey, I owe ya a cigar! Took out the 256 micron I just bought and put one of my old 128's in at it worked.... still getting crappy 3dmark2001 score tho'. oh well, back to tweaking.

[NDD]

Yeah, 133/33 can't consider as o/cing, as it's "natural" mode. Yet, if you can, get another processor just to see how it works, I went thru few till I find mine http://www.sysopt.com/forum/smile.gif
Another thing, even thought you doing "standard" o/cing with 133/33, is changing CAS setting from 2, which you probably have, to CAS3.
Good luck !

Best Regards ...