Well, I run Vista64, so stability NEVER happens with my new systems anyway. :(
I'm awaiting the Vista edition with the first service pack before I leave the trusty XP behind... so you never got this OS stable enough mate ? Is it the OS or the board ? as I'm going 64 bit too to take benefit of the extra ram I have here
Getting quite annoyed here atm, I have this Abit mobo with bios v 12 updated..
I also have OCZ Reaper PC8500 ram..
Tried all voltages 1.85 stock to 2.3v and on 5-5-5-15 cant get it to run 1066 mhz..
I have a Q6600 CPU in this rig... FSB is 1066 so i run fsb 1:1.. should work fine.. but cant seem to get ram working full speed system proves too unstable i.e crashes in super pi or gets error or crashes in game.. not what id expect for new kit
Should i have to put up with running it at defult pick up settings @ 667mhz?? when £130 was payed so i could have fast ram.
Likely to be board is fussy?, OC options for my quad seem a little weird i mean can only change FSB vs multi... cant seem to set bus speed as an option.. this bord was £190 from OCUK!
God damn it with this board I had to updtate to Bios V12 so I can use an E6850 and now I magetting sound problems again with an Audigy ZS Platinum EX. The sound is crackling all over with SLI to the point it is unusable. It happened before and I reverted to an older BIOS and all worked.
If anyone knows of any solution.
http://forum.abit-usa.com/showthread.php?t=127501
Running it now and I can for the first time, run my ram at 1066. Be aware though; if you are running a quad, you will not be able to run your fsb as high as you can with the 1.2 bios. At least this has been my experience with any of the 1.3x bios's, as well as with 1.2b6. 1.2release still lets me go to 1330fsb stable. Not sure where the ceiling is with 1.3, but it's somewhere around 1260fsb or so, for me.
Not a big deal for me since my multi is unlocked up/down, but may be a consideration if you are multi-locked upwards. Also, I can run my ram at 3-3-3-6 1T with bios 1.2 but cannt get 1T with 1.3 bios. Again, no big deal since I'm getting great results running with 1.3, ram@1066 5-5-5-15 2T.
Finally, realize that all of the above is with MY system, running 4 sticks, so if you are running with just two sticks, your results may vary, greatly.
Hell broke loose on my PC lately. First I bought this god damn E6850 but i needed another CPU too for my HTPC so fine with this. After I updated to BIOS v12 problems started.
Everything run nicely and stably @ 4GHZ 443fsb and then suddenly Kabooom! random reboots. No matter what it would not run at those settings anymore. I reduced the oc to 3.6Ghz and everything fine again (8x44? fsb). Then suddenly some days later kabooom! again no go. However, the board would run fine at stock settings or so it seemed (did not run stability tests). Then I updated to BIOS 1.3 (dos update) and that was it. I only managed to boot once after clearing CMOS numerous times and removing all memory and one 8800GTX.
Finally when I put all back in the board seems dead. The post messanger displays 8.3 code which is power related and last time I saw it on an IN9 32MAX it was dead. The board starts and it shuts down on its own a few seconds later.
But here is what I will do: I will buy another board tomorrow (eVGA probably) and see what i will do to this piece of :banana::banana::banana::banana: that I can not even rma (I cut the stock heatpipes). Oh well it was nice while it lasted.
Extreme oc'n comes at a price......
And sometimes you pay way too much for a board that claims to be an "overclocking monster" and it won't boot at anything but stock settings:(. Hopefully the latest RMA comes back a winner...
Well I did it I got rid of the IN9-32 MAX and replaced it with an EVGA 680i A1 revision. I also grabbed a quad and now I am happily crusing @ 3.6 Ghz 400FSB no sweat at all. I just set it up and it runs like a dream and finally both my DD Maze waterblocks are finally put into good use cooling both the NB and SB.
I will buy yet another Abit IN9 now so I get access to another set of heatpipes to RMA the one I have dead. Then I will sell this one to a friend that does not overclok (will sell it 50% less) and will change the replacement at the store with something else an HD maybe.
Damn this is the 3rd Abit board I kill during the last 8 months and I think that I overstressed it so much that the PWMs or some capacitors crapped out since it was squeeling like mad.
That happens with all system voltages set at max (except SB at 1.65v) a 450 FSB and 4Ghz CPU with 1.6950 Voltage. What was I thinking? Would this thing endure much ofc not!
I've been overall happy with mine! Runs great, all info in sig.
Built a new pc for my dad in July featuring this mobo as a good foundation for a quad core 8800GTX etc..
Also got some OCZ Reaper pc8500 ram for the board... auto pics up at 800mhz with 1.85V runs fine prime 95 stable etc... but
Problems arrise with memory when trying to get it to run at its rated speed of 1066mhz... tried with OCZ/Corsair Dominator at 1:1 ratio for Q6600 cpu for 1066MHZ... upped vots 2.1-2.3 still prime unstable.. all settings are accepted by ram and mobo but system seems unstable! i.e doesnt boot into windows proporlly freezes half way or is unstable during game or prime 95..
Basically cant get ram to run its full rated speed with recomended settings, tried even with my own ram thats run fine past 1300mhz 5-5-5-15 and guess what at 1066mhz on my dads pc still has issues...
Its problem with my bord?, 680I chipset?, memory controller?
Additonal info:
IN9 32Max mobo
Q6600 CPU @ 2.4Ghz (stock)
Corsair Dominator PC8500 (2x1Gb)
8800GTX
Mobo bios '12'
Case Tenjim 09 with good airflow
:shrug: :shrug:
From my experience with the IN9 its a really decent board for overclocking dual cores, but when it comes to quads its terrible! Thats probably half your problem. For example, my X6800 went to 3.9ghz no probs on this board, but my Q6600 would blue screen at the windows loading screen even at 3ghz. For comparison, 3.4ghz is stable on my EVGA so far, and im still going.
Its certainly not the best board for quads imo.
Im not trying to overclock here, im just trying to get my dam memory to run at its rated speeds!! i could understand if i was expecting too much but merely trying to get what should be fine working:
Q6600 @ 2.4 1066Mhz FSB 1:1 with memory @ 1066... 5-5-5-15 @ 2.1V on corsair mem.. defult bios 800mhz runs fine but cant on 3 different sets of ram run at the rated performence speeds... this is silly for £180 mobo!
:shrug: :shrug:
Flash to bios 13 on it ...thats supposed to fix that issue.
Abit forums;) http://forum.uabit.com/index.php
It's not an easy board to work with, imo. You need to keep the NB cool so add a fan to it.
Had a look hard to find something spesific to my problem as there quite a few problems on there... but hopefully Bios 13 will fix issue...
Would this fan be okay for the NB? or is it too thick?
http://www.overclockers.co.uk/showpr...=57&subcat=818
Hi all got to my dads yesterday, updated bios from 12 to 13...
Rig:
Q6600 (B3)
2 x 1Gb Corsair Dominator PC8500
8800Ultra
At all stock settings i.e bios mem pickup @ 800Mhz safe...
Prime 95 can run over hour with no errors!! temps mid 50's with low rpm fan in Tuniq Tower120...
Then when i set in Bios ram @ 1;1 ratio with FSB of mobo to be 1066Mhz.. With 2.1V and mem timmings 5-5-5-15-2T which is recomended settings boot into windows okay then run prime 95... all threads die after 8 mins!!
Also ive noticed the Bios doesnt allways hold the settings you saved previously!!
Any advice how get ram running rated settings without instabilty as this bord is £180 and shouldnt have problems with a slow PC8500!! my Am2 bord does 1200Mhz on ram with ease never seen problems with 1066mhz!!
The ram may be getting hot. Try some active cooling on them to see if that makes a difference. You may also need to bump vdimm up a notch, which would actually be my first guess anyway.
Ram isnt the ISSUE here, ram works fine 1200mhz + on same settings same volts in my Amd rig... but wont work at rated settings on this mobo!!
Bios updated to V13... still problems tried upping NB Vcore slightly from 1.35V to 1.4V which you shouldnt have to DO! and its sorted the instabilty!
Not amazed with this mobo in that repect also BIOS doesnt hold settings that well i.e changes back after month or so!
My bad. Was just trying to help. But yes, the relation between NB voltage and vdimm seems to be well established with this mobo when OC'ing and/or running 4 sticks, but I'm surprised you had to increase NB with stock settings.
OK, I have just about had it with this board. I think I need to RMA it, and just call it a day. Maybe a different MoBo would be something to think about as well...
After the months of tweaking and testing and hassle with Vista64 Ultimate I gave up, removed 2 sticks of my beautiful Corsair Dominator and reinstalled XP SP2. Problems should mostly go away, right?
Wrong!
The problems only started. At first everything seemed to be running fine, then I got my second 8800GTX....and guess what? Now nothing wants to work. No problem, I think its time to flash the BIOS, because everything I have tried was with the BIOS that shipped with the board.
Now, I have unknown device errors, I can't install the mass storage device drivers, and the machine likes to get caught in random boot loops when I reboot, for no particular reason.
As if this all weren't bad enough, the machine INSISTS that I need to register windows, WHICH IT WONT LET ME DO BECAUSE IT CANNOT FIND THE T1 INTERNET CONNECT I AM CONNECTED TO. So, even if I got the machine running, it wouldnt matter because my copy of windows is obviously only good for about 24 days before I need to register...
Oh, and BTW, this is the second fresh install of XP SP2 I have tried, and it still isn't working.
I don't know about the rest of you guys, but I can't even get this piece of :banana::banana::banana::banana: to run stock speed and boot stable. IMHO, this board is a huge waste of money and I am about ready to take it out to the dessert and shoot it.
Anyone else EVER had this sort of a problem from a board, and more specifically, a BIOS update?
--Skrips