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

I have had this board for a couple of months now, but recently I have tried overclocking the rig but have been having trouble getting it prime stable. Before I installed the board I did the PWM bolt mod and the PWM says around 60-70C under load. I have flashed to bios 14 and I have played with my memory and it is good till 1135Mhz before it starts to have error in Memtest86. Anyways I have been having trouble getting my Q6600 stable at 3.6GHZ. I can get prime95 small FFT's stable at 1.52v, but I can't get the large stable even at 1.54v. Here is my settings:

FSB: 400
Divider: 1:1 (Mem 4-4-4-12)
vcore: 1.54v
cpu vtt: 1.35V
mch: 1.42v
ICHIO: 1.60v

Thanks

suggest you loosen up the memory timings to 5-5-5-18-42 and then, jack your vcore up some more....mch and ichio need to be increased also.

Hello friends,

I had bought this mainboard (IP 35 Pro) about two months ago, but I did install it just this morning. I even didn't turn the board on to watch the temps of PWM and CPU, I went straight with ace's bolt mod! and just for a check with my success or failure please tell me what you think about this temps at idle?! please note that I used a simple white thermal paste on regulators beside the cpu.

Core2 e6320 @ 400*8 = 2800 @ 1.38v stock cooler
G.Skill DDR2 800 cl4 @ DDR1000 4-4-3-5 @ 2.3v
4x12cm fan 2 intake 2 outtake

the result :
@ idle :
cpu = 34 C
system = 32 C
PWM = 40 C

@ load after 30 min of orthus 2006
cpu max @ 56
system max @ 38
pwm max @ 52

So am I going with right temps?

and the must important thing! I cant boot to windows over FSB 420!!! is it a limitation with e6320 ?

Thanks!

Ace-a-Rue I have tried running CAS 5 at 800MHZ, and increased the voltage which didn't help. 1.55V for 3.6Ghz seems a little high compared to what everyone using for there G0. Maybe my G0 stepping A721 isn't as good.

Thanks

Hey, I am having trouble flashing my motherboard
I boot into dos and run the runme.bat but I get an insufficient memory message

Any advice?

