I've been plagued with a persistent booting error that really has me stumped. I am reasonable tech literate, but I know someone here likely knows a hell of a lot more and probably experienced this themselves. Here is the issue and the background.
System: An HP Pavillion 9000 desktop with some upgrade parts (RAM and video card) origially had WIndows 7 and has since been upgraded to 8.1
Recently I was having a drive issue. I replaced the drive with a new one. I have a Windows 2012 server so I just restored to the new drive. All went well. THEN THE TROUBLE BEGAN.
Out of nowhere on restarts I would get an error that a device was not able to be located and I could restart or use other start options. I could go to F8 and safe mode and get in with no issue.
None of the Windows 8.1 quick fixes worked. I then started to think the issue was the previous disk had a restore partition from HP (a D: drive). I had not partitioned the new drive. So I went back in, wiped it, partitioned it and named it the same thing (REPAIR_PARTITION) and ran the Server restore again restoring the C drive and the D drive HP restore partition.
Things looked good.
But throughout the next few weeks I continually have the same issue. On a restart I get a BSOD and the generic error message
RECOVERY
Your PC couldn't start properly - a required drive isn't connected or can't be accessed.Error code 0xc))))))e
You'll need to use the recovery tools on your installation media. If you don't have any installation media copntact your system administration
Press Enter to try again
Press F8 for Startup settings
I end up going through all kinds of things and nothing works - and then I end up with 8 hours of restoring form the server again.
I have a sneaking suspicion this is somehow related to a custom boot sequence and that D partition. The reason for this is because this usually happens after the computer tries to restart and then just stops three times. This is usually what triggers Windows 8 to go to recovery. I noticed the error message starts with RECOVERY.
I think maybe Windows wants to go to that partition to access the Windows repair stuff.
I don't know. But the bottom line is that every restart is a gamble and I am at my wits end.
It is the same set of error message and I can also get to safe mode, but it won't reboot to windows.
Very frustrating. Any info and assistance would be appreciated.
System: An HP Pavillion 9000 desktop with some upgrade parts (RAM and video card) origially had WIndows 7 and has since been upgraded to 8.1
Recently I was having a drive issue. I replaced the drive with a new one. I have a Windows 2012 server so I just restored to the new drive. All went well. THEN THE TROUBLE BEGAN.
Out of nowhere on restarts I would get an error that a device was not able to be located and I could restart or use other start options. I could go to F8 and safe mode and get in with no issue.
None of the Windows 8.1 quick fixes worked. I then started to think the issue was the previous disk had a restore partition from HP (a D: drive). I had not partitioned the new drive. So I went back in, wiped it, partitioned it and named it the same thing (REPAIR_PARTITION) and ran the Server restore again restoring the C drive and the D drive HP restore partition.
Things looked good.
But throughout the next few weeks I continually have the same issue. On a restart I get a BSOD and the generic error message
RECOVERY
Your PC couldn't start properly - a required drive isn't connected or can't be accessed.Error code 0xc))))))e
You'll need to use the recovery tools on your installation media. If you don't have any installation media copntact your system administration
Press Enter to try again
Press F8 for Startup settings
I end up going through all kinds of things and nothing works - and then I end up with 8 hours of restoring form the server again.
I have a sneaking suspicion this is somehow related to a custom boot sequence and that D partition. The reason for this is because this usually happens after the computer tries to restart and then just stops three times. This is usually what triggers Windows 8 to go to recovery. I noticed the error message starts with RECOVERY.
I think maybe Windows wants to go to that partition to access the Windows repair stuff.
I don't know. But the bottom line is that every restart is a gamble and I am at my wits end.
It is the same set of error message and I can also get to safe mode, but it won't reboot to windows.
Very frustrating. Any info and assistance would be appreciated.
