| Previous | Next |
| INVALID_WORK_QUEUE_ITEM | END_OF_NT_EVALUATION_PERIOD |
BOUND_IMAGE_UNSUPPORTED
Unsupported bound image during load for BOUND_IMAGE_UNSUPPORTED
BOUND_IMAGE_UNSUPPORTED is bug check code 0x00000097. Bound images store precomputed import binding information. This bug check indicates the loader found a bound-image state that was not acceptable for the current kernel load path.
How to read it in a dump for BOUND_IMAGE_UNSUPPORTED
- Identify which image was being loaded and whether it is a boot-start driver or kernel component.
- Image signing, timestamp, import binding, and architecture mismatch are relevant evidence.
- Do not treat it as a simple missing DLL without confirming loader status.
What to check for BOUND_IMAGE_UNSUPPORTED
- Verify driver version, architecture, signature, and recent updates.
- Check for stale or patched kernel drivers.
- Rebuild or replace the suspect driver instead of editing binding data manually.
References for BOUND_IMAGE_UNSUPPORTED
- Boot-start driver distribution disk
- Microsoft Bug Check Code Reference
- Analyze a kernel-mode dump with WinDbg
Dump evidence for BOUND_IMAGE_UNSUPPORTED
For BOUND_IMAGE_UNSUPPORTED, 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 “BOUND_IMAGE_UNSUPPORTED”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for BOUND_IMAGE_UNSUPPORTED
- Run WinDbg
!analyze -v, then inspect the documented meaning of each BOUND_IMAGE_UNSUPPORTED parameter instead of relying only on the probably-caused-by line. - For BOUND_IMAGE_UNSUPPORTED, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with bound / image.
- For BOUND_IMAGE_UNSUPPORTED, 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 BOUND_IMAGE_UNSUPPORTED before collecting the dump and event logs. For BOUND_IMAGE_UNSUPPORTED, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Dump evidence for BOUND_IMAGE_UNSUPPORTED
For BOUND_IMAGE_UNSUPPORTED, 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 “BOUND_IMAGE_UNSUPPORTED”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for BOUND_IMAGE_UNSUPPORTED
- Run WinDbg
!analyze -v, then inspect the documented meaning of each BOUND_IMAGE_UNSUPPORTED parameter instead of relying only on the probably-caused-by line. - For BOUND_IMAGE_UNSUPPORTED, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with bound / image.
- For BOUND_IMAGE_UNSUPPORTED, 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 BOUND_IMAGE_UNSUPPORTED before collecting the dump and event logs. For BOUND_IMAGE_UNSUPPORTED, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.