How to Fix MEMORY_IMAGE_CORRUPT Blue Screen Error (0x000000A2)

## CONTENT

Quick Answer

The MEMORY_IMAGE_CORRUPT blue screen error (Bug Check 0x000000A2) occurs when Windows detects corruption in the in-memory image of an executable file. Microsoft documents this bug check as a failed cyclic redundancy check (CRC) on a memory range.

This error does not necessarily mean that a RAM module is defective. Memory instability, hardware problems, firmware issues, and other system-level problems may need investigation. Start by running Windows Memory Diagnostic, checking recent hardware and driver changes, and examining crash dumps if the problem continues.

What Is MEMORY_IMAGE_CORRUPT?

Windows loads executable images into memory when running operating-system components, drivers, and applications. During an integrity check, Windows may detect that data in a memory range does not match its expected CRC value.

A CRC (Cyclic Redundancy Check) is an integrity-checking mechanism used to detect unexpected changes in data. When Windows detects the documented memory-image corruption condition, it may stop the system and display the MEMORY_IMAGE_CORRUPT blue screen.

Microsoft also documents memory checks during system wake operations. Therefore, crashes occurring immediately after waking from sleep deserve particular attention.

MEMORY_IMAGE_CORRUPT Bug Check Parameters

The bug check uses four parameters. Parameter 1 identifies the violation type, while the remaining parameters provide additional information depending on the violation.

These parameters provide diagnostic information. They do not directly identify a defective RAM module or a specific physical hardware component.

Common Causes and Contributing Factors

The stop code identifies a memory-image integrity failure, but it does not independently establish the underlying root cause. Investigate the following possibilities:

1. RAM Problems

Defective memory modules, unstable memory operation, or memory-controller problems can contribute to data corruption. Memory diagnostic failures provide useful evidence for further hardware investigation.

2. Unstable Memory Overclocking

Manually configured memory timings or enabled XMP/EXPO profiles may cause instability when the memory configuration is not supported or stable with the processor and motherboard.

3. Driver or Firmware Problems

Recently updated drivers, incompatible device software, or firmware problems may contribute to system instability. Investigate these areas when the crash began after a hardware or software change.

4. Windows System File Corruption

Corrupted Windows components or protected system files may cause operating-system problems. DISM and System File Checker can investigate certain types of Windows corruption, although they are not specific fixes for bug check 0xA2.

5. Sleep and Resume Problems

If the computer crashes immediately after waking from sleep, investigate memory stability, BIOS/UEFI firmware, and relevant device drivers.

6. Motherboard or Other Hardware Issues

Memory slots, motherboard circuitry, processor memory controllers, or other hardware problems may require further investigation if the error continues despite software troubleshooting.

Symptoms of MEMORY_IMAGE_CORRUPT

Common symptoms include:

• Blue screen displaying MEMORY_IMAGE_CORRUPT.
• Windows stop code 0x000000A2.
• Unexpected system restarts.
• Crashes after waking from sleep.
• Repeated blue screens during normal computer operation.
• System instability following hardware or driver changes.
• Different stop codes appearing across multiple crashes.

These symptoms are not exclusive to this error. Crash dumps and hardware diagnostics are needed to narrow down the cause.

How to Fix MEMORY_IMAGE_CORRUPT in Windows

1. Restart the Computer and Check Whether the Error Returns

If the error occurred only once, restart Windows and monitor the computer.

1. Save any available work.
2. Restart the computer.
3. Check whether Windows starts normally.
4. Use the computer and observe whether the blue screen returns.
5. If the crash occurred after sleep, check whether waking the computer reproduces the problem.

Record the error code, date, time, and circumstances surrounding the crash.

2. Disconnect Recently Connected Hardware

A recently connected peripheral or hardware component may contribute to system instability.

1. Shut down the computer.
2. Disconnect nonessential USB devices, docking stations, external drives, and recently connected peripherals.
3. Keep only the devices required to operate the computer.
4. Start Windows and check whether the error returns.
5. Reconnect devices individually if the system becomes stable.

If reconnecting a particular device consistently reproduces the crash, investigate its driver, firmware, and compatibility.

3. Run Windows Memory Diagnostic

Windows Memory Diagnostic checks installed memory for certain memory problems.

