IP35-E average max FSB with a quad?

[soccerballtux]

I could test this myself, but I don't have a quad, and I've heard that a quad makes a difference because of the stress on the PWM (is there less stress with the 45nm CPUs?)

So basically I'm trying to figure out if I'll need to spend the extra money on the q9550 over the q9450.

 

[Spammeh]

You're gonna need to strap a fan to the pwm if you stick a quad onto that ip35-e and overclock. My pwm is peaks at 84c with q6600 at 3.3ghz with 1.50vcore bios. That temp is with a 40mm minikaze strapped just in front of the pwm!

I'm guessing pwm temp will be lower with a 45nm quad though.

 

[Gillbot]

You may be able to clock a quad but over time it will degrade the board. My bro had a Q6600 on his IP35-E and over time he kept losing stability.

 

[Spammeh]

how far did he push it temp and voltage wise gillbot?

 

[KeaBorg]

My q66 was at 1.59v in bios which was 1.45loaded in windows or 1.49 unloaded I had the fsb up around 480ish but it was never stable til I dropped it below the 450 mark. I'm his brother btw

 

[Tweakin]

The IP35-E is not a great board for quad oc'ing. I tweaked my Q6600 for some time and finally gave up as the speed vs longt-term stabilitly on this board did not make sense.

It's a great board for c2d's and oc'ing...just lacks the pwm gustoness for quads...IMO

 

[Ratman6161]

I don't know why you all seem to think the IP35-E isn't a good overclocker with quads. One thing I notice is that you all seem to be running way higher voltages than I am. I only bumped my cpu voltage up one notch from stock and didn't increase any other voltages at all to get to 3.2 Ghz. At 3.0 Ghz it runs great at stock voltage.

Perhaps you were using older steppings of the Q6600?

As long as you don't try to get too extreme, it does in fact overclock quite well. Running a 2.4 ghz chip at 3.2 counts as quite well in my book at least, given that its running at the same clock speed as $1000+ cpus.

 

[KeaBorg]

Originally posted by: Ratman6161
I don't know why you all seem to think the IP35-E isn't a good overclocker with quads. One thing I notice is that you all seem to be running way higher voltages than I am. I only bumped my cpu voltage up one notch from stock and didn't increase any other voltages at all to get to 3.2 Ghz. At 3.0 Ghz it runs great at stock voltage.

Perhaps you were using older steppings of the Q6600?

As long as you don't try to get too extreme, it does in fact overclock quite well. Running a 2.4 ghz chip at 3.2 counts as quite well in my book at least, given that its running at the same clock speed as $1000+ cpus.

I was running mine QUITE higher then you were running yours also. 3.6ghz isn't 3.2ghz. I've also had mine in windows and semi stable at 3.7 but by no means were either of those prime stable, I have the same board with my current cpu which is a e8400 doing 4.2ghz without a sweat, the IP35-E doesn't put out enough power for a quad period, over time the vdroop gets worse and worse til one day it's not stable and you have to back it down.

 

[Gillbot]

The higher you clock, the more stress you put on the board.

 

[Spammeh]

Originally posted by: KeaBorg
My q66 was at 1.59v in bios which was 1.45loaded in windows or 1.49 unloaded I had the fsb up around 480ish but it was never stable til I dropped it below the 450 mark. I'm his brother btw

1.59vcore - I guess that was done with water?

 

[bryanW1995]

well, I have two ip35-e's with quads. one has a q6600 and the other has q9450. the q6600 had some stability issues at 3.5, so I backed vcore down to 1.50 bios (1.44 load) and lowered the oc to 3.4. so far it is rock solid running seti 24/7 for that past few weeks. my pwm never gets over 64c, so I'm not sure why the other user's pwm was getting so hot. I have an average at best case with 3 80mm fans, but I do have a tuniq on this unit.

The q9450 rig has a zalman on it. I used to run it at 3.4 when I had it at work, but now that it's at my house it's backed down to 3.2. I went fanless on my zalman overnight a few weeks ago and now have some, uh, "stability isues", but before that it had never given me any issues. I have kept voltages very low on this unit as heat is a problem both for the zalman and for my computer room.


One thing that seems to have helped both of my ip35-e's is the newer bios. I can't remember if I'm on 16b02 or 17, but both of those significantly improved vdroop. Time will tell if that increases their longevity, though I think that it probably will. I only paid ~ $65 for both mobos, too, so if they start to flake out on me it won't be much of a burden to replace them with beefier models in the future.

 

