| Previous | Next |
| ERROR_DS_VERSION_CHECK_FAILURE | ERROR_NOT_SAFE_MODE_DRIVER |
ERROR_RANGE_NOT_FOUND
What ERROR_RANGE_NOT_FOUND means
Range-list APIs track occupied, free, mapped, or owned intervals. The failure means no entry covers the specified start and length under the requested matching rules.
Where it appears
- resource arbitration and device address ranges
- memory, file extent, or virtual-address bookkeeping
- drivers maintaining allowed or reserved intervals
Likely causes
- off-by-one or overflow in range endpoints
- the interval was already removed or split
- caller used a different coordinate space
- concurrent updates changed the list
What to collect
- requested start, length, and inclusive/exclusive semantics
- complete range list at failure time
- operation history that inserted, split, or deleted ranges
- integer width and overflow checks
How to respond
Normalize endpoint arithmetic and retry only after refreshing the authoritative list. Do not fabricate a matching interval. Drivers should protect range mutations and log both hexadecimal boundaries and ownership.
References
Looking for a different code? Search another status or error code.