| Previous | Next |
| ERROR_UNEXPECTED_MM_MAP_ERROR | ERROR_BAD_FUNCTION_TABLE |
ERROR_UNEXPECTED_MM_EXTEND_ERR
What this result means
ERROR_UNEXPECTED_MM_EXTEND_ERR is a Windows system result. The Windows memory manager encountered an unexpected problem while extending a section, mapped file, image, or backing store. The code is a summary; storage and memory-manager events usually contain the actionable detail.
Why it can appear
- the backing file or volume ran out of space or could not extend
- filesystem, filter-driver, or storage errors interrupted section growth
- a mapped-file size changed concurrently in an unsupported way
- memory-manager metadata or a driver interaction exposed an internal inconsistency
Diagnostic workflow
- record the mapped file, requested new size, volume free space, filesystem, and allocation mode
- collect System, storage, filesystem, and filter-driver events around the first failure
- check for concurrent truncation, replacement, sparse-file, encryption, or snapshot activity
- test with third-party filesystem filters disabled in a controlled environment
Correct recovery and handling
Restore storage health and free space, then recreate the mapping or restart the owning component. Do not continue writing through a mapping whose extension failed because subsequent offsets may not be backed as expected.
Administrator and support checklist
- confirm whether the condition is isolated to one machine, one user, one file, or one application build.
- Compare the host reporting this result with a known-good system using the same Windows edition and policy.
- Review updates, drivers, security-policy changes, restores, and infrastructure incidents that preceded this result.
- Preserve logs and dumps associated with this result before rebooting when the failure may be intermittent or destructive.
- Use vendor-supported repair or rollback steps for it instead of copying system files or disabling protections ad hoc.
Developer guidance
When handling it, log the API or subsystem that returned it, the first lower-level failure, relevant object identifiers, process and thread context, and safe operation parameters. Preserve the original numeric Value rather than converting it to an unrelated HRESULT or NTSTATUS. Retry it only when the evidence shows a transient dependency; deterministic it cases involving policy, format, compatibility, or integrity should fail fast.
What to record in telemetry
- Windows build, architecture, and component version for the result event
- the first result timestamp and the operation then in progress
- process, thread, session, and target object associated with it
- warnings or lower-layer status values immediately preceding it
- whether retry, restart, rollback, or repair changed the result outcome
Example investigation pattern
Investigate it by reproducing the operation once with detailed logging, then correlate that timestamp with Windows events and lower-layer traces. Compare the affected object or process with a known-good one, change one variable at a time, and stop retrying When it is deterministic. That method keeps the first relevant failure from being hidden by secondary cleanup messages.
Related and easily confused conditions
This is broader than ERROR_DISK_FULL. A full disk is one cause, but filter-driver, mapping-lifecycle, and filesystem failures can produce the same memory-manager summary.
Operational note
Do not diagnose it from its text alone. The result can cross subsystem boundaries and may summarize an earlier, more specific event. The first failure in time is normally more useful than the last message printed during cleanup.
References
Looking for a different code? Search another status or error code.