| Previous | Next |
| STATUS_RESOURCE_NAME_NOT_FOUND | STATUS_FLOAT_DENORMAL_OPERAND |
STATUS_ARRAY_BOUNDS_EXCEEDED
A processor or runtime bounds check failed
This exception identifies an explicit bounds-check failure, historically associated with processor or compiler-generated bounds instructions. It is not automatically raised for every out-of-range C or C++ array access; ordinary unchecked memory corruption may instead cause an access violation later or remain undetected.
Use the disassembly to identify the bounds operation and recover the compared index and limits from registers or nearby memory. The immediate defect may be an incorrect index, but the index can also have been corrupted earlier. If sanitizers or a managed runtime generated the check, retain their diagnostic metadata and source mapping rather than treating the exception code as the complete report.
What to inspect
- Locate the bounds-check instruction and capture the compared operands.
- Map the check back to the source array, index, and expected element count.
- Inspect earlier writes if the index value is implausible.
- Do not assume uninstrumented native arrays would raise the same status.
References
- Microsoft Learn: Specific Exceptions
- Microsoft Learn: EXCEPTION_RECORD
- Microsoft Learn: Exception Dispatching
- Microsoft Windows SDK metadata: ntstatus.h
Looking for a different code? Search another status or error code.