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

[jonmcc33]

I don't think the double boot thing is an issue at all. Weird at first but if you never power down then how would you even notice it? If you reboot it won't do it.

Edit- Got my 6400 up to 2.8GHz already. Still not even getting hot. Wow, I didn't realize how good these Core 2 Duos were at overclocking. Amazing!

 

[SantaAna]

Hey fellas,

Was looking throug BIOS for changing keyboard from OS to BIOS. Could not find it. Could you help me out?

 

[blitzcat]

Originally posted by: jonmcc33
Well Serpent, got my IP35-E up and running now. Used the LGA775 bracket to install my XP-90 on my E6400. Got it to 333FSB and 2.66GHz already with only small bump of vCore. Running Vista Business right now, surprisingly Vista runs better on an Intel system than my old Opteron 165 system.

The Hynix DDR2-667 works fine although I'll want to upgrade in the near future. I'm going to continue exploring how far I can push it. Thanks again for such an amazing thread that convinced me to make this purchase. I really owe ya one.

Hi, i have Hynix DDR2-667 mem too, Hynix FP-Y5 to be precise. I run it @800mhz with 4-4-4-12 timing 1.95vdimm on my IP35-E

 

[jonmcc33]

Originally posted by: SantaAna
Hey fellas,

Was looking throug BIOS for changing keyboard from OS to BIOS. Could not find it. Could you help me out?

Look in the manual on page 2-13 under USB 2.0 Operation Mode.

 

[blitzcat]

@SerpentRoyal
After updating my BIOS from 11 to 13 beta, it seems my cpu temp arise about 10-15 C. Is that normal? I once worried that my Big Typhoon was getting loose.

 

[jonmcc33]

Originally posted by: blitzcat
Hi, i have Hynix DDR2-667 mem too, Hynix FP-Y5 to be precise. I run it @800mhz with 4-4-4-12 timing 1.95vdimm on my IP35-E

I'm still increasing my overclocks slowly yet surely. Up to 3GHz on my 6400, RAM/FSB is at 375MHz.

 

[aiya24]

i just flashed to beta 13 and noticed my cpu temps (not core temps) are higher than usual. is this normal for beta 13?

 

[hokiealumnus]

Originally posted by: blitzcat
@SerpentRoyal
After updating my BIOS from 11 to 13 beta, it seems my cpu temp arise about 10-15 C. Is that normal? I once worried that my Big Typhoon was getting loose.

Originally posted by: aiya24
i just flashed to beta 13 and noticed my cpu temps (not core temps) are higher than usual. is this normal for beta 13?

The temperature change actually happens w/ v.12 & v.13beta BIOS updates. Versions 10 & 11 both read the CPU Temperature from the Tcase sensor and 12 & 13beta read either from one of the Tjunctions or an average of the two (not sure which). This leads to a ~15c jump in the CPU Temperature reading in the BIOS and on the CPU reading in Speedfan (because it goes through the BIOS).

I just offset my CPU reading in Speedfan by -14 (added 1c to be safe) to show the correct Tcase temperature. There is a lengthy sticky on this on the abit forums, which are unfortunately down now or I'd link to it. Anyway...the short answer is, yes that is normal.

 

[hokiealumnus]

Originally posted by: Tangman85
Well, double boot is fixed unless power cable is plugged out?

Regarding BIOS 13 though, is it still BETA or is it actually released? Don't see it on the homepage

Yes, it's still a beta version. You can download it from the first page in this thread or over at the abit forums.

Originally posted by: SantaAna
Hey fellas,

Was looking throug BIOS for changing keyboard from OS to BIOS. Could not find it. Could you help me out?

It's in the "Integrated Peripherals" / "OnChip PCI Device" / "USB Device Setting" menu.

 

[hokiealumnus]

Originally posted by: jonmcc33

