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

[kadozer]

seriously i tried 1.41 and then it posted in bios i backed timing from 4,4,4,12 to 5,5,5,14 it would act like was gonna start loading windows then blank screen so i cranked cpu vcore up to 1.4 this with fsb at 475 and it just kept resetting actualy went into windows in safe mode it bsod upon reboot so went back to my old settings fsb 438 and its fine so my question is what other voltages need to be changed for cpu besides vcore?? or maybe this e6750 just hit a wall . thanks

Try Ichio 1.60 CPU VTT: 1.23 (be careful with this setting can be a board killer) Play around with GTLREF to 63-64.
I have no idea what your system is but this is all assuming you have a high quality PSU and enough juice to power it.

[MADMAX22]

Well doing some playing with my 3110 and 2 gigs of ballistics and my pro version 1.0 I was trying to see how high a fsb I could get.

Well funny thing I can boot into memtest and run test 5 for 20min or more all the way up to 560fsb, however getting into windows is another story. 533 is about as high as I can get into windows and run any type of stability test.

I guess the SB is giving up the ghost. WHen I boot at 560fsb it says bootmanger is corrupt or missing. As soon as I lower fsb it will boot into windows no issue LOL.

[redrumy3]

I have a quick question

i usually run my Q6600 @ 3.6 using 450 x 8 1:1 which is DDR2-900

but i decided to try 400 x 9 4:5 which comes out to DDR2-1000

now which is better to run, i figured maybe 1:1 was better but im not sure :P

still trying to get my mobo to boot 500 x (X) 1:1 but i cant seem to get it =|

i know my ram can do DDR2-1000 cause well they are DDR2-1000 sticks

[Imitation]

Anyone else having issues with latest version of uguru while running the official 16 bios and a 45nm chip? When i go into uguru to change the fsb or something it shows the vcore at .3 volts with a max available setting of .6! WTF is that all about? My bios shows all the correct values but uguru is messed up, I'm afraid to use uguru if it applies .3 to my cpu or worse, some OTHER value that could toast something.

[resyn]

Anyone else having issues with latest version of uguru while running the official 16 bios and a 45nm chip? When i go into uguru to change the fsb or something it shows the vcore at .3 volts with a max available setting of .6! WTF is that all about? My bios shows all the correct values but uguru is messed up, I'm afraid to use uguru if it applies .3 to my cpu or worse, some OTHER value that could toast something.

I'm running the v16 official release, my uguru stuff works fine, i don't use it too much, but everything reads correctly. I haven't had any problems with this bios come to think of it, and it definitely helped out my vdrop considerably compared to the other bios version. Try reflashing, I've had some strange issues come up from perhaps a "bad flash", and they fixed themselves after reflashing..

