- Joined
- Apr 22, 2001
Seeing as how no matter how many times I try I can not seem to get the multipliers to work properly, I figure I may as well give FSB overclocking a shot.
As expected, problems have arisen.. and these diagnostic LED's on the board are just buggin me now :\ I have a stick of 128mb pc133 ram, but I can reach a max of about 116fsb with stability, anything greater and it won't post. Usually stops at "Decompressiong bios image to ram" after a reboot. Well anyway, I figure maybe that's just a strange fsb to be playing with so I decided to set the jumper on the board to default to 133bus (the jumper gives you the option of 100-132, and 133-160).. here's what occurs when I set it to 133fsb:
LED's all go RED which is the first step and means (System Power ON) but do not even twitch to the next test which is (Early Chipset Initialization). However, in certain situations (i'm currently unaware as to what provokes this) it displays 0100 which means (Failure to initialize keyboard controller).
Should I begin blaming the board? Or perhaps realize that maybe my chip just doesn't like 133fsb? Maybe I should just go crazy ;D
And yes, I have updated the bios.
As expected, problems have arisen.. and these diagnostic LED's on the board are just buggin me now :\ I have a stick of 128mb pc133 ram, but I can reach a max of about 116fsb with stability, anything greater and it won't post. Usually stops at "Decompressiong bios image to ram" after a reboot. Well anyway, I figure maybe that's just a strange fsb to be playing with so I decided to set the jumper on the board to default to 133bus (the jumper gives you the option of 100-132, and 133-160).. here's what occurs when I set it to 133fsb:
LED's all go RED which is the first step and means (System Power ON) but do not even twitch to the next test which is (Early Chipset Initialization). However, in certain situations (i'm currently unaware as to what provokes this) it displays 0100 which means (Failure to initialize keyboard controller).
Should I begin blaming the board? Or perhaps realize that maybe my chip just doesn't like 133fsb? Maybe I should just go crazy ;D
And yes, I have updated the bios.