New
#1
Mystery Start-Up Issue - Need Help Diagnosing
Short history:
Built a new rig from parts back in the Spring. It's been running beautifully for most of a year. Then, overnight, it started doing something strange. When I tried to start up, it would hit a BSoD loop. If I loaded the Win7 install disc and did nothing with it, just restarted from that. It would load up fine.
That went on for about a month while I was trying to figure out what the problem was. Then the issue shifted. The computer started loading directly to the BiOS. It recognized that the drives were there in theory, but wouldn't start the OS. I had done several scans and attempted fixes on the OS before this happened (not directly before), and assumed that this was just an escalation, so I decided to cut my losses, reformat the partition where the OS was, and reinstall Windows.
I did this, reloaded the needed drivers and software for my hardware, and everything was fine, for a week. Then one day the computer started up to the BiOS again. This time it didn't detect the HD containing the OS. I did some futzing and found that the problem was inconsistent, and just swapping cables would sometimes solve it. Once it's up and running it has no issues of any kind.
So, here's where I've landed now, and I'm thinking it may be hardware related, but I'm hoping the smart folks here can help me figure out where the hitch is.
When I try to start the computer, one of 3 things happens:
- The computer goes to BiOS and does not detect the main HD
- The computer tries to start windows, BSoD's and restarts to System Repair
- (After swapping some cables around) Computer puts up the WinXP load screen, BSoD's and if I restart from the Win7 install disc, the computer will start up fine
Once the computer has started up, none of the diagnostics are showing a problem. When Option 2 goes to System Restore it sometimes decides that the root cause was a "bad driver" or else says that it cannot find a problem. It can never find a restore point (though I've created ones when the computer started up properly).
It seems like the driver errors are more likely erroneous. It seems to make the most sense that the problem is somewhere with the drive, the SATA cable/handling, or mobo, but I have no idea what to do to trace the problem from here.
Any savvy folks around think they have an idea of what's going on?