Able to load to bios, then: "Inaccessible Boot Device"

thetylero

Reputable
Jan 5, 2015
59
0
4,640
After many hours of fiddling with the system to get it to show a video feed, i have finally been able to load into bios. Now, the system will not load into Windows.
 
Solution



Backing up a system image to one of the other drives right now.

Also, it turns out that my ram played a part in all of this. I had it overclocked from 1333 to 2400(the kind i bought was meant for this, i bought it as 2400 but it said you had to do the OC yourself, so i did.) on day one and it has worked fine for well over a year now. But, recently it has decided that i...


Yup. The drive is named and set as the first boot device.
 
on another pc, download this and create a bootable win 10 USB or DVD: Win 10 Media creation tool

change boot order so that usb or dvd first, HDD second
boot into installer, on screen after language choices, select repair this pc, not install
follow these steps:

1. At the blue screen, click Advanced Options
2. Click Troubleshoot
3. Look for a Startup button, I forget its proper name
4. A list of boot options is displayed
5. Click Restart
6. Upon restarting you'll be taken to the boot options you previously saw in #4
7. Boot into Safe Mode only
8. Once you're back into your desktop through Safe Mode, Reboot your PC and everything should be back to normal
TLDR: Boot into Safe Mode, then Restart your PC

http://www.tomshardware.com/forum/id-2760985/inaccessible-boot-device-reset.html

Steps 1 & 2 are in reverse order, it should be troubleshoot, advanced, but rest is right :)

see if that helps.
 


I already did this with my Win8 ISO. Booted, Repair this PC and it was unable to solve it and told me to just restart once again.
 


Worst comes to worst, i can get to W10iso. And yes, the W8iso loads up and i can get to the blue screen.
 
better than nothing,

how about try troubleshoot/advanced/start up repair

also try troubleshoot/advanced/command prompt and type Chkdsk /f /r (spacing is needed)

The INACCESSIBLE_BOOT_DEVICE bug check frequently occurs because of a boot device failure. During I/O system initialization, the boot device driver might have failed to initialize the boot device (typically a hard disk). File system initialization might have failed because it did not recognize the data on the boot device. Also, repartitioning the system partition or installing a new SCSI adapter or disk controller might induce this error.
This error can also occur because of incompatible disk hardware. If the error occurred at the initial setup of the system, the system might have been installed on an unsupported disk or SCSI controller. Some controllers are supported only by drivers that are in the Windows Driver Library (WDL). (These drivers require the user to do a custom installation.)

https://msdn.microsoft.com/en-us/library/windows/hardware/ff559218%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

http://appuals.com/best-fix-steps-to-fix-inaccessible_boot_device/
 




"The type of file system is NTFS.
Cannot lock current drive.
WIndows cannot run disk checking on this volume because it is write protected."

update: i've been working on my system for 5 hours now. I've had enough for today, and i appreciate your help. Will try again tomorrow.
 
Sure, i am helping you, i don't expect you to be here :)

Sorry I couldn't give you an easy answer, I wish there was one besides do a fresh install as that does fix it.. painful though.

you can try doing a reset of win 10, that is on the page next to troubleshoot.

why did you mention locking drive? or is that an error from windows as sometimes it locks the drives itself: http://www.thewindowsclub.com/the-drive-where-windows-is-installed-is-locked
 



I would like to avoid a reinstall.
I quoted the error that was given to me in command prompt after I entered the "chkdsk /f /r"
 
I just did a Google search on "write protected hdd" and came up with a PC World magazine article with a pretty simple fix. Here's the link:
http://www.pcworld.com/article/245174/restore_access_to_a_write_protected_hard_drive.html .

I'm curious to know how a hard drive becomes write protected because I've never seen this happen. My guess is that maybe Windows sets it that way when it's doing certain updates and the computer is somehow shut down before it completes. Anybody have any insight?

Good luck.
 


Not sure if this is a factor in all of this, but the OS drive is an SSD. I will read the article and update again.
 


Alright, good to know. I am unable to get it to display once again, and i'm really not sure what to do.
 
Well are you ready for a "hammer and tongs" solution? Since you have an SSD and a HDD, what I'd do would be to make a new partition on the HDD (maybe 50 GB) and install Windows 10 in that. It doesn't have to be anything more than the minimum install, just something to get you up and running. Then you'd be able to apply the solution in the article without having to lose anything on the SSD. I'd think you could do that in under 2 hours; it seems like the minimal install to a HDD took me about an hour the last time I did it.

Good luck.
 


I will take this step as soon as i can, but, for the time being, i can't get it to give a display signal.
 



I can't even load into bios at this point. No display whatsoever, no matter the configuration. I removed all the drives, removed the GPUs, disconnected fans, everything. Will not display.


update: taking a lunch break.
 



Alright, i'm back now. It came up and displayed one time and then locked up on me.

 


Well, the PSU i ordered will be here to tomorrow and we will go from there.