Update 3/10/2011 (2): Switching harddrive slots once again allows Windows to load, but crashes are much more frequent than they were previously. It's clear that the issue has to do with the hard drive controller... Or a loose connection anywhere else in the system :(
Update 3/10/2011: After switching components back and forth, the system began to refuse to boot (no beeps, no video). I removed it from the case, and was able to get it booting again by switching the hard disks to a different slot. Windows asked to restart due to hardware changes, and I allowed it. After that, my system failed to launch windows (it reboots after the "loading Windows" screen).
At this point, my guess is that either the RAID controller or the SATA slots on the Motherboard have become damaged. I'm hoping the failure to boot isn't due to subsequent damage caused while I was troubleshooting. However, I have yet to have an actual test on the system fail, so I'm still somewhat mystified.
After moving my video card to a different PCIe x16 slot, I was able to run my test case without errors. Moving it back resulted in immediate errors again. I'll be spending tonight and tomorrow getting my PC sufficiently back together to run more strenuous tests on it, and hopefully make myself more certain.
Naturally, as soon as I posted the above, the test case failed with the same error message. Apparently the test case isn't as reliable as I thought it was.
My computer has suddenly started crashing to a blue screen with the following text:
call your hardware vendor for support
*the system has halted*
The crash occurs randomly during normal use. I have thus far always been able to reproduce it by transferring the contents of a large folder... But I'm not sure if this is caused by the file transfer, or simply because the transfer takes long enough for something else to trigger it.
A bit about my hardware
I have an dual core Intel CPU, and Asus motherboard. Video card is by nVidia, and connects via PCIe. My hard drives are in pairs, and connect via SATA to a RAID controller on the motherboard. They are configured to use a RAID0 configuration.
What I've tried so far
There is nothing in the Windows Event Log.
WhoCrashed was unable to find any crash records.
ScanDisk runs to completion (it launches prior to Windows load) and reports no errors.
MemTest reports no errors (to 200% coverage).
System temperatures are in the range of 40 to 50 degrees Celsius, with video card temperatures in the range of 60 to eighty degrees Celsius.
I have stripped the system down to a minimal configuration (hard drive, video card, one memory module, motherboard, CPU, power supply). The problem still occurrs.
I've reset the CMOS by removing the motherboard's battery for an extended period of time.
However, this has allowed me to rule out a few components:
It is not the video card because the problem still occurred after replacing the video card another one I had on hand.
It is not the hard drive or anything software related because the problem occurred after a fresh installation of Windows on a replacement hard drive.
It is not the hard drive cables because I replaced those with new ones and still had the problem.
It is not the power supply because the problem still occurred after replacing the power supply with another one I had on hand.
It is probably not the memory because I've tried three different memory modules in three different memory slots and was still able to replicate the issue.
It is probably not an issue of the motherboard grounding against the case because I've completely removed the motherboard from the case, and still encounter the issue.
Is there anything I can do to confirm what's causing the issue? At the moment it seems as though it must be either the motherboard or CPU, but those are both difficult components to replace... In addition, both components are relatively new (two to three years old).
I will gladly edit in any additional information I can get my hands on, and/or focus the question as I can find more details...