[18 is # 1]

no i need new ram i found out this ram pretty much sucks after i bought it its the ddr2 6400 team xtreem dark ram 2x1 gig my mch is up from 1.25 to 1.29 allready unless you mean go higher then that

Run Memtest and make sure you don't have a bad stick.

[18 is # 1]

What is the highest vDIMM most RAM can take and still benefit? I recall reading back in the days of DDR that most chips used by manufacturers gain no overclockability by increasing the vDIMM over recommended specs. Is this still the case today?

Depends on the stick. The OCZ I have coming takes up to 2.4v ...I don't think I would put that much in most dimms...but I'm not Ace.

[Ace-a-Rue]

Anyone else having issues with latest version of uguru while running the official 16 bios and a 45nm chip? When i go into uguru to change the fsb or something it shows the vcore at .3 volts with a max available setting of .6! WTF is that all about? My bios shows all the correct values but uguru is messed up, I'm afraid to use uguru if it applies .3 to my cpu or worse, some OTHER value that could toast something.

you have a bios corruption feeding to Uguru...clear CMOS with battery out for about 5 minutes (unplug the power cord)...after resetting CMOS back to normal, go into the bios and load optimized defaults...now, SAVE...re-enter the bios reset your overclock settings..SAVE!

if this does not correct Uguru, then uninstall, reboot, and now re-install Uguru.

[Ace-a-Rue]

Depends on the stick. The OCZ I have coming takes up to 2.4v ...I don't think I would put that much in most dimms...but I'm not Ace.

neither am I

[JamesBong420]

Well doing some playing with my 3110 and 2 gigs of ballistics and my pro version 1.0 I was trying to see how high a fsb I could get.

Well funny thing I can boot into memtest and run test 5 for 20min or more all the way up to 560fsb, however getting into windows is another story. 533 is about as high as I can get into windows and run any type of stability test.

I guess the SB is giving up the ghost. WHen I boot at 560fsb it says bootmanger is corrupt or missing. As soon as I lower fsb it will boot into windows no issue LOL.

im in the exact same boat.. dfi p35 gets this chip to 590s FSB totally orthos stable... on the ip-35 pro i cant even stay stable at 512mhz.. i can boot into windows up to 545.. but it is not even close to stable..

[Imitation]

you have a bios corruption feeding to Uguru...clear CMOS with battery out for about 5 minutes (unplug the power cord)...after resetting CMOS back to normal, go into the bios and load optimized defaults...now, SAVE...re-enter the bios reset your overclock settings..SAVE!

if this does not correct Uguru, then uninstall, reboot, and now re-install Uguru.

Thanks Ace, I'll def try to get the battery removed this time when i clear it. I tried it via the back panel switch and it cleared my settings, but it must not really clear EVERYTHING out. We'll see.

[TheSMJ]

uGuru sees my vCore as -.775something, while all the rest of the voltages are correct. Frankly I'd rather just ignore it anyways given the fact that I dont plan to mess with this setting outside of the BIOS anyhow.

[DJConan]

I could use any suggestions with a problem that just occurred last night.

I removed a hard drive that I no longer needed installed. After removing the hard drive, my system stalls at post code 25. Last night, a few power cycles and a few times I got into BIOS, but that has been it. I've been trying to get it to work all day today and it will not go past post code 25 at all.

I stripped everything out. No cards installed except video. No drives connected. I've reset CMOS, pulled the power cord and yanked the battery. I've tried an old PCI video card, different RAM sticks and another PSU.

Connecting the old hard drive didn't do anything. I don't have a spare CPU or mobo around to swap those. Could it be the CPU or most likely the mobo? Anybody know what the warranty period is on these mobos?

Thanks.

[Ace-a-Rue]

uGuru sees my vCore as -.775something, while all the rest of the voltages are correct. Frankly I'd rather just ignore it anyways given the fact that I dont plan to mess with this setting outside of the BIOS anyhow.

what uguru version are you using?...3.107?

[Ace-a-Rue]

I could use any suggestions with a problem that just occurred last night.

I removed a hard drive that I no longer needed installed. After removing the hard drive, my system stalls at post code 25. Last night, a few power cycles and a few times I got into BIOS, but that has been it. I've been trying to get it to work all day today and it will not go past post code 25 at all.

I stripped everything out. No cards installed except video. No drives connected. I've reset CMOS, pulled the power cord and yanked the battery. I've tried an old PCI video card, different RAM sticks and another PSU.

Connecting the old hard drive didn't do anything. I don't have a spare CPU or mobo around to swap those. Could it be the CPU or most likely the mobo? Anybody know what the warranty period is on these mobos?

Thanks.

i had this problem one time when i initially got the board...i think my problem was a bad memory stick...what you need to do if you can get into the bios is set 2.1v for Vdimm and then save to see if that helps...just post/boot with one stick and try it in different slots, just to rule out a dimm slot problem...one of the descriptions for code '25' is, "assign memory & I/O resource."

[DJConan]

i had this problem one time when i initially got the board...i think my problem was a bad memory stick...what you need to do if you can get into the bios is set 2.1v for Vdimm and then save to see if that helps...just post/boot with one stick and try it in different slots, just to rule out a dimm slot problem...one of the descriptions for code '25' is, "assign memory & I/O resource."

Thanks for the suggestion. I just gave that a shot. It won't go past C1 with the stick in another slot. I tried 4 different sticks. When I did get into the BIOS last night, I did set the memory voltage back up thinking that was the problem, but that wasn't it. Of course now, the BIOS has been reset. I just removed the mobo from my case to verify that there are no shorts. I don't know anything else I can do.

Who'd a thunk pulling out a hard drive would create so much trouble?

I guess in order to RMA the board, I'm going to have to undo the "bolt mod?" I hope I have those plastic clips saved somewhere...

[TheSMJ]

what uguru version are you using?...3.107?

3.1.0.3. Where do I find the newer version?

I recall trying a newer version at one point, and crashed almost as soon as I tried to start it.

[Ace-a-Rue]

it is posted on the first page of this thread...but, here it is: ftp://ftp.abitshop.com/pub/utilities/uguru/3.107.zip

[Ace-a-Rue]

Thanks for the suggestion. I just gave that a shot. It won't go past C1 with the stick in another slot. I tried 4 different sticks. When I did get into the BIOS last night, I did set the memory voltage back up thinking that was the problem, but that wasn't it. Of course now, the BIOS has been reset. I just removed the mobo from my case to verify that there are no shorts. I don't know anything else I can do.

Who'd a thunk pulling out a hard drive would create so much trouble?

I guess in order to RMA the board, I'm going to have to undo the "bolt mod?" I hope I have those plastic clips saved somewhere...

before undoing anything...let the board sit over night with nothing plugged in, except for the cpu, and CMOS set to clear with the battery out...put in one memory stick, VC and that's it...start it up to see if it works...BTW...did you recently flash the BIOS?

[FlimFlam00]

So I need help.

I flashed to the beta 17, and it borked, and I got a new BIOS chip today which had 10 installed on it. 16 gave me problems on my old chips. When I went from 14 --> 16 my display adapters wouldn't show, as soon I as rebooted, and 2 of 3 monitors wouldn't work.

So when I got the new BIOS chip I retried 16, but got the same problem. Sometimes my sata drives won't show. Anyway, I reverted back to 14 on my board, and now when I boot, my display adapters won't show and my Nvidia drivers don't load.

Seems to be a direct correlation between these problems and the BIOS. I load the drivers in the admin account in Vista which I enabled, but it doesn't seem to work. It syas access is denied for the drivers and theat there are problems with my video cards in the device manager.

Sys specs:

e8400
ip-35 Pro
2 x (2 x 2gb) Corsair Dominatos 8500c5
8800 Utra
Netcell raid card
Soundblaster audigy
tj07
Corsair 650w psu
RaptorX
3 x 74gb Raptors
400gb hd
500gb hd
250gb hd
200gb hd

Ubuntu loads just fine...

Edit: fresh install of Vista x64

Edit 2: Great, now it doesn't pick up the onboard sata chip (doesn't see drives), and cannot enable usb in the bios, so I cannot flash. This sucks. 4th ip-35 Pro board total.

[DJConan]

before undoing anything...let the board sit over night with nothing plugged in, except for the cpu, and CMOS set to clear with the battery out...put in one memory stick, VC and that's it...start it up to see if it works...BTW...did you recently flash the BIOS?

No, haven't done a flash since I first received the board back in December. I just removed a hard drive that I didn't need and that's it. I had to remove the video card to get the hard drive out. I applied for an RMA already (need my system for work), but I'll try what you suggested and see if anything happens tomorrow. Thanks again.

[FlimFlam00]

So the BIOS doesn't pick up my sata drives, or usb. Initially it will pick up the keyboard, but it drops during the post.

I disconnected all my sata drives and left only a botable usb in, which it picks up. I get t the command prompt my have no keyboard action from usb or ps/2 so I cannot flash.

Also, it picks up my e8400 at 2.04 GHz even though thermal management options are not showing in BIOS, which is the least of my worries, but most options in the bios do not have an "enabled" options showing.

So weird, and I loved this board but I am about to snap both my dead ip-35s in half at this point.

Edit: found a native ps/2, and with all sata drives disconnected, I was able to work at the command line, and flash the BIOS back to 16. Great success!

[resyn]

So the BIOS doesn't pick up my sata drives, or usb. Initially it will pick up the keyboard, but it drops during the post.

Edit: found a native ps/2, and with all sata drives disconnected, I was able to work at the command line, and flash the BIOS back to 16. Great success!

Phew, good to hear.. As I was reading your post up above, I was going to recommend a ps2 keyboard, but I see you've got it..great!
I had the same issue, i had a bios flash go bad, would only let me boot up on floppy, however my normal USB keyboard wouldn't work.. luckily i had a ps2 laying around...

[Ace-a-Rue]

always recommended to have an USB to P/S2 adapter laying around as backup.

[Ace-a-Rue]

So the BIOS doesn't pick up my sata drives, or usb. Initially it will pick up the keyboard, but it drops during the post.

I disconnected all my sata drives and left only a botable usb in, which it picks up. I get t the command prompt my have no keyboard action from usb or ps/2 so I cannot flash.

Also, it picks up my e8400 at 2.04 GHz even though thermal management options are not showing in BIOS, which is the least of my worries, but most options in the bios do not have an "enabled" options showing.

So weird, and I loved this board but I am about to snap both my dead ip-35s in half at this point.

Edit: found a native ps/2, and with all sata drives disconnected, I was able to work at the command line, and flash the BIOS back to 16. Great success!

looking at your specs in your above post i see a mulitude of hard drives attached...i've heard a few instances of people having trouble with the Raptor drives geting recognized...might want to try swapping out sata cables to see if the helps.

you do know that there is an "OS" or "BIOS" option setting for the USB mouse and keyboard...i would put those two into the "BIOS" mode 24/7