KK266 will not boot when jumpered to 133

gerryko

Member
Dec 19, 2000
42
0
0
I want to overclock my Iwill KK266 so I switched the jumper to 133 but the system will not boot.
Am I doing something wrong here? Can't get to the bios with the jumper set to 133.
 

dahbusdriver

Junior Member
Dec 11, 2000
14
0
0
try this.

1)set jumper to 100
2)boot into bios and lower multiplier (i used 7.0 to start with on my 1000mhz Thunderbird). Also make sure the voltage to the core is not too high because for some reason I think mine was above default.
3)shut down
4)set jumper to 133
5)reboot

it should work. it did for me.
 

WarCon

Diamond Member
Feb 27, 2001
3,920
0
0
Read some of the other posts on here, there have been alot of probs being found with that mobo. And I think 133 fsb was one of them.
 

Jakki0

Member
Nov 29, 1999
119
0
0
To dahbusdriver:
are those instructions for a unlocked chip or a locked one? I ask because my duron is a 750MHz locked and I am wondering if they could work for me.
 

dahbusdriver

Junior Member
Dec 11, 2000
14
0
0
those instructions were for the unlocked. to change the multiplier your cpu must be unlocked. i unlocked mine with the rear window de-fogger kit from autozone. it's pretty easy, just take your time.
 

gerryko

Member
Dec 19, 2000
42
0
0
Still will not post at 133 x 5 (800 Duron) 1.6 v
I know my multiplier is unlocked because I can do 7x100
Do I have to RMA this mobo or will Bios updates be able to fix this?
There's a lot of shipping charge from Hawaii.

This is a 1.1 version board
 

gerryko

Member
Dec 19, 2000
42
0
0
Believe me I'm no expert, but basically connecting the L7 bridges ups the core voltage of the Duron to 1.85 volts.
So after connecting those bridges, go into the bios and reduce the multiplier (for me 5.5 is good because that is going to be multiplied by 133 soon and I have a Duron rated at 800 mhz, so I have a lot of room to play with.
Shut down, pull power plug (important), set jumper to 133.
Reboot, in bios readjust core voltage to 1.6 , and multiplier desired.

If you do not post you might try shutting down, clearing your cmos, set for safe defaults, optimal defaults, reduce multiplier and try again.

This seems to work for version 1.1