| Previous | Next |
| ERROR_NO_PAGEFILE | ERROR_NO_EVENT_PAIR |
ERROR_ILLEGAL_FLOAT_CONTEXT
What this result means
ERROR_ILLEGAL_FLOAT_CONTEXT is a Windows system result. This result belongs to the legacy virtual-DOS-machine and floating-point emulation path. It does not usually indicate that an ordinary modern x64 process performed an invalid calculation. It means Windows could not provide the processor or emulated floating-point state expected by a real-mode or compatibility workload.
Likely causes
- an old DOS or 16-bit application is running through a compatibility layer that is incomplete or unsupported
- virtualization software did not expose or preserve the expected floating-point state
- the executable or emulator mixed real-mode assumptions with a host environment that does not implement them
- memory corruption changed the saved processor context before exception delivery
How to diagnose it
Record the process architecture, virtualization product, host and guest Windows versions, exact executable, and whether the failure occurs only after suspend, snapshot restore, or debugger attachment. A crash dump should include the exception record and thread context so the floating-point state and instruction pointer can be inspected.
Correct handling
Do not retry the same instruction in a loop. Run the application in a supported virtual machine or emulator, or replace it with a supported build. If the failure appears in a modern native process, treat it as possible context corruption and investigate the preceding exception-handling or instrumentation code.
Where this code is usually encountered
- A 16-bit or DOS compatibility component executes x87 code while the emulator has no valid saved floating-point frame.
- A virtual machine resumes an old workload after a snapshot or debugger transition and restores incomplete processor state.
- Instrumentation or exception code replaces a thread context without preserving the floating-point portion.
Evidence worth collecting
- the exact failing instruction and exception record
- x87 control, status, tag, and instruction-pointer fields
- the emulator or hypervisor version and snapshot history
- whether the failure reproduces in a clean supported virtual machine
Practical diagnostic sequence
- Confirm that the process is actually a legacy or emulated workload; seeing this code in a native x64 process changes the investigation toward context corruption.
- Reproduce without debuggers, API hooks, or compatibility shims so that altered exception delivery can be ruled out.
- Compare a failing thread context with one captured before the transition that triggers the problem.
- Test the same binary in a supported VM image rather than changing host-wide floating-point settings.
Guidance for developers
Code that calls GetThreadContext, SetThreadContext, or implements an emulator must request and preserve the relevant floating-point context flags. Recovery is safe only when the runtime can reconstruct the complete machine state; otherwise terminate the emulated task and report the transition that lost it.
Guidance for administrators
Keep the original executable and VM image together with the dump. Migrating the workload to a supported emulator or replacing the legacy program is usually safer than attempting host registry or firmware changes.
How to interpret it correctly
Do not confuse this result with an ordinary divide-by-zero or invalid-operation exception. Those report a numeric fault in valid processor state; this result says the execution environment could not supply the state itself.
Example failure pattern
A useful reproduction matrix varies host architecture, emulator version, snapshot restore, debugger attachment, and the instruction sequence that first touches floating-point state. A failure that appears only after restoring or replacing a thread context strongly implicates state preservation rather than the application’s numeric input.
Retry and recovery policy
Automatic retry is inappropriate because the same instruction will execute with the same incomplete context. Restart only the isolated legacy task after saving evidence; repeated incidents should disable that compatibility path until the emulator or context-management defect is corrected.
References
Looking for a different code? Search another status or error code.