| Previous | Next |
| FP_EMULATION_ERROR | BOOTING_IN_SAFEMODE_MINIMAL |
BAD_EXHANDLE
The result bug check has a value of 0x000000A7. This bug check indicates that the kernel-mode handle table detected an inconsistent handle table entry state.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
BAD_EXHANDLE Parameters
None
Dump evidence
Preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line. - Find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with exhandle.
- keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Distinctive failure boundary
This result identifies executive object handle corruption. Inspect the failing handle value, owning process handle table, object type, close/reference history, and any driver that passes handles across process or kernel boundaries. A stale, double-closed, kernel-only, or fabricated handle points toward object-manager misuse rather than general memory pressure.
Separating the result from neighboring bug checks
Use handle tracing or Driver Verifier where appropriate, and check whether the stack is closing, duplicating, referencing, or waiting on the handle. Preserve the original dump and use the documented parameters and stack to verify this distinction before changing drivers or platform configuration.
Looking for a different code? Search another status or error code.