XP 1800+ can't run at 133 FSB. Help!

[jbahseng]

I just bought an AMD XP 1800+ from the for sale forum and I just got it this evening. Well, the seller just put the cpu in an oem plastic case and shipped it in an envelope. And some of the pins on the cpu were bented and the cpu can't fix into the socket 462 because of the bented pins. After spending 45 mins to straighten up the pins, i finally got it fix into the socket but i can't get the cpu to work at 1.53 GHz (133 FSB). The computer will lockup after the memory scan or during the windows load up if i set the FSB at 133 MHz. I'd to settle down to 100 FSB and the cpu works at 1.15 GHz (100 FSB) with no problem. I'd try to format and reinstall win 98 se, set the FSB as 133/100 (I'm using crucial 256 mb PC 133 @ CAS2), flash the motherboard bios (ECS K7S5A) and have no luck at all. The cpu simply don't work under 133 Mhz. What can i do to make the cpu work at 133 FSB? I don't think it's the motherboard because i'd used a 1.4 GHz @ 133 FSB with no problem. I might be wrong but i don't have an extra motherboard to test it. Here is my setup :

AMD XP 1800- (1.15 GHz @ 100 FSB )
Crucial 256 mb PC 133 Sdram (CAS 2)
ECS K7S5A (unknown rev, can't find it on the board, had flashed the newest bios)
Asus 16 mb tnt2 Vanta
Seagate Barracuda 4 80 GB
on board sound
Linksys NIC
Enermax 350 watt (fc)

 

[bjarne1973]

Hi

You should get a replacement for your damaged CPU. When the pins on the CPU is bent, the CPU might have been damaged inside.

 

[jbahseng]

This is bad :

133/133 FSB with L1 Internal cache and L2 external cache enable == > 1.53 GHz
lockup when the windows start

133/133 FSB with L1 Internal cache enable and L2 external cache disable == > 1.53 GHz
lockup when the windows start

133/133 FSB with L1 and L2 cache disable == > 1.53 GHz
able to get into windows, but it's very slow and getting bsod

100/133 FSB with L1 and L2 cache enable == > 1.15 GHz
no problem at all, surf net and play rtcw for 3 hours with no problem.

Looks like the chip was defective

 

[dunkster]

It does sound bad, it could possibly be a BIOS problem with cpu-recognition.

In the 'CPU Operating Speed' BIOS section, try setting it to 'User Define' instead of cpu model, and manually assigning correct multiplier factor and cpu clock at 133 and dram speeds at 133.

Hope this helps!

 

[LikeLinus]

I would demand my money back.

What moron sent a CPU like this? PLEASE tell us so we can add this person to our Do Not Trade list.

 

[jbahseng]

<< It does sound bad, it could possibly be a BIOS problem with cpu-recognition.

In the 'CPU Operating Speed' BIOS section, try setting it to 'User Define' instead of cpu model, and manually assigning correct multiplier factor and cpu clock at 133 and dram speeds at 133.

Hope this helps! >>



I'd set the cpu and dram speed at 133/133 or 133/100, both setting failed and the comp lockup during windows boot up. It work flawlessly with 100/100 or 100/133 FSB though. I'd used a 1.4 GHz with 133/133 setting with no problem so i don't think is the motherboard causing the problem. I'd flashed to the newest bios and it still don't work (1/25/02). Anyone with a ECS K7S5A has the same problem?



<< I would demand my money back.

What moron sent a CPU like this? PLEASE tell us so we can add this person to our Do Not Trade list. >>



The seller is new to the for sale forum and i guess he just made a mistake. He did send out the cpu in the same day(with Fedex ground) i sent out my payment and keep good communication through out the whole time.