Windows 10: INACCESSIBLE_BOOT_DEVICE BSOD

Hello, I’ve recently ran into a problem where my computer is stuck in a BSOD loop. The error code is INACCESSIBLE_BOOT_DEVICE, as mentioned in the title. I have tried using an installation media USB and running chkdsk /F, system startup repair, bootrec commands, sfc /scannow and even a system restore point, all leading to the same unfortunate result. The last option I had was this solution from another forum post: Here. I followed the steps well and removed one of the RollupFix patches, however, I seem to be unable to remove the other one Package_for_RollupFix~31bf3856ad364e35~amd64~~1

:)

 

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?

 

Moving to RAID 0 - INACCESSIBLE_BOOT_DEVICE


I am converting an existing Windows 10 Pro laptop to RAID 0 - and I keep getting to the final boot where it says INACCESSIBLE_BOOT_DEVICE. What am I doing wrong? The laptop has two 1 TB Samsung 850 SSDs that are identical. Laptop is a HP Zbook 17.

Here are my steps:

1. Made a good System Image of C: drive on separate external SSD drive connected by USB. D: drive didn't have anything on it to be saved.
2. Used Win 10 Pro DVD to delete all partitions/format drives.
3. Went into BIOS and changed from AHCI to RAID, and also to turn on ability to do Control-I to get to Intel RST ROM.
4. Rebooted, did Control-I, created a RAID 0 of the two disks.
5. Rebooted, installed Windows 10 fresh. Verified it would reboot on its own.
6. Rebooted, went into Repair on Windows 10 DVD. Selected external SSD image to do image restore from.
7. Rebooted - verified on Control-I that the RAID 0 array is listed as "bootable"
8. Rebooted - get INACCESSIBLE_BOOT_DEVICE.

The place it dies - I see the little Windows 10 blue window, and the spinning circle at the bottom - then I get the blue screen with the message.

I think I listed everything I did - what am I missing?

 

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?