[START-UP ERROR] Cannot Boot Windows 7

CustomerSupport

Commendable
Apr 24, 2016
5
0
1,510
Hello,

I am having issues starting up my Windows 7 due to "the boot selection failed because a required device is inaccessible".

Some background information:
I was having some issues earlier with bluestacks loading and occasionally I found a way to fix it without it going to bluescreen. With much testing (and bluescreening) it was a roughly 40% chance for it not to bluescreen and to work fine. I believe I may have screwed something up by bluescreening my computer so much... in any case, the final bluescreen occurred and I got the above message and the computer wouldn't start Windows 7.

Present information:

  • 1. I have scoured the internet to a certain degree trying to find some fixes, but I was not able to find anything pertaining to my issue (usually it was about something else or similar, but not the same; I have tried those steps as well, but I fear I may be worsening the situation)
    2. I have followed the instructions on the error screen to put in a windows disk and to try startup recovery. (I have tried to repair the startup, but it has come to my understanding it is trying to repair the E: drive (where the windows disk is) instead of the actual windows boot - is this normal?)
    3. I have performed chkdsk on my C (HDD) and D (SSD, where my windows is located) drive. Both drives stated that there were no errors and is fine. I am running 2 harddrives and I read this may have an effect on repairing the boot...
    4. On F8 there is no use last known method or safe mode, it just gives me boot options.
    5. I have moved the boot priority around so that it boots from disc first (this solved the issue where it kept saying, in the windows 7 repair window, that the disc was not compatible.
    6. Windows boot manager is on the D: drive and the boot loader is on the E: drive. (It's not unknown)
    7. The scannow command constantly says that a repair is scheduled and I need to restart the computer, but the computer can't even get past the error screen to activate the schedule so it is a loop of asking me to restart.

Possible causes/solutions:

  • - With respect to point 2 listed above, is there anyway to have the startup recovery repair the D: drive instead of the windows disk? As mentioned in point 3, both drives are fine and there were no detected errors. I'm thinking I may have to run one of those create a new startup (not the masterboot), but am not sure if this would screw up a simple problem.
    - Is there something wrong with point 6?
    - I've read that I could reinstall windows on my HDD and the files in the HDD would just be named windows.old, but the files would still be there. Would my issue still be here because I'd still have the previous windows error? I'd like to refrain from this action as it may complicate things further.

If my descriptions are not detailed enough, please let me know and I can attach some pictures I took to supplement the information.

Thank you for taking your time for reading and providing assistance!
 
"2. I have followed the instructions on the error screen to put in a windows disk and to try startup recovery. (I have tried to repair the startup, but it has come to my understanding it is trying to repair the E: drive (where the windows disk is) instead of the actual windows boot - is this normal?)"
.......this is definitely not normal unless ur boot files are divided between d drives...tht is why it is always suggested to install windows with only d target drive connected......

"3. I have performed chkdsk on my C (HDD) and D (SSD, where my windows is located) drive. Both drives stated that there were no errors and is fine. I am running 2 harddrives and I read this may have an effect on repairing the boot... "
...........install Hard Disk Sentinnel and see whats going on with d disks...ur several BSOD experiments might have messed up d disks...

"4. On F8 there is no use last known method or safe mode, it just gives me boot options."
.........that is usually not a good sign...it might indicate a corrupted boot sequence...

"6. Windows boot manager is on the D: drive and the boot loader is on the E: drive. (It's not unknown)"
.........according to my experience, ths is not ideal...as i mentioned on point 2....

u can try to repair, but according to ur vivid details, it seems like ur system files r totally messed up...not sure how much it ll repair...
if i were u, ideally i wud be looking for a clean install...
 

CustomerSupport

Commendable
Apr 24, 2016
5
0
1,510
Thanks for your response Hellfire13.

In response to your responses:

Some more background info: The computer was setup at a store, I had paid them to build it and install windows on it when I picked out all the parts.

Are you sure my boot files are divided? I had asked them initially to install my Windows on the SSD for quick startup. The E: drive is where the windows disk was inserted and it seems to be picking that up. I only have 2 drives and that is the C and D; E is the windows disk.

I can't install anything on the computer anymore because it currently can't start up. I'm currently using another desktop temporarily. Since my D drive may be messed up, can i just reformat it and reinstall windows on that? Logically, it seems like it should work as the D drive is ONLY for windows .

Please see some attached screenshots that I took with my phone for the present error.

http://imgur.com/a/NBgeE
[It's a gallery]

As mentioned previously, the start-up repair on the windows disk doesn't seem to do anything, the screen still stays the same upon restart. Is there any command prompts which I can perform to fix? I can provide more screenshots if it helps narrow down the issue.

Again I thank you for taking your time to help! I really appreciate it :D

 

CustomerSupport

Commendable
Apr 24, 2016
5
0
1,510
I`m going to see if anyone else has something to add before I go that route.

Going to that as the last solution, if I were to do that, I should reformat the Disk 1 Partition 2 right (please refer to the last image on imgur)? Taking another look at Disk 1 Partition 2, it says that the free space is the same as the total space... I am pretty sure that it should be the one where my windows drive is loaded onto...
 
"Is there any command prompts which I can perform to fix?"

In response to that, i would suggest...if u can manage to enter d command screen, u can try to run the following 2 commands...

chkdsk /f/r

sfc /scannow

Tips & More Information

When running sfc /scannow from outside of Windows, like from the Command Prompt available when you boot from your Windows disc or flash drive, or from your System Repair Disc or Recovery Drive, you'll have to tell the sfc command exactly where Windows exists, as in this example:

sfc /scannow /offbootdir=d:\ /offwindir=d:\windows

The /offbootdir= option specifies the drive letter, while the /offwindir= option specifies the Windows path, again including the drive letter.

Note: Depending on how your computer is setup, the Command Prompt, when used from outside of Windows, doesn't always assign drive letters in the same way that you see them from inside Windows. In other words, Windows might be at C:\Windows when you're using it, but D:\Windows from the Command Prompt in System Recovery Options.

 

CustomerSupport

Commendable
Apr 24, 2016
5
0
1,510
Hello Hellfire13, I did the chkdsk /f/r for both the C and D drive, it came back saying nothing wrong was detected. Is this normal or does that just mean my drives are perfectly fine?

If that does mean the 2 drives are fine, is it safe to assume that sfc /scannow will attempt to mend the windows startup file?

Since my C: drive is rather large, it has taken a few hours to finish the chkdsk; I will proceed with the sfc scannow tomorrow to see what information it will bring up. From my understanding of previously using sfc /scannow, originally without inputting the offbootdir or offwindir paths, it default stated that a repair was schedule, please restart your computer (I believe this was brought up from the initial repair startup that I clicked on the windows drive). Does this have any effect on future sfc /scannow on the d and c drives? Could you help me understand as to why the windows disk startup repair attempts to repair the startup of the disk instead of the system?

Thanks!



EDIT: I just did the sfc scannow just now and the error came up for the offwindir and offbootdir stating that windows resource protection could not start the repair service. Could you please look at a few of the screenshots I took?

http://imgur.com/a/r6aj7

The first pic is the scannow results
Second and Third pic is the startup repair from the disk (as you can see it is not repair the system it seems....)
Fourth is the results for chkdsk D drive
Final and fifth is the results for the chkdsk and C drive
 
ok...first of all...i am not able to open d link right now due to sum issue...i ll have to check tht later...
secondly to get back to ur sfc query...sfc is system file checker, and it will mend all system file related issues including startup...
but it will do only that...it will first try to locate where the system file is and then do a integrity investigation of each system file...
d reason it could not initiate is bcoz maybe it could not locate ur windows boot files...

"Could you help me understand as to why the windows disk startup repair attempts to repair the startup of the disk instead of the system?"
windows startup repair is a utility that tries to rectify issues related to windows booting process...it has got nothing to do with the drive itself...
its effect is only on the boot files and their initiation...

now...
chkdsk is a gud utility but it may not always reflect d true integrity of a hdd...when i had issues, chkdsk returned perfect results for me but it didnt solve d problem...later on when i substituted d disk anyway...i realised there was a drive issue...

if u can...
i wud suggest tht u detach the D drive, where u said ur windows is supposed to be...then attach it to ur other desktop and check whether it boots or sfc scanow initiates successfuly...also install hard disk sentinnell on the other computer and check d health of d drive...
 

CustomerSupport

Commendable
Apr 24, 2016
5
0
1,510
Is there any other option than to remove the drives and to switch them around? I'd really like to avoid removing stuff just incase I screw things up even further. Have you had a chance to look at the imgur galleries, perhaps there is something wrong there which can be fixed through commands?
 
i dont see very many options here unless someone else suggests sumthng else...
if u r not confident with d hardwares inside d cabinet, i wud suggest that u refrain from doing it urself n seek professionsl help from a proper shop...
i am sorry, i didnt get d opportunity to see d images yet...i ll revert back to u once i see thm...