[Fixed - Thanks] In a pinch, need help with Abit IP35-E and E8400

[bigpow]

Desperately looking for a solution to this problem:

System won't boot, with "ambulance alarm" through speaker.
As soon as power button is pushed, it boots and then immediately shut downs.
Then 1-2 sec later, it turns back on. But it's alarming.

Able to see the display, showing VGA BIOS and then it's stuck at Abit BIOS screen where it says press Tab or Del. And of course, none worked.

This is a new build and I've no way to check the parts one by one. (except VGA)
My other systems are AMD s939.

I was wondering if any of you had encountered this problem or know the nature of this mobo/CPU, and willing to give me a hand.

-Is it the mobo not recognizing the CPU?
-Is it the CPU that was DOA?
-Is it the RAM (that won't boot at 1.8V default)?

Here's what's in it:
CPU Intel C2D E8400
Mobo Abit IP35-E Rev 1.0
RAM OCZ 2x1GB DDR2-800 2.1V


Thanks again - please assist

 

[Sylvanas]

So nothing happens once you see the POST screen? Have you tried reseting the CMOS jumper? Are you sure everything is connected properly, sometimes an alarm sound is used because thing like powers cables are not connected so you'll want to check the 4pin molex, 24pin mobo power and ATX 12v are all connected properly. The boot and then shutdown only to reboot again is the Abit IP35-E's 'Double boot' issue which is due to an issue in the Bios that can hopefully be fixed in future revisions (I think there was a a BETA that fixed this already). This is normal however if it were a failure in inadequate voltage being supplied to the DRAM I'd doubt It'd even boot, however you might want to try just 1 DIMM and see if that helps.

 

[ghost recon88]

Make sure the keyboard is plugged in, and clear the CMOS jumper.

 

[Regalk]

Probably BIOS not recognizing the C2d 8400 - question is HOW to flash when you need a "recognizable" CPU to do so (maybe get a cheap C2D celeron or take it to a local shop)

 

[xavier es]

I had similar problems with my IP 35-E, tho not with a E-8400 but a E-6750. The problem may very well be the bios not recognizing your 8400 . But are you aware of the "cold boot issue" with the IP35's? Go over to the abit forums and there is quite a bit about it. I also had the ambulance siren , reseating the cpu stopped that. the double boot is nothing to worry about.

 

[Tempered81]

i wouldnt think anything is doa at this point, i just installed my ip35e & e8400 yesterday, i had 2 problems 1. needed to update to 45nm bios (15) 2. my old ide hard drive was bad and i didnt know it.

 

[Heidfirst]

if you mean the hi lo ("ambulance siren") that's usually due to either a temp, voltage or a fan rpm being out of set warning levels.
Do you have the hsf properly fitted (the stock Intel 4 peg design is poor & often not fitted correctly)?
Do you have an rpm sending fan connected to the CPUFan header?

& I would initially be troubleshooting with only 1 DIMM installed.

 

[bigpow]

Okay, it's working now.
Many thanks for your responses, I really appreciate them.

Here's what happened:
1) I didn't use the Intel stock HSF (using a Ninja+YL 120mm), I connected my Yate Loon directly to PSU. This was the cause for the ambulance/hi-lo siren/alarm. Even after I disabled the CPU Fan EQ and CPU Fan Check from BIOS, it was blaring every time I rebooted.
2) Somehow the original BIOS didn't like any of my hard drives. Tried 3 SATA HDD and all refused to work.
3) Another problem that was more serious, was the fact that its BIOS didn't like the E8400. I tried clearing CMOS at least a dozen times, with various methods posted in AT forum and Abit forum. I almost gave up and left it dead (unplugged power cable, removed CMOS Battery, put Clear CMOS jumper to its place) for hours (playing Undertow on my Xbox). It then somehow managed to boot - which I took advantage of by updating the BIOS to latest official (#15). Which also fixed the HDD detection problem above.

I'm still not quite pleased since:
1) Latest Abit BIOS #15 for IP35-E is not stable (it behaves differently on every boot)
2) Still has the obnoxious double-boot problem (hate it simply because I'm worried about my hard drives being powered on and off and on repeatedly)

For those who want to know how high I run my E8400, it's at stock 3GHZ
I can't find a stable OC settings, I tend to blame: the lousy Abit BIOS (20%) and the cheap OCZ Dual Gold XTC (80%).
I plan to get a decent OC RAM (DDR2-8000 and above). We'll see which one is the dead-weight.
On the good side, E8400 seems to be able to do 3.6GHZ at stock, 4.5GHZ at 1.35V (CPU stress test only, since any test with RAM would fail).
I guess you really get what you paid for huh? (IP35-E $60 AR, OCZ 2GB $17 AR)

The quest continues...

Once again, thanks AT members.

 

[Heidfirst]

Originally posted by: bigpow
2) Still has the obnoxious double-boot problem

it shouldn't unless you are completely removing power (switching off at PSU or wall socket) from the mobo when shutdown in which case it (& other P35s) will do it on initial boot.
If you aren't completely removing power from the mobo then something isn't stable (& again you will see this behaviour on other P35s like Asus, Gigabyte etc.).

and the cheap OCZ Dual Gold XTC (80%).

OCZ Gold is known to be fairly problematic on the IP35 series, even Platinum is a lot better.

 

[Tempered81]

man how are you guys getting a 500mhz fsb with 800mhz memory!?!? I cant get my 800mhz mems to OC at all past approx 950mhz

 

[spinejam]

Originally posted by: jaredpace
man how are you guys getting a 500mhz fsb with 800mhz memory!?!? I cant get my 800mhz mems to OC at all past approx 950mhz

have you tried relaxing your memory timings?

my patriot llk 800mhz ddr2 was EPP: 5 5 5 15 @ 1000mhz per CPU-Z but I had to run 'em @ 5 5 5 16 in my IP35 and IP35-E.