Abit IP35-E Review (500MHz FSB board)...$90 @ NewEgg + $6.61 ship

[SerpentRoyal]

There's an Abit windows flash utility. Download BIOS to the HDD. Make sure BIOS is reset to DEFAULT. Turn off AV, FW, and all non-essential application when you flash in windows.

 

[jonmcc33]

Originally posted by: SerpentRoyal
There's an Abit windows flash utility. Download BIOS to the HDD. Make sure BIOS is reset to DEFAULT. Turn off AV, FW, and all non-essential application when you flash in windows.

Thanks. Didn't realize it was on the CD. FlashMenu, eh? Worked like a charm. No more dual POST. Thanks again Serp!

Oh, I never run a firewall in Windows. Quite useless IMO.

 

[rodrigu3]

here's a funny story, I was running prime 95 overnight to test for stability and at around 5AM my pc starts beeping like mad, like a police siren WEE-WAH-WEE-WAH... prime was still running fine so I thought it was overheating or blowing up, looked at my temps, below 50 - then I just realized I had found a new prime # lol

on another note though, I've hit a FSB wall at about 350Mhz, it will post, but windows will not boot (no blue screen it just gets stuck) any ideas? I was running at 7x 358 with relaxed timings and voltages all bumped up when it failed (it wasn't the voltage) - should I try running memtest to see if my ram is crap? I hope it isnt

 

[jhigh2000]

Originally posted by: SerpentRoyal
Based on my test, this BIOS is the SAME as the BETA BIOS. No problem at all, except my 1M Super Pi time went from 16.250 to 16.610 with 13 BIOS.

Hmm....Is this due to slightly looser default timings? If so, would it be possible to compensate for this small performance loss by running a slightly higher FSB without compromising stability?

 

[hokiealumnus]

Originally posted by: rodrigu3
here's a funny story, I was running prime 95 overnight to test for stability and at around 5AM my pc starts beeping like mad, like a police siren WEE-WAH-WEE-WAH... prime was still running fine so I thought it was overheating or blowing up, looked at my temps, below 50 - then I just realized I had found a new prime # lol

on another note though, I've hit a FSB wall at about 350Mhz, it will post, but windows will not boot (no blue screen it just gets stuck) any ideas? I was running at 7x 358 with relaxed timings and voltages all bumped up when it failed (it wasn't the voltage) - should I try running memtest to see if my ram is crap? I hope it isnt

What components are you running (please include a link to your exact RAM). When I hit a wall like that after dropping my multiplier, I found the CPU needed more voltage. Tven though its frequency was relatively low, it still needs more juice for the higher FSB. Also, if you haven't already, drop your CPU : DRAM ratio to 1:1. Need to know what RAM you have before I can really go further.

 

[rodrigu3]

Crucial Ballistix DDR2 800, 4-4-4-12 2.2V (2x1Gb dual channel)

I don't believe it was my core voltage though, because I had set it to 1.465 in bios, I had also tried bumping up the NB and SB voltage to no avail. I always OC with ram at relaxed timings and 1:1. Right now, I have it stable at 10x 300Mhz @ 1.42V (voltage drop is 0.2 and vdroop is 0.02) mem at 1:2 with 4-4-4-12 2T @ 2.1V

just seems strange that this board (IP35-E) should hit 400Mhz relatively easily but fails at 350 - temps are not a problem, NB temp is fine (heatsink feels warm to touch, not hot) and core temp is 30C idle, 45-47 w/ prime95 as reported by both speedfan and coretemp

 

[SerpentRoyal]

Originally posted by: rodrigu3
here's a funny story, I was running prime 95 overnight to test for stability and at around 5AM my pc starts beeping like mad, like a police siren WEE-WAH-WEE-WAH... prime was still running fine so I thought it was overheating or blowing up, looked at my temps, below 50 - then I just realized I had found a new prime # lol

on another note though, I've hit a FSB wall at about 350Mhz, it will post, but windows will not boot (no blue screen it just gets stuck) any ideas? I was running at 7x 358 with relaxed timings and voltages all bumped up when it failed (it wasn't the voltage) - should I try running memtest to see if my ram is crap? I hope it isnt

CPU model number? Always use the highest CPU multi for best core speed. May need to raise VTT, NB, and SB with junk RAMs.

 

[rodrigu3]

e2180

 

[SerpentRoyal]

Originally posted by: jhigh2000

Originally posted by: SerpentRoyal
Based on my test, this BIOS is the SAME as the BETA BIOS. No problem at all, except my 1M Super Pi time went from 16.250 to 16.610 with 13 BIOS.

Hmm....Is this due to slightly looser default timings? If so, would it be possible to compensate for this small performance loss by running a slightly higher FSB without compromising stability?

I think Abit tinkered with the RAM timing. The penalty is about 300MHz core speed. That's why I'm still running 12 BIOS.

 

[SerpentRoyal]

Originally posted by: rodrigu3
Crucial Ballistix DDR2 800, 4-4-4-12 2.2V (2x1Gb dual channel)

