Windows 10: BSOD on boot: inaccessible_boot_device (Windows 10)

Hi all, I recently disassembled my computer to clean it since it gets very dusty. For reference, this is not the first time I've taken my computer apart; I know how to correctly take it apart and put it back together. I made sure everything was connected properly and that nothing was broken/damaged. However, I think in the process, I must have somehow reset my BIOS in some weird way. Now, when I try to boot back into windows, i get a blue screen, a big frowny face, and the error: "inaccessible_boot_device".I know for a fact that I put everything back together the right way since I also have a 100gb Debian dual boot setup with GRUB bootloader, and I was able to boot into my Debian just fine, and everything works exactly as it should. I tried running the GRUB auto configuration thing, and it says it's able to find the windows .efi or something, but it doesn't change anything; the same inaccessible_boot_error appears when I try to boot into Windows.I've tried the diagnostic tools in the advanced recovery options, but nothing works. I'd like to avoid having to reset my entire computer if I can, so please, does anyone have any suggestions? Also, here is a snapshot of my system specs (taken from my Debian https://i.gyazo.com/140cbf51196718c9...d24d71b7d3.png

:)

 

BSOD during boot every other time

Auggy,

Problem is linked to the Intel chipset SATA AHCI RAID controller driver (an ICH10R on my motherboard). Something goes wrong between it and Windows 10. I've seen this BSOD once at boot time: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (iaStorA.sys). Therefore,
I've upgraded the "Intel® Rapid Storage Technology (Intel® RST) RAID Driver" from 14.5.0.1081 to 14.6.0.1029, which then led to a systematic INACCESSIBLE_BOOT_DEVICE BSOD.

To fix the INACCESSIBLE_BOOT_DEVICE, I've restored my system to its previous point, thanks to a Windows 10 iso.

As something fails with my internal RAID 1 array at boot time, on which my system disk is hosted, it explains why nothing can be written on system logs.

For now, I'm torn: rolling back to Seven and waiting for a compatible driver release before trying to upgrade again to Windows 10, or keeping the 14.5.0.1081 driver and staying with the every other time BSOD at boot time. Hum hum...

Note: FYI, driver download link is Télécharger Pilote et l’Interface de la Technologie de stockage Intel® Rapid

 

Spaceport.sys missing or corrupted

Hi,

I recently booted into this Linux DVD to try it out. I was trying to mount the c:\ drive and it told me to run this command. I ran the command, and then rebooted back into Windows. I get a BSOD (INACCESSIBLE_BOOT_DEVICE) or (KERNEL_DATA_INPAGE_ERROR spaceport.sys).
Can someone help me fix this?

Thanks.

 

Assuming you have a UEFI partition check your BIOS settings and make sure the boot device is set to Drive C: Windows Boot Manager.

If it's not UEFI then just change the boot option priority to C:

 

Hi shadowfreud,

Welcome to the 10forums *Smile

Could you check in the BIOS if you see the storage device?