BOUND_IMAGE_UNSUPPORTED (0x00000097) Blue Screen Error: Causes and Troubleshooting
Quick Answer BOUND_IMAGE_UNSUPPORTED (0x00000097) is a Windows bug check associated with a blue screen error (BSOD). The stop code alone does not establish t...
Quick Answer
BOUND_IMAGE_UNSUPPORTED (0x00000097) is a Windows bug check associated with a blue screen error (BSOD). The stop code alone does not establish the root cause of a crash. Investigate the exact error details, recent system changes, and available crash dump evidence before attempting repairs.
If Windows crashes repeatedly, back up important data when possible, check recently changed drivers and software, and use Microsoft's debugging tools to analyze the crash dump if necessary. Do not assume that updating a driver, repairing system files, or replacing hardware will resolve this specific error without supporting evidence.
What Does BOUND_IMAGE_UNSUPPORTED Mean?
Windows uses bug checks to stop the operating system when it encounters a serious condition. The identifier 0x00000097 corresponds to BOUND_IMAGE_UNSUPPORTED in Microsoft's bug check reference.
This is an uncommon error. The stop code by itself does not provide enough information to identify the cause of an individual crash. Additional information, such as bug-check parameters, system configuration, and crash dump analysis, may be needed to determine what happened.
Symptoms
Depending on the circumstances, a Windows system experiencing this bug check may show the following general stop-error symptoms:
- A blue screen displaying the BOUND_IMAGE_UNSUPPORTED stop code.
- An unexpected system restart or shutdown.
- Repeated crashes during startup or normal operation.
- A crash dump file being created before the system restarts, if dump collection is configured and succeeds.
These are general Windows crash symptoms, not symptoms uniquely associated with this particular bug check.
Possible Causes
The exact cause must be established through diagnosis. The following are general areas to investigate rather than confirmed causes of bug check 0x00000097.
- Recent driver changes: A newly installed or updated driver may be relevant if the crashes began immediately afterward.
- System software changes: Recently installed software that uses low-level system components may warrant investigation.
- Hardware or firmware changes: Newly installed devices or recent configuration changes may provide useful diagnostic clues.
- Operating system problems: Other Windows errors or system corruption may indicate a broader issue requiring investigation.
- Insufficient diagnostic evidence: Without a crash dump or additional details, the actual cause may remain undetermined.
A module name shown on a blue screen or in a crash report is a clue, not conclusive proof that the module caused the failure.
How to Troubleshoot BOUND_IMAGE_UNSUPPORTED (0x00000097)
1. Record the Stop Code and Recent Changes
Before changing system settings, record the complete stop code and any additional information displayed on the blue screen.
- Photograph the error screen if it disappears before you can record its details.
- Note when the crash occurred and what the computer was doing at the time.
- Record any recent driver installations, Windows updates, software installations, or hardware changes.
- Determine whether the error occurred once or has repeatedly occurred under similar conditions.
This information helps narrow the investigation and prevents unnecessary changes to a working system.
2. Restart Windows and Check Whether the Error Returns
If Windows starts normally after a single crash, save important files and monitor the computer for further problems. A successful restart does not prove that the underlying issue has been resolved.
If the computer repeatedly crashes or cannot start normally, avoid unnecessary restart attempts. Use Windows Recovery Environment when appropriate and protect important data before attempting repairs that could affect the installation.
3. Review Recent Driver Changes
If the problem began after a driver update or hardware installation, investigate the relevant device first.
- Open Device Manager.
- Inspect relevant devices for warning symbols or reported device problems.
- Open the device's properties and review its driver information and device status.
- Check the computer or device manufacturer's official support website for a compatible driver.
- If a recent driver update is strongly associated with the crashes, consider rolling it back when the option is available and appropriate.
Driver rollback or reinstallation is a general troubleshooting measure, not a confirmed fix for this specific stop code. Avoid third-party driver download sites and do not remove essential storage or boot drivers without an appropriate recovery plan.
4. Check Windows Update
Review Windows Update and its update history to identify recent changes that might be relevant to the crash.
- Open Windows Settings.
- Navigate to Windows Update and check for applicable updates.
- Review the update history for installations around the time the crashes began.
- Check the computer manufacturer's support website for relevant compatibility information.
Install applicable updates from trusted sources. If the problem began immediately after a particular update, investigate its known issues and supported removal or recovery options before uninstalling it.
5. Check Windows System File Integrity
If other evidence suggests that protected Windows system files may be damaged, use Microsoft's Deployment Image Servicing and Management (DISM) tool and System File Checker (SFC). These tools address general system-image and file-integrity problems; they are not documented as guaranteed fixes for BOUND_IMAGE_UNSUPPORTED.
Open Windows Terminal or Command Prompt as an administrator and run the following command:
DISM.exe /Online /Cleanup-Image /RestoreHealthDISM attempts to repair the running Windows image. Depending on the system, it may require access to Windows Update or an appropriate repair source.
After DISM finishes, run:
sfc /scannowSFC scans protected system files and attempts to repair integrity violations. Review the final result and follow any instructions it provides.
If either command reports an error, record the complete message before attempting additional repairs. Do not manually replace Windows system files with files obtained from unofficial sources.
6. Review System Events
Event Viewer may contain information about related device failures, service errors, or system events occurring around the crash time.
- Open Event Viewer.
- Navigate to Windows Logs > System.
- Review critical and error events near the time of the blue screen.
- Compare the timestamps with recent system changes and other diagnostic evidence.
An event recorded at the same time as a crash is not necessarily its cause. Use event details as supporting evidence rather than treating every critical or error entry as a confirmed explanation.
Advanced Troubleshooting: Analyze a Windows Crash Dump
If the error keeps recurring and basic checks do not identify a likely cause, analyze a crash dump. This approach is particularly useful for IT support technicians and system administrators.
1. Locate the Crash Dump
Check the following standard locations:
%SystemRoot%\Minidump— commonly used for small memory dumps.%SystemRoot%\MEMORY.DMP— commonly used for larger kernel, automatic, or complete memory dumps, depending on the system configuration.
A dump file may not exist if crash-dump collection was not configured, the system could not write the file, or the crash occurred under circumstances that prevented dump creation.
Preserve the original dump and work on a copy where practical. Crash dumps can contain sensitive information, so do not upload them to public forums or share them with untrusted parties.
2. Analyze the Dump with WinDbg
WinDbg is Microsoft's debugging tool for analyzing Windows crashes. Install it from an official Microsoft source and open the relevant dump file.
In the debugger command window, run:
!analyze -vThis command requests a detailed automated analysis of the crash dump. Review the reported bug-check code and parameters, stack trace, module information, and other available findings.
Ensure that symbols are configured appropriately and that the dump corresponds to the crash being investigated. An incomplete dump, missing symbols, or limited diagnostic data may prevent a definitive conclusion.
3. Interpret the Results
Use the debugger's findings alongside the crash circumstances and recent system changes.
- Check whether the dump confirms the expected bug-check code.
- Review the stack trace and relevant module information.
- Compare repeated crashes to see whether the same components appear in similar circumstances.
- Check relevant driver versions and manufacturer documentation before making changes.
A driver or module identified during automated analysis is not necessarily the original cause. Avoid replacing system files or removing drivers solely because their names appear in the report.
Driver Verifier should not be the first troubleshooting step. It can deliberately trigger a system crash when it detects a driver violation. Use it only when justified by the evidence and when appropriate recovery access is available.
Verification
After making a targeted change, check whether the original problem recurs under the same or similar conditions.
- Confirm that Windows starts and operates normally.
- Repeat the activity that previously triggered the crash, when safe.
- Review new system events and crash dumps for additional failures.
- Verify that any changed driver or software remains compatible with the computer and installed Windows version.
One successful restart is not sufficient to prove that the problem is permanently resolved. If the error returns, preserve the new evidence and compare it with the earlier crash.
Recovery Options
If Windows cannot start normally, Windows Recovery Environment may provide access to Safe Mode, System Restore, or supported update-removal options, depending on the installation and available recovery configuration.
Before attempting a major recovery operation, back up important files where possible. If BitLocker device encryption is enabled, make sure the required recovery key is available before entering recovery workflows that may request it.
For a work-managed computer, consult the IT administrator before changing drivers, security software, firmware, or system configuration. If the error persists, provide the technician with the exact stop code, Windows version, recent changes, relevant event records, and available crash dump analysis.
Frequently Asked Questions
Is BOUND_IMAGE_UNSUPPORTED (0x00000097) a hardware error?
The stop code alone does not establish a hardware failure. Additional evidence is needed to determine whether the problem relates to hardware, drivers, software, or another system condition.
Does this stop code always mean a driver is incompatible?
No. Do not infer a confirmed root cause from the stop-code name alone. Investigate the bug-check details and available crash dump before deciding on a corrective action.
Can I fix this error by reinstalling Windows?
Reinstalling Windows should not be the first response to an isolated crash. Start with evidence collection and targeted troubleshooting. Consider reinstallation only when justified by the diagnosis and after making appropriate backups.
Where are Windows crash dump files stored?
Small memory dumps are commonly stored in %SystemRoot%\Minidump. Larger dumps are commonly stored at %SystemRoot%\MEMORY.DMP. Actual availability depends on dump settings and whether Windows could write the file.
Should I use Driver Verifier to find the cause?
Only when simpler diagnostic methods are insufficient and you understand its recovery implications. Driver Verifier can trigger a bug check when it detects a violation, so it is not an appropriate first step on an unstable everyday computer.
Sources
- Microsoft Learn: Bug Check Code Reference
- Microsoft Learn: Bug Check 0x97 — BOUND_IMAGE_UNSUPPORTED
- Microsoft Learn: Bug Checks (Blue Screens)
- Microsoft Learn: Analyze a Kernel-Mode Dump File by Using WinDbg
- Microsoft Learn: Handling a Bug Check When Driver Verifier Is Enabled
- Microsoft Support: Use the System File Checker Tool to Repair Missing or Corrupted System Files
CONTENT
Quick Answer
BOUND_IMAGE_UNSUPPORTED (0x00000097) is a Windows bug check associated with a blue screen error (BSOD). The stop code alone does not establish the root cause of a crash. Investigate the error details, recent system changes, and available crash dump evidence before attempting repairs.
If Windows crashes repeatedly, back up important data when possible, review recently changed drivers and software, and analyze the crash dump if necessary. Do not assume that updating a driver, repairing system files, or replacing hardware will resolve this specific error without supporting evidence.
What Does BOUND_IMAGE_UNSUPPORTED Mean?
Windows uses bug checks to stop the operating system when it encounters a serious condition. The identifier 0x00000097 corresponds to BOUND_IMAGE_UNSUPPORTED in Microsoft's bug check reference.
This is an uncommon error. The stop code by itself does not provide enough information to identify the cause of an individual crash. Additional information, such as bug-check parameters, system configuration, and crash dump analysis, may be needed to determine what happened.
Symptoms
Depending on the circumstances, a Windows system experiencing this bug check may show the following general stop-error symptoms:
- A blue screen displaying the BOUND_IMAGE_UNSUPPORTED stop code.
- An unexpected system restart or shutdown.
- Repeated crashes during startup or normal operation.
- A crash dump file being created before the system restarts, if dump collection is configured and succeeds.
These are general Windows crash symptoms, not symptoms uniquely associated with this particular bug check.
Possible Causes
The exact cause must be established through diagnosis. The following are general areas to investigate rather than confirmed causes of bug check 0x00000097.
- Recent driver changes: A newly installed or updated driver may be relevant if the crashes began immediately afterward.
- System software changes: Recently installed software that uses low-level system components may warrant investigation.
- Hardware or firmware changes: Newly installed devices or recent configuration changes may provide useful diagnostic clues.
- Operating system problems: Other Windows errors or system corruption may indicate a broader issue requiring investigation.
- Insufficient diagnostic evidence: Without a crash dump or additional details, the actual cause may remain undetermined.
A module name shown on a blue screen or in a crash report is a clue, not conclusive proof that the module caused the failure.
How to Troubleshoot BOUND_IMAGE_UNSUPPORTED (0x00000097)
1. Record the Stop Code and Recent Changes
Before changing system settings, record the complete stop code and any additional information displayed on the blue screen.
- Photograph the error screen if it disappears before you can record its details.
- Note when the crash occurred and what the computer was doing at the time.
- Record any recent driver installations, Windows updates, software installations, or hardware changes.
- Determine whether the error occurred once or has repeatedly occurred under similar conditions.
This information helps narrow the investigation and prevents unnecessary changes to a working system.
2. Restart Windows and Check Whether the Error Returns
If Windows starts normally after a single crash, save important files and monitor the computer for further problems. A successful restart does not prove that the underlying issue has been resolved.
If the computer repeatedly crashes or cannot start normally, avoid unnecessary restart attempts. Use Windows Recovery Environment when appropriate and protect important data before attempting repairs that could affect the installation.
3. Review Recent Driver Changes
If the problem began after a driver update or hardware installation, investigate the relevant device first.
- Open Device Manager.
- Inspect relevant devices for warning symbols or reported device problems.
- Open the device's properties and review its driver information and device status.
- Check the computer or device manufacturer's official support website for a compatible driver.
- If a recent driver update is strongly associated with the crashes, consider rolling it back when the option is available and appropriate.
Driver rollback or reinstallation is a general troubleshooting measure, not a confirmed fix for this specific stop code. Avoid third-party driver download sites and do not remove essential storage or boot drivers without an appropriate recovery plan.
4. Check Windows Update
Review Windows Update and its update history to identify recent changes that might be relevant to the crash.
- Open Windows Settings.
- Navigate to Windows Update and check for applicable updates.
- Review the update history for installations around the time the crashes began.
- Check the computer manufacturer's support website for relevant compatibility information.
Install applicable updates from trusted sources. If the problem began immediately after a particular update, investigate its known issues and supported removal or recovery options before uninstalling it.
5. Check Windows System File Integrity
If other evidence suggests that protected Windows system files may be damaged, use Microsoft's Deployment Image Servicing and Management (DISM) tool and System File Checker (SFC). These tools address general system-image and file-integrity problems; they are not documented as guaranteed fixes for BOUND_IMAGE_UNSUPPORTED.
Open Windows Terminal or Command Prompt as an administrator and run the following command:
DISM.exe /Online /Cleanup-Image /RestoreHealthDISM attempts to repair the running Windows image. Depending on the system, it may require access to Windows Update or an appropriate repair source.
After DISM finishes, run:
sfc /scannowSFC scans protected system files and attempts to repair integrity violations. Review the final result and follow any instructions it provides.
If either command reports an error, record the complete message before attempting additional repairs. Do not manually replace Windows system files with files obtained from unofficial sources.
6. Review System Events
Event Viewer may contain information about related device failures, service errors, or system events occurring around the crash time.
- Open Event Viewer.
- Navigate to Windows Logs > System.
- Review critical and error events near the time of the blue screen.
- Compare the timestamps with recent system changes and other diagnostic evidence.
An event recorded at the same time as a crash is not necessarily its cause. Use event details as supporting evidence rather than treating every critical or error entry as a confirmed explanation.
Advanced Troubleshooting: Analyze a Windows Crash Dump
If the error keeps recurring and basic checks do not identify a likely cause, analyze a crash dump. This approach is particularly useful for IT support technicians and system administrators.
1. Locate the Crash Dump
Check the following standard locations:
%SystemRoot%\Minidump— commonly used for small memory dumps.%SystemRoot%\MEMORY.DMP— commonly used for larger kernel, automatic, or complete memory dumps, depending on the system configuration.
A dump file may not exist if crash-dump collection was not configured, the system could not write the file, or the crash occurred under circumstances that prevented dump creation.
Preserve the original dump and work on a copy where practical. Crash dumps can contain sensitive information, so do not upload them to public forums or share them with untrusted parties.
2. Analyze the Dump with WinDbg
WinDbg is Microsoft's debugging tool for analyzing Windows crashes. Install it from an official Microsoft source and open the relevant dump file.
In the debugger command window, run:
!analyze -vThis command requests a detailed automated analysis of the crash dump. Review the reported bug-check code and parameters, stack trace, module information, and other available findings.
Ensure that symbols are configured appropriately and that the dump corresponds to the crash being investigated. An incomplete dump, missing symbols, or limited diagnostic data may prevent a definitive conclusion.
3. Interpret the Results
Use the debugger's findings alongside the crash circumstances and recent system changes.
- Check whether the dump confirms the expected bug-check code.
- Review the stack trace and relevant module information.
- Compare repeated crashes to see whether the same components appear in similar circumstances.
- Check relevant driver versions and manufacturer documentation before making changes.
A driver or module identified during automated analysis is not necessarily the original cause. Avoid replacing system files or removing drivers solely because their names appear in the report.
Driver Verifier should not be the first troubleshooting step. It can deliberately trigger a system crash when it detects a driver violation. Use it only when justified by the evidence and when appropriate recovery access is available.
Verification
After making a targeted change, check whether the original problem recurs under the same or similar conditions.
- Confirm that Windows starts and operates normally.
- Repeat the activity that previously triggered the crash, when safe.
- Review new system events and crash dumps for additional failures.
- Verify that any changed driver or software remains compatible with the computer and installed Windows version.
One successful restart is not sufficient to prove that the problem is permanently resolved. If the error returns, preserve the new evidence and compare it with the earlier crash.
Recovery Options
If Windows cannot start normally, Windows Recovery Environment may provide access to Safe Mode, System Restore, or supported update-removal options, depending on the installation and available recovery configuration.
Before attempting a major recovery operation, back up important files where possible. If BitLocker device encryption is enabled, make sure the required recovery key is available before entering recovery workflows that may request it.
For a work-managed computer, consult the IT administrator before changing drivers, security software, firmware, or system configuration. If the error persists, provide the technician with the exact stop code, Windows version, recent changes, relevant event records, and available crash dump analysis.
Frequently Asked Questions
Is BOUND_IMAGE_UNSUPPORTED (0x00000097) a hardware error?
The stop code alone does not establish a hardware failure. Additional evidence is needed to determine whether the problem relates to hardware, drivers, software, or another system condition.
Does this stop code always mean a driver is incompatible?
No. Do not infer a confirmed root cause from the stop-code name alone. Investigate the bug-check details and available crash dump before deciding on a corrective action.
Can I fix this error by reinstalling Windows?
Reinstalling Windows should not be the first response to an isolated crash. Start with evidence collection and targeted troubleshooting. Consider reinstallation only when justified by the diagnosis and after making appropriate backups.
Where are Windows crash dump files stored?
Small memory dumps are commonly stored in %SystemRoot%\Minidump. Larger dumps are commonly stored at %SystemRoot%\MEMORY.DMP. Actual availability depends on dump settings and whether Windows could write the file.
Should I use Driver Verifier to find the cause?
Only when simpler diagnostic methods are insufficient and you understand its recovery implications. Driver Verifier can trigger a bug check when it detects a violation, so it is not an appropriate first step on an unstable everyday computer.
Sources
- Microsoft Learn: Bug Check Code Reference
- Microsoft Learn: Bug Check 0x97 — BOUND_IMAGE_UNSUPPORTED
- Microsoft Learn: Bug Checks (Blue Screens)
- Microsoft Learn: Analyze a Kernel-Mode Dump File by Using WinDbg
- Microsoft Learn: Handling a Bug Check When Driver Verifier Is Enabled
- Microsoft Support: Use the System File Checker Tool to Repair Missing or Corrupted System Files
Was this guide useful?
Your answer helps us keep BISONKB accurate and practical.