1. Press Windows + R.
2. Enter the following command:

mdsched.exe

1. Click Restart now and check for problems (recommended).
2. Allow the computer to restart and complete the memory test.
3. Wait for Windows to start again.
4. Review the diagnostic results.

If memory errors are reported, investigate the RAM modules, memory slots, motherboard compatibility, and memory configuration. A failed test does not automatically identify which component is defective.

If the result is not displayed after restarting, check Event Viewer under Windows Logs > System for events from the MemoryDiagnostics-Results provider.

4. Check BIOS/UEFI Memory Settings

If XMP, EXPO, or manually configured memory timings are enabled, test the computer using the manufacturer's standard memory configuration.

1. Identify the motherboard or computer model.
2. Consult the manufacturer's BIOS/UEFI documentation.
3. Check whether memory overclocking or custom timings are enabled.
4. If appropriate, restore the standard memory configuration.
5. Save the settings and restart Windows.
6. Monitor the computer for further crashes.

Do not randomly change memory voltage or timings. Seek qualified assistance if you are unfamiliar with firmware configuration.

5. Install Available Windows Updates

Install applicable Windows updates to obtain available operating-system improvements and compatible updates.

1. Open Windows Settings.
2. Select Windows Update.
3. Click Check for updates.
4. Install applicable updates.
5. Restart the computer if requested.
6. Check whether the blue screen returns.

6. Update or Roll Back Device Drivers

If the problem began after installing new hardware or updating a driver, investigate the related device driver.

Update a driver

1. Right-click Start and open Device Manager.
2. Expand the category containing the relevant device.
3. Right-click the device.
4. Select Update driver.
5. Choose Search automatically for drivers.
6. Install an applicable update and restart Windows.

Roll back a driver

1. Open Device Manager.
2. Locate the device whose driver was recently updated.
3. Right-click it and select Properties.
4. Open the Driver tab.
5. Select Roll Back Driver if available.
6. Follow the instructions and restart Windows.

Download drivers from the official computer, motherboard, or device manufacturer's website. Do not assume that every driver appearing in a crash dump is responsible for the error.

7. Repair Windows System Files Using DISM and SFC

If Windows also exhibits system-file corruption or other operating-system problems, use Microsoft's built-in repair utilities.

Open Command Prompt as an administrator and execute:

DISM.exe /Online /Cleanup-image /Restorehealth

DISM checks and attempts to repair the Windows component store. An internet connection may be required to obtain repair files through Windows Update.

After DISM completes, execute:

sfc /scannow

System File Checker scans protected Windows system files and attempts to repair detected corruption.

Wait until the scan reaches 100% and review the result.

• No integrity violations: SFC did not find protected system-file corruption.
• Corrupt files successfully repaired: SFC repaired the detected files.
• Some files could not be repaired: Further Windows repair investigation may be necessary.

Restart Windows after completing the repairs. These tools do not repair defective RAM or guarantee a solution for MEMORY_IMAGE_CORRUPT.

8. Run Manufacturer Hardware Diagnostics

If the error continues, use the diagnostic tools provided by the computer or motherboard manufacturer.

1. Identify the exact computer or motherboard model.
2. Visit the manufacturer's official support website.
3. Locate the hardware diagnostic utility or instructions.
4. Run available memory and relevant hardware tests.
5. Record any diagnostic error codes.

If errors are reported, a qualified technician can test individual memory modules and slots where the hardware permits.

Before opening a desktop computer, disconnect power and follow appropriate electrostatic-discharge precautions. Laptop memory may be soldered or inaccessible without disassembly.

Advanced Troubleshooting Using Crash Dumps

IT support technicians and system administrators can use Windows crash dumps to investigate bug check parameters, loaded modules, and execution stacks.

1. Locate Windows Crash Dump Files

Windows commonly stores crash dumps in these locations:

The actual location depends on the configured dump type and system settings.

To review the dump configuration:

1. Search for Advanced system settings.
2. Open the Advanced tab in System Properties.
3. Under Startup and Recovery, click Settings.
4. Review the Write debugging information option.
5. Check the configured dump type and destination.

2. Analyze the Dump Using WinDbg

Microsoft WinDbg can analyze Windows crash dump files.

