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

[Avathar77]

Hi guys I need a bit of a info!
I have an Abit IP35 Pro V1.1 (Bios V18ZZZ) with bolt mod running with a Q6600(1.325VID) and 4GB of OCZ reaper PC2 8500 Ram.
Just ordered an OCZ Agility 3 60GB SSD, should be with me on Tuesday. But reading some posts I am wondering if I need the V19 Bios update posted in OCZ Forums?

[glen]

Hi guys I need a bit of a info!
I have an Abit IP35 Pro V1.1 (Bios V18ZZZ) with bolt mod running with a Q6600(1.325VID) and 4GB of OCZ reaper PC2 8500 Ram.
Just ordered an OCZ Agility 3 60GB SSD, should be with me on Tuesday. But reading some posts I am wondering if I need the V19 Bios update posted in OCZ Forums?

The v19 bios in the ocz forums is actually v17 with the latest sb drivers (its a typo), the 18zzz is the latest and will be a better choice , make sure you use achi and the lnewest intel rst drivers.

[Ligushka]

I'm not sure what exactly the "V19" BIOS on that forum is, never examined it. I don't really care, either.

This BIOS has all the latest option ROMs at the date of this posting, and will be sufficient for your needs. See the first post on this page for all the latest drivers.

And Realtek HD Audio R2.61 has been released. See the first post for valid links.

[Avathar77]

Thank you very much for the quick response! I have already updated the drivers it is just the bios I was not sure about. With the recent talk about the cold boot issues with OCZ SSD's I was(am) a bit worried. I will stick with 18ZZZ bios.

[Ligushka]

Unfortunately the versioning of BIOSes now is confusing. Where did you get your 18ZZZ BIOS from? Are you certain that it has newer option ROMs than the "original" 18ZZZ offering from the Lejabeach site?

[Avathar77]

i downloaded it from http://www.lejabeach.com/ABIT/IP35Pro/

Direct link is http://www.lejabeach.com/ABIT/IP35Pr...ro%2018ZZZ.rar

Is this not the correct bios version?

[Ligushka]

It is correct, and is sufficiently new to use with your SSD without issue, but I have a newer one with newer Phoenix AHCI, JMicron, and Realtek PXE ROMs. I would suggest updating.

[Avathar77]

Oh Ok I Have downloaded that using your link but didn't update as both bios has the same name(18ZZZ) but your one is "b18-0117.ZZZ" and dated 17/01/2011, the one I have flashed is Called "07-05-10.ZZZ" and dated 05/07/2010 thats the one from lejabeach web site.

So I will flash it in the morning and will update. Thanx for the help. Must sleep now it is close to 5am and I have to wake up again in less than 4 hours

[NightshadowUK]

The v19 bios in the ocz forums is actually v17 with the latest sb drivers (its a typo), the 18zzz is the latest and will be a better choice , make sure you use achi and the lnewest intel rst drivers.

Don't v17 and 18 prevent you from entering the BIOS with a USB keyboard once AHCI is enabled?

[Ligushka]

Don't v17 and 18 prevent you from entering the BIOS with a USB keyboard once AHCI is enabled?

I believe so, yes. I can't fix that.

[Avathar77]

So I updated the bios, and got my SSD(OCZ Agility 3 60GB) it is blazing fast even in SATAII but I have the cold boot issue as well any advice?

[Ligushka]

Which cold boot issue?

[Avathar77]

Which cold boot issue?

When I start the PC after a complete shutdown(off from mains as well) it doesnt recognise the SSD in bootup and in bios. Have to do a hard reset via the reset button(some times several times) for the PC to "see" the SSD.

[Ligushka]

When I start the PC after a complete shutdown(off from mains as well) it doesnt recognise the SSD in bootup and in bios. Have to do a hard reset via the reset button(some times several times) for the PC to "see" the SSD.

Weird. I'd verify SATA data/power cable connections and check if there's a firmware update for your SSD.

[Avathar77]

Weird. I'd verify SATA data/power cable connections and check if there's a firmware update for your SSD.

Have tried it in all 6 SATAII ports and SSD came with 2.06 thats the latest.
Is there a way to know which version of RAID/AHCI driver is in the the bios you have listed?

[Ligushka]

If you carefully watch the ROM screens at bootup you should be able to tell which version you have.

