| Previous | Next |
| MILERR_TERMINATED | MILERR_INTERNALERROR |
MILERR_BADNUMBER
MILERR_BADNUMBER is a Windows Media Integration Layer (MIL) HRESULT. It indicates that a graphics calculation received a non-finite, out-of-range, or otherwise unusable number.
What to check for MILERR_BADNUMBER
- Validate coordinates, dimensions, opacity, timing, and transform values for NaN and infinity.
- Check conversions between pixels, device-independent units, and floating-point types for overflow.
- Preserve the original input values in diagnostics so the source of the invalid number can be identified.
Microsoft documentation about WPF hardware-accelerated rendering
Diagnostic interpretation of MILERR_BADNUMBER
MILERR_BADNUMBER has the HRESULT value 0x8898000A. AllStat records the condition as “MILERR_BADNUMBER”. For MILERR_BADNUMBER, in practice, interpret that wording at the boundary owned by the Windows component or COM interface that returned the HRESULT, rather than treating the value as a generic Windows message.
Evidence to capture for MILERR_BADNUMBER
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x8898000A value before a wrapper converts it to an exception or Boolean result.
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions MILERR_BADNUMBER or the milerr / badnumber operation.
- For MILERR_BADNUMBER, check the documented return contract of the specific API because the same HRESULT can require different recovery in different interfaces.
Retry and recovery for MILERR_BADNUMBER
Retry MILERR_BADNUMBER only when the owning API documents a transient state or after the condition described as “MILERR_BADNUMBER” has changed. For MILERR_BADNUMBER, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.
Looking for a different code? Search another status or error code.