1. Install WinDbg using Microsoft's official distribution.
2. Open the relevant crash dump file.
3. Allow the debugger to load the required symbols.
4. Enter the following command in the debugger command window:

!analyze -v

This command performs verbose crash analysis.

Review the following information:

• BUGCHECK_CODE: The reported bug check code.
• Arguments: The four bug check parameters.
• MODULE_NAME: A module associated with the analysis.
• IMAGE_NAME: An image associated with the analysis.
• STACK_TEXT: Stack information that can help identify the execution path.

Do not assume that a module listed in the analysis is necessarily defective. Correlate the findings with memory tests, recent changes, and repeated crash patterns.

3. Compare Bug Check Parameters Across Crashes

If multiple crash dumps are available, compare their bug check codes and parameters.

Look for repeated parameter patterns and examine whether the crashes occur during the same activity, such as waking from sleep or operating a particular device.

Repeated patterns may help narrow the investigation, but the parameters alone cannot establish the exact faulty component.

4. Protect Crash Dump Information

Use the least extensive dump type that provides sufficient diagnostic information. Avoid collecting complete memory dumps unnecessarily.

What to Do If Windows Cannot Start

If the computer repeatedly crashes during startup, use Windows Recovery Environment (WinRE) where available.

1. Allow Windows to enter the recovery environment if automatic recovery starts.
2. Select Troubleshoot.
3. Open Advanced options.
4. Consider running Startup Repair.
5. If the problem began after a recent update, consider the applicable update-uninstall option.
6. If a suitable restore point exists, consider using System Restore.

Some recovery operations may require a BitLocker recovery key. Protect important data before performing major recovery operations.

Do not immediately reset or reinstall Windows because of a single MEMORY_IMAGE_CORRUPT crash.

How to Verify That the Error Is Resolved

After troubleshooting, monitor the computer under normal operating conditions.

• Windows starts without displaying the 0x000000A2 error.
• The computer wakes from sleep normally if sleep previously triggered the crash.
• Memory diagnostics do not report recurring errors.
• Relevant hardware and drivers operate normally.
• No new crash dumps report the same bug check.
• The computer remains stable during normal workloads.

If the problem returns, preserve the latest crash dump and diagnostic results for further investigation.

When to Contact Hardware Support

Contact the computer manufacturer or a qualified hardware technician if:

• Memory diagnostics repeatedly report errors.
• The system continues crashing with standard memory settings.
• Multiple hardware tests report failures.
• The computer exhibits other signs of hardware instability.
• The issue persists despite appropriate software troubleshooting.

Provide the computer model, RAM configuration, BIOS/UEFI version, bug check parameters, crash timestamps, and hardware diagnostic results.

Frequently Asked Questions

Does MEMORY_IMAGE_CORRUPT mean my RAM is faulty?

No. RAM problems are an important possibility, but the error does not automatically prove that a memory module is defective. Run memory diagnostics and investigate other hardware and system-level causes.

Can a driver cause the 0x000000A2 blue screen?

A driver issue may be worth investigating, particularly when the problem begins after a driver update or hardware installation. However, the bug check alone does not establish that a particular driver is responsible.

Why does MEMORY_IMAGE_CORRUPT happen after sleep?

Microsoft documents memory checks during system wake operations. If the crash occurs after waking from sleep, investigate memory stability, firmware, and relevant device drivers.

Can Windows Memory Diagnostic fix this error?

No. Windows Memory Diagnostic is a testing utility, not a repair tool. It can help identify certain memory problems that require further investigation.

Can DISM and SFC resolve MEMORY_IMAGE_CORRUPT?

They can repair certain Windows component and protected system-file problems, but they are not specific fixes for this bug check and cannot repair defective physical memory.

Should I reinstall Windows to resolve this blue screen?

Reinstallation should not be the first troubleshooting step. Investigate memory stability, recent driver changes, firmware, and hardware diagnostics before considering major recovery operations.

Sources

• Microsoft Learn – Bug Check 0xA2: MEMORY_IMAGE_CORRUPT
• Microsoft Learn – !analyze (WinDbg)
• Microsoft Learn – Generate a Kernel or Complete Crash Dump
• Microsoft Support – Using System File Checker in Windows
• Microsoft Support – Update Drivers Through Device Manager in Windows