[Ligushka]

JMicron JMB363 Storage Controller driver R1.17.63 WHQL is out. Download

[Ligushka]

Yay, JMicron released an update to their JMB363 option ROM, version 1.07.28. Release notes have not been updated, so I have no clue what's changed yet. I'll have a lot of fun updating 13 BIOS versions soon...

And Realtek HD Audio driver R2.62 was released a few days ago, see links at the top of this page.

[zalophus]

IP35 Pro BIOS 17- Problem started with random blue screens, when system idle. Now, upon latest reboot splash screen froze for over two minutes. Tried resetting CMOS, and then unplugging power cord for hour. Splash screen still freezing. Finally just left the splash screen, and finally (4+ minutes) screen changed and gave me a "cmos check sum error-Defaults loaded". Was then able to finish boot, but before I try restart, thought I'd check with the experts for advice.

[Ligushka]

Replace your CMOS battery, to begin with.

[zalophus]

Replace your CMOS battery, to begin with.

Thanks-That seems to have solved the CMOS Check Sum Problem, but could the battery also be cause of Blue Screens? Time will tell, I guess.

Thanks again for prompt response.

[Ligushka]

Glad I could help. If you could zip up the contents of the %systemroot%\Minidump folder and upload it somewhere, I can analyze the crash dumps to hopefully figure out the cause of your blue screens.

[zalophus]

Glad I could help. If you could zip up the contents of the %systemroot%\Minidump folder and upload it somewhere, I can analyze the crash dumps to hopefully figure out the cause of your blue screens.

I think I figured out the attachment method. Hope this helps.Minidump.zip

[Ligushka]

The causes given for your BSODs (oldest to newest):

Rtlh64.sys
AvastSvc.exe (VISTA_DRIVER_FAULT)
explorer.exe (VISTA_DRIVER_FAULT)
AvastSvc.exe (VISTA_DRIVER_FAULT) - Pool_Corruption
svchost.exe (VISTA_DRIVER_FAULT - fileinfo.sys
System (VISTA_DRIVER_FAULT) - NuidFltr.sys
System (VISTA_DRIVER_FAULT) - Pool_Corruption
System (VISTA_DRIVER_FAULT) - HIDCLASS.SYS

I suggest installing the latest Realtek Ethernet driver (download Vista and WinServer 2008 Auto Installation Program (SID:1457676) [assuming you're still running Vista here], and do a Repair install if prompted) to potentially solve that first Realtek sys BSOD, but the rest seem to indicate some hardware issue. I see you are overclocking; verify your temperatures at idle and load, as well as power supply voltages (best to check with a multimeter). Run IntelBurnTest, then if that passes, memtest86+ for an extended period of time (24 hours or more) to rule out CPU/RAM issues. If any errors result, go back to stock speeds and test again. If no issues, then your overclock has an issue somewhere.

[zalophus]

The causes given for your BSODs (oldest to newest):

I suggest installing the latest Realtek Ethernet driver (download Vista and WinServer 2008 Auto Installation Program (SID:1457676) [assuming you're still running Vista here], and do a Repair install if prompted) to potentially solve that first Realtek sys BSOD, but the rest seem to indicate some hardware issue. I see you are overclocking; verify your temperatures at idle and load, as well as power supply voltages (best to check with a multimeter). Run IntelBurnTest, then if that passes, memtest86+ for an extended period of time (24 hours or more) to rule out CPU/RAM issues. If any errors result, go back to stock speeds and test again. If no issues, then your overclock has an issue somewhere.

Thanks Ligushka-Did the Realtek update.
When Blue Screens started, I stopped the overclocking and have everything set defaults, with no effect on the occurrences of Blue Screens. I run Real Temp and all my temps have stayed in the 35F range, with 50F+ under Prime Load. I will run the Burn Test, and the memtest86+, and do the PS voltage test shortly .

Coincidentally, the Blue Screens started when I installed Avast Free AV, recently, and occur only after full scans. Took me a while to figure that out, as I have been running the full scans at night. Finally ran a full one today, and Voila, up came the blue screen, so I have since uninstalled Avast and returned to MSE. I have also run Scan Now, and it did some repairs to my sys files.

So, all-in-all, with your advice and lots of other forum folks, I hope I have this problem solved.

Thanks again for your kind assistance.