Computer reads Athlon TBird 1333 as 1066

Daley

Junior Member
Dec 6, 2000
22
0
0
I have no idea what's going on with this, out of the blue my bios tells me my 1333mhz
is now 1066mhz. I have not ever OC'd the processor and I've tried flashing the bios to
a earlier release 3.5 although the 4.0 build did work originally.

My system specs..
Amd Thunderbird 1333 mhz AYHJA
Soltek SL-75DRV KT266
512mb Crucial PC2100 Cas 2.5 DDR
 

HappyPuppy

Lifer
Apr 5, 2001
16,997
2
71
Has it ever read 1333? At any rate, go into the bios and set the FSB to 133 with a multiplier of 10.
 

geek167

Senior member
Aug 14, 2001
516
0
0
DIE n00b and your repetetive topic! AUGH! Set the FSB to 133 MHz!!!!! Why is this question asked once a day here/!?!?
 

Crucial

Diamond Member
Dec 21, 2000
5,026
0
71
Welcome to Anandtech forums. Please dont let the comments of one reflect on us all.
 

axia55

Platinum Member
May 22, 2001
2,912
0
0
Some motherboards have a jumper that lets you sets the FSB from say, 100-132 and then 133-. Check that out.
 

minendo

Elite Member
Aug 31, 2001
35,560
22
81


<< DIE n00b and your repetetive topic! AUGH! Set the FSB to 133 MHz!!!!! Why is this question asked once a day here/!?!? >>


Why dont you chill out and maybe take some time to see that he has been a member of Anandtech since December 2000?

It sounds like your FSB might have gotten changed. Try setting it to 133 and see if you can get the processor to be recognized as 1333MHz again.
 

Aquinas

Member
Jun 28, 2000
143
0
0
Hi! This is not a stupid question at all. All of us need to learn at some point. In fact, this poor guys hasn't even responded to the new posts. It could be that there is more to his problem. There is a really good chance that his multiplier is simply set incorrecty. Perhaps he doesn't know how to change it...or even what it is. I think even basic questions like this should be asked in the forums. It would be nice if he researched it by searching for the answer ahead of time but we have all been in shoes before I suppose...cheers.
 

Daley

Junior Member
Dec 6, 2000
22
0
0
Thanks for the replies, guys and girls?. As it turns out the processor
had been doing a slowburn, shortly after I posted the message the
processor totally fried. The fsb was the first thing I had checked.
Lucky it was under warranty. Ncix gave my a new processor within
four hours :)

Thanks
 

Daley

Junior Member
Dec 6, 2000
22
0
0


<< Has it ever read 1333? At any rate, go into the bios and set the FSB to 133 with a multiplier of 10. >>



No need for the rudeness, as it turns out the proc was cooked. Shows
what you know Kook!!
 

Daley

Junior Member
Dec 6, 2000
22
0
0


<< Welcome to Anandtech forums. Please dont let the comments of one reflect on us all. >>



I never would there is always one kid that won't play nicely in
the sandbox..