Tweet
Last Christmas I got my comp... and I never really fixed this problem (worked on it for a while and just gave up) The problem is that my Athlon XP 1800+ will only be recognized as an Athlon XP and only run at 1.14 Ghz as opposed to 1.33. It doesn't sound like much but the extra .2 ghz probably costed me 75-100$.
The reason why it does this is that the mobo is only running at 100 mhz FSB. When I set the FSB to 133 mhz the computer properly recognizes the processor but it won't boot so that doesnt do much good. When I start up with the 133 mhz I get a stop error saying that a system file is corrupt (the first time it was ntfs.sys but it changes). I've reformatted the system recently and the problem still occurs. If you need the specs for my mobo I can't get it to you until tomarrow, sry (I know its supposed to run 133 mhz system bus and is compatible with Athlon XP, and I've also updated the bios) Any help on this would be greatly appreciated
And my other question is if I settle with the slower FSB (and hence a slower processor) will the slower FSB really slow down the overall performance. I don't know how much the FSB speed contributes to performance so I really don't know. Thanks alot
The mobo is FIC AD11 (the Athlon XP one).
Although it says 266 FSB I can assure you that it only runs at 100 or 133 mhz. Also, I looked for the clock multiplier again in Bios and couldn't find it. The closest one to that is "CPU Host/PCI Clock" (this setting was under the Frequency/Voltage Control category) the options for this setting are:
Default (currently checked)
100/33 MHz
120/30 MHz
133/33 MHz
Two days ago I checked the 133 MHz assuming that was the FSB speed. Then the monitor wouldn't respond and my comp wouldnt post so I changed the jumper on the mobo to 133 MHz. The monitor then responded and it posted but it wouldn't boot (that is where I got the error messages) but I could go into Bios and change the setting back to default and then I changed the mobo jumper to 100 mhz and my comp was back to normal (but still at the slower speed).
If I do end up buying another mobo and Athlon XP mobo's to recommend??
Thanks
The reason why it does this is that the mobo is only running at 100 mhz FSB. When I set the FSB to 133 mhz the computer properly recognizes the processor but it won't boot so that doesnt do much good. When I start up with the 133 mhz I get a stop error saying that a system file is corrupt (the first time it was ntfs.sys but it changes). I've reformatted the system recently and the problem still occurs. If you need the specs for my mobo I can't get it to you until tomarrow, sry (I know its supposed to run 133 mhz system bus and is compatible with Athlon XP, and I've also updated the bios) Any help on this would be greatly appreciated
And my other question is if I settle with the slower FSB (and hence a slower processor) will the slower FSB really slow down the overall performance. I don't know how much the FSB speed contributes to performance so I really don't know. Thanks alot
The mobo is FIC AD11 (the Athlon XP one).
Although it says 266 FSB I can assure you that it only runs at 100 or 133 mhz. Also, I looked for the clock multiplier again in Bios and couldn't find it. The closest one to that is "CPU Host/PCI Clock" (this setting was under the Frequency/Voltage Control category) the options for this setting are:
Default (currently checked)
100/33 MHz
120/30 MHz
133/33 MHz
Two days ago I checked the 133 MHz assuming that was the FSB speed. Then the monitor wouldn't respond and my comp wouldnt post so I changed the jumper on the mobo to 133 MHz. The monitor then responded and it posted but it wouldn't boot (that is where I got the error messages) but I could go into Bios and change the setting back to default and then I changed the mobo jumper to 100 mhz and my comp was back to normal (but still at the slower speed).
If I do end up buying another mobo and Athlon XP mobo's to recommend??
Thanks
and that didn't fix it either:cry:
Comment