Windows 7 Memory Diagnostic Tool Crashed My System

I've pulled the RAM one stick at a time.

Windows still refuses to load. It still gets stuck at the Windows 7 loading screen and never loads windows.

I did a system restore to an earlier date and it STILL didn't fix it.

I've checked my RAM, HD, and scanned my system files using the tools above. What else could it be??

My POST screen for the motherboard is still crawling by... could this be a problem with the MOBO??? When my POST screen goes by fast, I know that windows will load fine... but that rarely happens now (read, it has only happened 2x in the last 4 days).

What should I do now? Get a whole new MOBO?

I'm going to try and reinstall windows 7 and wipe the partition... but if that doesn't fix it... OR it doesn't let me for some unknown reason... then I guess I should replace the whole MOBO, RAM and CPU.

I'm at my wits end here. I've never run across something like this before, which leads me to believe that it is hardware related to my MOBO... something that I can't test for with no other obvious solutions.

My MOBO is an EVGA 790i Ultra, just in case anyone knows something about this MOBO that I'm not aware of.

I've also updated "My System Specs" to help out, just in case something is there that would.

OK... here's the damage...

I noticed on my POST screen (after not noticing it) that one of my HD's was missing from the list. As the problem progressively got worse, my POST screen would hang on the IDE checks.

After 2-3 times of it doing this, and entering the BIOS setup, I noticed that one of the HD was not being detected.

I unplugged the HD that was not being detected and BAM! The whole system started running like clock-work. One of my HD's seemed to be failing.

I switched out the SATA port with another HD to check to see if the port was damaged, but the port worked fine with the other functioning HD.

I then switched the cables to see if the cable was somehow damaged and now all 3 HD's are running fine.

So, either my one HD is failing intermittently, or there was a build-up of corrosion on the SATA connector that was interfering with the communication.

Time will tell.

Thanks for all the suggestions. Maybe this will help out someone else some day.

You are welcome.