So i'm starting a new thread to consolidate and make it easier to understand the problem, as the old thread is getting a little more cumbersome. if you want to take a look, it's here:
http://www.tomshardware.com/forum/274569-31-build-bsod-crashes-diagnose#t2021391
I've been getting Blue Screens since I built my new machine a few weeks ago. Here are the relevant facts:
i7 860 Lynnfield CPU
Asus P7P55D
Sapphire Radeon 5770
Corsair 750HX 750W modular PSU
WD Caviar Black 1TB (intended system drive)
WD Caviar Green 1TB (intended backup drive)
Lian Li PC-7F case
Windows 7 Professional x64 OEM
-The Blue Screens Always happen at the exact same point in startup - right at the end of the windows 7 loading screen, where it should transition from the windows logo to the cursor.
-The machine will flash a blue screen and auto-restart. When it restarts, it will offer to run Windows recovery mode. It will crash at the end of loading this recovery mode and display a blue screen, but when i restart it loads the recovery mode without a problem.
-The message i've seen the most often is "IRQL_NOT_LESS_OR_EQUAL", but i've also seen "SYSTEM_OPERATION_FAILURE".
-I am consistently able to fix the problem by running the Windows 7 recovery mode and either loading a recovery point or running the auto-repair utility. Once it is done running, upon restart, it will load Windows without a hitch.
-I have never had an issue with stability or any crashes once the system makes it into the Windows desktop, and i've had it running overnight multiple times.
-I have run the Western Digital Disk diagnostic utility on both Hard Drives, using the 'extended' test, and have come back with no errors.
-I have run memTest86+ for 14 hours, and encountered a single error.
-I flashed the BIOS of the motherboard to the latest version.
-I have installed Windows multiple times on both hard drives, and have had the same error with both (although for more than a week i had no problems with the 'Green" drive.
-The crashes seem to happen after letting the computer sit for a long period of time, like overnight, for example. I very rarely have trouble restarting multiple times immediately after running the Windows 7 repair utility, but it will crash the next day after no changes to the system.
-I installed a fresh copy of Windows on the Caviar Black drive and only installed the Windows updates, refraining from installing ANY 3rd person drivers, and it crashed after letting it sit overnight.
I'm pretty much stumped at this point. Some of the issues are really confusing me; especially that it seems to crash after letting the computer sit for awhile, and that it only crashes during windows startup. I'm running out of things to test.
What would you all recommend as far as further tests, or likely causes? I'm having trouble believing it's hardware at this point because it never has trouble once i'm booted up into Windows, and the startup repair utility is able to fix the issue consistently (albeit temporarily). However, a clean install of Windows with nothing installed except the windows updates suffered the same issue. I'm no expert with computer troubleshooting, but this seems like a tricky one to diagnose.
http://www.tomshardware.com/forum/274569-31-build-bsod-crashes-diagnose#t2021391
I've been getting Blue Screens since I built my new machine a few weeks ago. Here are the relevant facts:
i7 860 Lynnfield CPU
Asus P7P55D
Sapphire Radeon 5770
Corsair 750HX 750W modular PSU
WD Caviar Black 1TB (intended system drive)
WD Caviar Green 1TB (intended backup drive)
Lian Li PC-7F case
Windows 7 Professional x64 OEM
-The Blue Screens Always happen at the exact same point in startup - right at the end of the windows 7 loading screen, where it should transition from the windows logo to the cursor.
-The machine will flash a blue screen and auto-restart. When it restarts, it will offer to run Windows recovery mode. It will crash at the end of loading this recovery mode and display a blue screen, but when i restart it loads the recovery mode without a problem.
-The message i've seen the most often is "IRQL_NOT_LESS_OR_EQUAL", but i've also seen "SYSTEM_OPERATION_FAILURE".
-I am consistently able to fix the problem by running the Windows 7 recovery mode and either loading a recovery point or running the auto-repair utility. Once it is done running, upon restart, it will load Windows without a hitch.
-I have never had an issue with stability or any crashes once the system makes it into the Windows desktop, and i've had it running overnight multiple times.
-I have run the Western Digital Disk diagnostic utility on both Hard Drives, using the 'extended' test, and have come back with no errors.
-I have run memTest86+ for 14 hours, and encountered a single error.
-I flashed the BIOS of the motherboard to the latest version.
-I have installed Windows multiple times on both hard drives, and have had the same error with both (although for more than a week i had no problems with the 'Green" drive.
-The crashes seem to happen after letting the computer sit for a long period of time, like overnight, for example. I very rarely have trouble restarting multiple times immediately after running the Windows 7 repair utility, but it will crash the next day after no changes to the system.
-I installed a fresh copy of Windows on the Caviar Black drive and only installed the Windows updates, refraining from installing ANY 3rd person drivers, and it crashed after letting it sit overnight.
I'm pretty much stumped at this point. Some of the issues are really confusing me; especially that it seems to crash after letting the computer sit for awhile, and that it only crashes during windows startup. I'm running out of things to test.
What would you all recommend as far as further tests, or likely causes? I'm having trouble believing it's hardware at this point because it never has trouble once i'm booted up into Windows, and the startup repair utility is able to fix the issue consistently (albeit temporarily). However, a clean install of Windows with nothing installed except the windows updates suffered the same issue. I'm no expert with computer troubleshooting, but this seems like a tricky one to diagnose.