Skip to content
PCDecoder
0x00000053NO_BOOT_DEVICEStop codeWidely reported

NO_BOOT_DEVICE (0x53): what it means and how to fix it

Updated Oct 17, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

NO_BOOT_DEVICE indicates that Windows cannot access the storage drive holding the files required to start the operating system. It usually occurs when a drive disconnects, boot priority changes in firmware, or the storage media fails. The first step is to disconnect all external drives and verify that your system drive appears in the BIOS or UEFI setup.

What it means

The NO_BOOT_DEVICE bug check carries a value of 0x00000053. It indicates that the early startup environment lost access to the primary storage drive or could not locate the Windows boot partition. According to Microsoft documentation, this stop code appears very infrequently on modern Windows installations.

The Boot Handoff

When you turn on your computer, the motherboard firmware (UEFI or BIOS) runs power-on self-tests and looks for a valid storage drive containing an operating system bootloader. Once located, firmware hands control over to Windows. If the system drive drops offline immediately before or during this handoff, Windows cannot load essential kernel files into memory. The operating system halts execution and raises bug check 0x53 to prevent unpredictable system state.

Why the Drive Disappears

A computer might fail to reach its storage media for several reasons. Physical hardware faults are common, such as a loose SATA data cable, an unseated M.2 NVMe drive, or a failing storage controller. Solid-state drives and traditional hard drives can also enter a read-only or unresponsive state when internal components degrade.

Firmware configuration issues can produce the same result. If motherboard settings reset after a battery failure or firmware update, the boot mode might switch between UEFI and Legacy CSM. When that happens, the firmware will scan the drive using the wrong structure and report that no usable operating system exists. Community reports frequently describe systems unexpectedly trying to boot from network adapters (PXE boot) or removable USB drives because the primary internal drive is no longer recognized by the motherboard.

Common causes

  • The internal storage drive disconnected or lost power during startup.
  • Motherboard firmware settings switched boot modes or altered the boot order.
  • The storage drive experienced a physical or controller failure.
  • Corrupted boot sector data prevented Windows from locating system files.
  • Removable USB media or network boot options took precedence over the internal drive.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Disconnect external storage devices

    Use this first to eliminate boot order confusion caused by external drives or memory cards.

    1. Shut down the computer completely.
    2. Unplug all USB flash drives, external hard drives, SD cards, and secondary peripherals.
    3. Power on the computer to check whether Windows loads from the internal drive.
    Did this fix it?

  2. Verify drive detection and boot order in UEFI/BIOS

    Use this if Windows still fails to start after removing external devices.

    1. Restart the computer and press the manufacturer setup key (such as F2, F10, F12, or Del) immediately on power-up.
    2. Navigate to the System Information or Storage screen and confirm that your internal drive is listed.
    3. Go to the Boot section and set the internal Windows Boot Manager or main drive as the primary boot option.
    4. Save your changes and exit the setup utility.
    Did this fix it?

  3. Reseat internal storage cables and drive hardware

    Use this on desktop PCs or laptops with accessible drive bays when the drive is missing from the BIOS screen.

    1. Power off the PC, unplug the power cable, and open the computer case.
    2. Locate the primary SSD or hard drive.
    3. Disconnect and firmly reconnect the SATA power and data cables on both the drive and motherboard, or remove and reinsert the M.2 NVMe drive into its slot.
    4. Close the case, reconnect power, and start the system.
    Did this fix it?

  4. Run Startup Repair from installation media

    Use this if the BIOS detects the drive but Windows still halts with bug check 0x53.

    1. Insert a Windows installation USB drive and boot from it.
    2. Select your language preferences and click Next.
    3. Click Repair your computer in the bottom-left corner.
    4. Select Troubleshoot, then Advanced options, and click Startup Repair.
    5. Allow the repair tool to diagnose the boot partition and restart the computer.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 13, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What is bug check 0x00000053?

Bug check 0x00000053 is the hex representation of NO_BOOT_DEVICE. It means Windows attempted to boot but could not communicate with the storage drive containing the system files.

Does 0x53 mean my hard drive is completely dead?

Not necessarily. It can indicate a loose cable, incorrect BIOS boot order, or corrupted startup records, though a dead drive is a possibility if the firmware cannot detect it at all.

Why does my PC show PXE or media failure after this error?

When the motherboard cannot detect the internal storage drive, it drops down the boot priority list to network boot (PXE), which fails if no local network boot server is configured.

More stop codes decoded