[SOLVED] boot_device_inaccessible BSOD, DISM & SFC refuse to work

[jessisastupid]

Hey all, I'm sure somebody has had this problem already, but i haven't been able to find a solution and i've been cracking at it for some 12 hours. I've always solved this issue (the several times it's happened before...) by reinstalling windows entirely, but tomorrow I have to record and i can't afford to reinstall.

I've been completely unable to get into windows save for my secondary drive's OS, and at this point I'm convinced I've tried everything. I've tried uninstalling latest packages through DISM (through windows built-in troubleshooter AND a ESD usb,) received an error code 2, moved on to trying to use SFC to fix DISM, however, i receive a "could not perform the requested operation" error, I've tried chkdsk (on multiple occasions) with no errors reported, I've even tried resetting windows through the troubleshooting menu, and it simply told me that it couldn't.

I'm sure its not the hard drive itself considering i can access it through the command prompt in the troubleshooting menu, make directories, write to files perfectly fine, and chkdsk /f /r returns zero errors. (although i have not gotten around to running a S.M.A.R.T scan) and I have no restore points or images. I've put the logs for SFC, DISM, and the automatic repair in a paste bin (linked below, I can also attach it if that's preferred.) I can supply other logs if requested, just let me know.

Possibly related side-note, my motherboard has been known to jostle SATA cables loose from time to time, and as a result disconnects my hard drive not uncommonly. I also noted some sounds of drive clicking, and some 1-2 minute freezes the day before, similar to those that would occur if you were to suddenly disconnect the drive a program is running on.

If anybody could point me to a thread in which this problem was solved or help solve this issue, that would be greatly appreciated. Thanks in advance.

SFC Log Dism Log Autorepair log
(let me know if there's any problems with the logs, pastebin has been buggy for me for some reason.)

 

[kerberos_20]

hi
CBS logs points to X:\windows for windows PE
Dism logs points to E:\windows for normal windows


how about you disconnect one of those and try repairing again?

 

[jessisastupid]

hi
CBS logs points to X:\windows for windows PE
Dism logs points to E:\windows for normal windows


how about you disconnect one of those and try repairing again?

Thank you for the quick reply, how would i go about disconnecting X, exactly? E: is my main windows install, it'd be counterintuitive to disconnect, i think. and X: isn't a drive i've attached, it's just the drive assigned for recovery by windows. (if this example makes more sense then my poor wording, if i press command prompt in windows recovery mode, it loads on X:\windows\system32\cmd.exe)

 

[kerberos_20]

okay, then u need to run this:
sfc /scannow /offbootdir=E:\ /offwindir=E:\windows

 

[jessisastupid]

okay, then u need to run this:
sfc /scannow /offbootdir=E:\ /offwindir=E:\windows

Tried running this, got the same error, 'windows resource protection could not perform the requested operation'

It didn't even attempt to verify this time, like it usually does, it simply auto-failed.

 

[kerberos_20]

is that E: mounted?
type E: if you get to E: partition

if yes, then you might have some access isue with WinSXS folder (SFC needs it)
ICACLS E:\Windows\winsxs

if not, its probably mounted as C:
in that case, commands will need to change with C letter
sfc /scannow /offbootdir=C:\ /offwindir=C:\windows

 

[jessisastupid]

is that E: mounted?
type E: if you get to E: partition

if yes, then you might have some access isue with WinSXS folder (SFC needs it)
ICACLS E:\Windows\winsxs

if not, its probably mounted as C:
in that case, commands will need to change with C letter
sfc /scannow /offbootdir=C:\ /offwindir=C:\windows

Yup, definitely mounted as E: (well, it's mounted as D: now, but i know exactly what drive it is.) navigated to my user downloads folder and found a file i downloaded just yesterday onto the drive, and the only other two available volumes are a system partition and a 517 hidden partition that's unlabeled.

Here's the output from icacls, it reads "D:" in this because i removed all of my secondary drives, just to be sure, and it assigned D: to this drive after a restart.

D:\Windows\Winsxs NT SERVICE\TrustedInstaller:(OI)(CI)(F)
                  BUILTIN\Administrators:(RX)
                  BUILTIN\Administrators:(OI)(CI)(IO)(GR,GE)
                  NT AUTHORITY\SYSTEM:(RX)
                  NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(GR,GE)
                  BUILTIN\Users:(RX)
                  BUILTIN\Users:(OI)(CI)(IO)(GR,GE)
                  APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(RX)
                  APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)
                  APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(RX)
                  APPLICATION PACKAGE AUTHORITY\ALL RESTRICTED APPLICATION PACKAGES:(OI)(CI)(IO)(GR,GE)

Successfully processed 1 files; Failed processing 0 files

Possibly related information, the command prompt window is in administrator mode (It quite literally reads Administrator: X:\windows\system32\cmd.exe)

 

[Colif]

X is a ram drive windows creates for the purposes it uses it for.

I also noted some sounds of drive clicking, and some 1-2 minute freezes the day before, similar to those that would occur if you were to suddenly disconnect the drive a program is running on.

you sure drive works still? might be an idea to back it up and replace if its been known to disappear.

boot drive inaccessible can also happen if the boot method has swapped

just thought i mention it

 

[jessisastupid]

you sure drive works still?

Almost certain. it's (as far as i can tell) a brand new drive, its far too early for it to be dead yet. And, i've been able to access and use it on several occasions, just not boot from it. I know drive clicking is a sign of death but It seems to be running just fine.

And i've had this issue happen before, on this particular motherboard. Twice, I think. It's always fixed itself whenever I just reinstalled windows, so i presumed its just corruption i let get out of hand.

might be an idea to back it up and replace if its been known to disappear.

I don't think it has anything to do with the drive, it's gotta be the mobo. It's happened to several drives before this, the SATA connectors are faulty or something and need to be adjusted occasionally, and i guess that causes problems on the drive's end?

boot drive inaccessible can also happen if the boot method has swapped

I've considered it but i'm not exactly sure where this would come into play. The error wouldn't happen if the MBR was incorrect, would it?