Skip to content
PCDecoder
0x00000043NO_SUCH_PARTITIONStop codeWidely reported

NO_SUCH_PARTITION (0x43): what it means and how to fix it

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

Quick answer

The NO_SUCH_PARTITION bug check indicates that Windows attempted to access a storage partition that does not exist or cannot be identified. This stop code appears very infrequently and typically points to corrupted disk partition tables, cloned drive misconfigurations, or disrupted drive links. Running Startup Repair from Windows Recovery is the recommended first step.

What it means

Windows relies on a clear map of your physical storage drives to find the files needed to operate. This map divides your hard drive or solid-state drive into structured areas called partitions. One partition holds the operating system files, another might store recovery tools, and a hidden system partition guides the boot process. When the kernel or a storage driver requests an operation on a specific partition identifier that is missing, nonexistent, or unrecognizable, the system halts with bug check 0x00000043, designated as NO_SUCH_PARTITION. Official documentation confirms that this bug check appears very infrequently during everyday computing. When it does emerge, it almost always stems from a sudden failure in the system storage configuration rather than an ordinary application crash. If a disk drive has been recently cloned, repartitioned, or converted between disk management schemes, reference pointers in the boot configuration can easily break. A drive letter or internal volume identifier that Windows expects to reach may point to an empty address. Physical hardware disruptions can trigger the same condition. If a storage controller disconnects during operation, a cable unseats, or an external drive holding system-linked volumes is removed, the partition disappears from the perspective of the operating system. When Windows attempts an essential input or output request against that missing target, it cannot complete the task safely. Halting execution with a blue screen protects the rest of the file system from corrupted write attempts. Resolving the crash involves restoring the partition map, repairing the Windows boot data, and verifying that the storage hardware remains properly detected by the computer firmware.

Common causes

  • A damaged or modified partition table has removed or altered the volume Windows is trying to access.
  • Storage drive cloning or repartitioning left stale drive identifiers in the system boot configuration.
  • A drive cable or storage controller lost connection while Windows was active.
  • The storage drive has sustained physical sector damage that makes partition metadata unreadable.

How to fix it

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

  1. Run Windows Startup Repair

    Use this as the first recovery step if Windows fails to boot or crashes immediately at startup.

    1. Power on your computer and hold down the power button as soon as Windows starts loading to force a shutdown.
    2. Repeat this process two times to trigger the Automatic Repair environment.
    3. Select Advanced options on the repair screen.
    4. Click Troubleshoot, then select Advanced options.
    5. Click Startup Repair and allow the tool to scan and correct disk partition entries.
    Did this fix it?

  2. Rebuild the boot configuration data

    Use this when the system partition map was altered by cloning, disk shrinking, or dual-boot removal.

    1. Boot your computer into the Windows Advanced Startup menu using installation media or the recovery environment.
    2. Select Troubleshoot, then Advanced options, and open Command Prompt.
    3. Type bootrec /fixmbr and press Enter.
    4. Type bootrec /fixboot and press Enter.
    5. Type bootrec /rebuildbcd and press Enter.
    6. Restart the computer to confirm Windows can locate the system partition.
    Did this fix it?

  3. Check drive connections and firmware detection

    Use this if the crash began after moving hardware, installing a new drive, or physical impact.

    1. Shut down the computer and disconnect the power cable.
    2. Open the PC chassis and ensure data and power cables are firmly seated on all storage drives.
    3. Power on the computer and press the manufacturer key (such as F2, F10, or Delete) to enter the UEFI or BIOS setup.
    4. Navigate to the storage or boot menu to confirm the system drive appears in the detected device list.
    5. Save settings, exit the BIOS, and attempt to boot Windows normally.
    Did this fix it?

  4. Scan the drive for file system corruption

    Use this when the computer boots into Windows or Safe Mode intermittently.

    1. Click the Start button, type cmd, right-click Command Prompt, and choose Run as administrator.
    2. Type chkdsk C: /f /r and press Enter.
    3. Press Y to confirm that the scan should run during the next system restart.
    4. Restart your PC and allow the disk check utility to verify partition integrity.
    Did this fix it?

Is it just you?

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

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

Sources

Frequently asked questions

What does NO_SUCH_PARTITION mean on a blue screen?

It means Windows attempted to access a storage partition using a reference that does not exist or cannot be found on your drive.

Is bug check 0x00000043 a common error?

No. Official documentation notes that the NO_SUCH_PARTITION bug check appears very infrequently.

Does error 0x43 mean my hard drive is dead?

Not necessarily. It usually indicates corrupted partition data or outdated boot references after disk changes, though severe hardware failure can also cause it.

More stop codes decoded