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

[SerpentRoyal]

Originally posted by: harbin
Serpent, I'd like to ask you a question about my system.

IP35-E, BIOS 13
E6420 Vcore=1.54v (set in bios), Abit EQ reports 1.47v under orthos.
FSB=462Mhz, RAM=926Mhz, G.Skill 2x1GB 800Mhz 2GBHZ, Voltage=2.2v, 4-4-4-12
Everything else upped 1 notch for the voltage
The system is stable for orthos 2 hours. (didn't try longer than 2 hours). CPU temp is 62-63under load.


Tunique T120
Antec Neo 450w
1 Maxtor 7200rmp 80G. 1 Liteon 20x SATA DVD burner.
X-Fi music
Abit Air Pace wireless PCI-E card.
Windows XP

My problem is sometimes after booting into XP, the system will not see the wireless card.

Remove and try the latest driver. Also remove and/or disable the Abit WiFi utility. You may have an issue with the WiFi card. Move the card to another PCI-E slot.

Also reset CMOS and retest at default configuration. You may have an unstable overclock. The X-Fi has been known to create a lot of problem with P35 chipset.

 

[Blacklash]

If you want to make sure it's not your ram and that your CPU is the culprit, set your ram to very relaxed settings like 5-6-6-15 or even 17 when you run Prime. When I have had my rig suddenly crash with Prime usually upping Vcore, NB, CPU VTT or ram voltage works. Usually, as others have stated, it's too low vcore or possibly NB as well. I have found it is very critical to have CPU VTT at the higher value when overclocking with my quad core past a certain point.

Blend = testing both, Small = CPU and Large = ram.

 

[SerpentRoyal]

A one notch bump in VTT, NB, and SB should be more than adequate unless we are working with OCZ RAMs. Those will require more juice at NB. I normally don't tinker with these parameters unless a 0.02-0.04V bump in Vcore yields no improvement.

 

[SerpentRoyal]

Originally posted by: Blacklash
If you want to make sure it's not your ram and that your CPU is the culprit, set your ram to very relaxed settings like 5-6-6-15 or even 17 when you run Prime. When I have had my rig suddenly crash with Prime usually upping Vcore, NB, CPU VTT or ram voltage works. Usually, as others have stated, it's too low vcore or possibly NB as well. I have found it is very critical to have CPU VTT at the higher value when overclocking with my quad core past a certain point.

Blend = testing both, Small = CPU and Large = ram.

Large mode draws the most juice and heat. My test routine includes two hours of Large mode, plus 15 minutes of S&M 100% heat mode. S&M also has a decent RAM tester module.

 

[jhigh2000]

Originally posted by: SerpentRoyal

Originally posted by: jhigh2000
I can run my q6600 at 9x333 at stock Vcore (Prime 95 small FFT) for 24+ hours without any errors, but unless I raise my Vcore a few notches, windows freezes about half the time on the XP splash screen while booting. Any thoughts as to why this is happening?

Adjust RAM voltage and timing to specs. Run Memtest86. Raise NB voltage by one notch. Orthos/Prime does not guarantee stability.

Thanks SerpentRoyal. My memory (Crucial Ballistix) is running at spec - 4-4-4-12 @2.2v, but at 667 MHz (1:1). Memtest86+ (including test #5) passes. At first I was exciting since I thought I was stable at stock VCore, but apparantly that is not the case . Here's a little more info on what is happening. When I reboot, XP freezes very early in the boot process (on the splash screen). After I hit reset, XP boots again, and goes to the startup problems screen. I choose "start windows normally" and it boots just fine. I can reproduce this behavior each time. As soon as I run the Q6600 at stock, the problem goes away.

Increasing the Vcore appeared to fix the reboot problem at first. My VID is 1.3. I had set the Vcore 2 ticks higher (i believe it was 1.34 in the BIOS). Unfortunately this morning it froze again during reboot.

I'm really surprised that it's stable with Prime95 but yet has issues booting. In any case, should I keep inching up the VCore to see if the problem goes away before I raise NB voltage?

Thanks again.

 

[hokiealumnus]

Jhigh, for what it's worth, I had a problem very similar to yours. I'd go into BIOS and try a new FSB. Save & exit and it would start up beautifully. Ran Orthos to test for stability, all three tests. Restarted to push it a little more...and nothing. It hung starting, didn't even POST.

Cleared CMOS and re-entered the exact setup...maybe I did something wrong? Nope...same behavior. Raised Vcore a notch and ran stability tests, which were fine before and fine this time. Restarted to see if it worked and it came up like normal.

 

[SerpentRoyal]

Originally posted by: jhigh2000

Originally posted by: SerpentRoyal

Originally posted by: jhigh2000
I can run my q6600 at 9x333 at stock Vcore (Prime 95 small FFT) for 24+ hours without any errors, but unless I raise my Vcore a few notches, windows freezes about half the time on the XP splash screen while booting. Any thoughts as to why this is happening?

Adjust RAM voltage and timing to specs. Run Memtest86. Raise NB voltage by one notch. Orthos/Prime does not guarantee stability.

Thanks SerpentRoyal. My memory (Crucial Ballistix) is running at spec - 4-4-4-12 @2.2v, but at 667 MHz (1:1). Memtest86+ (including test #5) passes. At first I was exciting since I thought I was stable at stock VCore, but apparantly that is not the case . Here's a little more info on what is happening. When I reboot, XP freezes very early in the boot process (on the splash screen). After I hit reset, XP boots again, and goes to the startup problems screen. I choose "start windows normally" and it boots just fine. I can reproduce this behavior each time. As soon as I run the Q6600 at stock, the problem goes away.

Increasing the Vcore appeared to fix the reboot problem at first. My VID is 1.3. I had set the Vcore 2 ticks higher (i believe it was 1.34 in the BIOS). Unfortunately this morning it froze again during reboot.

I'm really surprised that it's stable with Prime95 but yet has issues booting. In any case, should I keep inching up the VCore to see if the problem goes away before I raise NB voltage?

Thanks again.

Flash to 12 BIOS. Load Optimized Default in BIOS. Now go back to BIOS and change USB mouse/keyboard support from OS to BIOS, 1:1 memory divider, 2.2Vdimm, and 5-5-5-15-2T timing. If stable at boot, then change FSB to 333 and raise Vcore to 1.4. Also experiment with higher VTT, NB, and SB (up one notch only). If you don't have boot issue, then you can gradually drop down Vcore.

 

[Modular]

Does anyone know if Crucial Ballistix DDR2 800 works with this board. I'd love to get some 800mhz memory in there then use dividers and OC an E2140 without having to really mess with my RAM.

 

[hokiealumnus]

It may work, but you're taking a chance. Some folks can't boot RAM that requires that high of a Vdimm without first using another stick that will boot @ 1.8v, going into BIOS and raising Vdimm, shutting down & installing their sticks. Makes it a pain to overclock too if you have to repeat that process after clearing CMOS.

Serpent doesn't like OCZ, but I've never had a problem booting with the RAM that I've got and it overclocks moderately well (will run 450MHz @ 5-5-4-15-2T w/ 2.05Vdimm actual & 450MHz @ 4-4-4-15-2T w/ 2.15Vdimm actual...BIOS settings are 2.1v & 2.2v respectively). Oh...and they are $1 cheaper AR. Experimenting to see if it'll get above 450MHz but no luck so far and I've tried several combinations of settings.

Of course, since Serpent hates OCZ, in fairness he prefers Kinston N5 DDR2-800 ValueRAM.

 

[imported_jnk]

ive reflashed the 12 bios. and still get 48-50c idle, and 55-60c load. ill be trying my cpu+hsf on another board probably tom, when my friends gets back.

 

[SerpentRoyal]

Originally posted by: hokiealumnus
It may work, but you're taking a chance. Some folks can't boot RAM that requires that high of a Vdimm without first using another stick that will boot @ 1.8v, going into BIOS and raising Vdimm, shutting down & installing their sticks. Makes it a pain to overclock too if you have to repeat that process after clearing CMOS.

Serpent doesn't like OCZ, but I've never had a problem booting with the RAM that I've got and it overclocks moderately well (will run 450MHz @ 5-5-4-15-2T w/ 2.05Vdimm actual & 450MHz @ 4-4-4-15-2T w/ 2.15Vdimm actual...BIOS settings are 2.1v & 2.2v respectively). Oh...and they are $1 cheaper AR. Experimenting to see if it'll get above 450MHz but no luck so far and I've tried several combinations of settings.

Of course, since Serpent hates OCZ, in fairness he prefers Kinston N5 DDR2-800 ValueRAM.

I also like the HP-Crucial DDR2 667 RAMs. $10/GB AR @ Hot Deals forum.

Kingston N5 DDR2 667 is also very good. Only about $50 at NewEgg. Quite a few here with 400MHz/2.0V/4-4-4-12-2T. That's as fast as those "overclocking" DDR2 800 modules with fancy heat spreaders.

 

[jhigh2000]

Originally posted by: Modular
Does anyone know if Crucial Ballistix DDR2 800 works with this board. I'd love to get some 800mhz memory in there then use dividers and OC an E2140 without having to really mess with my RAM.

I have Crucial Ballistix DDR2 800 and they boot out of the box 1.8v. (5-5-5-15 i believe).

 

[SerpentRoyal]

Originally posted by: jnk
ive reflashed the 12 bios. and still get 48-50c idle, and 55-60c load. ill be trying my cpu+hsf on another board probably tom, when my friends gets back.

Could be a bad CPU thermal output. I still believe that you have poor contact at the CPU heat sink if you're running 50C idle at default BIOS settings. Your PWM and SYSTEM temperatures are good.

 

[SerpentRoyal]

Originally posted by: jhigh2000

Originally posted by: Modular
Does anyone know if Crucial Ballistix DDR2 800 works with this board. I'd love to get some 800mhz memory in there then use dividers and OC an E2140 without having to really mess with my RAM.

I have Crucial Ballistix DDR2 800 and they boot out of the box 1.8v. (5-5-5-15 i believe).

Most will boot okay, but we have seen a few that will not POST due to manufacturing tolerances.

 

[Modular]

I was looking at those HP sticks. I guess this really can be a true value OC'ers board!

 

[jhigh2000]

Originally posted by: SerpentRoyal

Flash to 12 BIOS. Load Optimized Default in BIOS. Now go back to BIOS and change USB mouse/keyboard support from OS to BIOS, 1:1 memory divider, 2.2Vdimm, and 5-5-5-15-2T timing. If stable at boot, then change FSB to 333 and raise Vcore to 1.4. Also experiment with higher VTT, NB, and SB (up one notch only). If you don't have boot issue, then you can gradually drop down Vcore.

I carefully compared my BIOS settings to the Optimized Defaults (I had everything written down for reference). The only difference was that I had the IDE controller disabled as I don't have any IDE devices. Just as a test, I enabled the IDE controller. Here's the weird part...the intermittant windows reboot problem appears to have gone away, even at stock Vcore. I've had 8 successfully reboots in a row which I could never do before.

Is it possible that windows was intermittently hanging trying to detect IDE controller?

Edit: I've read several threads about intermittent boot problems with the IP35 and Corsair PSU's (I have the 520HX), so now I'm also wondering if this could be part of the problem.

 

[SerpentRoyal]

Originally posted by: Modular
I was looking at those HP sticks. I guess this really can be a true value OC'ers board!

Keep in mind that the $10 HP will do 400MHz @ 2.0V/5-5-5-15-2T timing. That's fast enough to take a 9x multi CPU to 3.6GHz. You should avoid 7x or 8x multi CPUs because they place too much stress on RAM, MB, and CPU.

 

[Modular]

Originally posted by: SerpentRoyal

Originally posted by: Modular
I was looking at those HP sticks. I guess this really can be a true value OC'ers board!

Keep in mind that the $10 HP will do 400MHz @ 2.0V/5-5-5-15-2T timing. That's fast enough to take a 9x multi CPU to 3.6GHz. You should avoid 7x or 8x multi CPUs because they place too much stress on RAM, MB, and CPU.

So I should stay away from the E2140 and just get the E2160?

Edit: I figured that at 800mhz the 2140 would top out at 3.2 (which is higher than I'll probably take it, but we'll see), thus making that combo perfect when coupled with this board.

 

[SerpentRoyal]

I'd go with 2160, but if you're short of a few bucks, then E2140 would also work.

 

[jonmcc33]

Originally posted by: jhigh2000
I've read several threads about intermittent boot problems with the IP35 and Corsair PSU's (I have the 520HX), so now I'm also wondering if this could be part of the problem.

Running my 6400 and Abit IP35-E on a Corsair HX520 myself. No problems at all from first boot nor through all the overclocking.

 

[SerpentRoyal]

Not a widespread problem with 520/620 units. I've seen confirmed failure to POST threads at Abit and Asus forum.

Heck, I didn't even have any problem hitting 3.49GHz with E4300 and the Antec SP350. No, this is not an endorsement. SP350 is JUNK. Heck, the whole line of SP is suspect. I lost two SP350s within weeks of use! This unit is an Energizer Bunny. I throw everything at it in 85F room and it's still humming along. Guess Antec will not upgrade this one for Earthwatts 380.

 

[imported_jnk]

will "spreading" the as5 with a plastic card make a difference? since it will be thinner than the usual line application as suggested by the as5 site? thus more contact.

 

[SerpentRoyal]

A thin layer of AS5 on the heat spreader works best for many users. Too thick of a layer reduces heat transfer efficiency.

 

[hokiealumnus]

I can confirm that spreading AS: Ceramique (which is thicker & sticker than AS5) with a credit card as thin as I could get it on both the HSF & IHS dropped my temps by ~2-3c idle and load. Make sure you leave paste on there as it's simple to scrape off altogether though.

 

[KIAman]

I'm about to upgrade to 8GB of ram with Windows XP 64. Does anybody have any issues with this board and 8GB of ram?

Thanks!