XP 2400+ being read as a Duron?

[Salvador]

I have a strange problem. I have a XP 2400+ processor and it's being read as a Duron 1.5 ghz. What's strange is that it was being recognized as a 2400+ processor and then I unhooked the computer and let it sit for a few days. When I hooked it back up, the BIOS had defaulted to 100/100 and it was being read as a 1.1 Duron. I went into the BIOS to chance the FSB settings to 133/133 and the processor is still being recognized as a Duron chip.

I have a ECS K7S5A Pro board with 2 sticks of Crucial 256mb DDR memory.

Any ideas? Does this sound like a CPU or motherboard problem?

TIA,

Sal

 

[LFT]

1. Check for possible motherboard driver updates
2. What version on Windows


Dave

 

[Salvador]

Driver updates or updated BIOS?

I'm using Windows XP Pro SP1.

What's so strange about this is that when I shut the system off to unhook it and set it aside while I worked on another system, it was running perfect. It detected the chip as a Athlon XP 2400+ as it should. Why would this have changed? I can understand it if the BIOS battery went dead on me and the BIOS was reloaded at default settings, but nothing else was changed. The time is still the same. All the ram timings are the same as what I had them at, etc..

What would make the system all of a sudden read the CPU as a Duron?

Weird.. I still have about a week warranty (I've had it for about 20 days now) on this OEM chip, so I'd better get this sorted before I'm SOL.

Thanks again.

Sal

 

[GreatDaleness]

Did you try resetting the Bios? That board does reset the CPU memory ratio at random for some reason. Usually you just set the FSB back to normal.

"I went into the BIOS to chance the FSB settings to 133/133 and the processor is still being recognized as a Duron chip."

what is recognizing it as a DUron? The BIOS or the OS or both?

 

[Salvador]

what is recognizing it as a DUron? The BIOS or the OS or both?

Both. Actually, it was the BIOS that I noticed first. On start up, I always look at what the BIOS is recognizing the chip as and when it detected it as a 1.1 ghz Duron, I went into the BIOS and changed the FSB from 100/100 to 133/133. It now reads as a 1.47ghz Duron when it should read as a XP 2400+ Ahtlon.

I'm going to try resetting the BIOS now. I'll even pull the CMOS battery and see what happens.

BTW.. I just tried running Prime95 on the CPU and it passed. I don't know if that will tell me anything or not.

Sal

 

[Salvador]

Ok.. Now it's being read as a XP 2400+. Another weird thing is that I set the FSB to 133/133 and then changed the RAM timings back to the way that I had them and before exiting the BIOS, I went back into the CPU area and it was back at 100/100. I changed it back to 133/133 saved and exited and now it's running like it should.

Now. If it doesn't hold these settings, could it be the CMOS battery? The board is ony a couple of months old, but I did remember hearing about a dead battery issue with the original ECS K7S5A boards. I'd think that I'd lose all the settings though if the battery was the cause.

Thanks again guys!

Sal

 

[GreatDaleness]

I don't know what it is, but I have the same kind of random problems with my K7s5a. I think it might be power related, because it used to happen alot when that machine had several pci cards in it. Now that those cards are out, it happens once every month or so. These boards are famous for such things.

 

[PELarson]

Originally posted by: Salvador
I have a strange problem. I have a XP 2400+ processor and it's being read as a Duron 1.5 ghz. What's strange is that it was being recognized as a 2400+ processor and then I unhooked the computer and let it sit for a few days. When I hooked it back up, the BIOS had defaulted to 100/100 and it was being read as a 1.1 Duron. I went into the BIOS to chance the FSB settings to 133/133 and the processor is still being recognized as a Duron chip.

I have a ECS K7S5A Pro board with 2 sticks of Crucial 256mb DDR memory.

Any ideas? Does this sound like a CPU or motherboard problem?

It is a problem with the ECS K7S5A pro motherboard. Noticed it happen to me when I was using a XP2200+. Power off seemed to correct it, or I never noticed it again. Wish I could help more.