[Spammeh]

Originally posted by: bryanW1995
well, I have two ip35-e's with quads. one has a q6600 and the other has q9450. the q6600 had some stability issues at 3.5, so I backed vcore down to 1.50 bios (1.44 load) and lowered the oc to 3.4. so far it is rock solid running seti 24/7 for that past few weeks. my pwm never gets over 64c, so I'm not sure why the other user's pwm was getting so hot. I have an average at best case with 3 80mm fans, but I do have a tuniq on this unit.

The q9450 rig has a zalman on it. I used to run it at 3.4 when I had it at work, but now that it's at my house it's backed down to 3.2. I went fanless on my zalman overnight a few weeks ago and now have some, uh, "stability isues", but before that it had never given me any issues. I have kept voltages very low on this unit as heat is a problem both for the zalman and for my computer room.


One thing that seems to have helped both of my ip35-e's is the newer bios. I can't remember if I'm on 16b02 or 17, but both of those significantly improved vdroop. Time will tell if that increases their longevity, though I think that it probably will. I only paid ~ $65 for both mobos, too, so if they start to flake out on me it won't be much of a burden to replace them with beefier models in the future.

yeah the pwm only really heats up that high in prime/linpack - it doesn't reach 84c normally ofc

I might give the newer bios a shot although it's working well with 14 final at the moment.

 

[KeaBorg]

Originally posted by: Spammeh

Originally posted by: KeaBorg
My q66 was at 1.59v in bios which was 1.45loaded in windows or 1.49 unloaded I had the fsb up around 480ish but it was never stable til I dropped it below the 450 mark. I'm his brother btw

1.59vcore - I guess that was done with water?

False, it was done using a TRUE and you can't go by 1.59 in the bios, as it was only 1.48 in windows and 1.45 loaded, but after a few weeks of having it at 1.45 loaded the droop would droop it to 1.40 which was not stable. I popped my 8400 in and the problems gone, think what you will but these boards SUCK for oc'ing quads. They can OC quads but they will not remain stable, they weren't meant to be abused as I've done. Before I had the q66 I had a e6550 doing 3.5ghz at 500fsb ALL day every day for a year +, but as soon as I had my quad in there 2-3 weeks later, I had to keep bumping the voltage to keep it stable in windows, hence the 1.59 bios 1.47 windows and 1.45 loaded.

 

[bryanW1995]

Originally posted by: KeaBorg

Originally posted by: Spammeh

Originally posted by: KeaBorg
My q66 was at 1.59v in bios which was 1.45loaded in windows or 1.49 unloaded I had the fsb up around 480ish but it was never stable til I dropped it below the 450 mark. I'm his brother btw

1.59vcore - I guess that was done with water?

False, it was done using a TRUE and you can't go by 1.59 in the bios, as it was only 1.48 in windows and 1.45 loaded, but after a few weeks of having it at 1.45 loaded the droop would droop it to 1.40 which was not stable. I popped my 8400 in and the problems gone, think what you will but these boards SUCK for oc'ing quads. They can OC quads but they will not remain stable, they weren't meant to be abused as I've done. Before I had the q66 I had a e6550 doing 3.5ghz at 500fsb ALL day every day for a year +, but as soon as I had my quad in there 2-3 weeks later, I had to keep bumping the voltage to keep it stable in windows, hence the 1.59 bios 1.47 windows and 1.45 loaded.

that's because you were using an older bios. vdrop is a huge problem with my ip35 pro as well...at least it was until I updated to bios 16. bios 16 or greater on any of the ip35 series seems to be the key for controlling vdrop. btw, some quick definitions:

vdrop: difference between vcore in bios and vcore at idle
vdroop: difference between vcore at idle and vcore at load

iirc my vdroop was actually the same or at least very close using the older bioses, but my vdrop was cut in half or better on both ip35e's and my ip35 pro. my vdrop+vdroop on my ip35 pro is now comparable to what I had with my e6750


@ spammeh: go to the abitusa forums and check out the fixes for the newer bioses. I usually don't like to update my bios, but many of the fixes on the newer ip series bioses have been very useful and probably worth the hassle.

 

[Spammeh]

Ah I'll give it a shot i think - Thanks Bryan. I've seen a few posts about people breaking their ip35-e with flashing and it makes me a bit wary as things are working at the moment

ps.
I've updated to the 16 bios now and vdroop looks the same!

 

[Gillbot]

Originally posted by: bryanW1995

Originally posted by: KeaBorg

