MSI K7T Turbo problem

[ericlp]

Got a 1 Ghz AMD Chip.

Changed the FSB to 133 ... Moving jumper 17. System now comes up to 1Ghz. But that is it. It won't even count the ram. It just comes up to first screen Main Processor: AMD Athlon(TM) 1000Mhz.

Tried reseating RAM and Clearing the CMOS.

Using some Micron/Crucial Ram 256Meg. Synch. 133Mhz. CL2

BTW this ram works fine at PC100 J17 On . But 750 Mhz isn't what I want to be running at.

Think I have bad RAM? OR?


Thank You for your help!

 

[clockhar]

So, what your saying is that everything works fine at 100 mhz FSB? If so, slowly overclock it until you approach 133. Then switch the jumper (J17 or whatever it is) back to 133 if it reaches it. Tell me what happens then ... oh yea, do you have the raid version of this board?

 

[ericlp]

slowly overclock it until you approach 133. Then switch the jumper (J17 or whatever it is) back to 133 if it reaches it

What do you mean overclock it? I'm not trying to overclock. I got a 1Ghz Chip. And it's suppose to run at 1Ghz. Yes it does have raid but, I am not using it(Nothing hooked up to it yet). Looks like you got the same board I got (KT133A). The documentation states. in order to get this to go to 1Ghz change the FSB to 133 X 7.5...

Maybe I am missing somthing but. Where in the BIOS setup can you specify the FSB settings? I thought it was iether 100 or 133 via jumper?

I am sure someone here knows how to set this up.

 

[DSB]

Let me ask a dumb question, what is the FSB rating of your CPU? is it a 100 or a 133. If its 100 and you set the jumper to 133, then you are trying to overclock and the CPU may not be able to handle it.

If the FSB is 133, then it sounds as if it may be a memory problem, make sure you set the bios to run a full memory check, this should spot any problems. Then try a different stck if memory, make sure it is AMD approved, try Crucial as they are usually super-compatible.

Hope this helps.

 

[ericlp]

I got AMD Thunderbird socket A 1GHz 266MHz Bus Retail Version.

I dunno seems to me if the chip can run at 100FSB then it could run at 133 with out any problems???

 

[DSB]

You are right, if the CPU is rated at 133 FSB then it should run at 133. If the system won't count ram them something else is wrong. Check the mobo manual to see if you can get the bios to auto detect the correct FSB for your Athlon. If the memory doesn't even count at 133 but is OK at 100, check in bios to make sure you don't have a setting somewhere which tells the bios to run the memeory at clk + 33 or something like that. Then it will be trying to run your memory at 166 (133 + 33) and that could be your problem.

 

[clockhar]

<<
What do you mean overclock it? I'm not trying to overclock. I got a 1Ghz Chip. And it's suppose to run at 1Ghz.[\q]

I didn't mean overclock your board. I just meant try to up the FSB little by little to see how high it goes. If that doesn't work, you might want to try and simplify the setup by taking everything out and reseting your CMOS. BTW, are you sure you got a 266 mhz FSB Thunderbird. Maybe you or the manufacturer screwed up the order some how. ... Also, I read some where that via screwed up on most KT133a chips it sent out from April on. So, how old is your MB? Maybe you got one of 'em faulty KT133a chips. You might want to return the board for a new one. Or just test out your config on another board (or your memory on another board). There are 20,000 things you could try out. Just try anything.
setup can you specify the FSB settings? I thought it was iether 100 or 133 via jumper?



... BTW, this has nothing to do w/ your issues, but when you are able to boot, does it take forever before it even begins to count the RAM? Mine does. Also, does your MB, spend like 20+ sec. checking for a RAID every time you boot? Mine does and those 2 long pauses are annoying???

 

[NesuD]

try setting the memory by spd in the bios if it isn't set to that already it should then set the memory settings to exactly the manufacturers specification for that bus speed. another thing you might try is removing all yourcards except the vid card ans see if it get through the mem test. check and see what the d-led code is that may also help pinpoint the problem.

 

[ericlp]

ClockHar... About how long is 'forever' for the ram to start counting?

Normally my board started counting the ram instantanisly after displaying the CPU speed.

I'll try leaving the system on and see if it will start counting the ram. I didn't even think to leave it on for longer then 30 seconds since I believe that even 30 Seconds is TOOOOOOOOO Long to wait.

I also get the 20 second searching for RAID... That is annoying...
I'll have a call into MSI pretty soon since. I iether want a replacment or a fix of some sort.


Nesud. Yeah I already pulled out all the cards. The only card in it... Is a WinFast Gforce II Pro Card... I've tried going into cmos and chaning it to pc 133. Still no go.

Also if this means anything I have no idea but the LEDS Stop on Green Red/Red Green witch stands for bios sign on.

I think that LED-D thing is a joke sorta...

Thanks for your help.

 

[ericlp]

I fixed it!!! Whoo-Hooo!

For some reason it didn't like the latest and greatest Flash.

So I used the .. W6330VMS.280 the 3rd one down from the top.

Flashed the system. Cleared C-Mos! And Wham-O! It works great!

Just ran the 3DMark 2001 and got a score 0f 2742 with out overclocking or overclocking the video card (YET!!) haha

Thanks for all your help!!!

 

[clockhar]

<< ClockHar... About how long is 'forever' for the ram to start counting?

Normally my board started counting the ram instantanisly after displaying the CPU speed.
>>



Mine waits about 15-20 sec before it even starts to count RAM. Others have posted the same problem. No one seems to know why some do it while other boards don't. Something to do w/ IDE configuration, but I did the same and same thing happens. Oh well, I guess I have to wait an extra min for each boot up.



<<
I also get the 20 second searching for RAID... That is annoying...
I'll have a call into MSI pretty soon since. I iether want a replacment or a fix of some sort.
>>



Weird. When I first got my board, this didn't happen. Then I reset my cmos and it comes up. I reset it again and the RAID wait goes away. I reset again and it stays (and has stayed since then). I can't get it to go away!!

I called MSI and the tech support guy is a joke. I don't even think he knows what I am talking about. He is just like 'that's part of the system - it happens all the time' ... I doubt it ... oh well, still a nice board

 

[NesuD]

thats great news Eric I am glad you were able to resolve the problem

 

[ericlp]

Clockhar... Yeah, that raid thing kept comming up for me right out of the box. Never got it to go away. Tho, I have NO problem with RAM count. You'd think they would make a jumper or bios disable switch for the raid. Altho, the way I look at it... I did buy the board with raid. So they probably figure if you bought it with the raid then you were going to use it.

Right now don't have the funds for a 2 40Gig Drives.

If I find a way to turn it off I'll PM you...

--Eric

 

[clockhar]

thanks, same here