Woe is Me!

[Driftwood]

Just embarked on my first (and possibly last ) attempt at building my "dream machine." This is a high end build using the latest components I could find at NewEgg. Used the "How to build your Dream Gaming PC" book as a guide. Here are my system components:

ASUS M2N32-SLI Deluxe Wireless Edition Socket AM2 NVIDIA nForce 590 SLI MCP ATX AMD Motherboard
AMD Athlon 64 FX62 Windsor 2000MHz HT Socket AM2 Dual Core
1 ASUS EN7950GX2/2PHT/1G Geforce 7950GX2 1GB GDDR3 PCI Express x16 Dual GPU
4 gigs CORSAIR XMS2 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Unbuffered
1 WD Caviar SE16 WD4000KS 400GB 7200 RPM SATA 3.0Gb/s HD for storage
2 WD Raptor WD1500ADFD 150GB 10,000 RPM SATA150 HD for a RAID 0 performance config
1 PLEXTOR 18X DVD±R DVD Burner E-IDE/ATAPI Model PX-760A
Windows XP Pro w/SP2

Here's how things started. After getting things assembled and powering on for the first time I found that I was getting a memory error (1 long beep followed by 2-3 short beeps). Tech Support for ASUS advised a mem error. Triple checked on mem compatibility with the mobo mfg and the mem mfg. NP there. Even did the mem86 test with NP. After further testing I established that the mobo had two bad memory slots. Sent the mobo back and got another one. Get the new one and no mem errors! But now I notice that the #1 integrated LAN port (there are two) on the mobo shows a steady green activity light with nothing plugged into it. Tried the connection and it doesn't work. The secondary connection works as does the wireless one but I digress. I set up the RAID configuration, load up windows, load drivers (several of which haven't passed the MS seal of approval) set/format additional partitions on the drives and things then start acting funny. The system will eventually "hang" and continuously attempt to reboot. I did get a MS error message that talked about potential driver problems AND a separate one saying "serious" hardware issue. When I called ASUS tech spt about the LAN activity light they told me that thiers does this too but theirs works. They stated I should try a little more testing. So that's where I'm at now. I'm sure I can return the mobo.....again......just for the LAN port not working. Do I try this MoBo one more time or go to something completely different? I am trying to make sure I'm not the one missing some small setting, jumper, etc that's causing me all this grief. I expected to pay a "price" for trying to be on the "bleeding edge" of technology by using components that have just been released but I didn't expect to have back to back bad mobos. My hope is that some of you gurus out there might be able to lend me the benefit of your experience.

[doctorgonzo]

Yes, I would RMA the motherboard. You paid for something that works. Asus is a good brand; you may just be encoutnering a string of bad luck.

Second, RAID 0 is a BAD IDEA with a capital B, especially on desktop computers. You gain very little, and in return you risk all of your data when just one drive in the array goes bad.

If you do get a new motherboard and you do reinstall Windows, make sure you get download the latest drivers from Asus. Then, install Windows with just the bare minimum hardware necessary: a hard drive and your DVD drive, that's it. Get Windows installed, get the motherboard drivers installed, get Windows updated, then add the rest of the hardware one piece at a time. If there are any problems, it will be obvious what is causing it.

[Driftwood]

Thanks for your reply Doc! I will certainly follow your suggestion for when the new mobo arrives. So you would give the same mobo a third try? I've read all the mobo reviews on NewEgg and there were a few folks that had similiar troubles with this board but the majority of people thought it was great. It just seems odd to me that two of these mobos (coming from different warehouses) would continue to have issues.

[doctorgonzo]

I had to RMA the motherboard in my latest build twice before I got a working board. Sometimes it happens.

[Driftwood]

Thanks again Doc. The thought of being on a first name basis with the RMA folks at NewEgg didn't really thrill me but if you say "stuff" like this happens that definitely makes me feel better about the situation. New mobo is on the way. I'll let you know how it turns out.

[Driftwood]

Hey Doc, here's the latest........did away with the RAID config and so far (fingers crossed) things have been running smooth as silk. RAID controllers were one of the issues with this board. It's still going back because of the LAN port not working.

[Driftwood]

Damn these things are finicky! Ok, 3rd mobo arrived today. Got it in with all the components, turned it on and no memory errors and the LAN ports seem to be ok (haven't tried them yet). System boots up, windows starts....HOORAY! It starts reconizing all the periphierals, keyboard, mouse, etc, etc. Everything seems ok and then I try to load a profile for my flight controller (Saitek X52) and POW! System crashes and won't reboot. It keeps rebooting trying to load windows with no luck. So, I'm starting from scratch again. Reformating the HD and reloading windows. The saga continues!

On another note I did have a question about memory. My mem stick labels say it's timing is 4 4 4 12 2T but when I check the bios it says the memory is running at 5 5 5 18 2T. Do I/should I change that to coincide with what the memory label says it should be? I was also told by the memory mfg (Corsair tech spt) when I was getting memory errors with the first mobo that I should set the DRAM voltage higher than what the bios sets it at automatically. Which setting should I use there?

[blue60007]

Do you have this or this.

If the 1st one - set it to 1.9V. I had a small issue that went away when I bumped it up a bit. If the 2nd one, Corsair says 2.1V. I'd see if you can get it going before you start tightning up the timings.

Just so you know, unless you have 64bit version of Windows, you won't be able to use more than about 3GB of that RAM. 32bit Windows can only use 4GB of RAM and it assigns some of that addressing space to other things, so you end up with about 2.75GB to 3.25GB left over.

[Driftwood]

Thanks for the reply Blue. I've got the 2.1 volt one. And I'll try that out if I ever get windows back up and running. I've tried reformating the C Drive from within Windows setup and am getting some "file missing" errors when trying to run WinXP setup. I tried CHKDSK and it says the drive is fine. So I'm trying it again since I went into DOS and found there was a Windows directory on the drive with only a few files in it. I've deleted it and am trying again. Any more suggestions from the audience would be great........... Oh yea, and what's the difference between "Quick Format" and just "Format?"

[Kareeser]

The quick format empties the Master Boot Record, which is basically a "Table of Contents" of your hard drive. Without it, the computer won't be able to see or find anything. Advantages: Much quick, plus, if you ever need your data back, it's still possible to retrieve it. (The chance becomes slimmer the longer you use the drive after formatting it)

The "not-so-quick" formatting option goes through your entire drive and writes zeroes into it, so all the data is lost (more or less).

[glc]

What are you using for a power supply in that thing?

[Driftwood]

I'm using a SILVERSTONE SST-ST60F ATX 600W Power Supply 90 - 264V. SLI certified. I believe I may be on the trail of the problem now (I hope) and that's the Mobo bios and getting them updated. Problem is at this point I'm still having great difficulty getting Windows reloaded. Not sure how to go about updating MoBo bios without windows up and running. I keep trying to reinstall and I'll get "unable to copy" file errors when it's going through setup. Sometimes if I keep hitting return it will copy but then others pop up. The few times I get into Windows setup and it attempts to start windows by rebooting the damn thing will go into a continous reboot. This is what I think the newer mobo bios will fix. Is it possible to update the mobo bios without having windows running?

[nicolaus corelius]

yes through a floppy. call asus or look up on their website on how to update the bios.

[Driftwood]

EUREKA! What a difference new BIOS makes! Got windows loaded finally after I flashed the bios with the latest update. Back to loading drivers and keeping my fingers crossed!

[blue60007]

Must've been a memory issue - AM2 is very picky about memory right now - and the BIOS update fixed it. Hope it works out all the way for you!