Originally posted by: Spammeh

Originally posted by: KeaBorg
My q66 was at 1.59v in bios which was 1.45loaded in windows or 1.49 unloaded I had the fsb up around 480ish but it was never stable til I dropped it below the 450 mark. I'm his brother btw

1.59vcore - I guess that was done with water?

False, it was done using a TRUE and you can't go by 1.59 in the bios, as it was only 1.48 in windows and 1.45 loaded, but after a few weeks of having it at 1.45 loaded the droop would droop it to 1.40 which was not stable. I popped my 8400 in and the problems gone, think what you will but these boards SUCK for oc'ing quads. They can OC quads but they will not remain stable, they weren't meant to be abused as I've done. Before I had the q66 I had a e6550 doing 3.5ghz at 500fsb ALL day every day for a year +, but as soon as I had my quad in there 2-3 weeks later, I had to keep bumping the voltage to keep it stable in windows, hence the 1.59 bios 1.47 windows and 1.45 loaded.

that's because you were using an older bios. vdrop is a huge problem with my ip35 pro as well...at least it was until I updated to bios 16. bios 16 or greater on any of the ip35 series seems to be the key for controlling vdrop. btw, some quick definitions:

vdrop: difference between vcore in bios and vcore at idle
vdroop: difference between vcore at idle and vcore at load

iirc my vdroop was actually the same or at least very close using the older bioses, but my vdrop was cut in half or better on both ip35e's and my ip35 pro. my vdrop+vdroop on my ip35 pro is now comparable to what I had with my e6750


@ spammeh: go to the abitusa forums and check out the fixes for the newer bioses. I usually don't like to update my bios, but many of the fixes on the newer ip series bioses have been very useful and probably worth the hassle.

He tried every bios under the sun, no help. The board is just dying.

 

[nyker96]

Originally posted by: Spammeh
Ah I'll give it a shot i think - Thanks Bryan. I've seen a few posts about people breaking their ip35-e with flashing and it makes me a bit wary as things are working at the moment

ps.
I've updated to the 16 bios now and vdroop looks the same!

I have 2x 35e, just flash using the windows util and set the chip to default speed before flashing though. I've done about 4 flashes with this method between the two boards, worked fine.

 

[KeaBorg]

Originally posted by: nyker96

Originally posted by: Spammeh
Ah I'll give it a shot i think - Thanks Bryan. I've seen a few posts about people breaking their ip35-e with flashing and it makes me a bit wary as things are working at the moment

ps.
I've updated to the 16 bios now and vdroop looks the same!

I have 2x 35e, just flash using the windows util and set the chip to default speed before flashing though. I've done about 4 flashes with this method between the two boards, worked fine.

There are so many dead and rma'd boards due to the Windows Flash Util crashing, read the abit tech support forums. I've used EVERY Bios from 14 through 18 and EVERY beta, the droop is still there so NO it's not a bios problem, my friend currently has my old quad and his board is starting to do the same thing as well.

 

[VirtualLarry]

Yeah, the IP35e sucks for quads. Dont use the windows flasher either, its buggy.

 

[VirtualLarry]

Yeah, the IP35e sucks for quads. Dont use the windows flasher either, its buggy.

 

[Tweakin]

I could never get my Q6600 stable with 8GB at anything above 3.0Ghz. This was a nice running system, but compared to my 6750@3.6GHz it seemed slow.

 

[KIAman]

My old IP35-E with Q6600 ran 450FSB 24/7 with 8GB of ram.

My trick to quads was to mess with VTT settings, mine was not stable until I had that setting 2 notches higher than default.

I did attempt 7x500FSB but at the time, my ram (rated ddr2-800) did not keep up.

 

[Tempered81]

440-460mhz

 

[aigomorla]

oh dont get me started on the IP35 series.

I HATE IT.

The board is absolute POS. Sorry if you own one.

But as you can see i did too, and it SUCKED hardcore compared to any other board i have touched.

Oh the ASUS P5QL-E comes very close tho, but its a lot more stable.

http://i125.photobucket.com/al...aigomorla/IMG_0862.jpg

Never buying another Abit or Same OEM maker board anymore. :\
Gill MSI falls in that catigory too. :X

 

[Ratman6161]

Originally posted by: VirtualLarry
Yeah, the IP35e sucks for quads. Dont use the windows flasher either, its buggy.

There again, if you are going for high overclocks at high voltages, perhaps it does suck. But I happen to like mine. Its working well for me and I paid less than $60 for it.