• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

No Boot - Abit IP35-E Long Repeating Beeps

D

dannyz

Junior Member
My computer has been running smoothly for a while now but I decided to upgrade some components.
I just bought a E8500 to replace my 2160. At the same time I bought a gtx260 to replace my 1900xt.

So my specs are this:
MB - IP35-E
Power - Corsair VX550W
CPU - E2160 -> E8500
Video - 1900xt -> gtx260
Ram - 2x1gb crucial ballistix
No extra components

I replaced the old parts both at the same time and found out that it would not POST. No video, no keyboard lights(no even a kb flash at startup), no beeps, everything else starts up correctly(fans, lights, etc).

When I backed out and went back to the old configuration(2160, 1900). When I try to boot up my previous working config there is still no post, no keyboard lights, no video. The only thing different is that I now hear a beep code. It is a repeated long beep that lasts forever.

Four second beep, two second silence, four second beep, two second silence, four second beep, etc.

Looking up the beep code says it may be a problem with the ram even though I did not touch it during the upgrade. I switch to only using one stick and tried every slot with no luck.

I have reset the CMOS is every way imaginable(jumper, battery, etc).

Mixing and matching both CPUs and GPUs also does nothing.

My previous bios settings were an overclocked 2160 to 3ghz(10x300) with a modest 1.37v
The ballistix was volted to 2.1 as recommended by the manufacturer. Though I am sure CMOS is in default config now.

I have heard about things like cold boot problem for the ip35-e and my room is indeed about 60-70F but I have let the cpu run for half and hour to get it warm and restarted with no luck.

I find it strange that with my 2160 I get beeps yet with the new 8500 I dont get anything.
On the 2160, i get the dual boot issue that comes with each ip35-e with unupgraded bios. On 8500, no dual boot. It seem i get less headway with the 8500 than the 2160.

I know this is a long post but does anyone have any ideas? I have tried a lot of things and open to any questions. The only thing I can think of is buying a new stick of ddr2 ram and trying to see if it works. I am skeptical because even if i try to boot with no ram, I still get the beep codes. Also I dont think the ram is bad, maybe just "overvolted"(even though thats what the voltage is supposed to be and CMOS is reset).

I would appreciate any help.

PS. I know I should have loaded the default bios beforehand and put in only one new component at a time.

EDIT:
I did some more testing.
E8500 with no ram - no post no beeps
E8500 with gtx260 - video card fan does not start
E8500 with 1900xt - video card fan works

Everything is connected and seated tightly.

I am kinda beginning to think my vx550W is too weak. But that would not explain why my original config does not boot anymore or the beeps.
 
Originally posted by: dannyz
I am skeptical because even if i try to boot with no ram, I still get the beep codes.
Click to expand...
Of course you do as it's telling you that you have a problem with RAM - you don't have any ... :roll:

Did you upgrade the BIOS to one that supports the E8500 prior to the CPU switch?

 
First of all I really appreciate your reply heid.

Second:
http://www.abit.com.tw/cpu-sup.../mb/intel_p35_ip35.htm
I have the E0 and the board came with the 15 revision bios.
Looks like it is compatible out of the box.
Also it doesnt answer why my 2160 and 1900xt stopped working.

Also brings up a good point. When I tried with 8500 with no ram, I dont get beeps. I dont think the 8500 is too power hungry for my system since it is lower fab and supposedly more power efficent. Also the GHz should be the same becaues i OCed my 2160 to 3Ghz.

I am stumped. I want to go to best buy and buy new ram and PS to test my components out and return them afterwards. Buying a new mb will be tricky though.
 
The long beep is RAM. Why it doesn't work with your new chip, I don't know. I do know that I tried an "ES" E8500 chip on my IP35-E (latest BIOS) and it would not go beyond POST.
 
Thanks for you reply Zap.

What i really want to know is why everything will not work with my old config. Did something break when i put in my new components? I dont think so, i was careful.
Only thing could be if I bent some pins on the MB.

Wierd thing is, when i put in my 8500 and RAM I get no beeps... without RAM no beeps.
When I put in my 2160 and RAM same long beeps... without RAM same exact beeps.

Any ideas are appreciated.
 
Here first try this: put in old chip update your machine to latest BIOS. then put the E8500 in. oh don't forget to RESET BIOS after the update. I believe there's a chance your BIOS is bit old. and yes like Zap I think long beep is RAM. I only had this problem once, when I didn't plug RAM in all the way on the ip35-e. let us know your progress.
 
Thanks for the reply nyker.

The problem is I get no video, no post. I dont even have a working floppy drive. This means no bios update. I updated to the lastest bios using the windows utility months ago also.
Resetting the CMOS would not downgrade my bios version.

About the ram, I am going to best buy tomorrow and buy a cheap stick of ddr800 and test it.

