Hating Asus A8N-SLI Premium - need alternative

Superguy

Member
Sep 12, 2005
132
0
0
Hey all,

My first post here. You guys seem pretty knowledgeable about A64 boards, so I thought I'd post and ask.

This is my first A64 build. I have built some Athlon machines, but not for myself. I've used Intel at home for the last several years. The X2's were just too compelling.

I bought an Asus A8N-SLI Premium and have had nothing but problems with it. I've reloaded XP about 5 times already, and it just won't stay stable ... even at stock speeds.

I've been using the 6.66 drivers, slipstreamed into my install. I'm not using NAM. The vCore doesn't work right (won't go above 1.36v) to overclock. My X2 3800+ seems to be capable of doing at least 2.5, but I think it needs a little more vCore to keep it stable.

Last night, after running fine overclocked, Windows ended up getting corrupted and went into and endless reboot cycle. Had to reinstall.

I'm going to slipstream the 6.53's into an XP image today, but after that, I'm really considering sending the board back.

So what would be a good choice?

Here are my needs:

I want to overclock
I want something that will just work, and work right out of the box and be stable. Maybe Intel's spoiled me here ...
I'd like somthing that's flexible so that I can add other PCI-E cards that are bigger ... like an x4 slot. I've read that most SLI boards will allow for the other x16 slot to work as an x8 in SLI, and usable for peripherals. As I'm using ATI, the SLI interests me mainly for flexibility.

I got the A8N-SLI as it had everything I could want on it. It just doesn't seem to be working out for me.

Here are my specs (as they stand right now)

A64 X2 3800+, running at stock
Asus A8N SLI Premium
Thermalright SI120.
2GB Mushkin PC4000 RAM (2 X 1GB)
Radeon x800 Pro
2 x 37GB Raptors in RAID 0
1 WD 250GB SATA drive
550W Antec TPII PS
Opticals
etc

I'm getting really frustrated. I'll admit I'm a noob on the AMD side, but I have been building systems for many years. I'd appreciate any help and insight you guys could offer.

Also, if anyone knows of a good beginners guide for OC'ing an A64 (or X2), I'd appreciate it. I'm not stranger to overclocking on the Intel side, but I'm still learning the ropes of the A64.

Thanks!

Super

 

mode101wpb

Senior member
Aug 16, 2005
445
0
71
I have the same board and I have zero issues. I'm not overclocking and used the latest drivers (non-beta), maybe it's something to do with using the X2, I have the 4000+?

If you want to overclock, then DFI Lanparty would be more for that purpose. There have been some reports of overclocking problems with this board.

 

Capt Caveman

Lifer
Jan 30, 2005
34,543
651
126
What bios are you using? What is your DRAM voltage? The early bios set the DRAM voltage to like 2.4v which isn't enough and the newer bios have raised the default voltage to 2.6v which is not enough for most RAM.

Personally, I haven't had any issues with this board and can oc my system to 2.75ghz.
 

Superguy

Member
Sep 12, 2005
132
0
0
Bios: 1006 (current). I was using the 1007 until I read about the vCore issues on here.

Mem voltage: 2.8v. That's what Mushkin has it rated at.
 

mode101wpb

Senior member
Aug 16, 2005
445
0
71
I thought the max Vcore of 1.45V with 1007 was causing some isses? At least that's what I read on the ASUS support forum?

I know 1008 is available, at least ASUS Update showed it.
 

Superguy

Member
Sep 12, 2005
132
0
0
Yes, more voltage options are available in 1006 vs. 1007, however, the vCore was still pegged at 1.36v in either version.

Bios and CPU-Z both showed the same thing.

I haven't heard of anyone posting results from the 1008 bios (I know it's beta). If someone has, I'd certainly be willing to try it if it helps.
 

mode101wpb

Senior member
Aug 16, 2005
445
0
71
You may want to look or post in the ASUS Support forum, it appears that some people aren't getting support feedback from ASUS. I can't say anything negative because I've had no issues yet.
 

Superguy

Member
Sep 12, 2005
132
0
0
Fine enough.

So if I end up ditching this board, which I may or may not do, what would be a good alternative, based on what the criteria I've listed so far?

Thanks,

Super
 

mode101wpb

Senior member
Aug 16, 2005
445
0
71
There has been a few people on the ASUS Support Forum that have X2 issues, I only suggested it as another means to get some more help. I wouldn't give up yet. The DFI comment was based on my original selection process, everybody told me to go DFI if I plan to overclock. Since I wasn't planning on it I went ASUS.

BIOS issues seem to be a big topic.
 

Superguy

Member
Sep 12, 2005
132
0
0
Yes, the more I read, the more I see that.

It's seeming like this board is just a POS until the bios gets straightened out ... and Asus isn't talking about fixing it on their forums.
 

orion23

Platinum Member
Oct 1, 2003
2,035
0
71
I have this board and I really hate it.
I run an X2 4800+ with latest drivers and bios (nvidia website, bios 1007)
I have had so many problems with the SATA controllers.
I have 7 SATA drives running and sometimes the PC will restart in regular time.
Other times the PC will take very, very long to restart, it usually hangs at the xp logo for a long time.
And other times it just doesn't restart at all and when I look in the bios, I find that the boot drive has changed its priority from 1st to last.

While installing a cpu fan, the original pin that held the back plate broke, (I replaced it with a better from zalman anyway)
Later when trying to remove a 6800 ultra I broke the little PCI-E guard, (that little white piece that locks the VGA)
 

mode101wpb

Senior member
Aug 16, 2005
445
0
71
Originally posted by: Superguy
Yes, the more I read, the more I see that.

It's seeming like this board is just a POS until the bios gets straightened out ... and Asus isn't talking about fixing it on their forums.


