Hello Siti Lestari
An INACCESSIBLE_BOOT_DEVICE stop error immediately after a storage configuration change is most commonly caused by a mismatch between the storage controller mode used when Windows was installed and the mode currently configured in firmware, such as switching between AHCI, RAID, Intel RST/VMD, or NVMe controller modes. The first thing I would verify is whether the BIOS/UEFI storage configuration was changed, because Windows may no longer be loading the correct boot-critical driver during startup.
If the system can be accessed through Windows Recovery Environment (WinRE), check whether the OS volume is visible using diskpart, list disk, and list volume. If the boot disk is not detected there, the problem is likely at the controller, firmware, cable, RAID metadata, or storage hardware layer rather than within Windows itself. If the disk is visible, inspect %SystemRoot%\System32\Config\SYSTEM offline and verify that the appropriate storage driver service, such as storahci, stornvme, iaStorV, or vendor-specific RAID drivers, is configured to start during boot.
I would also review C:\Windows\ntbtlog.txt (if boot logging was previously enabled) and the offline setup and recovery logs under C:\Windows\Panther\ and C:\Windows\System32\LogFiles\Srt\ for driver-loading failures. If the issue started immediately after modifying the controller mode, reverting the controller to its previous setting is typically the fastest validation method. When the root cause cannot be corrected directly, use WinRE Startup Repair, System Restore, or an offline driver injection procedure to restore access to the boot device and return the system to a bootable state.
If my answer is useful for you, please hit Accept the answer for me please.
HL.