Hey all,
Just replaced an old 100MHz FSB 1.0GHz Athlon with a 2000 XP. The problem is that its posting as a 1250MHz (12.5x100) chip, not 1667 (12.5x133).
Ive 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. Ive even tried manually changing the multiplier so that its wrong, but it will still post as 1250MHz.
BIOS is latest version, but its not an old motherboard anyway.
PSU is a Zalman 300W, Ive tried disconnecting all power plugs but the motherboard, so I dont think its that.
Searched on the internet and it seems a few people get this, but people say change the settings in the BIOS / Motherboard (which Ive done) or change the battery (really? the board is about a year old) - didnt find positive replies to changing the battery either.
Anyone know whats going on? :?
Edit: finally got it working! :)
How?
Just in case anyone else has the same problem in the future.
Normally things like this happy when BIOS resets to fail safe defaults... loading optimized defaults normally solves it :)
If the motherboard doesnt allow you to post the chip in the "100Mhz" setting - meant for earliest Socket A chips - then reset the BIOS. Figure out how to do this first before doing it - I thought because the GA-7N400L was an nForce2 it would behave exactly like an NF-7S and I tried the quick-off-quick-on trick a bit too many times that I think I corrupted my Windows installation.
Once you manage to post in the "100MHz" setting, you should be able to "overclock" the chip to the proper 133MHz setting (or beyond should you desire). Might seem strange that posting in the "133MHz" setting acts like a 100MHz setting no matter what you do, but posting in the "100MHz" setting lets you do whatever you want to the FSB.
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.
QuoteNormally things like this happy when BIOS resets to fail safe defaults... loading optimized defaults normally solves it
I tried the 2 pre-saved settings in the BIOS quite early on to no avail. That was one of the many solutions I read elsewhere. Seems people have varying degrees of success (and quite a lot seem to be Gigabyte owners!).
Could just be that "CPU INTERFACE" is disabled, or something along those lines.
Mine allows you to define clock speeds but wont actually activate them unless I turn on something else (think its called cpu interface).
Or... a jumper on the board that is forcing the processor to run at 100mhz instead of what you set.