- Joined
- Oct 31, 2002
- Location
- Portland, OR
So here's the thing... For about 5 months or so I have been playing happily with a decently overclocked BD7 RAID. What I have on it is a 1.6 Northwood, 512MB PC2700 DDR, Gf4 Ti4200, and 2 Seagate 60Gb Barracuda IV HDs. It has been running great at 140Mhz FSB giving me a comfortable 2.24GHz CPU speed. This is with stock voltages and the retail HS and fan for the CPU.
A few days ago I pulled out the CPU to try it in another box that was having some problems. When I released the tabs on the HS and pulled it out the CPU came with it, stuck to it. I visually inspected both the CPU and the MB and neither looked damaged even though the CPU was yanked out without releasing the lever on the ZIF socket.
When I put everything back together and booted up I got a message during POST that the CPU had changed or was not functioning. I checked all of the CMOS settings and rebooted. This time I got a checksum error. I clocked it down to 120mhz FSB and this time got almost into W2k and then got an error referencing ACPI support in the BIOS (don't remember exact message). When I clock it back down to 100 or 110Mhz FSB everything seems to work just fine, anything higher causes problems.
I know the CPU is ok because I tried it at 140Mhz on a friend's BD7II. It seems to me that I damaged something on the MB when I pulled the CPU out. What's wierd is that I'm not having anything go wrong when I run at lower bus speeds. I would think that if physical damage has caused it to not boot at 120Mhz, I should at least be having some problems at 110.
Can anyone tell me if I am overlooking something? If it is because I damaged the ZIF socket are there any ideas on undoing this damage?
Also, I guess I can pass along to everyone that they should BE CAREFUL when removing a P4 with a retail HS. I'm probably not the only one who has had their's get stuck.
A few days ago I pulled out the CPU to try it in another box that was having some problems. When I released the tabs on the HS and pulled it out the CPU came with it, stuck to it. I visually inspected both the CPU and the MB and neither looked damaged even though the CPU was yanked out without releasing the lever on the ZIF socket.
When I put everything back together and booted up I got a message during POST that the CPU had changed or was not functioning. I checked all of the CMOS settings and rebooted. This time I got a checksum error. I clocked it down to 120mhz FSB and this time got almost into W2k and then got an error referencing ACPI support in the BIOS (don't remember exact message). When I clock it back down to 100 or 110Mhz FSB everything seems to work just fine, anything higher causes problems.
I know the CPU is ok because I tried it at 140Mhz on a friend's BD7II. It seems to me that I damaged something on the MB when I pulled the CPU out. What's wierd is that I'm not having anything go wrong when I run at lower bus speeds. I would think that if physical damage has caused it to not boot at 120Mhz, I should at least be having some problems at 110.
Can anyone tell me if I am overlooking something? If it is because I damaged the ZIF socket are there any ideas on undoing this damage?
Also, I guess I can pass along to everyone that they should BE CAREFUL when removing a P4 with a retail HS. I'm probably not the only one who has had their's get stuck.