Windows 10: Cannot boot after BSoD "INACCESSIBLE_BOOT_DEVICE"

Hi, I got a bluescreen with "INACCESSIBLE_BOOT_DEVICE" this morning and haven't been able to boot my laptop since (build version should be 19041.1081 I think?). I woke up the laptop from standby as usual and was greeted by the programs I had last used, but none of my input devices worked: neither my USB mouse nor the builtin trackpad or keyboard. The system itself appeared to still be running as I saw the network icon change from no access to wireless and finally wired access. I tried going back to standby and hitting power again to the same results. So finally I reset the laptop by holding the power button down until it turned off. This happened once before and was resolved by powering down and back up. But this time - and ever since - I got the aforementioned bluescreen. The SSD with Windows on it doesn't seem to be defective, it still shows up in BIOS, I can access it via CMD and chkdsk finds no problems. I haven't installed any new hardware or connected new USB devices recently, so my assumption is that some Windows update is the culprit (I found one whose installation date was the previous day, more on that later). Booting from a newly created Windows 10 usb stick (using Windows Media Creation Tool), I tried numerous things to no avail: Before starting the list: I don't have any system restore points or system images or other pre-existing backups - I know. Startup Repair - returns "Startup Repair couldn't repair your PC"Uninstall Updates - both "latest quality" and "... feature updates" fail with "We ran into a problem and won't be able to uninstall the latest quality/feature update of Windows"sfc /scannow - ends with "Verification 100% complete" and "Windows Resource Protection could not perform the requested operation"chkdsk c: /f - shows "no problems" and "no further action required", but also "Failed to transfer logged messages to the event log with status 6."dism /Image:c: /Cleanup-Image /RestoreHealth completes successfullythe entries for Boot Manager and Boot Loader from bcdedit show correct identifiers and partitions bootrec /fixmbr works, but bootrec /fixboot returns "Access denied", and bootrec /rebuildbcd returns 0 found Windows installations. If I run bootsect /nt60 sys first bootrec /fixboot succeeds, but doesn't help with the underlying problemC:\Windows\System32\config\RegBack is emptyusing list volume in diskpart (on the correct disk) shows none of the partitions as BOOT or SYSTEM, the small FAT32 partition is Hidden and I tried assigning it a letter, formatting it (FAT32 again) and running bcdboot C:\windows /s N: /f UEFII also booted a Macrium Reflect 7 stick and tried the the option to repair startup or boot problems to no availother recommendations online involving ren c:\boot\bcd bcd.old fail because I don't have C:\Boot\using dism, I found one update package (package_for_servicingStack~31bf3856ad364e35~amd64~~19041.1081.1.2, seems to be related to KB5003690) installed the day before and tried to remove it but couldn't because it is marked as permanent Naturally, I would like to avoid reinstalling Windows (that laptop contains my master's thesis code and development environment and is the only machine I have powerful enough to run the Virtual Reality stuff I need for it). So my first question is if there's anything else I can try to fix this. In the increasingly more likely seeming case that I have to bite the bullet and reinstall, how can I minimize having to reinstall / reconfigurate programs afterwards? Please help me, I'm getting very desperate

:)

 

Windows BSOD loop: "INACCESSIBLE_BOOT_DEVICE" after repartitioning and installing Ubuntu Gnome

Windows 10 x64 v1607 won't boot after I reprtition my single 1TB HDD and installed Ubuntu Gnome 16.04.1 LTS amd64. it keeps doing a BSOD "INACCESSIBLE_BOOT_DEVICE".

My exact steps:

1. Boot from Ubuntu Gnome 16.04.1 LTS amd64 on USB drive.
   
2. 'Try Ubuntu Gnome' option.
   
3. Shrink Windows partition from 850GB to ~= 350GB in GParted.
   
4. Move recovery partition (I have created a System Repair Disk) (also in
   GParted)
   
5. Create new ~=350GB FAT32 Partition.
   
6. Use Ubuntu Gnome installer; use 'install alongside Windows' option. Installer succeeds.
   
7. Restart. Grub menu comes up, select Windows. Windows shuts down. I didn't see exactly what happened, but I came back and my PC was competely off. Turn back on.
   
8. Grub comes back, Windows again. Windows bluescreens with 'INACCESSIBLE_BOOT_DEVICE'. Restarts. Automatic Repair fails. Restart.
   
9. Choose Windows at Grub again. Same bluescreen. This time no Automatic Repair - just shuts down.
   
10. Choose Ubuntu Gnome at grub. Boots successfully.
    
11. Restart, choose Windows. Again, bluescreen, no automatic repair.
    

I can access my Windows partition from Ubuntu Gnome. I created a Restore Point before I started the steps above. Can I use my Restore Point, and if so, how? Or should I use my recovery drive? Or get a fresh Windows image and reinstall?

 

INACCESSIBLE_BOOT_DEVICE after Windows Update


My Windows 10 Pro PC received the latest round of updates, and when it restarted, it bluescreens with the error INACCESSIBLE_BOOT_DEVICE.

I did a system restore to a previous restore point, and everything booted and ran perfectly, but of course it then goes out to get the latest updates, and the same thing happens with it bluescreening and throwing the INACCESSIBLE_BOOT_DEVICE error.

I followed many suggestions from a Google Search including disconnecting all drives other than the boot drive, running chkdsk /f on the boot drive, allowing Windows 10 to "auto-fix startup problems", and several other things, and it always bluescreens.

I temporarily disabled the Windows Update service so it doesn't go out and auto-grab the updates, but at some point, I will need to apply updates, and I expect future updates to result in the same bluescreen error.

Suggestions?

 

ughhh! BSOD on boot

I guess my computer BSOD on boot right before getting to windows. not sure what the problem is though, everything is stable.

It gave me a list of two files in windows that could have caused the problems