Originally posted by: blitzcat
Hi, i have Hynix DDR2-667 mem too, Hynix FP-Y5 to be precise. I run it @800mhz with 4-4-4-12 timing 1.95vdimm on my IP35-E

I'm still increasing my overclocks slowly yet surely. Up to 3GHz on my 6400, RAM/FSB is at 375MHz.

Good job, keep it up! The highest I could get on air was 3.4GHz w/ 1.505Vcore set in BIOS (1.464v actual after Vdroop). Any higher FSB and it's not stable (even tried 3.42). Any higher Vcore and temps go above 75c.

I'm quite happy with it, but luck of the draw wasn't with me; I'm sure there are E4400s that can hit 3.5, which was my ultimate goal. This one could probably do it, but it would 1. take it above 1.5v (1.525 set in BIOS), which is the max on intel's spec page (and I can't bring myself to exceed it) and 2. require water cooling.

That said, the OC in my sig is what I run 24/7 with only one little notch above default Vcore. So 50% overclock 24/7 with barely any increase in Vcore, plus temps that barely break 60c? ...what's not to like?

 

[aiya24]

Originally posted by: hokiealumnus

Originally posted by: blitzcat
@SerpentRoyal
After updating my BIOS from 11 to 13 beta, it seems my cpu temp arise about 10-15 C. Is that normal? I once worried that my Big Typhoon was getting loose.

Originally posted by: aiya24
i just flashed to beta 13 and noticed my cpu temps (not core temps) are higher than usual. is this normal for beta 13?

The temperature change actually happens w/ v.12 & v.13beta BIOS updates. Versions 10 & 11 both read the CPU Temperature from the Tcase sensor and 12 & 13beta read either from one of the Tjunctions or an average of the two (not sure which). This leads to a ~15c jump in the CPU Temperature reading in the BIOS and on the CPU reading in Speedfan (because it goes through the BIOS).

I just offset my CPU reading in Speedfan by -14 (added 1c to be safe) to show the correct Tcase temperature. There is a lengthy sticky on this on the abit forums, which are unfortunately down now or I'd link to it. Anyway...the short answer is, yes that is normal.

thanks, i thought it was along those lines since its now close to my coretemp readings.

 

[SerpentRoyal]

Originally posted by: blitzcat

Originally posted by: jonmcc33
Well Serpent, got my IP35-E up and running now. Used the LGA775 bracket to install my XP-90 on my E6400. Got it to 333FSB and 2.66GHz already with only small bump of vCore. Running Vista Business right now, surprisingly Vista runs better on an Intel system than my old Opteron 165 system.

The Hynix DDR2-667 works fine although I'll want to upgrade in the near future. I'm going to continue exploring how far I can push it. Thanks again for such an amazing thread that convinced me to make this purchase. I really owe ya one.

Hi, i have Hynix DDR2-667 mem too, Hynix FP-Y5 to be precise. I run it @800mhz with 4-4-4-12 timing 1.95vdimm on my IP35-E

Avoid OCZ stuffs and you'll be fine. It's best to limit Vdimm to 2.0V under normal use. Version 12 and 13 reflect the actual core temperature (just like coretemp). Therefore, your CPU will increase by about 15C. All E21x0 and E4xx0 chips should be fine up to about 70-75C.

 

[ArchAngel777]

Serpent,

I wonder if you can help me figure out something here.

I switched to water this weekend and created a duct so my rear fan blows right on PWM. I was able to stabalized PWM for the most part. It peaks at 83c under large FFT (or so I *think* it peaks there. CPU is a nice cool 68c (hottest core)... Pumping 1.46v under load through it @ 3.6Ghz - 400x9.

Well, after running P95 Large FFT the system will shut off... I find this odd because my PWM temps are not above the shutdown limit, nor is my CPU anywhere near my my shutdown temperature (90c). I verified with Core Temp and CPU Right mark...

So, I am trying to figure out why the system is shutting down on me... It ONLY happens in Prime95 FFT... I can use CPU Burn-in (slightly less stressfull stead @ 67c CPU / 73c PWM) and it works fine...

So I am not sure what to think at this point... I might just leave it be at this point and forgoet about running P95. Everything else runs great and the CPU runs cooler than when I had it on air.

 

[ArchAngel777]

I think I figured it out... Well, I shouldn't say that our I will end up jynxing myself...

Anyway, I found that the NB was very hot to the touch... I suspect there is another temperature guage for the NB that isn't display in BIOS or in their AbitEQ (crap software) software... The chip is scaling hot after the computer shuts down... So, I riged up a 120mm fan right up next to it. Testing Orthos now... Large FFT...

Edit ** Damn, that was not it... Oh well, at least the NB is cool to the touch now.

I decided to run the next more stressfull thing than Orthos Large FFT... Program called OCCT. Pretty good because it is not just one thing over and over, steady... It brings temps to peak, then drops it down a few, brings up back up... etc.. Here is a screenshot.

Q6600 @ 3.6Ghz 1.5v

I am happy enough, not worried, but I wish I knew why P95 Large FFT is causing my system to shutdown 8 minutes into the test... FYI Wattage draw with large FFT = ~415 and OCCT is around ~405...

 

[SerpentRoyal]

Originally posted by: ArchAngel777
Serpent,

I wonder if you can help me figure out something here.

I switched to water this weekend and created a duct so my rear fan blows right on PWM. I was able to stabalized PWM for the most part. It peaks at 83c under large FFT (or so I *think* it peaks there. CPU is a nice cool 68c (hottest core)... Pumping 1.46v under load through it @ 3.6Ghz - 400x9.

Well, after running P95 Large FFT the system will shut off... I find this odd because my PWM temps are not above the shutdown limit, nor is my CPU anywhere near my my shutdown temperature (90c). I verified with Core Temp and CPU Right mark...

So, I am trying to figure out why the system is shutting down on me... It ONLY happens in Prime95 FFT... I can use CPU Burn-in (slightly less stressfull stead @ 67c CPU / 73c PWM) and it works fine...

So I am not sure what to think at this point... I might just leave it be at this point and forgoet about running P95. Everything else runs great and the CPU runs cooler than when I had it on air.

Shut down or restart? Turn off all temp monitoring in BIOS. I would be more comfortable with sub 75C PWM. You should be able to strap a small 40mm fan to the PWM heat sink to keep temp well under 80C. Problem with water cooling is that you will need to cool the NB, SB, and MOSFETs with additional fans. Spontaneous reboot is usually due to lack of Vcore. I'd bump Vcore up 0.02-0.04V and retest.

Also note that most older quads will top out around 3.4GHz. Back-off to 3.55GHz and retest.

 

[ArchAngel777]

Originally posted by: SerpentRoyal

Originally posted by: ArchAngel777
Serpent,

I wonder if you can help me figure out something here.

I switched to water this weekend and created a duct so my rear fan blows right on PWM. I was able to stabalized PWM for the most part. It peaks at 83c under large FFT (or so I *think* it peaks there. CPU is a nice cool 68c (hottest core)... Pumping 1.46v under load through it @ 3.6Ghz - 400x9.

Well, after running P95 Large FFT the system will shut off... I find this odd because my PWM temps are not above the shutdown limit, nor is my CPU anywhere near my my shutdown temperature (90c). I verified with Core Temp and CPU Right mark...

So, I am trying to figure out why the system is shutting down on me... It ONLY happens in Prime95 FFT... I can use CPU Burn-in (slightly less stressfull stead @ 67c CPU / 73c PWM) and it works fine...

So I am not sure what to think at this point... I might just leave it be at this point and forgoet about running P95. Everything else runs great and the CPU runs cooler than when I had it on air.

Shut down or restart? Turn off all temp monitoring in BIOS. I would be more comfortable with sub 75C PWM. You should be able to strap a small 40mm fan to the PWM heat sink to keep temp well under 80C. Problem with water cooling is that you will need to cool the NB, SB, and MOSFETs with additional fans. Spontaneous reboot is usually due to lack of Vcore. I'd bump Vcore up 0.02-0.04V and retest.

Also note that most older quads will top out around 3.4GHz. Back-off to 3.55GHz and retest.

It actually shut downs... Then it pauses for about 10 seconds, restarts and somtimes will shut off immediately (sensor likely is picking up that something is too hot still) again and repeat until it posts back up again. Sometimes it works fine on the second post, others the third... So far the only problem is with Large FFT.

If I clock her at 3.2Ghz @ 1.35v I can keep PWM to 67c PWM with my new setup. Once I switched to water, things started to look better with PWM. But since I jacked up Vcore another .15v, I am in a whole nother ball game.

I could increase the voltage 0.O! But, I'd rather not push past 1.5v.

Everyting else is stable... No random crap or anything with OCCT, CPU Burn-In, 3DMark @ 640x480, Lost Planet @ 640x360... Definately love my new setup though!

 

[SerpentRoyal]

Chip out out gas or insufficient Vcore.

 

[ArchAngel777]

Originally posted by: SerpentRoyal
Chip out out gas or insufficient Vcore.

Yep, sort of what I figured then. Though I did notice that it shut downs at the same spot in Orthos, regardless of temp... Right before the switch to test #9 it goes BAM OFF!

So I lowered vcore by one notch just to see something... Then I will try and raise it two notches...

 

[hokiealumnus]

Aye, that's exactly what mine does with Vcore too low. Bumping it up a notch generally gets it running just peachy. Once you're at the very upper limits of your chip, it takes even more to get just a tiny increase in FSB. Not much for you to do except seriously over volt your chip (and chance killing it) or buy a new one and start playing again!

 

[ArchAngel777]

Originally posted by: hokiealumnus
Aye, that's exactly what mine does with Vcore too low. Bumping it up a notch generally gets it running just peachy. Once you're at the very upper limits of your chip, it takes even more to get just a tiny increase in FSB. Not much for you to do except seriously over volt your chip (and chance killing it) or buy a new one and start playing again!

Are you sure 100%? So, you can run Prime 95, then about 10 minutes into it, it would shut off? You were able to bypass the issue by increasing vcore? I am just curious if you did that and can confirm.

Anyway, this is what *I* can confirm with my particular chip... I dropped Vcore down one notch, and now it has been running for 20 minutes, far past where it kept rebooting before... Wierd... The good news is that PWM = 75c and it stays there under load... My CPU hits max load after like 2 minutes (I love water!) it takes about 15 for PWM To hit the peak...

Anyway, I will keep everyone informed... So far so good though... My IP35-E keeps chugging along...

 

[SerpentRoyal]

Plot CPU core speed (Y axis) vs Vcore (X axis) on regular graph paper. The graph should be linear until you reach the point of CPU saturation where a lot of Vcore will result in a small increase in CPU core speed. For dual core, the linear range is 0.04Vcore per 90MHz core speed. My E4300 is still "linear" up to 1.505Vcore. At this setting, the peak core temp under load is 78-80C at 85F ambient. That's just too hot. PC runs fine under Orthos in sub 70F room.

 

[hokiealumnus]

What I can tell you for sure is that when I set FSB to a frequency it doesn't like, it will boot into Windows fine & start everything up. I'll get CPUz, coretemp, speedfan & Orthos up and running. After 30sec to 1.5min, if FSB is too high for Vcore, it'll simply crash to blank screen & reboot. Note no 10 second pause; the only pause is the double-boot. While rebooting, on the way back, I bump Vcore up a notch, boot into Windows, rinse & repeat. Once Orthos is stable for a while, I try upping FSB and continue on the journey.

 

[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?

 

[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.

 

[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.