Hope fully a new bios will let me up the FSB, its maxing out at 465, capping my cpu overclock at 3720. I underclocked memory and cpu multiplier and it is definately the FSB crashing the system :(

on the topic of bios flashing, what is the most stable flashing method besides the floppy, I threw all of mine out :(

I just put together a new rig for my dad with this mobo and I'm having problems with uGuru. I installed it, restarted (like it asked) and soon as it loads it gets the "abit uGuru Application has encounted a problem and needs to close..." I used the latest uGuru from Abit's website and I can't figure out the problem. :shrug:

Quote:

---

Originally Posted by vafan13

I just put together a new rig for my dad with this mobo and I'm having problems with uGuru. I installed it, restarted (like it asked) and soon as it loads it gets the "abit uGuru Application has encounted a problem and needs to close..." I used the latest uGuru from Abit's website and I can't figure out the problem. :shrug:

---

are you using vista 32 or 64?

Quote:

---

Originally Posted by need bb

Ace-a-Rue I have tried running CAS 5 at 800MHZ, and increased the voltage which didn't help. 1.55V for 3.6Ghz seems a little high compared to what everyone using for there G0. Maybe my G0 stepping A721 isn't as good.

Thanks

---

the luck of the draw with processors....are you trying 1:1 with the FSB to memory ratio?

Quote:

---

Originally Posted by SaII

on the topic of bios flashing, what is the most stable flashing method besides the floppy, I threw all of mine out :(

---

USB...use my guide to get you there.

Quote:

---

Originally Posted by sean_php

Hello friends,

I had bought this mainboard (IP 35 Pro) about two months ago, but I did install it just this morning. I even didn't turn the board on to watch the temps of PWM and CPU, I went straight with ace's bolt mod! and just for a check with my success or failure please tell me what you think about this temps at idle?! please note that I used a simple white thermal paste on regulators beside the cpu.

Core2 e6320 @ 400*8 = 2800 @ 1.38v stock cooler
G.Skill DDR2 800 cl4 @ DDR1000 4-4-3-5 @ 2.3v
4x12cm fan 2 intake 2 outtake

the result :
@ idle :
cpu = 34 C
system = 32 C
PWM = 40 C

@ load after 30 min of orthus 2006
cpu max @ 56
system max @ 38
pwm max @ 52

So am I going with right temps?

and the must important thing! I cant boot to windows over FSB 420!!! is it a limitation with e6320 ?

Thanks!

---

temps look good.

FSB can be affected by memory timings and FSB to memory ratio...when trying to overclock to the maximum always use 1:1 FSB to memory ratio and loose memory timings...once you have reached the max FSB then you can start tightening up the memory timings and adjust the FSB to memory ratio.

Quote:

---

Originally Posted by vafan13

I just put together a new rig for my dad with this mobo and I'm having problems with uGuru. I installed it, restarted (like it asked) and soon as it loads it gets the "abit uGuru Application has encounted a problem and needs to close..." I used the latest uGuru from Abit's website and I can't figure out the problem. :shrug:

---

Thats because the version on your cd is newer than whats on the web site.:shrug:
Uninstall it and use your cd version.

man, i have had this board for almost 2 months now and i cant get it working.....i just finally for sure decided the mobo is bad. Ive been through a LOT of troubleshooting on the Abit forums and nothing seems to help....way too much to type about what i have posted there if you are interested heres the thread link http://forum.abit-usa.com/showthread.php?t=127754
Ill try to sum it up...originally i was having problems during xp setup and i was getting the bsod. So, naturally memtest was the first thing i tried...i had like 2000 errors within 20 min in memtest using 1 or 2 sticks in diff dimms. Someone suggested that my raptors might be the problem in raid 0 which didnt make any sense to me but i figured i might as well try it. Sure enough, i unplugged the raptors ran memtest for 2 hours and had 0 errors. So i was like ***.....plugged one raptor back in installed xp on one drive and had it up and running for about a day. Went on vacation for a week, came home fired up my pc only to be greeted by the C1 memory error on the lcd post and my gpu fan running at 100%. Nothing worked, cleared cmos everything and still C1.....tried 1 stick 2 sticks different dimms all that still no luck. I figured the RAM died somehow while i was gone so i RMAd it back to crucial. Got the new sticks from them monday and was excited to throw them in and use this rig thats been sitting here for a month. Fired it up, nothing but the C1 and gpu fan @ 100%. Tried the sticks in all diff combos again and nothing. At this point im like seriously *** is going on....went to circuit city and bought a stick of PNY ddr2 rated for 1.8v since i know that the ballistix take 2.2 to run to make sure the ram not getting enough juice wasnt the problem. Got home last night put it in only to once again be greeted by the C1 error. I really have no idea what to even try at this point, im setting up the RMA on abit's website as we speak because i am out of ideas I'm hoping someone here might have something else i can try before i give up and drain my loop, unmount my blocks, RMA my mobo etc. because i REALLY dont want to do all that lol....thanks for taking the time to read this guys, i appreciate it

Hmm my sig didnt post with my msg...weird here it is
Modded Antec 900 (cable management being revised atm) http://s73.photobucket.com/albums/i230/myerz635/
PC P&C Silencer 750
Q6600 G0 soon to be OCed
Abit IP35 Pro
2 GB Crucial Ballistix DDR2 667 (AA663)
8800 GTS 640 @ 700/1050
2x74 GB Raptors in RAID 0
X-Fi XtremeGamer

Water Setup
D-Tek Fuzion Cpu Block
Swiftech MCW30 Northbridge
Swiftech MCR320 Radiator
Swiftech MCP655 Pump

have you unhooked the the raptor drives again to see if you can get the C1 post error code?

clearing CMOS won't do it when you have problems like you are having...clear cmos AND pop the battery out for about 5 minutes...make sure the power plug is also unplugged.

are you even getting a post screen?...if not, try a different VC...PCI or PCIe

yea i just unhooked them again, no dice.....i cleared the cmos and took the battery out for 30 min yesterday with no luck....unfortunately all i have are AGP vid cards laying around

UPDATE : Wow, i feel like an idiot after all this time.....took out my video card and booted it without one and it got right past the C1 and went to 7F. My video card had some sort of weird :banana::banana::banana::banana: on the middle of the pci-e connector so i cleaned it off put it back in and got to 7F. I dont have it hooked up to anything i was just trying out diff ideas and reading the lcd post to see if i could get past the C1. Thanks for the help man, honestly after building PC's for 4 years i seriously cannot believe i didnt check the vid card earlier :( It worked perfectly fine in my last rig so i didnt think anything of it! Oh well, thats what forums like these are for :)

does your VC require an aux power?...also...there is an additional power molex plug adjacent to the 2nd PCIe slot...plug power into that female molex.

refer to page 1-6 in your manual.

well, i got it booted up into xp setup. Now i am having the original problem i had on day 1....BSOD when RAID on the onchip sata device is enabled. If i go back to bios and set the onchip sata to ide setup works fine. When i get the BSOD its right before xp setup reaches the part where it detects your hard drives and lets you create your partitions :confused:


Update: XP setup refuses to work and bsod every time in raid. I have 2 copies and both do the same thing even with slipstreamed raid drivers. So i decided to try vista ultimate 64-bit and it worked on the first try....its currently installing right now so we will see how it works out. *crosses fingers*

The BSOD is caused by incorrect drivers. You can include AHCI/RAID drivers by hitting F6 when the XP setup starts. Make sure you have the RAID/AHCI drivers on a floppy and VIOLA, it will detect the drives, install the drivers AND best of all NO BSOD.

IMO you should always install the RAID drivers even if you dont use them. This way when you DO decide to use it, when you capture your image, you wont have to rebuild the whole image from scratch. :up:

I've had my ABIT35 Pro running for 3 weeks with no problems. Last night I powered it down normally. This morning I get a Post Code 25. I have a PCI Express Video card. It is 3 weeks old also. What should I check first? Code 25 is early PCI Initialization - memory assign and also check for valid vga device. Should I buy a cheap PCI express (or just PCI?) video card and try that? (unfortunately my spares are AGP). Or, should I swap out the memory first? The memory is also 3 weeks old. Thanks for any help.

could someone explain to me what does cpu vtt and cpu glref mean, and do they make or break an overclock?

vista installed no problem with no bsod....xp however would refuse to install regardless of slipstreaming drivers or hitting F6 and loading them from floppy. Very strange....oh well ive always wanted to try vista anyway. No other problems so far, time to start OCing :D

just a quick question.....have you guys been using uguru to OC or have you been doing it the old fashioned way in bios? just wondering because hitting f10 to save and exit bios shuts my computer off completely for about 2-3 seconds and turns it back on instead of just restarting.....dunno if this is normal for this mobo but its annoying. Ive always used OCCT for stress testing, anybody have any other suggestions besides orthos or prime?

Why do it in the BIOS if you dont have to? :yepp:

Quote:

---

Originally Posted by chawks2

Why do it in the BIOS if you dont have to? :yepp:

---

haha very true....i was just wondering if it was as stable/reliable as doing it in the bios itself :cool:

Quote:

---

Originally Posted by myerz635

just a quick question.....have you guys been using uguru to OC or have you been doing it the old fashioned way in bios? just wondering because hitting f10 to save and exit bios shuts my computer off completely for about 2-3 seconds and turns it back on instead of just restarting.....dunno if this is normal for this mobo but its annoying. Ive always used OCCT for stress testing, anybody have any other suggestions besides orthos or prime?

---

the only reason to go into the bios other than very minor superficial tweaks is to change the memory strap...that cannot be done from windows or through Uguru.;)