I want to stress that I made absolutely sure everything is seated/connected as tightly as possible.

I have also ordered a new mb with 2nd day delivery. Spent some money and got a Rampage Formula. I am going to try the new ram and motherboard as a test and return what i dont need.
 
ok let us know how it went for you. it maybe your board or something else dying, at this point tough to tell. I had an old 754 die on me, since i only got one 754 machine, had nothing to test it with, eventually swapped out to a new board and cpu and everything came back.

you can test out the stuff when your new board gets here. it might be the board if you get no video at all.
 
Quick update:

Looks like you guys were both right.

Put in a stick of corsair ram with the 2160 and got POST. There is something wrong with the crucial ram. It would not fail memtest; I think it has something to do with the voltage. Even though I cleared CMOS and it defaulted to 1.8v the ram doesnt seem to work. Puzzling. Maybe because it has been at 2.2v (EPP) for so long it doesnt want to go back. If anyone has any insights about this I would love to hear.

The reason why the 8500 doesnt work is because my mb bios version doesnt support it. Heid you were exactly right, I was just mistaken about which bios version I had. When I tried to update with the abit windows utility(keep in mind I dont have a floppy) from bios version 14 to 17(latest) it doesnt seem to work. I have the latest version of the utility. I cannot update any other way. If anyone know about this subject please let me know. There is a way in the windows utility to update from a file, but this is risky(i got burnt from it before) because I dont have any way to go back if something goes wrong. If the bios get corrupted during the update then I am toast. There will be no post for an entirely different reason.

EDIT:
The argument that the crucial ballistix will not boot unless you put in some other ram and up the voltage to 2.2 doesnt make sense to me. How did the ballistix every boot in the first place then?
 
Thanks for the update.

You can try using a flash drive to do the BIOS flash. There are a number of guides on how to do that found on Google.

It is possible that the Ballistix RAM deteriorated just enough to not POST on 1.8v.
 
Yeah I have been try to figure out how to boot from a cd and do the update. Problem is that I have a SATA hd and cdrom. It looks for a ide drive and I dont have SATA drivers on the cd. Even if I did I read it will not work. Catch 22.
Anyone know a solution please dont be shy.

Also I am going to buy some new ram, not a big fan of these ballistix anymore. Even though they look so cool. I may also buy a new flash drive but it is so close to black friday and I am really cheap.
 
I updated to the version 18 bios and it still doesnt post.
My 260's fan actually doesnt spin and it looks like everything else is running on half power. I am pretty sure my PS is powerful enough to run this.
I dont know, I think my MB is having trouble with 45nm cpus even though bios 15 should introduced support for it.
Got any ideas?
 
@dannyz -- Looks like the others helped you here but I'm not surprised it was your RAM. The same exact thing happened to me several months ago. 2 of my 4 sticks of Ballistix went bad on the same day. I use 2x1gb + 2x512 in my IP35-E and took everything out except for 1 512 stick and it booted fine. Checked every slot, booted. Then put the other 512 stick in and it booted. Tried slots 1&3 & 2&4 -- okay.

Then did the same thing with the 2x1gb sticks and nothing -- except those long beeps you had. So I knew the RAM had gone bad. In hindsight, I had been using 2.05v for 8 months. Even though they were rated for 2.2v, most of us that have used Ballistix know they can run on less vDIMM, even with OCing.

The great thing though is Crucial cross-shipped me new PC2-8500 Tracers in place of the old PC2-8000 regular Ballistix sticks I had and now I got better RAM and free bling! And now I run all 4 slots filled again on just 1.90v @ 480mhz.

PITA I know, but Crucial is still is a great company to deal with on RMAs. Make sure you ask for double-sided RAM when you RMA and ask for the Tracers if the type you had are EOL or all they have are single-sided (which are bad OCers and have been dying with greater frequency).
 
Originally posted by: ghost recon88
Originally posted by: DanDeighan
Originally posted by: Heidfirst
you may have to go with a beta BIOS for EO support.
Click to expand...

Do you have a pointer to the beta bios? Thx!
Click to expand...

Try this one

Edit: And read this post here.
Click to expand...

:thumbsup: Bravo! Thank you

Flashed this beta bios, it shows version 00 instead of 18 (latest official BIOS from Abit for the IP35-E). Booted and ran my e2180 just fine.
Shut down and installed the e8400 rev E0, booted up in to BIOS. CPU temps showed as 36 instead of the previous 98 degrees C!
Made the necessary changes in the BIOS and rebooted in to Windows XP. Came up the first time no problems!
Thank you very much ghost recon88 😀

Hopefully this works well until (and if) an official BIOS is released.

