2000XP posts as 1250MHz (not 1667MHz)

[ACiD303]

Hey all,

Just replaced an old 100MHz FSB 1.0GHz Athlon with a 2000 XP. The problem is that it's posting as a 1250MHz (12.5x100) chip, not 1667 (12.5x133).

I've changed the settings on the motherboard (Gigabyte GA-7N400L), AND in the BIOS - tried 100/133/166 FSB speeds and they all post as 1250MHz. I've even tried manually changing the multiplier so that it's wrong, but it will still post as 1250MHz.

BIOS is latest version, but it's not an old motherboard anyway.
PSU is a Zalman 300W, I've tried disconnecting all power plugs but the motherboard, so I don't think it's that.

Searched on the internet and it seems a few people get this, but people say change the settings in the BIOS / Motherboard (which I've done) or change the battery (really? the board is about a year old) - didn't find positive replies to changing the battery either.

Anyone know what's going on?

[awm]

Look at the motherboard dip switches/jumpers, I had a similar problem and it was set at the wrong bus speed.

[dave87]

Yup, need to set it to 133FSB one way or another.

Changing the multiplier wont work unless its an early chip, in which case you'd face stability issues anyway...

[ACiD303]

This is very bizarre. Got it working, but very bizarre.

After a few BIOS resets (as it would no longer post - and managing to corrupt a Windows installation along the way), it allowed me to POST the chip in the 100MHz setting even though it should be 133MHz. From there I could "overclock" it to 133 (well, beyond too but how stable's another question). . . so it seems normal now. A bit toasty, but got it working

Begs the question why would you have a 133/166 setting if you cant use it - Gigabyte implicitly states that this setting is for palamino/t-bred//bartons etc. (any XP chip), yet you use the 100 setting meant for early Socket A Athlon/Durons.

[streetster]

This is very bizarre. Got it working, but very bizarre.

After a few BIOS resets (as it would no longer post - and managing to corrupt a Windows installation along the way), it allowed me to POST the chip in the 100MHz setting even though it should be 133MHz. From there I could "overclock" it to 133 (well, beyond too but how stable's another question). . . so it seems normal now. A bit toasty, but got it working

Begs the question why would you have a 133/166 setting if you cant use it - Gigabyte implicitly states that this setting is for palamino/t-bred//bartons etc. (any XP chip), yet you use the 100 setting meant for early Socket A Athlon/Durons.

My First gigabyte (7zx-r or something) socket a motherboard didnt actually support 133mhz fsb despite having "100/133 fsb" in massive writing on the box... which was fine for my duron 750 but I ended up getting a nforce2 board when i upgraded to an athlon XP...