IWill KK266-R + 1.2 'C' Thunderbird...

[memnoch411]

I can get this chip to run at 132Mhz fine but when I switch the jumper to 133 it woun't even POST!
I have Rev. 1.1 and the bios is updated with Iwill's March 5th update and the chip is [edit]factory unlocked[/edit]. Anyone have any ideas?

 

[jaybert]

I dont know if this has anything to do w/ it...but the kk-266's have been recalled, dunno what the reason is or why..just an idea

 

[digi187]

the rev 1.2s were recalled... anything else works good

 

[gdfleo]

I can send you an e-mail directly from Iwill telling me how to do this.Haven't tried it myself yet.
ver.1.1

 

[memnoch411]

That would be cool. My email is d_liepold@yahoo.com.

Was just looking at another thread that said the 1.2's are coming out unlocked. Sure enough, I set my multiplier at 13 and voila!... 1300Mghz. I still want that 133 FSB though.

 

[memnoch411]

Well, after browsing through other threads I connected my L7 bridge (there was only 1 left to connect) giving me a default voltage of 1.87 (according to Via's Hardware Monitor) and I still could not get it to boot at 133. I've tried setting the multiplier to 12, rebooting, multiplier to 9(default), rebooting, shutting down, switching FSB jumper and still nothing. CMOS clearing and different multiplier settings were thrown in the mix also.
*Sigh* What am I missing here? AAArgh!!!!

 

[kgraeme]

I can't get to 133 either. I have a 900Mhz with L1 and L7 unlocked, and even if I drop the multiplier down to 5x, it won't post at 133. I can't even run stable at much more than 120 FSB. The memory can handle it. It's Mushkin, and I have it running right now at +33 host bus, so it's at 153 and stable.

 

[dennilfloss]

If it were a 'B' Tbird, I'd say that maybe you have one of those mobos that need you to switch a jumper to go from 'up to 132MHz' to '133+MHz'. Some mobos like the MSI K7T Turbo will try to post for a fraction of a second at default multiplier x 133MHz, that is for you guys 12x133 for a B Tbird. Above what your system can handle,so no post before Bios gets a chance to take over. Many threads in the mobo forum describe this problem. However, I don't know why there should be a problem with a C Tbird, unless your mobo reads it as a B. If that is the problem, you have to modify the L6 bridges to give it a lower default multiplier.

thread

 

[memnoch411]

I don't think that is the case (with me anyway). I have gotten this chip to POST at 1.5G (windows protection errors though) so even if it was trying to boot at default settings the chip would still be able to handle (i have kingmax PC150 Ram also). Currently I am running at 12x120@1.87(L7's connected) and everything is maxed out in the BIOS except for HSTCLK wich is at default insteaad of +33. Let me know if there is a flaw in my logic because I am completely stumped at this point and am ready to give up my first born just so I can get up to 133fsb!

 

[radium]

i have a 1.2 C core bird also, and on my first boot i went to 140 x 10. it runs with zero flaws at that speed, doesn't like 145 x 10 or 150 x 10. in fact at 150 x 10 i get the same protection faults that you get. i'm wondering what it will take to get past that.... anyways just thought i would let you know that in case you get the 1.5ghz fever

also i'm using a kt7a motherboard

 

[tblubrd]

Memnoch, I think you may have downloaded the wrong bios. While it shouldn't matter, the board you have is (my guess) not the one the March 5 bios was supposed to correct. Check this link and see if your board is a product no.35102A (mine is also a version 1.1 but it's not that product no.). I have the same board version you do but I had no trouble posting to 150mhz before loading an OS. Currently at 140mhz and tweaking.

 

[memnoch411]

yup, it's 35102A. the bios and my board that is. you almost got my hopes up.

 

[memnoch411]

Anybody else got some tricks up there sleeves I can try? I'll be talking to IWill tech support today so hopefully they will have some more options to. I'll keep ya all updated.

 

[memnoch411]

Well... I just got off the phone with Iwill tech support and they were absolutely no help at all. All they said is that it SHOULD work. well, no chit cherlock. He then went on to say it may be a bad CPU EVEN though I can get it to POST at 1.5 and run stable at 1.44 and run it at 132fsb. Now I'm in a bad mood. *sigh*

 

[Kuz]

Id put the jumper on the 133 setting and then make sure to clear the cmos when its there. Then cross your fingers and boot !

 

[etech]

With the bus set to 133 your processor is trying to boot at 1596 until it reads the bios. Chances are it isn't going to make it.

Tom's Hardware had an article on changing the default multiplier. Might be worth a look.

 

[etech]

With the bus set to 133 your processor is trying to boot at 1596 until it reads the bios. Chances are it isn't going to make it.

Tom's Hardware had an article on changing the default multiplier. Might be worth a look.

 

[memnoch411]

My default multiplier is 9. I have the 'C' version 1.2G chip. with the jumper on 133 it would be booting up at 1200(1197)Mghz.

 

[memnoch411]

Well, I finally figured it out! It turned out to be because of my sound card. Wether it was the sound card or the fact that it was in PCI slot 5 causing me to not be able to boot with the jumper on 133 i'm not sure about. I probably should have tried to put something else in that slot just to find out for sure but i was just so damn happy i forgot about it. heh heh
For your information it was a Phillips Accoustic edge sound card and I am using an All-In-Wonder Radeon.
I am currently running at 1416Mghz (9.5x149) with fastest memory timings (w/ auto-interleave) and 1.70v. So far so good.
Thanks to everyone for their help. woohoo!