You're stuck with a boot loop or 'No Boot Device' after a RAM or motherboard swap. I get it.
It looks like the hardware is fine, but the computer won't start. Usually, it's a simple firmware mismatch on your storage drive. Most people think it's a dead part. But more often, the drive's firmware is too old for the new motherboard or RAM settings.
The Fix: Update the Storage Drive's Firmware
Here's what you need to do. First, check the model and firmware version of your drive. You can do this from another PC or a bootable USB with a small tool like CrystalDiskInfo or the manufacturer's software.
Step 1: Identify Your Drive
On a working computer, connect your drive (if it's an internal SSD, use a USB to SATA adapter). Download and run CrystalDiskInfo. It's free and shows the model and firmware version. Write them down. For example, a Samsung 860 EVO might show firmware version RVT04B6Q.
Step 2: Find the Latest Firmware
Go to the drive maker's support site. For Samsung, it's the Samsung Magician software. For Kingston, Kingston SSD Manager. For Crucial, Crucial Storage Executive. For Western Digital, the WD Dashboard. Download the tool that matches your drive.
Step 3: Update the Firmware
Run the tool on the working PC with your drive connected. It will check for updates. If there's a new firmware, click update. Do not interrupt it. It takes maybe 10 minutes. Once done, shut down, put the drive back in your problem PC, and boot.
Example: Samsung Magician shows RVT04B6Q. Update to RVT04B6Q-03. This fixes a power state bug that causes DRIVER_POWER_STATE_FAILURE on some boards.Why This Works
Storage drives have their own tiny operating system called firmware. It talks to the motherboard's UEFI or BIOS. When you change RAM or the motherboard, the drive's firmware might not handle the new power states or memory timings. For example, a client had a 2TB Samsung 860 EVO that worked fine on an Intel Z370 board. He swapped to an AMD B550 board. The drive would boot once, then crash with error 0x0000009F. Updating the firmware fixed it. The old firmware didn't know how to handle the new AMD chipset's power management.
Less Common Variations
NVMe Drives
NVMe drives are more sensitive. If you have a WD Black SN750 and you move it to a new laptop, it might not show up at all. Update the firmware using the manufacturer's tool from a different machine. Sometimes you need to use a USB enclosure to flash it if the drive isn't detected.
Older SATA SSDs
Old drives like the Intel 520 series often have known bugs that cause boot loops on newer boards. Intel's Toolbox can update them, but Intel stopped supporting it. Use a third-party tool like Parted Magic or a live Linux USB with the nvme-cli command if it's NVMe. For SATA, you might need to boot from a CD-ROM (yes, that old).
RAID or Motherboard RAID Controllers
If you're using a RAID array, updating firmware can break the array. Always back up your data first. For hardware RAID, update the controller's firmware too, not just the drives.
Prevention - How to Avoid This
Before you swap a motherboard or RAM, check the drive maker's site for firmware updates. Do it before you start. Keep a bootable USB with the manufacturer's firmware tool handy. Also, update your motherboard's BIOS to the latest version. Some boards fix drive compatibility issues through BIOS updates. I've seen a 2021 BIOS update for ASUS X570 boards that directly addressed Samsung SSD power state bugs.
Pro tip: After you update the firmware, clear the CMOS (remove the battery for 30 seconds) before first boot. This forces the board to renegotiate the drive's parameters fresh.
If you don't want to mess with firmware, stick to drives from the same generation as your motherboard. A 2020 drive on a 2024 board might work, but it's a gamble. I've had clients with no issues for years, then a BIOS update breaks everything. Updating the drive firmware is the real fix. Don't waste time reinstalling Windows or swapping RAM sticks. Start with the drive's firmware.