I don't believe it was my core voltage though, because I had set it to 1.465 in bios, I had also tried bumping up the NB and SB voltage to no avail. I always OC with ram at relaxed timings and 1:1. Right now, I have it stable at 10x 300Mhz @ 1.42V (voltage drop is 0.2 and vdroop is 0.02) mem at 1:2 with 4-4-4-12 2T @ 2.1V

just seems strange that this board (IP35-E) should hit 400Mhz relatively easily but fails at 350 - temps are not a problem, NB temp is fine (heatsink feels warm to touch, not hot) and core temp is 30C idle, 45-47 w/ prime95 as reported by both speedfan and coretemp

Not much you can do with a bum CPU. Try 1.505Vcore and 9x multi. E21x0 and E4xx0 should top out around 425MHz FSB.

 

[rodrigu3]

sorry, bum CPU? do you mean mine in particular or the model itself?

 

[SerpentRoyal]

An "F" CPU. Most will do 3.2GHz. Some will hit 3.6GHz. A few may be stuck at 2.8GHz. You have a 3.0GHz chip. Try 5-5-5-15-2T with 12 BIOS.

 

[hokiealumnus]

Originally posted by: SerpentRoyal

Originally posted by: jhigh2000

Originally posted by: SerpentRoyal
Based on my test, this BIOS is the SAME as the BETA BIOS. No problem at all, except my 1M Super Pi time went from 16.250 to 16.610 with 13 BIOS.

Hmm....Is this due to slightly looser default timings? If so, would it be possible to compensate for this small performance loss by running a slightly higher FSB without compromising stability?

I think Abit tinkered with the RAM timing. The penalty is about 300MHz core speed. That's why I'm still running 12 BIOS.

They definitely did. Here's a post I have over at abit. Maybe folks here have input as well:

Is anyone having trouble with RAM overclocks with BIOS v.13? v.12 allowed me to run the specs in my sig, but I cannot get DDR2-900 stable with this BIOS. Dropped timings to 5-5-5-15-2T instead of 5-5-4-15-2T, raised Vdimm to 2.2 from 2.1 and even tried raising tRFC from auto (which runs 42) to 44 with no success. Any clue as to what that's about?

UPDATE - Wow, they really messed with the RAM settings. Backed off to 10x280, with the RAM running DDR2-840 at 4-4-4-15-2T, which was never a problem before. It wouldn't load into windows. Had to back off to 5-5-4-15-2T. I guess the speed loss is irrelevant with this crazy RAM speed loss. Likely back to v.12 for me.

 

[dreddfunk]

Interestingly, I just started testing my 2140/IP35-E/HP DDR2-667 system and I can't get it to POST beyond a FSB of 255. It will do 250 on default vcore and 255 on a vcore of 1.465, but anything more and it won't even POST, let alone boot to windows. At 250x8 it's Orthos-stable for over an hour, with temps at 50-51 under 100% load. After it fails to POST, I have to reset CMOS in order to boot again.

I'm very new to this so there are a ton of things I could be doing wrong. I won't be bitter if the chip can't go beyond 2.0GHz, but I'd be a little surprised if it wasn't me. The RAM and MB are still way under their rated speeds, though, so I'm a little confused.

Details:
e2140, stock cooler, vcore is set to 1.465, and speedstep and C1E are disabled
Abit IP35-E, NB & SB still on default voltage
HP-branded DDR2-667 (Micron) 3x1GB, 5-5-5-15 @ 1.8v, 1:1 ratio.
HD zero-filled prior to building the system
Antec SuperLanboy case with front & rear 120mm fans

 

[SerpentRoyal]

Originally posted by: dreddfunk
Interestingly, I just started testing my 2140/IP35-E/HP DDR2-667 system and I can't get it to POST beyond a FSB of 255. It will do 250 on default vcore and 255 on a vcore of 1.465, but anything more and it won't even POST, let alone boot to windows. At 250x8 it's Orthos-stable for over an hour, with temps at 50-51 under 100% load. After it fails to POST, I have to reset CMOS in order to boot again.

I'm very new to this so there are a ton of things I could be doing wrong. I won't be bitter if the chip can't go beyond 2.0GHz, but I'd be a little surprised if it wasn't me. The RAM and MB are still way under their rated speeds, though, so I'm a little confused.

Details:
e2140, stock cooler, vcore is set to 1.465, and speedstep and C1E are disabled
Abit IP35-E, NB & SB still on default voltage
HP-branded DDR2-667 (Micron) 3x1GB, 5-5-5-15 @ 1.8v, 1:1 ratio.
HD zero-filled prior to building the system
Antec SuperLanboy case with front & rear 120mm fans

Flash to 12 BIOS with the "WB" switch (see my 1st post). Load Optimized Default. Boot back to BIOS 2nd time. Change USB keyboard and mouse support from OS to BIOS. Change memory divider to 1:1. Change memory voltage to 2.0. Change memory timing to 5-5-5-15-2T. Change Vcore to 1.465. Change GTLREF to 65%. Hit F10.

