K7S5A Pro and cpu settings?

[fyxxer32]

Got a used cpu from a friend. Athlon 1.2 ghz. I'm upgrading my sons pc. Bought a new K7S5A Pro and put it all together. 40 gb Maxtor, GeForce MX 200 , 512 mb pc133, etc. Aaaanyway, in the bios I've tried to set it to 100/133 , then it wont boot. It only will run at 100/100. What am I doing wrong? I thought this thing would run at that setting.

[Darthv15]

Did you try setting it to 133/133?

[woodbutcher]

fyxxer32
I've heard of that issue before but always with the non-pro version.
I take it the Athlon cpu is 200 mhz?
Do you have a spare stick of DDR 2100 you can throw in it to check out wether the no-boot issue is with the sdram only?

WB

[Peter M]

The board should and does work with 100 MHz CPU and 133 MHz SDRAM. However, just like any other performance chipset, it is not tolerating PC133 SDRAM that doesn't actually live up to that specification. Set to 100/100 and run memtest86 to assert whether that RAM is essentially OK. Then switch to 100/133 with the slowest RAM timings possible (higher numbers mean slower timings). If no go, then well, not much you can do, other than use better RAM.

[fyxxer32]

Did you try setting it to 133/133?

Havent tried that,yet. I "guess" it is a 200 mhz cpu, I just clipped it in. I will run memtest. EXACTLY what and where should I change the timings? In the bios I mean. What should I start with?

well first thing is i'd try to find out what the fsb of the chip is no need to waste the speed if it can be set at 133/133...these boards default it to 100/100 no matter what. but your memory settings should be able to go 133w/o issues. the timings on my board are set to normal timing mode, spd cas latency , 6 whatever that was sorry might not be in your bios, 4 same thing. I run the oc'able bios from cheepoman with an oc of 143/143 on my xp2000 with pc133 need some ddr i know but it works fine for now

[Omardeth]

i have to agree with peter here sounds like the pc133 ram just doesn't do pc 133 . i have used a few of these boards , but i used ddr , and haven't had any problems with them .

[Eladijaz]

Greetings,
There were 2 revisions of the 1200 Athlon. One running with 133mhz fsb (x2) and one running with 100mhz fsb (x2). If yours is a 100mhz FSB cpu (revision 'B') then running memory synchronously with ram is going to give you equivalent (or better) performance anyway (when compared to running it 33% faster at 133mhz memory speed). So a setting of 100/100 will give you an equivalent or perhaps better scenario than 100/133 anyway. Certainly you would be better running at 100mhz memory speed and lower (better) CAS latency than 133mhz asynchronously with a higher (worse) CAS latency.
If any of that doesn't make sense just shout and I'll explain in more detail.

Check at bootup and note what the cpu speed is. If you are set to 100mhz FSB and it says it's a 1200mhz cpu then it is revision 'B' and should be run at that speed (100mhz FSB) with the memory also set to 100mhz.
If it says it is a 900mhz cpu then it is a revision 'C' and you need to run it at 133mhz FSB to make use of its full potential and the memory should preferably but not necessarily also be set to 133mhz in this case.

If it appears that you need your memory to run at 133mhz then go into advanced settings in BIOS and set cas latency to 'spd'. If that doesn't help try CAS 2.5 or 3. Also try running memory speed at normal or safe.

Regards,
Elad.

[Peter M]

These are versions, not revisions. There have been three or so revisions of the Thunderbird, all of them available in both 100 and 133 MHz versions.

It's the "B" versions that are 133 MHz, the 100 MHz ones are "A". "C" is 166, "D" is 200 - but these two haven't been available before Athlon-XP.

[nukes]

Actually, the 'B' version is 100mhz fsb, and the 'C' is 133mhz fsb.
I don't know where you get this from:

"C" is 166, "D" is 200 -

But its wrong.