| Previous | Next |
| STATUS_DECRYPTION_FAILED | STATUS_NO_RECOVERY_POLICY |
STATUS_RANGE_NOT_FOUND
No matching range satisfies the requested interval operation
STATUS_RANGE_NOT_FOUND is the negative lookup result for range-list operations. Depending on the caller, it can mean an exact range was not present for deletion or that a search could not find a free interval satisfying minimum, maximum, length and alignment constraints.
Do not reduce the diagnosis to “the address is missing”. Range-list APIs operate on 64-bit intervals and can represent hardware resources or other indexed regions. For a deletion, compare start, end and owner with the recorded entry. For an allocation-style search, log the minimum and maximum bounds, requested length and alignment; a large enough total gap may still be unusable because no correctly aligned contiguous interval fits.
Source-level implementations of the RTL API also show another important distinction: exact deletion and free-range search can both return the same status through different paths. The operation name must therefore be retained with the code.
What to inspect
- Whether the caller was deleting an exact interval or searching for an available interval.
- Start/end/owner for exact deletion, or bounds/length/alignment for a search.
- Range-list mutations between lookup and update; stale snapshots can make a previously valid interval disappear.
References
- ReactOS source: RtlDeleteRange and RtlFindRange
- Microsoft: Hardware resource maps
- Microsoft: Hardware resources
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.