9 replies
by wcp
by etolentino
by thechas
I have seen a web post, and have personally fixed several Socket A system problems by manually setting the CPU clock and multiplier in BIOS settings.
I have only seen this problem on systems with SDRAM.
The BIOS detects the CPU properly, it just sets the bus and multiplier incorrectly.
Some BIOS's set the bus speed wrong, and thus under-clock the CPU.
For what ever reason, AMD CPUs don't respond well to being under-clocked.
If you have PC-133 SDRAM,
set the bus clock to 100MHz.
Set the multiplier to 10X.
Set the RAM clock to FSB + PCI, or 133MHz.
Chas
by alpha-male
I agree with Chas completely....additionally, on many of the early Athlons, the systemboards do not detect the CPU voltages correctly. MAKE SURE that the voltage you are running at is correct for your processor. I can't tell you how many times I hadto change the autodetected voltages because they were running an Athlon with "too much juice".
Hope this helps!
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending