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

[Yelf]

I've about had it with Vista and am considering going back to XP. Vista mail support sucks, read SLOW (Outlook 2003, Live Mail, and Windows Mail). I need Hotmail support and Outlook Express so far is the winner. I've heard conflicting stories about hotmail support being phased out at the end of June for anything but Live Mail, it would suck to go back to XP only to have MS yank OE hotmail support. Any guidance one way or another?

OK back to my system: IP35 Pro, E8400, CORSAIR XMS2 DHX 4GB @ 4-4-4-12 2.2v Bios 16
Not much in this thread on 45nm CPU OC's, any suggestions on a starting point? Need to find some info on the gtl settings, think mine are at default 67% right now.

Thanks guys

[Ace-a-Rue]

OK back to my system: IP35 Pro, E8400, CORSAIR XMS2 DHX 4GB @ 4-4-4-12 2.2v Bios 18

where did you get bios 18 for this board?

[Yelf]

Sorry about that, I am using 16.

[theELVISCERATOR]

I've about had it with Vista and am considering going back to XP. Vista mail support sucks, read SLOW (Outlook 2003, Live Mail, and Windows Mail). I need Hotmail support and Outlook Express so far is the winner. I've heard conflicting stories about hotmail support being phased out at the end of June for anything but Live Mail, it would suck to go back to XP only to have MS yank OE hotmail support. Any guidance one way or another?

OK back to my system: IP35 Pro, E8400, CORSAIR XMS2 DHX 4GB @ 4-4-4-12 2.2v Bios 16
Not much in this thread on 45nm CPU OC's, any suggestions on a starting point? Need to find some info on the gtl settings, think mine are at default 67% right now.

Thanks guys

so are mine at sigged speed.

[Pntgrd]

Help! I have been running for months with the system in my sig. Other than 3 rma bouts with my Ballistix all has been well. Tuesday night I started having trouble getting out of sleep mode, took a hard reboot. Last night it wouldn't come back at all but it was late so I didn't check what could be the cause, just figured it was the Ballistix again. I was so sure I even ordered up some Gskill this AM from the Egg. Whan I got home tonight I started looking for the offending stick. Last night when I tried I noticed that the bios had been reset. On trying to boot tonight I reset the bios but it would hang on the reboot. It did this with all 4 sticks one at a time. The error code at the hang is E4. I finally found that the code is for bios corruption (I think). So I pulled tha battery and rset the thing for 30 minutes and it still hung at E4. I went back to bios and changed the vdimm from Auto to 2.2v and for whatever reason it finally booted up. I put in another stick of ram and that booted fine as well. It is late and I am going to stop for the night. I will try adding the other 2 sticks and redoing my o/c tomorrow. What caused this episode and what the he** is an E4 code anyway? I really don't want to deal with this again.

[Ace-a-Rue]

Help! I have been running for months with the system in my sig. Other than 3 rma bouts with my Ballistix all has been well. Tuesday night I started having trouble getting out of sleep mode, took a hard reboot. Last night it wouldn't come back at all but it was late so I didn't check what could be the cause, just figured it was the Ballistix again. I was so sure I even ordered up some Gskill this AM from the Egg. Whan I got home tonight I started looking for the offending stick. Last night when I tried I noticed that the bios had been reset. On trying to boot tonight I reset the bios but it would hang on the reboot. It did this with all 4 sticks one at a time. The error code at the hang is E4. I finally found that the code is for bios corruption (I think). So I pulled tha battery and rset the thing for 30 minutes and it still hung at E4. I went back to bios and changed the vdimm from Auto to 2.2v and for whatever reason it finally booted up. I put in another stick of ram and that booted fine as well. It is late and I am going to stop for the night. I will try adding the other 2 sticks and redoing my o/c tomorrow. What caused this episode and what the he** is an E4 code anyway? I really don't want to deal with this again.

there is a 4E in the manual...suggest you read that one...it might be saying your vcore is insufficient.

for whatever reason, your memory is requiring higher than normal Vdimm...feed it what it wants!

[Pntgrd]

there is a 4E in the manual...suggest you read that one...it might be saying your vcore is insufficient.

for whatever reason, your memory is requiring higher than normal Vdimm...feed it what it wants!

Thanks Ace. I couldn't find the manual last night, I really need to straighten up a bit. I wonder why after almost a year it all at once wants more juice? It has been solid at 3.6 with 1.4325v in bios all that time. This is puzzling

[edit]
I have had a thought. System is back to running 3.6 and seems to be running like it should. I have an idea what may have happened. I was working with a wireless gaming adapter on the Tuesday when I started having the problems. I needed to plug in an additional network cable to the second nic and was leaning over the top of the case reaching over the back to plug it in. I had hit the k/b PS2 cable and was trying to plug it back in, kinda feeling around for the hole. Could I have hit the BIOS reset switch an moved it just a bit. Could that have caused a BIOS corruption, which seems to be what I had?