• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Athlon 1133 Problem

Dittohead

Member
I just bought an Athlon at 1.13 gHz and put it in my ABIT KT7 but I've been having a problem. As far as I can tell it only runs at 850 mHz. I've changed the multiplier factor in the BIOS to 11x but it doesn't change anything. I've updated my BIOS and that didn't help. I suppose the processor could be 850 mHz (although it's supposed to be a 1133 mHz). I'm really stumped here. Any help would be appreciated.
 
What is the multiplier at right now? What is the FSB? My best guess is that you have it at 8.5 x 100 when it should be 8.5 x 133.
 


<< Ah. You're right. I have the FSB set at 100. That should fix it. Thanks. >>


Glad I could help. Hope its all up and working for you now.
 
Unfortunately that did not fix the problem. However, I do know one (rather costly) way to fix it now. I appreciate the help.
 
Honestly, I can't say for sure. However, I think I have two sticks of 133 and an additional stick of 100. I guess that other stick would create a problem, huh?

Edit: I took out the PC100 assuming it might cause a problem (would it?). No change. But I'm fairly sure my motherboard is the source. When I change the FSB it scales the PCI bus speed, which might cause problems. I happen to have a brand new KT7A which I'm not using. I think the processor would work fine with it. Only one way to find out I guess.
 
The problem is that the kt7 (kt133) board you are using doesnt support a 133mhz multiplier which the 1.133 athlon reguires. The Chip is supposed to run at 8.5 x 133 = 1133 but as your board cant manage the 133mhz bus speed you are stuck at 8.5 x 100. The only way around the problem is by unlocking the multiplier and increasing it to 11x or 11.5x or change for a kt133a based board or upwards.
 
Back
Top