| Previous | Next |
| STATUS_DIRECTORY_IS_A_REPARSE_POINT | STATUS_SOURCE_ELEMENT_EMPTY |
STATUS_RANGE_LIST_CONFLICT
The new interval conflicts with range state that is already recorded
STATUS_RANGE_LIST_CONFLICT belongs to interval-management logic. Windows RTL range lists model inclusive start/end ranges with attributes, owners and sharing flags. A conflict means the requested interval cannot be added or merged under the current sharing and conflict rules.
Diagnose the numeric endpoints first. Off-by-one errors are especially damaging because these ranges use both a start and an end; code that stores a byte count as the end value accidentally expands every interval. Also preserve the owner and shared-range flags. Two overlapping intervals can be legal in one policy and conflicting in another.
The ReactOS RTL implementation is useful as an independently implemented source-level reference for the public range-list API shape and demonstrates that range-list operations track start, end, flags, user data and owner separately. Do not infer that the status always refers to memory addresses: callers can use range lists for resource windows and other 64-bit intervals.
What to inspect
- The requested inclusive start and end values in hexadecimal and decimal.
- The existing overlapping range, its owner, attributes and shared flag.
- Conversion code between length-based and end-based representations.
References
- ReactOS source: RTL range-list implementation
- Microsoft: CM_RESOURCE_LIST
- Microsoft: Hardware resources
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.