MSI K7T Turbo BIOS v2.5 (NON BETA)

[AirJames]

Here's an email regarding the mutliplier issues
I have already checked this issue and will inform our BIOS engineer. We might implement this with our new BIOS release, in the near future.
This problem exist because the duron microcode can only support the following combination you tried. If we get the new microcode we can add it to our BIOS.

We are sorry for the inconvenience.

-----Original Message-----
From: James Cho [mailto:jcho2@san.rr.com]
Sent: Wednesday, March 14, 2001 1:44 AM
To: support@msi.com.tw
Subject: Multiplier problem with Duron 600

This processor worked fine at 1000Mhz on an Abit Kt7 RAID. I bought the K7T
turbo Raid a week ago and it only boots up at 1000Mhz sometimes. It boots
at 600, the default speed, after shutting down sometimes. I've been on
Anandtech forums and other amd/via forums and all the people are getting the
same problems. Here's one post:
Hi yodel,

I have the same problem (almost) with you (using the V2.4 and V1.0b16). I
did some experiment again and found the "multiplier bug" like you did. I can
do 7.5x133 with my Duron 600 (w/ KT7A), and from what I got by changing the
multiplier I get these results:
6x133=800 (6x133) ok
6.5x133=866 (6.5x133) ok
7x133= fail
7.5x133= fail
8x133= fail
8.5x133= fail
9x133=665 (5x133) ok
9.5x133=731.5 (5.5x133) ok
10x133=800 (6x133) ok
10.5x133=866 (6.5x133) ok
11x until 12.5x=fail

fail=no post/hang
ok=load windows and stable

Weird huh? I already contacted MSI about this and I'll let you know. Btw, do
you have the voltage problem too? On my Turbo-R if I set the voltage to
1.525V, I'll get 1.65V. Set it to 1.6V, I'll get 1.725V and so on.

 

[TungFree]

tracerbullet,
Ivanov has a 900mhz T-bird and mostly the one meg and over T-birds have peroblems the below a meg worked fine b4 as I recall from a few weeks back.

 

[tracerbullet]

Once I get Windows up and running and doing everything I want (if ever), I'll launch into the O/C. I wonder if maybe it wasn't the 7 x 120 ~ 10 x 120 at monentary bootup that did it. If the multipliers are off, maybe I was gunning on a 12 x 120 or something wierd instead - as might be indicated by AirJames's post of that multiplier not running.

I'm considering that my first step will be to alter the bridges to set a different default multiplier, perhaps just 7 or 8 to take care of it, but am unsure about how to do that yet.

 

[domino888]

I have duron800 with the bios v2.5.
default: 8
8.5: 8.5
9: 7
9.5 7.5
10 8
10.5 8.5
11&up hang

So,seems for different cpu, same multiplier set
will generate different actual value.

 

[RBuck]

An update: (I've been sick as a dog so I haven't been posting..)

I did finally get the board to do correct multipliers, with the 1.6overclockers bios and 133fsb. I have an unlocked 1gig tbird. This is exactly what I did to get to 7.5x133=1000mhz. I will be going higher but figured I'd start at 1gig with 133fsb for a baseline and it has been running beautifully, I will be happy if this is as high as it will go. 133fsb is very noticeable on an athlon. And, this motherboard ROCKS, you just have to be willing to work with the quirks and crappy tech support.

If you'll remember from my post, the board was correctly resulting from 5.5, 6 and 6.5 multipliers. The board was in 100fsb mode, so I set the 6x multiplier. It came up correctly as 600mhz. I powered down the system and toggled the 133fsb mode with the jumper. I then booted up the system and it came up as expected at 800mhz. I then went to the bios, changed my multiplier to 6.5. Exited bios, saving changes and came up as expected at 866mhz. I then went into the bios and very nervously changed my multiplier to 7 (you'll remember this was resulting in 1100mhz in 100fsb mode, meaning it was translating as a x11 multiplier, and 11x133 = 1466mhz eek!). Exited bios, saving changes and monitor went into power save, system started making a repeated beeping sound (very scary). I quickly unplugged my PSU (hate the delay caused by ATX power supplies, so I go for the source ). I changed my fsb jumper back to 100fsb mode, and powered her back on. Low and behold it came up at 700mhz!. Powered it back off, removed the jumper and wallah it came up as 933mhz! So the 7x multiplier was working! I then went into the bios and changed my multiplier to 7.5x (nervously). Exited the bios, saving changes. And bam, got the beeping again and monitor went to power save. Unplugged the PSU (quickly) and this time, I just plugged the PSU back in and re-applied power. Wallah, came up at 1000mhz with 133mhz fsb!!!

