| Previous | Next |
| ATDISK_DRIVER_INTERNAL | MULTIPLE_IRP_COMPLETE_REQUESTS |
NO_SUCH_PARTITION
Missing partition object in storage path for NO_SUCH_PARTITION
NO_SUCH_PARTITION is bug check code 0x00000043. This bug check is about a kernel storage reference to a partition that cannot be resolved. It is usually tied to disk layout, partition enumeration, filter-driver state, or a stale reference after storage topology changed.
How to read it in a dump
- The dump stack should show whether the failing path is volume manager, disk class, partition manager, file system, or a storage filter.
- Arguments are secondary to the object and device stack visible in WinDbg.
- This is different from INACCESSIBLE_BOOT_DEVICE; it does not necessarily mean the boot volume was lost.
What to check
- Check disk/partition changes, virtual disk attachment, SAN path changes, and storage filter drivers.
- Inspect device objects, volume manager state, and recent disk reconfiguration.
- For boot-time failures, compare BCD, firmware boot order, and partition table visibility.
References
Dump evidence
Preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line. - find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with such / partition.
- keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.