A8N-SLI Deluxe reboot

[Orbital]

Hey all im having a bit of trouble with this bored and i have done everything i could come up with including RMAing it (Asus said there was nothing wrong with it) so im hoping maybe somone here could point me into the right direction.

Basically the computer is randomly rebooting primarily during stuff like windows updates and when i was installing a patch for a game earlier it would reboot everytime. It would install for a bit and then just reboot. Iv gone through everything from reseating the cable checking temperature, bios settings, and voltages and everything seems to be fine nothing stands out to me from what iv seen. I am trying to get the system to work stable in a raid 0 configuration of the Nvidia controler. Any ideas or thoughts would be apriciated and thanks in advanced.

The system specs are

Win XP Pro 32bit
A8N-SLI Deluxe (Bios 1013)
AMD 64 X2 4400+ (runing at about 32C idel with a vcore of 1.36)
1gig of Corsair XMS3200 Dual-Channel DDR400
2 Western Digital Caviar SE 250 GB SATA2
BFG Geforce 7800GTX
ENERMAX EG565P-FMA WHISPER II ATX 12V PSU
and a PX-716SA DvD burner

 

[imported_Technomancer]

When it reboots, do you get a blue screen with all sorts of numbers and memory addresses that you can't read because it's only on screen for a split second?

 

[Orbital]

I just went back to try and install the patch again and it did it again and yeah that blue screen came up for a split second before the computer went into full reboot.

 

[imported_Technomancer]

I don't know for sure but I suspect that's either something to do with the HD's or memory, or how the motherboard handles these. I'm suspecting HD's though because in that split second of blue screen I can see a long list of memory addresses and hex code. I used to have similar crashes, but in my case (no pun intended) it only and rarely happened when my system was loading something big from the HD's, from Half Life 2 levels to Windows XP. It hasn't happened to me in a month at least though. If it does turn out to be the HD, then I wouldn't check vibration, as vibration wouldn't cause consistent failures.

Since I don't know for sure, this is still conjecture. I still wouldn't rule out memory. I noticed that we both are using the same type of Corsair memory, mine's just higher density so it could be something about the Corsair memory, which I hope is not the case.

The last option I've just thought of though, would be how some software drivers or how the BIOS is set in controlling memory/addressing. Whatever the source of the failure is, it is consistent, and these are things to check for with those characteristics.

Again, this is conjecture, but I'm sure someone can help shed light on this...

EDIT:

I'm just running a single 'Cuda 250 Gb, no RAID 0 for me. I don't think it's a problem with the RAID controller.

 

[Orbital]

Hrrrmm so is ther nothing that can actually be done to fix this asside from possibly try other ram and HDs? What i find to be the stranges is that my friend has a pretty much identical setup and he dosent seem to be having the same issues. Could it be the way something is setup in the bios?

 

[openwheelformula1]

How many harddrives do you have? did you install Nvidia IDE SW drivers? Go into the bios and see if all your hdds show up.

 

[Orbital]

I have 2 HD's and yeah i did install the IDE SW Drivers, when i enable the raid in the Bios the HD's dont show up under the main page anymore, but when i turn it off they do.

 

[Orbital]

Would the HD's not showing up in the bios be causing this? Or is that normal.