| Previous | Next |
| STATUS_PARITY_ERROR | STATUS_NOT_COMMITTED |
STATUS_UNABLE_TO_DECOMMIT_VM
The decommit range does not describe committed private pages
Decommit removes committed backing while preserving the surrounding reservation. The range must belong to a compatible private allocation; section views and image mappings follow different lifecycle rules. Current NtFreeVirtualMemory documentation explicitly allows a decommit range to include already uncommitted pages, so this status should not be explained by that condition alone.
If this status is observed, preserve the exact native call and operating-system context. Check invalid flags, range overflow, incompatible mapping type, or an internal/legacy path whose contract differs from documented NtFreeVirtualMemory. Do not invent a retry rule from the status name alone.
What to inspect
- Query every region crossed by the requested range and verify state and allocation base.
- Check page rounding so the call does not include an adjacent uncommitted page.
- Audit rollback and destruction paths for duplicate decommit operations.
References
- Microsoft: VirtualFree
- Microsoft WDK: NtFreeVirtualMemory
- Microsoft: VirtualQuery
- ReactOS source: virtual memory manager
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.