Boot into windows and check that FSB = RAM speed with CPUz. If you cannot enter windows above 260MHz FSB, then run memtest86, test #5 for 50 loops at 255MHz FSB to test RAMs. One of the stick may be defective. Test overclock with two sticks of RAM.

I've seen some issues with TP PSU but the chance of a bad PSU is very small in this case. It's best to test the system outside the case.

 

[jonmcc33]

Originally posted by: SerpentRoyal

Originally posted by: jhigh2000

Originally posted by: SerpentRoyal
Based on my test, this BIOS is the SAME as the BETA BIOS. No problem at all, except my 1M Super Pi time went from 16.250 to 16.610 with 13 BIOS.

Hmm....Is this due to slightly looser default timings? If so, would it be possible to compensate for this small performance loss by running a slightly higher FSB without compromising stability?

I think Abit tinkered with the RAM timing. The penalty is about 300MHz core speed. That's why I'm still running 12 BIOS.

Mine still hit 3.2GHz like before. Didn't lose any performance that I can see.

 

[mrgrey1970]

:shocked:

I`ve just updated to the 13 BIOS, reset my modest overclock to what it was before, set my memory timings as they were previously (4-4-4-12) and windows would not fully boot. Dropped timings back to default (5-5-5-18 2T) and windows now appears fine again.

The double boot issue is still there too...is it possible to downgrade my BIOS or do the looser timings not matter too much?

 

[jonmcc33]

Reset your CMOS. That's what I had to do.

 

[mrgrey1970]

I have reset CMOS twice, makes no difference

 

[SerpentRoyal]

Originally posted by: jonmcc33

Originally posted by: SerpentRoyal

Originally posted by: jhigh2000

Originally posted by: SerpentRoyal
Based on my test, this BIOS is the SAME as the BETA BIOS. No problem at all, except my 1M Super Pi time went from 16.250 to 16.610 with 13 BIOS.

Hmm....Is this due to slightly looser default timings? If so, would it be possible to compensate for this small performance loss by running a slightly higher FSB without compromising stability?

I think Abit tinkered with the RAM timing. The penalty is about 300MHz core speed. That's why I'm still running 12 BIOS.

Mine still hit 3.2GHz like before. Didn't lose any performance that I can see.

Run 1M Super Pi with 12 vs 13 BIOS. Better yet, run 32M.

 

[dreddfunk]

Originally posted by: SerpentRoyal
Flash to 12 BIOS with the "WB" switch (see my 1st post). Load Optimized Default. Boot back to BIOS 2nd time. Change USB keyboard and mouse support from OS to BIOS. Change memory divider to 1:1. Change memory voltage to 2.0. Change memory timing to 5-5-5-15-2T. Change Vcore to 1.465. Change GTLREF to 65%. Hit F10.

Boot into windows and check that FSB = RAM speed with CPUz. If you cannot enter windows above 260MHz FSB, then run memtest86, test #5 for 50 loops at 255MHz FSB to test RAMs. One of the stick may be defective. Test overclock with two sticks of RAM.

I've seen some issues with TP PSU but the chance of a bad PSU is very small in this case. It's best to test the system outside the case.

Serpent - thanks for the reply. I flashed the BIOS first thing when I built it on Thursday, but I'll check to ensure that I have 12. I didn't load optimized default, so I will do that. I did switch keyboard and mouse support to BIOS and change the memory divider to 1:1. I haven't tried setting memory voltage to 2.0, so I'll do that as well. I'll also manually set the timings. The vcore is at 1.465, but I'm not familiar with GTLREF.

I'll run memtest at 255 once I've got all the settings right and report back.

Thanks again, your experienced advice is greatly appreciated.

 

[jonmcc33]

Originally posted by: SerpentRoyal
Run 1M Super Pi with 12 vs 13 BIOS. Better yet, run 32M.

I had the 11 BIOS initially. I don't get into the habit of flashing the BIOS all the time. It still overclocks, I haven't seen any performance drop and the dual POST issue is gone. That's when I leave my crap alone. I once toasted an Asus A8R-MVP by flashing the BIOS when I didn't need to.

 

[Hitmonchau]

Hey guys, I just got done with my build with this board and a 6550. I haven't overclocked or changed any voltages and I'm using the intel heatsink and fan (10% silver compound also used). The problem is my cpu is idling at 50C and during the COD4 demo it wll get over 70C!! Do I have a bad processor?

 

[SerpentRoyal]

CPU cooler is probably not properly attached. Re-read the instruction. Take the MB outside the case if necessary to make sure all four pins are in.

 

[mrgrey1970]

Originally posted by: Hitmonchau
Hey guys, I just got done with my build with this board and a 6550. I haven't overclocked or changed any voltages and I'm using the intel heatsink and fan (10% silver compound also used). The problem is my cpu is idling at 50C and during the COD4 demo it wll get over 70C!! Do I have a bad processor?

You definately have a problem there as I too have an e6550 and it`s currently idling at 26c, on full load maybe 56-57c. Oh, and it`s overclocked to 3 Ghz on stock cooling.

As Serpentroyal has already suggested see if the HSF is properly seated