Windows Stop Code 0x00000043: NO_SUCH_PARTITION

Quick Answer

NO_SUCH_PARTITION (0x00000043) is a Windows stop code that Microsoft describes as very infrequent. Its dedicated documentation confirms the name and value but does not provide a detailed cause, parameter definitions, or a specific repair procedure. The name alone does not prove that a partition has been deleted or that its data is lost. Microsoft Learn

If the error repeats, preserve important data, review recent storage and driver changes, and collect a crash dump. If a disk or volume is also missing, inspect its status before deciding on a repair.

What Is Known About This Error?

Storage symptoms and recent changes can guide the investigation, but they should not be presented as confirmed causes of every 0x43 crash. Microsoft Learn

Before You Begin

• Back up important files that remain accessible.
• Record the complete stop code, crash time, and any displayed driver filename.
• Note recent cloning, partition resizing, disk replacement, storage-driver updates, or virtual-disk changes.
• Have administrator access available for diagnostic tools and driver rollback.
• Keep the BitLocker recovery key available before entering Windows recovery options.

Data-protection warning: If an existing disk unexpectedly appears as RAW, Unallocated, or Not Initialized, do not format it, create a replacement volume, or initialize it while trying to recover its files. Microsoft’s guidance distinguishes preparing an empty disk from recovering existing data. Microsoft Learn

Recommended Troubleshooting

1. Confirm the Error and Recent Changes

Verify that the actual Windows stop code is 0x00000043. A message about a missing partition in another program is not sufficient to identify this bug check.

Record whether the crash began after a storage or driver change. Preserve the relevant application logs and any record of the previous disk layout.

2. Inspect Disk Status if Storage Is Missing

If Windows starts and a disk or volume is unavailable:

1. Search for Computer Management.
2. Right-click it and select Run as administrator.
3. Open Storage > Disk Management.
4. Record the affected disk’s capacity, status, and partition layout.
5. Take a screenshot for technical support.

Cancel an initialization prompt if the disk should contain existing data. Leave EFI System and Recovery partitions unchanged. Microsoft notes that these contain files needed for startup and recovery. Microsoft Learn

These observations help determine the next investigation; viewing a partition does not establish why Windows crashed.

3. Check a Missing External Disk’s Connection

For an ordinary external data disk:

1. Shut down the PC before disconnecting or changing connections.
2. Check its power supply and cable.
3. Reconnect it directly to the PC rather than through a USB hub.
4. Restart and inspect its status again.

Microsoft includes cable, port, and power checks in its missing-disk troubleshooting guidance. If the disk remains unavailable and contains important unbacked-up data, seek recovery advice before attempting changes to its layout. Microsoft Learn

4. Review an Identified Driver Change

If crash timing or dump analysis points to a recently updated device driver:

1. Right-click Start > Device Manager.
2. Open the device’s Properties.
3. Select Driver > Roll Back Driver, when available.
4. Follow the prompts and restart if requested.

If rollback is unsuitable, obtain a compatible driver through Windows Update or the manufacturer’s official website. Make one targeted change at a time. support.microsoft.com

Recovery: If the change causes a new problem, restore the previous driver where possible or reinstall the appropriate vendor package. Changes to a controller hosting the Windows disk should follow the system vendor’s procedure.

If Windows Cannot Start Normally

Use Safe Mode if the Windows Recovery Environment is available:

1. Select Troubleshoot > Advanced options > Startup Settings > Restart.
2. Press 4 or F4.
3. Investigate or reverse the suspected driver change.
4. Restart normally to test.

An encrypted device may request its BitLocker recovery key. Safe Mode cannot establish whether a partition is intact or restore missing data. support.microsoft.com

Advanced Troubleshooting: Analyze the Crash Dump

When Windows successfully writes a dump, common default locations are:

Open the relevant dump in WinDbg with appropriate symbols and run:

!analyze -v

Review the recorded stop code, call stack, and module information alongside recent changes. This command analyzes the crash; it does not repair partitions or recover files. learn.microsoft.com

Because Microsoft does not publish 0x43-specific parameter meanings, do not interpret its arguments using another bug check’s parameter table. If the dump is inconclusive, provide the findings, disk-status screenshots, and configuration history to IT support or the relevant vendor. Microsoft Learn

How to Verify the Fix

After a supported correction:

1. Confirm that Windows starts normally.
2. Check that expected data volumes and files are accessible.
3. Verify that backups complete successfully.
4. Repeat the activity that previously preceded the crash, where practical.
5. Monitor for recurrence across multiple sessions.

If the crash returns, preserve the newest dump. If storage remains missing, treat data recovery as a separate unresolved issue.

Frequently Asked Questions

Does this stop code prove that a partition was deleted?

No. Microsoft’s published description does not establish partition deletion as the cause. Check the disk layout and crash evidence. Microsoft Learn

Should I initialize a disk that previously held files?

Do not initialize it as a recovery attempt. Microsoft’s initialization procedure is intended for new disks without existing data; protect or recover existing files first. Microsoft Learn

Should I create a new volume in unexpected unallocated space?

Not while trying to recover files that should already be there. Microsoft specifically advises against creating a new volume in that situation. Microsoft Learn

Will boot-repair commands always fix 0x43?

No universal boot-repair procedure is documented for this code. Establish whether the actual problem involves startup configuration, storage access, or another component before selecting a repair.

Can a healthy-looking disk still require crash investigation?

Yes. Disk status alone does not identify the cause of a Windows stop error. Continue with dump analysis if crashes recur.

Conclusion

For NO_SUCH_PARTITION, preserve data and establish the actual disk state before making storage changes. Microsoft provides limited detail for this rare code, so use recent-change history and crash analysis to select a supported correction.

Sources

• Microsoft Learn — Bug Check 0x43: NO_SUCH_PARTITION.
• Microsoft Learn — Troubleshoot Disk Management.
• Microsoft Learn — Initialize new disks.
• Microsoft Learn — Stop code error or bug check troubleshooting.
• Microsoft Support — Update drivers through Device Manager in Windows.
• Microsoft Support — Windows startup settings.