Bsod loop due to full disc, stop code inaccessible device.

Maskandmirror · 08 Sep 2019

Posting here since it involves bsod, but unfortunately I can't follow the usual posting guide as logging is impossible.

I came home today to find my pc powered off, because an electrician came and turned off the power in the house for a while.
Turning it on, it loops between the stop code 'inaccessible boot device' and the automatic repair screen. The computer won't start in safe mode either, and also when I tried to reset Windows it says there isn't enough space on the disc.
Seems to be identical to the problem stated here, but unfortunately op didn't return to the thread and it got closed! Everything that happened in the thread matches my case.,except that I'm using the current version of Windows 10 64bit.

https://answers.microsoft.com/en-us/...3-01f6b8fa0ca3

It's probably true that there isn't enough space, is there any way I can just clear some files from the command prompt to get it to work again? Or using a USB drive? Or perhaps a way to connect with a laptop to clear some space?

Thanks for reading!

Ztruker · 08 Sep 2019

See here: Windows 10 Recovery Tools - Bootable Rescue Disk from KYHI

It allows you access to a non-working system - and provides a visual means to repair the system You would have to download the ISO and then burn it to USB or CD to create a bootable WinPE disk.

It will allow you to backup your system to an external hard drive (buy one if you don't have one, $50 online). Also allow you to delete files from your hard drive to hopefully free up enough space to do things.

The first thing you need to do is run chkdsk /f /r against your Windows 10 partition. You can find out what that is using Kyhi's rescue ISO also. That in itself may resolve the problem. If not you can try Macruim Reflect's boot repair tool that is also on Kyhi's rescue iso.

Maskandmirror · 10 Sep 2019

Thank you for your response, it was very helpful!

I used the tool successfully to boot from an sd card. All the drives are accessible except the U drive which I think is the larger partition of the ssd on which windows is installed. It says it does not have a recognised file system and needs formatting when I run chkdsk or try to access it. I used the included tool to rescue the contents onto an external drive, which took most of a day. I guess the next step is to let it format the U partition? I'm not sure what will happen to the system once those files are gone, though it looks like the C partition is fine

Edit : actually I think I rescued the wrong drive. It's very confusing because the drive letters are all different from usual and there are some I don't recognise. I'm not sure how to proceed since I can't identify the drive that's not working

Ztruker · 10 Sep 2019

You Win 10 drive will have these folders on it at a minimum:

Program Files
Program Files (x86)
Users
Windows

Find that partition then run chkdsk /f /r against the drive letter assigned to it.

I label my drives so I know what each one is, no matter what drive letter it has.

Attachment 246967

I know this won't help you now but consider it for the future.

zbook · 10 Sep 2019

The drive letters often change in Windows Recovery Environment (RE).
There are multiple methods to identify the Windows drive.
One method is to open the Windows advanced troubleshooting menu > command prompt > enter drive letters then dir to view the contents of each drive.
Important files can typically be saved on drives with failure to boot unless there is drive failure or ransomware.
Inaccessible boot device may be able to be fixed by various troubleshooting steps.
Backing up files is an extra level of safety to protect the important files during troubleshooting.

Maskandmirror · 10 Sep 2019

Running chkdsk took a while and said it had made some file system repairs, but it has not made any difference to what happens when I try to boot the system normally.

Ztruker · 10 Sep 2019

Download KYHI's Windows 10 Recovery Tools - Bootable Rescue Disk and burn it to a flash drive. Boot it and run Macrium Reflect. Follow Macrium Reflect's Fix Windows Boot Problems directions to see if it will fix the Windows boot problem. Has done so for me on numerous Windows 10 systems.

Maskandmirror · 11 Sep 2019

I ran the tool as directed but strangely saying 'yes' to reboot the system didn't work. I tried again, same result, so I powered off manually.
On startup got the bsod again, but when it automatically restarted nothing seemed to happen - the computer is flashing its 'thinking' light and making the associated noises but no other hardware has initialised. Is it working on something related to Macrium? I'm scared to interrupt it

Ztruker · 11 Sep 2019

No, Macrium is no longer involved. Did you remove the Rescue USB flash drive? You could try booting it again, then open a Command Prompt and run chkdsk x: /f against the OS drive. Replace X: with the drive letter, which may or may not be C:

Easiest way to see is to use the dir command:

dir c:
dir d:
dir e:

Look for Program Files, Program Files (X86), Program Data and User folders. That will be the drive you want to run chkdsk against.

See if it fixes any file system errors. Try booting normally after doing that.

Maskandmirror · 11 Sep 2019

Okay, the result is a new bsod on booting the system normally. I'll try chkdsk through the USB bootable again. Errors 0xc0000001 and 0xc0000098.

I sometimes still get the old bsod, but with the difference that it does not restart the system when it says it will, and seems to just power off instead. I'm not sure that it turns off properly though as I can still hear noise from the computer.

Attached pictures of new errors. Should i make an install disc?

Edit: the system won't automatically boot from the USB anymore. Trying to do it manually but there are so many devices listed in bios I don't have any idea which it is.