| Previous | Next |
| STATUS_FLOAT_UNDERFLOW | STATUS_INTEGER_OVERFLOW |
STATUS_INTEGER_DIVIDE_BY_ZERO
The divisor for an integer divide was zero
The processor raises this exception when an integer DIV or IDIV operation cannot proceed because the divisor is zero. The faulting instruction has not completed, so a handler that intends to continue would need to correct the operand and understand the language-level semantics; simply advancing the instruction pointer produces an undefined result for the caller.
Inspect the divisor at the machine level and then trace it back to the source expression. A zero value may come from missing validation, integer truncation, a race that changed shared state, or corrupted input. The same hardware divide exception can also occur when the quotient cannot fit the destination, so the full register state and operand size are important.
What to inspect
- Decode the divide instruction and capture dividend, divisor, and operand width.
- Trace the zero divisor to its validated source value.
- Check for concurrent modification or narrowing conversions.
- Do not skip the instruction without defining a valid result for the caller.
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.