• 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.

Why does K7S5A read a 1.2Ghz Duron as an 800Mhz Duron?

2

2336

Elite Member
Folks, I thought I had this K7S5A all figured out. I'm running a Duron 1.2Ghz and it's showing up as a 800Mhz duron in the POST screen and when I run Motherboard monitor it tells me that it's running at 797Mhz. I've even swapped in a brand new 1.2Ghz Duron and same thing. Is there a known problem as far as reading Durons? Is there a BIOS fix for this? Also, where would I go to download the overclocker's BIOS for this? Any help would be greatly appreciated. Thanks again gang.🙂

P.S. All of the other K7S5As that I've set up have used either older T-Bird CPUs or Athlon XPs, this is the first that I've configured with a Duron.
 
I'm not familiar with that board but I would check in the BIOS to see if the multiplier is set correctly for your Duron.
 
Fireman, in the BIOS it's showing that the system is running 100/100 and the multiplier is 12x yet whenever I run SiSoft Sandra or Motherboard Monitor it shows the CPU as running at 797Mhz.
 
Originally posted by: 2336
Fireman, in the BIOS it's showing that the system is running 100/100 and the multiplier is 12x yet whenever I run SiSoft Sandra or Motherboard Monitor it shows the CPU as running at 797Mhz.
Click to expand...

Shouldn't that be 133/133 instead of 100/100? What happens if you change the bus speed?
 
Which bios version are you using currently? i'll check to see if the early ones had problems... mine reads my duron 950 correctly.
Is it a duron with a Morgan core? Cause there were a few bios updates to fix a similar problem with morgans, especially 1.2/1.3 i think.
 
Folks, the PCB rev. is 3.1 and the BIOS is dated 10/29/02, which is the most recent one I've found on ECS's website. I sent an e-mail to ECS's tech support and they told me to go into the BIOS and change the CPU frequency to 133. Now I ain't the sharpest tool in the shed, but don't all Durons run on a 100Mhz FSB? BTW, the CPU is a 1.2Ghz but I'm not sure if it's a Morgan core or not. How can I tell?
 
You're correct on both, the 1.2GHz Durons are all Morgans, and they are designed to run 100MHz/DDR200. I have a K7S5A myself, which I've used with my 1.0GHz Duron (Morgan core) at 100/100, 133/133 (lucky me, made this on default voltage) and 100CPU/133RAM (slower than 100/100, for the record).

I've thought about this, but cannot think why it would behave that way unless someone's been up to monkeyshines with your board before you bought it. What RAM are you using in there, out of curiosity?
 
It's a brand new motherboard. the anti-static bag hadn't even had the seal broken and it's running one 512MB stick of PC133 PNY and one 128MB stick of PC133 Crucial. Weird, huh?!
 
Tom, this is actually a friend's computer and I won't have access to it until tomorrow, but I'll try that and let you know what happens. I've got a bad feeling I might be having to do an RMA, though. Hope I'm wrong.
 
Strange problem indeed. One last thing to try, take out the 128 meg stick of ram and try running with only one. running with 2 sticks of sdram often causes strange and random problems. it's worth a shot.
Here's what i think is happening from a look around at k7s5a board. I'm guessing your clock speed is actually at 66 MHz with a multiplier of 12, resulting in a speed of around 792, which the computer bumps up to the closest speed, that of an 800. I'm not sure why it's mis-reading the cpu and running at the wrong clock speed. I see your bios reports 100/100, but try to run a program like WCUPID to be sure and get some more readings. hope that helped a bit.
-Krugger
-edit- see another problem just like yours here link
maybe add to that thread too so people can see its not an isolated thing, maybe talking to another person with the problem would help too.
 
Just tried with an Athlon T-Bird 1Ghz and it was reported as a 500Mhz CPU in the POST screen, WinXP's system properties showed it as a 497Mhz CPU. I have now tried it with three known to be good CPUs and all three exhibit this weird behavior. Tried all three in my daughter's MSI K7T Pro 2A and they all ran fine and were reported correctly. Another thing that just reared it's ugly head. Seems that the bottom PCI slot is not working properly. I have installed three different PCI modems and all three were showing that they were properly installed, WinXP installed it's digitally signed drivers, diagnostics showed good but when attempting to dial-up it couldn't open the port. Changed the last modem, a Diamond SupraMax 56K to the #3 PCI slot and BINGO! Dialed up, and logged right in! Weird huh?! I just e-mailed ECS tech support with my latest observations. Depending on what they say I think it might be RMA time. What do you guys think?

Rick
 
Gang, just installed and ran SiSoft Sandra again. Checked the MainBoard specs this time and regardless of whether the CPU FSB is set for 100 or 133 in the BIOS it still is running at 66Mhz FSB!
 
Something is Not Right with that picture :Q If you didn't need SDRAM support then you would hear me spouting off how great the A7N266-VM is, as a potential alternative. I have 20 at work (so far), very nice stable foolproof un-overclockable boards. 🙂

edit: and yep, I'm thinking it's definitely RMA time.
 
I've seen a total of maybe 3 other ppl on that other board with this problem, where it's stuck at 66, but no solutions as of yet.
Maybe RMA
Krugger
 
ECS tech support was no help. Their only solution was to change the FSB of the CPU in the BIOS to 133 from 100 and that did nothing. The board is on it's way back as we speak.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top