Printable View
I've been playing a little with the Fatal1ty AN8 SLI now and I didn't like the board at all until I found SysTool.Quote:
Originally Posted by Major
uGuru seems to change things permanently in the BIOS (not like ClockGen) and besides that, it loads guruclock with windows, which could screw up the settings.
Disableing this with msconfig and only using SysTool has definitely made me change my mind about the board. BIOS 17 seems pretty ok aswell.
WTF 1.4GHz>>>>3.75GHz OC...that's pretty good dude...you got any links for that Celeron OC
Quote:
Originally Posted by crotale
Ok Abit is back in the rig ;)
Much better already after Chew* gave me the heads up about removing the battery and clearing cmos.
Fresh install of window done without a hitch, about to start OCing :D
NP major and its nice to have someone as xtreme or xtremer than me playing around with this motherboard.
Now onto memory testing. next up is Crucial ballistix PC4000.
Testing at ddr 400 netted good results much like my bh-5.
DDR 400 1/1 cpu at stock timings that were stable 2-2-2-6-1T(4x256mb single sided)
DDR 500 using the 500 memory setting in bios cpu still at stock.
2.5-4-4-8-2T. 1T is definitely an issue with the 4x256mb sticks I have installed. I will try later with just 2 and also test each stick individually to see if one stick is holding back the rest.
Ok scratch the above apparently this stuff is not as stable in this board as I thought it was. Doom 3 crashed after 5 minutes. played around with timings a little and started running prime and it wont even make it 5 minutes in prime. Mind you my cpu is at stock so I highly doubt its cpu issues. I contacted crucial to see what they say and if they can give me a list of timings/bios that they found to work.
Anybody have an issue when using the DDR 500 setting with evrything stock? When I use it CPU-Z reports the memory as running at 129.2 with a CPU/14 Ratio. :confused:
Pay no attention to that. Instead do this. Run sandra bandwidth test at ddr 400 then run it again at ddr 500 if it increases then you are sucessfully running at ddr 500. So far to date memtest 86+ and cpu-z do not identify the ddr 500 setting correctly to my knowledge.Quote:
Originally Posted by NorthernYankee
Thanks for the heads up. I have been overclocking P4's for the last 2 years and Athlon 64's are a totally different beast.
Quote:
Originally Posted by Major
Stike Three, and you outa here !! :mad:
Anyone want to buy an Abit AN8 SLI ? lol
I got rid of mine!!! lol
I'm slowly getting agravated with mine and this crucial 4x 256 mb of pc 4000. Prolly gonna toss it in my gigabyte and see how it does before i pull my hair out. I'm now down to testing each stick individually to see if i got a bad stick and have one of my delta 80 mm fans blowing on it to remove heat as an issue.
Most of the issues went away after I took Chew*'s advice and removed the battery for a few minutes while I cleared CMOS. But I couldn't even get windows installed unless I used 2t, and that was with optimized defaults. I was able to OC to 3060mhz stable using 2t. But with the X2 it limited my Vcore to 1.7v and I need 1.73 to get back to 3140mhz where I was with the DFI NF4.
Crucial ballistix results = the suxxors. Stock cpu speed ddr 500 divider. I'm putting this in my gigabyte now if it passes prime at same timings or tighter abit may no longer be my first choice as a mobo anymore.
Note that crucial rates these at 2.5-4-4-8 and most people can do 2.5-3-3-7 and my timings are grossly loose yet still failing prime............
http://members.cox.net/wmdieselmc26/cucial%20fails.bmp
you probably know this but prime95 gives out the stupidest results, some people prime for 24+ hours and once they hit the games it freezes.Quote:
Originally Posted by chew*
http://www.nordiccrew.com/crotale/ocsm.jpgQuote:
Originally Posted by dinos22
Did you try BIOS 17? Some people say it solves some 1T problems.Quote:
Originally Posted by Major
nice work
Quote:
Originally Posted by crotale
yah not even 5 minutes in doom 3 and it bsod'ed also which lead me to start rechecking prime stability. Meanwhile while I type this the the gigabyte has already passed 5 tests in prime 95 while my abit passed 0 times on numerous tries( about 5 hours worth of testing timings). Not to mention the timings its doing it at are quite embaressing to my abit board ill post screenies later. Not sure what it will overclock to though.........but its passing prime at 2.5-3-3-7 at ddr 500 now.Quote:
Originally Posted by calcal
chew are you the guy who posted a ss of you doing 396 htt o your an8 sli?Quote:
Originally Posted by chew*
Yep 395 htt and then i pulled a 330 fsb tccd and then i pulled a 268 fsb bh-5 run and for the life of me i cant get this crucial ballistix to work at all :(Quote:
Originally Posted by calcal
Here's what its doing in the gigabyte first shot. Just set a few timings in bios that were tighter than the memory is rated at and bam. Very dissapointing that I can't get it to run at all in the abit.
http://members.cox.net/wmdieselmc26/4x256%20crucial.bmp
why do you run Prime at stock speeds
to eliminate my cpu from the instability equasion. and thats actually ddr 500 just a64 tweaker dont recognize it right. plus that cpu barely gets 2.2 gig at 1.45 v so since its my sons pc i dont really like to OC it. BTW its an 0518 cpu and it sux. consequently it has a max case temp of 55C. anyone see a pattern there :)
EDIT* Ok this is as tight as i can get the timings on the gigabyte board. Wish it ran this good on the ABIT. And this screenshot id for you dino. I overclocked my sons pc just to make you happy :) note its a stock heatsink with the thermal pad still intact............
http://members.cox.net/wmdieselmc26/...%20timings.bmp
btw i saw that post over at abit-forums :)
nice overclocks =D
for your problem, it seems that abit board doesnt like micron chips, but i dunno
talking about OCing
i got to try another Venice 0516GPAW....not bad for starters :D
http://img391.imageshack.us/img391/4...erpi3zk4vu.jpg
it's a CPU...it's gotta be OCd hehehehe
everything's got to be OCd :p: hehehehe good on ya dude....
Quote:
Originally Posted by chew*
your OCing through windows?Quote:
Originally Posted by Major
.......... .
No I was OCing in the bios, the setting just wouldn't hold.Quote:
Originally Posted by Ket
That was fixed though by removing the battery and clearing CMOS for 15 minutes. After that the settings stayed. I also heard that the Abit uGuru program in windows could cause the settings to return to default too.
I'm back on DFI NF4 now
I only really saw a couple of issues with the Abit, using my X2 and 2x1gig Ballistix I could only run 2t even with optimized defaults loaded. I tried BIOS 13,16, and 17 all the same. Also it would hang during post about 50% of the time requiring a power off reset. Also using the X2 I only had the option of up to 1.7vcore and I needed 1.725 or more to obtain max OC on the X2 that I had with the DFI