New Prescott won't boot...?

[redken]

Hi guys!

I finally got my 3.2E yesterday. Put it in and it won't boot up.
I checked the volts and vcore is 1.47 (with droop mod).
I spent the rest of the night trying to figure out what it is and still haven't been able to get it to boot.
Moving the droop trimmer up or down gave me a Bios check sum error on my ATI AIW (twice) and proceeded to look for a floppy or cd, but the ati is working fine so I know it's not that.
I even left it clearing the bios all night, but nothing.

:confused:

[musk]

Redken,

What Bios do you have. I put a 3.2e in a friends machine last night and it wouldn't boot with 1014. I put 1018 and it booted fine.

try dropping your vcore to default or 1.375
I had more success at lower vcore because of the over-volting that occurs with the droop mod.
I moved up from a low vcore slowly and had better results than when I jacked it up too high too soon.

I ended up with 1.44 actual (Droop mod) and 240 FSB with my 3.2e

musk

[redken]

Redken,

What Bios do you have. I put a 3.2e in a friends machine last night and it wouldn't boot with 1014. I put 1018 and it booted fine.

try dropping your vcore to default or 1.375
I had more success at lower vcore because of the over-volting that occurs with the droop mod.
I moved up from a low vcore slowly and had better results than when I jacked it up too high too soon.

I ended up with 1.44 actual (Droop mod) and 240 FSB with my 3.2e

musk

I'm using 1018.004 (beta). I can't lower the vcore since I can't even get into the bios.

[jaydog]

I would put your 2.4 back in and see if it starts up, something doesn't sound right

[Stratcat]

I'd definitely suspect the 1018 beta firstly, & agree w/both posters. Drop in the P4C, and if it boots, retro the BIOS to 1015, and dump the 1018 beta for good. I'm using 1015 w/my 3.2 P4E, & it works fine. If ya gotta' have 1018, go w/the 'release' version from the USA server, if available.

Musk is absolutely right: The 3.2 P4E needs 1015 or higher. I actually managed to retro from 1015 to 1014, when trying to 14X multi, WITH MY 3.2 IN THE MACHINE! It immediately refused to re-boot after successfully loading 1014!!! I had to go back to dropping in my P4C, boot, upgrade back to 1015, and then shut-down & re-install the 3.2 P4E. Now everything's fine.

My first bet's on the beta BIOS causing the prob.

JMO

GL

Strat

[uclajd]

redken,

I have exact same issue whenever I go from my 2.4C to a Pressy on my P4P800, BIOS checksum error on boot (although I have found if I clear the CMOS between processor switches, this usually doesn't happen).

When you turn PC on and get the checksum error, Just have a burned CD (or floppy) with the newest BIOS on it (don't you have a 1018 final for that board?), being sure to name the BIOS file "P4C800.rom" (or whatever your board asks for), and let it flash. Sometimes this takes twice, maybe even three times, and a hard shutdown after. And you might have to clear the CMOS with the jumper too.

Lesson learned: Always clear CMOS when switching processors.

And 1015 won't work with Prescotts in my P4P800. :bang head

[FyreDaug]

gave me a Bios check sum error on my ATI AIW (twice) and proceeded to look for a floppy or cd, but the ati is working fine so I know it's not that.

I got that on my x800 I donno what it was about. But I got a new board and it still wont boot. Must be the chip. Everything is defaulted (pulled battery) and still nothing.

[redken]

Thanks for the help guys!
I had flashed to Bios 1018 (final) with no luck.
I tried the CPU on another P4C800E-D (1016 bios) and it didn't work. I had ordered it OEM from Newegg. When I got the package, the CPU had gotten out of the plastic cover it came in and was loose inside the box. It had a few bent pins.
I had managed to straighten them out pretty well, but apparently it didn't survive. So...it's going to be exchanged.
Needles to say, I'm not happy with how they packaged this CPU. They should have put at least a staple on the plastic cover so the CPU would not come loose.

[woutertal]

Sorry it happened to you Redken. Hopefully you get hasslefree replacement.

[woutertal]

Hey this is soemthing bigger I thnik. There's another thread with two users posting the same no boot problems

http://www.ocforums.com/showthread.php?t=335972

[superamd]

I have been building computers for years and have never just given up on trying to get a system working.... until now. I explained what I did in another post but I will give you a short run of it. 3.2e no post on 2 Mboards, (one abit one ecs both had prescott support) 3 working sticks of ram, 3 powersupplys (including antec 350), In a case and out of case on antisaticbag, 2 heatsinks, 2 video cards.... What other component could be causing the problem except for the CPU? SO I took the CPU back and switched it out for another brand new one. Still the same problem. I Did everything I could think of and I couldnt get it to post. Both revisions were SL7L7 made in phillipines. And at this point I gave up and took everything back. 2 Days of struggling to get it to post and I gave up. WTF???????????????

[redken]

I have been building computers for years and have never just given up on trying to get a system working.... until now. I explained what I did in another post but I will give you a short run of it. 3.2e no post on 2 Mboards, (one abit one ecs both had prescott support) 3 working sticks of ram, 3 powersupplys (including antec 350), In a case and out of case on antisaticbag, 2 heatsinks, 2 video cards.... What other component could be causing the problem except for the CPU? SO I took the CPU back and switched it out for another brand new one. Still the same problem. I Did everything I could think of and I couldnt get it to post. Both revisions were SL7L7 made in phillipines. And at this point I gave up and took everything back. 2 Days of struggling to get it to post and I gave up. WTF???????????????

I second everything you said.
My stepping is an e5 costa rica

[FyreDaug]

Check your ram, or try new sticks. My problem was ram. Both sticks went.

[man_utd]

All you can do is troubleshoot one at a time. If you have done everything to eliminate all but cpu error, send it back and ask for a new one.