Solved: NO BOOT DEVICE (0X00000053) BSOD Crash on Windows 10/11
The NO BOOT DEVICE (0x00000053) Blue Screen of Death (BSOD) is a critical error that prevents your Windows 10 or 11 PC from starting. This error indicates that the system cannot locate the bootable device, often due to hardware issues, corrupted files, or driver problems. If you encounter this issue, dont panicthis guide will walk you through diagnosing and fixing it step by step.
What Causes the NO BOOT DEVICE (0x00000053) Error?
The error occurs when Windows fails to detect or access your boot drive during startup. Common causes include:
- Loose or faulty SATA/IDE cables connecting the hard drive or SSD.
- Corrupted system files or registry entries.
- Failing or unrecognized storage hardware (HDD, SSD).
- Outdated or incompatible drivers (especially disk controllers).
- Malware or disk errors affecting the boot partition.
- Improper shutdowns or power outages during updates.
How to Fix NO BOOT DEVICE (0x00000053) in Windows 10/11
### **Method 1: Check Physical Connections**
If the issue is hardware-related, start by ensuring your storage drive is properly connected.
- Power off your PC and unplug it from the power source.
- Open the case (if comfortable) and re-seat the SATA data cable connecting your hard drive or SSD to the motherboard. Ensure its securely plugged in both ends.
- If using an SSD, try a different SATA port on the motherboard if available.
- Reconnect any power cables (SATA power) to the drive and ensure theyre not damaged.
- Reseat the RAM sticks (if comfortable) or test with one stick at a time to rule out memory issues.
### **Method 2: Run System File Checker (SFC) and DISM**
Corrupted system files can trigger this error. Use Windows built-in tools to repair them:
- Boot from a Windows installation USB (if you cant boot normally).
- Select “Troubleshoot” > “Advanced options” > “Command Prompt.”
- Run the following commands one by one, pressing Enter after each:
DISM /Online /Cleanup-Image /RestoreHealthsfc /scannow - Restart your PC and check if the issue persists.
### **Method 3: Run CHKDSK to Check for Disk Errors**
If the boot drive has errors, CHKDSK can repair them:
- Open Command Prompt as described above (from the Windows installation USB).
chkdsk C: /f /r
Note: Replace “C:” with your boot drive letter if different.
### **Method 4: Update or Reinstall Drivers**
Outdated drivers can cause this error. If you can access Safe Mode:
- Press Win + X, then select “Device Manager.”
- Expand “Disk drives” and right-click your storage device, then choose “Update driver.”
- If the issue persists, use a third-party tool like Snappy Driver Installer to reinstall drivers.
### **Method 5: Reset BIOS/UEFI Settings**
A misconfigured BIOS can prevent booting. Reset it to defaults:
- Restart your PC and enter BIOS (usually by pressing F2, F12, DEL, or ESC during startup).
- Look for “Load Optimized Defaults” or similar and select it.
- Save changes (F10) and exit. Try booting again.
### **Method 6: Test the Hard Drive**
If the drive is failing, back up your data immediately:
- Use a live Linux USB (e.g., Ubuntu) to check the drives health via terminal:
sudo smartctl -a /dev/sda - Look for errors like “Reallocated Sectors” or “Pending Sectors.” If found, replace the drive.
### **Method 7: Rebuild BCD (Boot Configuration Data)**
A corrupted BCD can cause this error. Fix it via Command Prompt:
- Open Command Prompt from the Windows installation USB.
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
FAQ: NO BOOT DEVICE (0x00000053) Questions & Answers
Q: Will this damage my data?
A: No, but if the drive is failing, back up critical files immediately. Use a live Linux USB to copy data before proceeding.
Q: Can I fix this without a USB bootable drive?
A: If your PC doesnt boot at all, youll need one. Create it using another computer with the Windows Media Creation Tool.
Q: Why does this happen after a Windows update?
A: Updates can corrupt system files or drivers. Rolling back updates via Safe Mode may help, but use System Restore if available.
Q: Is my SSD/HDD dead if I see this error?
A: Not alwaysit could be a loose connection or software issue. Test with another drive to confirm.
Q: How do I prevent future BSODs?
A: Keep Windows updated, avoid abrupt shutdowns, and use regular backups.
Last Updated: December 13, 2025
Tested on: Windows 10 (22H2) & Windows 11 (23H2)