**Official ABIT IP-35 Pro Review/Overclock/Guide Thread**

[18 is # 1]

If you want to sell 2 of the good ones let me know. I'm lookin' at G.Skill, Geil, Muskin, and supertalent....decisions,decisions.

Go to tankguys.com
I spent $42 plus shipping.

[Halvie]

Sorry if this has been covered already....I read through about 100 pages and didn't see anything so...

Ok just got a e8400 and IP35pro tonight and was having the weird temp probs many were having with the bios 14. Flashed to 16 and now CPUZ is showing half clock speed and the same vcore that it was showing under the old bios (i bumped it by .2).

Is bios 16 more stable for wolfdales than 14? Any bios setting suggestions. I am having trouble getting it stable above 3.5. Should I leave the options in "CPU Feature" alone or turn them off?

Thanks for any help you can give.

[lyl]

Sorry if this has been covered already....I read through about 100 pages and didn't see anything so...

Ok just got a e8400 and IP35pro tonight and was having the weird temp probs many were having with the bios 14. Flashed to 16 and now CPUZ is showing half clock speed and the same vcore that it was showing under the old bios (i bumped it by .2).

Is bios 16 more stable for wolfdales than 14? Any bios setting suggestions. I am having trouble getting it stable above 3.5. Should I leave the options in "CPU Feature" alone or turn them off?

Thanks for any help you can give.

i am also wondering what rev is the best for the wolfdales atm. thanks

[18 is # 1]

i am also wondering what rev is the best for the wolfdales atm. thanks

16 final was made for Wolfdales.

Careful with 17b4, some reported problems...check on abit forums:

http://forum.uabit.com/showthread.php?t=124502&page=145

[NapalmV5]

16 final was made for Wolfdales.

Careful with 17b4, some reported problems...check on abit forums:

http://forum.uabit.com/showthread.php?t=124502&page=145

well 16 final is the worst bios for my 2 x e8400

17b4 here with no issues, actually has better memory scores in Everest too.
500x8 on my E3110 @ 1.32 vcore 24/7

gotta give the 17b4 a try then..

[OC4/3]

Sorry if this has been covered already....I read through about 100 pages and didn't see anything so...

Ok just got a e8400 and IP35pro tonight and was having the weird temp probs many were having with the bios 14. Flashed to 16 and now CPUZ is showing half clock speed and the same vcore that it was showing under the old bios (i bumped it by .2).

Is bios 16 more stable for wolfdales than 14? Any bios setting suggestions. I am having trouble getting it stable above 3.5. Should I leave the options in "CPU Feature" alone or turn them off?

Thanks for any help you can give.

16 final is a must for wolfdale14 have a huge vdroop,something like .2v

[MikeB12]

14 have a huge vdroop,something like .2v

I've heard people complain about vdroop on some IP35pro's, but mine's .04v with 14..

also I have 2 GA-P35-DS3L's running Q6600's and they have different vdroops using the same bios. one is .06 and one is .09

so I don't know how much a bios ver really has to do with vdroop, I think it's more the board itself.. just like different chips in the same stepping oc different, different boards in the same rev with the same bios have different vdroops.

otherwise it would be more uniform across boards in the same model and mfr date..

[OC4/3]

I've heard people complain about vdroop on some IP35pro's, but mine's .04v with 14..

also I have 2 GA-P35-DS3L's running Q6600's and they have different vdroops using the same bios. one is .06 and one is .09

so I don't know how much a bios ver really has to do with vdroop, I think it's more the board itself.. just like different chips in the same stepping oc different, different boards in the same rev with the same bios have different vdroops.

otherwise it would be more uniform across boards in the same model and mfr date..

That huge droop only occur on E3110(Wolfdale) and IP35 Pro bios 14Something like .15v-.2v,after flash to 16 final,it is much more normal But i am using a bad E8400 now

[Ace-a-Rue]

That huge droop only occur on E3110(Wolfdale) and IP35 Pro bios 14Something like .15v-.2v,after flash to 16 final,it is much more normal But i am using a bad E8400 now

if you are using the difference from what is set in the bios and what is readout as actual voltage, that is a big mistake...vdroop is the difference between actual voltage at idle and the actual voltage at load in windows....forget what the indicated bios voltage setting is set to.

[MikeB12]

if you are using the difference from what is set in the bios and what is readout as actual voltage, that is a big mistake...vdroop is the difference between actual voltage at idle and the actual voltage at load in windows....forget what the indicated bios voltage setting is set to.

I always thought...

Vdrop = difference between bios vcore and windows idle vcore.
Vdroop = difference beteen bios vcore and windows load vcore.


at least that's what most users complain about on the internet when reporting vdroop and vdrop. but vdroop is usually what's discussed most because it's what effects stability testing under 100% load. maybe it's just a big misconception, dunno.. but a lot of people think this when reporting vdroop. so many of the posts your read are defined this way... even if it is wrong..

[Evilsizer]

That huge droop only occur on E3110(Wolfdale) and IP35 Pro bios 14Something like .15v-.2v,after flash to 16 final,it is much more normal But i am using a bad E8400 now

well on Bios 16 with E7200, idle v = 1.3,load = 1.27... was smaller with 65nm but 45nm is pulling more current. the 4phase pwm is prolly being stressed a bit more then before.

Did abit ip35pro support celeron d347? If yes, with which bios?

with any of them... since its older then core 2 and is a netburst based cpu. you will want to stick with bios 14 though for that one, imo.

[Yelf]

Any suggestions on the following settings? (Enable, disable, default) Maybe even what they do.
Bios 16
E8400 CPU

Thermal Control
Limit CPUID MaxVal
C1E Function
Execute Disable Bit
Virtualization Technology
EIST Function


Thanks!