Tech Problem: AMD XP 2500+

[chodadog]

A mate of mine bought a 2500+ processor. Thing is, it's defaulting to 1.1 Ghz. Obvious solution, go into the BIOS and set it right. Once we have the correct settings, it boots up as an AMD XP 2500+ on the startup screen, but then bam, it turns off within 30 seconds. We assumed it was to do with some kind of overheating, but everything feels pretty cool. Surprisingly cool, actually.

Any ideas?

[4Pics]

You set it to 133/133?

Also what kind of cpu fan?

[T[H]C]

Break it down to the bare components, could be a bad stick of ram that wont let it boot. take out the nic, sound card,... just do mb, ram, cpu, vid card and see if it boots. reset the bios. play with different parts. if you cant get it to work after awhile than it will prob be the mb or cpu

[DrewKole]

if its abit, get the latest bios patch, was an error with the bios...

If not, do the same, 2500's have a bug with a few motherboards.

Btw, if he gets a decent fan, some good compound, he can overlock it to 2200+ like I did.

[Chaldoray]

I had the same problem...
Go into the advanced bio changed it to 166mhz

[KRL]

I put the AMD Athlon XP 2500+ with the Barton Core in the PC I just built.

Its fast as fuck.

I suggest checking your Bios version, Bios settings, the memory, and the board itself could be bad.

The older BIOS have some issues with these new 3200 memory chips that can overclock on the 400 Front Side Buses also.

[johnbosh]

Maybe a bios update is availible? I also should call the store where I bought it

[chodadog]

Originally posted by Chaldoray
I had the same problem...
Go into the advanced bio changed it to 166mhz

THC, thanks for the suggestion. But it seems to boot up just fine when it's left at 1.1 Ghz. It only fucks up when we get it to the correct speed, so i'm pretty sure it's the processor.

We also thought it might have been a windows XP problem, not being too happy with the hardware upgrade, but we tried booting up with the hard drives disconnected, and it still turned off. So that rules out that one too.

His mobo is an Asus a7n8x-x.

Drew, when you mentioned overclocking it to 2 Gig, i thought what the fuck.. 'Cause we were under the impression that the core speed was about 2.2 Ghz. I see now that it's only 1.83. So perhaps we've been using the wrong clock multiplier.

Cause it does show the right processor when we set the FSB to 166. Hmm. Thanks guys.

[chodadog]

By the way, quick question..

The FSB is 333 Mhz, and i know that i'm supposed to set it to 166 in the BIOS. So for the multiplier.. working with the core speed.. Should it be..

166 x 11 (multiplier) = ~1.83 Ghz, or
333 x 5.5 (multiplier) = ~1.83 Ghz

The manual was pretty unclear on the subject.

[evilregis]

I had a similar problem on an on-site call once where the persons computer was shutting down after about 5 seconds into booting up. I opened up the case, removed all but one stick of RAM, yadda yadda yadda... put in known good cards... same thing. After fucking around trying to figure this out... the dick had installed his heatsink on backwards. The clip was facing the back of the case and apparently it's supposed to face the front of the case. I removed it, put it on correctly, and all was fine.

[chodadog]

Originally posted by evilregis
I had a similar problem on an on-site call once where the persons computer was shutting down after about 5 seconds into booting up. I opened up the case, removed all but one stick of RAM, yadda yadda yadda... put in known good cards... same thing. After fucking around trying to figure this out... the dick had installed his heatsink on backwards. The clip was facing the back of the case and apparently it's supposed to face the front of the case. I removed it, put it on correctly, and all was fine.

Are you serious? hahaha. Damn. I'll have to check that next time i go to my buddy's place. Another friend installed it for him. Wouldn't surprise me if it was something silly like that.