| Previous | Next |
| STATUS_FLOAT_INVALID_OPERATION | STATUS_FLOAT_STACK_CHECK |
STATUS_FLOAT_OVERFLOW
The floating-point magnitude was too large to represent normally
Overflow occurs when the rounded result has a magnitude beyond the largest finite value of the destination format. Depending on rounding mode and sign, a masked operation can produce infinity or the largest finite number while setting overflow and inexact flags. If overflow is unmasked, Windows reports this exception.
Check where precision changes. A value valid in double precision can overflow when stored as float, converted to an integer-like format, or evaluated by a lower-precision vector path. Exponential growth, unit mistakes, and unchecked accumulation are common sources. Inspect the operation before the value becomes infinity, because later calculations may only show secondary invalid or divide conditions.
What to inspect
- Capture operands, result format, and rounding mode at the faulting instruction.
- Check narrowing conversions and mixed-precision library boundaries.
- Trace exponential, accumulation, and unit-conversion inputs for range errors.
- Preserve earlier floating-point status flags before clearing or retrying.
References
- Microsoft Learn: _fpieee_flt
- Microsoft Learn: _control87 and _controlfp
- Microsoft Learn: /fp floating-point behavior
- Intel: Floating-Point Reference Sheet
Looking for a different code? Search another status or error code.