Wierd O/C on IWill kk266 and Duron 700...need help

[FiDo14DiDo]

I unlocked the bridges okay (I think) with the defogger method but when I boot up with the multiplier set at 9@100, it boots up at 800/850. Then when I reboot, it shows up as 550/600 (on the same multiplier settings!!!). I have adjusted the vcore voltage accordingly with each multiplier change.

Anyone have any clue what is going on??? Even if the chip has low overclocking ability, it still should show up as 9@100=900 before it locks up, right? Thanks

 

[ivanov]

try updating to the new bios that's released already... that might help... if not, you may not have unlocked the bridges properly

 

[Angst]

It's not a penciling problem...there's a small batch of rev 1.2 boards that have serious multiplier issues (most CPU's get stuck at 8.5). This is the case with my KK266 + tbird 900...latest BIOS revision (dated march 3, i believe) says it fixes CPU frequency problem, but it doesn't. I'm currently awaiting an RMA for my board...

 

[PlunX]

I was also unfortunate to get a KK266 with multiplier problems.. RMA that sucker and get one without the multiplier problem.

 

[MoPiC42]

Bump...

I just bought a KK266 from new egg (where does it state what version it is?) a couple of days ago (3/4). I also got a Duron 800 (upgrade planet) and a 256 MB stick of PC133 CAS2 (crucial).

I have the same problem with the 100/133 jumper - won't post, but I thought that might be a Duron problem.

I also have a weird oc problem - on auto settings, it found it (correctly) at 800 MHz, but any setting I put higher than X8.0 (or auto) gives me 850 as a max. If I hadn't penciled correctly, it should still be giving me 800 (so I think I did unlock it right).

I updated to the newest bios (3/5 according to IWill's site) before trying to oc.

I REALLY don't want to RMA this thing - my old setup (Asus P2B-F and P3-450 and 256 MB PC100) is already spoken for, and I can't be without right now.

Is there an older bios that works? How can I tell what revision I have? Is there anything I can do? Is this a problem that they are able to fix in the bios (or is it unfixible via BIOS, requiring an RMA)?

Thanks!