Quick help with a Athlon xp 3000.

[cu3ed]

Hi,

I was running a sempron 2500 on an as rock board at 333mhz. Ive upgraded to an Athlon xp 3000 which is also 333mhz.

But the computers reading it as a 2200 operating at 1750mhz.

Now the jumper settings are the same as for the Sempron and the Bios is showing a 166 core speed (333mhz)

why is it showing this?

I think the cpu multiplier is 10.5 and not 13 as it should be, but the bios does not seem to let me change this?

Any help please?

 

[GodMac]

Hi, I had a similar problem with the ASUS A7N8X mobo with a 2800 CPU. Worked fine after a BIOS upgrade. Check to see if there are any updates.


Also, check to make sure that your mobo will support the 3000 and double check your jumper settings. I know its a different board but the early ASUS had a screen printing error on the mobo jumpers so check the latest online support manual for the mobo. You've probably already done the above but I can't think of anything else. Timings look fine.

 

[cu3ed]

No mate that seems like a good path to try, i havent updated the BIOS for about 5 months now, so ill have to check with the mobo site.


Thanks for you help!.

 

[meaz]

the semptron 2500+ is meant to run at 10.5 x 166 = ~1750MHz.

edit: maybe your 3000+ is a 200FSB one that runs at 10.5 x 200 = 2100?

 

[PinkFloyd]

I'm almost certain theat the 3000 was a 200fsb cpu.....
unless there was both a 166 and a 200fsb one. (different cores)

What core is it?

 

[Gaverick]

There were 333 FSB and 400FSB versions of the Athlon 3000+. I think you need to change the jumpers on the motherboard to make it 13x multi. If you type your mobo model number then manual into google the first link is usually the manual in .pdf form with all the jumper setttings.

 

[GodMac]

There is definitely two versions. The AXDA3000DKV4E model is an Athelon 400FSB, the AXDA3000DKV4A is a 333FSB as far as I can remember. Your mobo should have a jumper on to take it into 333/400FSB range. As before just double check.

 

[cu3ed]

Sorted, its reading it fine now!!!!


Thanks for all the imput poeple, much appreciated.

 

[GodMac]

cu3ed, what was the actual fix? Just so anyone having the same problem can search and get the answer.