So the secret, at least for my system is to disconnect power after exiting and saving the bios changes. If the system is allowed to boot itself, it will fumble the FSB. Now, I have rebooted this system both warm and cold many times since applying the 7.5x133=1000 and haven't had a hitch yet. The multiplier is sticking through everything. So, Im very happy. I'll soon be revving it up higher Hope this helps everyone, lemme know how your experimenting goes!

 

[tracerbullet]

Awesome.

If you take a glance around over the last few days, I reiterated the multiplier problem in another thread, redundant info basically acknowledging that all boards have this goofy problem.

Someone else recently posted (it's at or near the top) this same thing, to pull the power plug during the restart, and it will stick the multiplier. So both of you are on to the same thing.

I noticed mine acted differently on a restart vs. a cold boot, but hadn't gotten this far into it. So for you and the other guy, kick ass!

We're some of the first with these boards, it's nice to finally have sorted through some of the bugs. It's almost time for someone to make an MSI K7T / K7T RAID setup FAQ. Any takers?

 

[hydrobum]

...sigh..I've been at this for half a day and still can't get this POS to boot up at 7x. did everything RBuck mentioned, but ....grrrrrrrrrrrr.... no can do.

It just hangs at 7x 133FSB. When I put it back to 100FSB, it just beeps, then have to reset the cmos.

help? :disgust:

 

[RBuck]

More info about your config and unlocking.

 

[w9design]

Here are my results with a Week 6 AXIA Athlon 1200:
All are 100% stable and post correctly unless stated.

12x100 : 1200MHz : obviously OK
13x100 : 1300MHz : Posts and runs fine
14x100 : 1400MHz : Will not POST at any voltage
15x100 : 550MHz : Apparently 15x is being remapped to 5.5x (or the other way around).
13x108 : 1400MHz : Just a control to show that it's not the processor that can't do 14x100.

Nate

 

[hydrobum]

I got a 900 tbird. My L1 bridges and L7 are connected...several times.
Tried connecting the L6 bridges so that it would boot up as a 700tbird, but still no can do. When I have it running at 6.5x133, it boots up fine. But if I change it to 7x133, all I get is a blank screen, no beeps.
So I stick the jumper back for 100FSB, then all hell breaks loose (beeps).
Pull the power supply, and then have to reset the cmos as it won't boot up again. Funny think I've noticed is that sometimes, it boots up at 900mhz when my jumpers are at 7x100. Weird huh.

Think I have decent cooling as I have the FOP32++ and 4 fans in my Antec sx830 case which sounds like an airplane when it's on. Voltage shouldn't be a problem as I have connected my L7 bridge to kick up the default vcore.

Anyway, hopefully I don't crush my cpu which I thought I did twice yesterday taking it off from the FOP32++ heatsink. What a pain!

 

[Regalk]

And yet MSI is being crowned as one of the most stable mobo manufacturers - hmmmm. I have a TBird 900 that runs at the following multipliers:
7 x 133 and all the way to 150 (did not ry higher)
7.5 x 133 to 143 - still no problems at this multiplier (I have to admit I only use 3DMark and burn in programs to test stability - no real life). Currently at 143 x 7.5 and have TV on left monitor and Internet on right monitor - DUAL babies
8 x 133 - absolutely no problems - read as 1066
8.5 x 133 would not boot.
At 100FSB can go all the way up to 10.5 X 103 but thats as far as stability goes.
I do not have a multiplier problem as others apear to be having except it does tend to beep a bit after a drastic change in multiplier SO I just power off and on again.
ONLY PROBLEM I can't power up normally - have to hit rset ONCE to power up (just like my A7V did in the past which was solved by closing L7). Closing all L7 does not help here.
Using the latest oC bios.
BUT HOLD ON it still can't beat my other machine with the IWILL KK266.

 

[YouniorX]

HELP!!!!! I just got my board (K7T Turbo R Rev. 3.0B) few days ago. I wanted to flash my bios to 1.0v16 (overclokers BIOS) but whatever I try, after it gets to flash utility screen(awdfl789) it just sits there untill i hit the reset switch. (Same thing with the 2.5 Bios). Did anyone try different flash utilities? Is there like a jumper setting or something that would keep my from being able to falsh the bios???
Please Help... I'm getting desperate....

 

[hocktwoie]

I had the same problem a few weeks ago. Someone told me to do this:

go into your BIOS setup and load defaults (either optimal or safe)
save and exit BIOS setup.

now try the flash utility.

It worked for me... hope it helps you out.

 

[YouniorX]

Thanks for the response Hocktwoie but unfortunately that didn't work for me. I have tried both optimal and fail safe defaults but sill when I try to flash the bios it gets to the flash utility screen and it just sits there until I reset the box.
Any other ideas???.....Anybody......Please!!!!!!!!!!!!!!!!!

 

[RBuck]

Yank all components from your system down to the bare bones. Video, (1) dimm, processor, floppy (to boot and flash) and thats it.