Next up...3.6Ghz?

 
Originally posted by: DanDeighan
Flashed this beta bios, it shows version 00 instead of 18 (latest official BIOS from Abit for the IP35-E). Booted and ran my e2180 just fine.
Shut down and installed the e8400 rev E0, booted up in to BIOS. CPU temps showed as 36 instead of the previous 98 degrees C!
Made the necessary changes in the BIOS and rebooted in to Windows XP. Came up the first time no problems!
Thank you very much ghost recon88 😀

Hopefully this works well until (and if) an official BIOS is released.

Next up...3.6Ghz?
Click to expand...
You saw page 4 of that uabit thread about not being able to take it much farther than 3.7 - 3.8ish due to this bios not actually adjusting vMCH, right? It's great you can get the E0 to function, but if you can't get that 4.1 - 4.2ghz reading we all expect from this stepping, owners of the IP35-E might as well settle for a C0. At least it's nearly a guaranteed 4.0ghz 😛
 
Originally posted by: brencat
Originally posted by: DanDeighan
Flashed this beta bios, it shows version 00 instead of 18 (latest official BIOS from Abit for the IP35-E). Booted and ran my e2180 just fine.
Shut down and installed the e8400 rev E0, booted up in to BIOS. CPU temps showed as 36 instead of the previous 98 degrees C!
Made the necessary changes in the BIOS and rebooted in to Windows XP. Came up the first time no problems!
Thank you very much ghost recon88 😀

Hopefully this works well until (and if) an official BIOS is released.

Next up...3.6Ghz?
Click to expand...
You saw page 4 of that uabit thread about not being able to take it much farther than 3.7 - 3.8ish due to this bios not actually adjusting vMCH, right? It's great you can get the E0 to function, but if you can't get that 4.1 - 4.2ghz reading we all expect from this stepping, owners of the IP35-E might as well settle for a C0. At least it's nearly a guaranteed 4.0ghz 😛
Click to expand...

I'm not really a hard core overclocker. I ordered an e8400, and got a rev E0 that didn't work at all for me. I would have been happy to have a rev C0. I just mention the 3.6 OC, because of it's rep as the "free" OC, that pretty much always works. And it is under the clocks mentioned in that thread, so it may work still for this hacked combo.
 
So all the questions are answered.

My 8500 wasnt working because it is E0 and the listing i linked to said it might not :/ I am just too blind(or stupid) to read the sheet correctly.

I just called into Intel support to get a RMA because I was convinced it was DOA and proudly claimed that the ip35-e supported the e8500 e0 stepping just to be slapped down to reality withthe correct facts. How embarrassing.

Thanks Heid, I am going to try the bios you linked to and see what happens. I was hoping for 4GHz+ but doesnt look good if you cannot up the voltage.

Oh and thanks for the tip about the crucial RMA bren. I was thinking about that. I actually picked crucial because a friend said they had the best support available. I am using the 2 sticks now in 2.2v If I change to anything else they will not boot. This makes it hard to use without a spare stick of something else to change to if I need to reset the CMOS. Very inconvienient.
 
Hmm. So is this thread proof that the IP35-E does NOT support the E0 stepping with official BIOS 18? I'm just surprised, if that were true, wouldnt we be hearing more reports?
 
I tried my 8500 E0 with that new beta bios from abit.eu and it doesnt work.
It may only work with 8400 and havent gotten to 8500/8600.

I am tired of this. Gonna get a new MB. I thought I was buying quality when I bought the ip35. Bah, hate buying old technology.
 
Originally posted by: VirtualLarry
Hmm. So is this thread proof that the IP35-E does NOT support the E0 stepping with official BIOS 18? I'm just surprised, if that were true, wouldnt we be hearing more reports?
Click to expand...
I'm surprised as well, but many are still using 65nm chips and others have upgraded to the E7XXX series or gone to Q6600. It's only the E0 E8XXX chips with this problem.
 
Originally posted by: brencat
Originally posted by: VirtualLarry
Hmm. So is this thread proof that the IP35-E does NOT support the E0 stepping with official BIOS 18? I'm just surprised, if that were true, wouldnt we be hearing more reports?
Click to expand...
I'm surprised as well, but many are still using 65nm chips and others have upgraded to the E7XXX series or gone to Q6600. It's only the E0 E8XXX chips with this problem.
Click to expand...

Yeah it's dissapointing, but I think this board was still a big winner over its lifespan. It's just at the very end we're starting to see its limitations. It IS a p35 board and basically obsolete at this point, so we can't expect much. But for someone like me who got a C0 (luckily, I guess) it has been a wonderful board to use and I see it humming away for another couple of years.

It is a royal PITA for people who buy E8xxx chips without realizing they're going to have an issue with E0. I'm glad we're all aware of it now so we can help people out in the future.

I suspect anyone building a new system wouldn't be getting this board anyway, so I think that might explain why we haven't seen a huge outpouring of problems. Most people buying E0 chips are likely to get a P45 board or something better these days. The majority of people who bought the IP35-E did so before the .45nm introduction.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top