I don't know about that, like I said I have no issues with mine and neither do hundreds of others. ASUS claims it supports the X2, maybe they should have never said that?
 

mode101wpb

Senior member
Aug 16, 2005
445
0
71
Originally I was going to go with a 4600+ X2, but passed due to the price. I installed a 4000+ San Diego for now, plan to go X2 in the near future when the price drops and more applications benefit from it.

 

Superguy

Member
Sep 12, 2005
132
0
0
The quandry continues.

It appears that I'm at least stable now running at stock. I started Prime95 before I went to bed last night and it was still running strong this morning. I'm expecting it to still be running when I get home from work tonight.

However, overclocking seems to be out of the question for the time being.

So ... now I have to decide whether to wait and see if Asus actually fixed the vCore, or to get a new mobo. Problem is, I'm not seeing another one I like.

I like what the Asus has to offer ... it has everything I want ... which is why I bought it in the first place. But crappy overclocking is a big downer, and other boards all have little things that could cause problems (ie Gigabyte not having screwholes for the hsf bracket), or don't have everything I want.

DFI seems a little out of my league for a first time A64 builder.

Decisions, decisions.

Super
 

virtualrain

Member
Aug 7, 2005
158
0
0
Some suggestions:

Try a Vcore setting of 1.475V or even 1.5V. That might work (it does for me).

Next, if you haven't already done so, go about your overclocking in a systematic way. Search the overclock forum here for an article that goes through it in a divide and conquour way.

To paraphrase that awesome article...

1) Test your boards HTT limit first by setting a low CPU multiplier and DDR100 RAM divider... Raise HTT til the system won't boot. The ASUS board should be good for 300MHz! To save some time, just try that and if it works, you likely won't be going any higher so move on to the next step.

2) Test your RAM limit by setting a low CPU multiplier and 1:1 (DDR400) RAM divider and slowly increase HTT using Memtest booted from CD to check for errors. This takes a long time as you may need to try different speeds and relaxed timings and different Vdimm settings until you find the sweet spot for your RAM. Don't do any of this testing in Windows as you will corrupt your install. Once you find what you think the sweet spot is, try running Memtest for several hours as heat may contribute to errors that only appear in later passes.

3) Test your CPU max overclock by using a low RAM divider (DDR100) and try increasing HTT with the top multiplier until the system won't boot. Back off a bit and that's your probably your max CPU overclock. I would back off 50-100MHz from this max value for stability purposes. Use the highest Vcore you feel comfortable with (I use 1.475V).

4) Combine the best speeds for your RAM/CPU. Run Prime and closely monitor temps.
 

rise

Diamond Member
Dec 13, 2004
9,116
46
91
Originally posted by: Superguy
DFI seems a little out of my league for a first time A64 builder.

Decisions, decisions.

Super


don't believe the hype.

it was my first complete build and i liked it so much i have 3 running here and built two others for friends/family.

most people who say they aren't for first time builders or need tweaking just to post have never even tried one.
 

BeakerChem

Senior member
May 11, 2005
219
0
0
To the OP, did you install the nVidia SW IDE drivers for this board? I got tons of stability and corruption issues that completely went away when I reinstalled windows and left out the SW IDE drivers.
 

mode101wpb

Senior member
Aug 16, 2005
445
0
71
I never installed those drivers period. The only IDE device I have is my optical drives.
 

jose

Platinum Member
Oct 11, 1999
2,079
2
81
I've had 2 - Asus A8N-SLI mobo's , nothing but problems.. I now have 3 - DFI mobo's (2 - ultraD's & 1 SLI-DR) all running fine.

I do not have any X2's though...
 

jose

Platinum Member
Oct 11, 1999
2,079
2
81
I got them from ZZF, the first was DOA. It would not post at all. The replacement was DOA every other day. Look at my sig. the 2 - 3500+ rigs were what I replaced w/ 2 - UltraD's.....

I lost 6 weeks w/out my system... ZZF is very crappy when it comes to RMA's......
 

Superguy

Member
Sep 12, 2005
132
0
0
Originally posted by: virtualrain
Some suggestions:

Try a Vcore setting of 1.475V or even 1.5V. That might work (it does for me).

Next, if you haven't already done so, go about your overclocking in a systematic way. Search the overclock forum here for an article that goes through it in a divide and conquour way.

To paraphrase that awesome article...

1) Test your boards HTT limit first by setting a low CPU multiplier and DDR100 RAM divider... Raise HTT til the system won't boot. The ASUS board should be good for 300MHz! To save some time, just try that and if it works, you likely won't be going any higher so move on to the next step.

2) Test your RAM limit by setting a low CPU multiplier and 1:1 (DDR400) RAM divider and slowly increase HTT using Memtest booted from CD to check for errors. This takes a long time as you may need to try different speeds and relaxed timings and different Vdimm settings until you find the sweet spot for your RAM. Don't do any of this testing in Windows as you will corrupt your install. Once you find what you think the sweet spot is, try running Memtest for several hours as heat may contribute to errors that only appear in later passes.

3) Test your CPU max overclock by using a low RAM divider (DDR100) and try increasing HTT with the top multiplier until the system won't boot. Back off a bit and that's your probably your max CPU overclock. I would back off 50-100MHz from this max value for stability purposes. Use the highest Vcore you feel comfortable with (I use 1.475V).

4) Combine the best speeds for your RAM/CPU. Run Prime and closely monitor temps.

Thanks. I'll try that.

System seems stable so far at stock. It ran Prime95 for nearly 23 hours without a problem.

To someone who asked about the SW driver, I'm not using it right now. I read that it sucked so I tried to avoid it as much as possible. When I was getting the data corruption, I installed it and it seemed to go away. But right now, it doesn't seem to be a problem.