Fix Windows Error 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH

Quick Answer

The Windows error 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH indicates that a driver or Windows system file may be corrupted or has an unexpected checksum. Microsoft also identifies disk errors, faulty RAM, and a corrupted paging file as possible causes.

Start by disconnecting unnecessary external devices and restarting the computer. If Windows starts, check for recent driver or software changes, run the System File Checker (SFC), and inspect the system drive for errors. If Windows cannot start, use Windows Recovery Environment (WinRE) to run Startup Repair or access other recovery options. If the error persists, investigate the storage drive and memory rather than repeatedly reinstalling Windows.

What Does STATUS_IMAGE_CHECKSUM_MISMATCH Mean?

A checksum is a value used to help verify the integrity of data. Windows checks certain executable images, including drivers and system components, before loading them. This error occurs when a file's header checksum does not match the expected value.

The error can appear during startup, while loading a driver, or during normal computer use. The exact symptoms depend on which file is affected and when Windows attempts to load it.

Microsoft documents this error as bug check 0xC0000221. The official reference is Bug Check 0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH.

Common Causes

• Corrupted Windows system files: Important operating-system files may have been damaged or modified unexpectedly.
• Driver corruption: A device driver may be damaged or incompatible with the current Windows installation.
• Storage problems: File-system corruption or a failing HDD or SSD can cause data to become unreadable or corrupted.
• Faulty RAM: Defective memory can contribute to data corruption and system crashes.
• Paging-file corruption: Problems affecting the Windows paging file may contribute to this error.
• Interrupted updates or unexpected shutdowns: These events may leave system files or pending operations in an inconsistent state.
• Malware: Malicious software can damage or modify system files, although this error alone does not establish a malware infection.

These are possible causes, not confirmed diagnoses. The file named in the error message, crash dumps, system logs, and hardware test results can help narrow the problem.

Symptoms of Error 0xC0000221

• A blue screen appears with the error code or its status name.
• Windows fails to start or repeatedly restarts.
• The system reports that a device driver could not be loaded.
• The computer crashes after installing a driver or Windows update.
• Startup becomes unreliable, or other file-system errors appear.

If the message identifies a particular file, record its complete filename before troubleshooting. It is useful evidence, but it does not automatically prove that the named component itself is the original cause.

Before You Begin

• Disconnect nonessential USB devices, external storage devices, docks, and other recently attached peripherals. Keep essential input devices connected.
• If Windows is accessible, back up important files before performing disk repairs or other recovery operations.
• If the drive is making unusual mechanical noises, repeatedly disconnecting, or reporting serious hardware errors, stop unnecessary repair attempts and prioritize data recovery.
• If BitLocker or device encryption is enabled, make sure the required recovery key is available before entering recovery or changing boot settings.
• If the computer is managed by an organization, contact the IT administrator before changing drivers, firmware, or recovery settings.

Method 1: Restart the Computer and Check Recent Changes

Begin with simple checks before making system changes.

1. Turn off the computer if it is stuck in a restart loop.
2. Disconnect nonessential external devices.
3. Turn the computer back on and check whether Windows starts normally.
4. If the error began immediately after installing a driver, application, or update, note the change.
5. If Windows starts, check whether the error returns during the same activity or when a particular device is connected.

If disconnecting a peripheral prevents the error, investigate its driver, firmware, cable, and hardware. Do not assume that the peripheral is defective solely because the error disappears.

Method 2: Repair Windows System Files Using SFC

System File Checker (SFC) scans protected Windows system files and replaces incorrect versions when it can obtain the appropriate files. Microsoft specifically recommends this utility when troubleshooting error 0xC0000221.

When Windows Starts Normally

1. Open Start and search for Command Prompt.
2. Select Run as administrator.
3. Enter the following command and press Enter.

sfc /scannow

Wait for the scan to finish. Do not close the command window while the scan is running.

Understand the Result

• Windows Resource Protection did not find any integrity violations: SFC did not detect violations in the protected system files it checked.
• Windows Resource Protection found corrupt files and successfully repaired them: Restart Windows and check whether the error returns.
• Windows Resource Protection found corrupt files but was unable to fix some of them: Repair the Windows component store using DISM, then run SFC again.
• The scan could not be performed: Check the command, permissions, Windows state, and whether an offline recovery procedure is required.

For additional details, see Microsoft's official SFC command reference.

Method 3: Repair the Windows Component Store Using DISM

If SFC cannot repair some files, the Windows component store may also need attention. DISM can repair the component store using suitable repair sources. This is a general Windows repair procedure, not a guaranteed fix for every occurrence of error 0xC0000221.

Use this method when Windows can start and you can open an elevated Command Prompt. An internet connection may be needed if Windows Update is used as the repair source.

1. Open Command Prompt as an administrator.
2. Run the following command.

DISM.exe /Online /Cleanup-Image /RestoreHealth

3. Wait for the operation to finish. It may take several minutes or longer.
4. After DISM completes, run SFC again.

sfc /scannow

If DISM reports that source files could not be found or the repair failed, do not repeatedly run the same command without investigating the error. A suitable Windows installation source or further diagnosis may be necessary.

Refer to Microsoft's guidance on repairing Windows image and component-store corruption.

Method 4: Check the Drive for File-System Errors

Storage errors can cause Windows files to become corrupted or unreadable. Check the file system, particularly if the computer has experienced other disk errors, slow reads, or unexpected shutdowns.

Run CHKDSK

On Windows, open Command Prompt as an administrator and run the following command, replacing C: if Windows is installed on another drive letter.

chkdsk C: /f

The /f parameter instructs CHKDSK to correct file-system errors it can repair. If the volume is in use, Windows may ask to schedule the check for the next restart.

Microsoft's 0xC0000221 guidance also mentions chkdsk /f /r for investigating and repairing file-system problems. The /r parameter includes the functionality of /f and checks for bad sectors while attempting to recover readable information. This can take considerably longer, especially on large or damaged drives.

chkdsk C: /f /r

CHKDSK cannot repair physically defective RAM or guarantee recovery from a failing storage device. If errors recur after repair, investigate the drive's health and hardware connections.

Method 5: Use Startup Repair if Windows Will Not Boot

If the error prevents Windows from starting, use Windows Recovery Environment (WinRE). Startup Repair can diagnose and repair certain startup problems, although it may not correct the underlying cause of a checksum mismatch.

Open Windows Recovery Environment

If Windows reaches the sign-in screen, hold Shift while selecting Power and then Restart. Alternatively, use Windows installation or recovery media if the installed system cannot start. Windows may also enter recovery automatically after repeated startup failures.

Run Startup Repair

1. On the recovery options screen, select Troubleshoot.
2. Select Advanced options.
3. Select Startup Repair.
4. Choose the Windows installation if prompted and provide the required credentials.
5. Allow the repair to complete, then restart the computer and check whether Windows starts.

If Startup Repair fails, note the reported result rather than repeatedly running it without a new diagnostic clue. See Microsoft's documentation for the Windows Recovery Environment.

Method 6: Roll Back a Recent Driver or System Change

If the error began after a driver installation or update and Windows can still start, investigate that change before replacing files manually.

1. Open Device Manager.
2. Expand the category associated with the affected device, if known.
3. Open the device's Properties and select the Driver tab.
4. If available, select Roll Back Driver and follow the prompts.
5. Restart Windows and check whether the error returns.

The rollback option may be unavailable if Windows does not retain an earlier driver. In that case, obtain a compatible driver from Windows Update or the computer or device manufacturer's official support site.

If the problem began after a Windows update, review the update history and consider the supported update recovery options available for your Windows version. Do not remove unrelated updates or drivers without evidence connecting them to the problem.

Method 7: Test the Computer's Memory

Faulty RAM is one possible cause of checksum mismatches and other forms of data corruption. Memory testing becomes particularly important when the error recurs after Windows system files have been repaired, or when crashes occur with different stop codes.

1. Save your work and close open applications.
2. Press Windows + R.
3. Enter mdsched.exe and press Enter.
4. Select the option to restart and check for memory problems, if Windows offers it.
5. Allow the test to complete and review the results after Windows restarts.

A clean result does not conclusively rule out intermittent memory problems. If errors are detected, consult the computer or motherboard manufacturer's memory-testing and service instructions.

If you recently changed memory modules, overclocking settings, or memory profiles, return to supported manufacturer settings for diagnostic testing. Before changing BIOS/UEFI settings, document the current configuration and ensure that any encryption recovery requirements are satisfied.

Method 8: Use System Restore if Available

If the error started after a recent system change, System Restore may help return system files, drivers, and settings to an earlier restore point.

1. Open Windows Recovery Environment.
2. Select Troubleshoot and then Advanced options.
3. Select System Restore, if available.
4. Choose a restore point from before the problem began.
5. Review the affected programs and drivers, then confirm the restoration.

System Restore is not available on every configuration, and suitable restore points may not exist. It is intended to roll back system changes rather than replace a backup of personal files. Review the recovery prompts carefully before proceeding.

Advanced Troubleshooting: Identify the Damaged Component

If the error persists, collect evidence before attempting more disruptive repairs.

• Record the named file: Note the driver or system filename shown on the blue screen or startup error. Do not manually delete or replace it.
• Review system logs: If Windows starts, open Event Viewer and inspect the System log around the time of the crash for related disk, driver, or hardware events.
• Inspect crash dumps: If a dump file is available, a qualified technician can use Windows debugging tools to investigate the failing component. A module mentioned in a dump is a diagnostic clue, not necessarily proof of root cause.
• Check storage health: Use the computer or storage manufacturer's supported diagnostic utility and review reported hardware errors.
• Investigate recurring corruption: If repaired files become corrupted again, investigate storage, memory, power, and other hardware problems rather than treating each file as an isolated failure.

Crash dumps may contain usernames, file paths, memory contents, or other sensitive information. Review and sanitize diagnostic files before sharing them publicly.

What to Do if the Error Continues

If the error persists after system-file repair, disk checks, and relevant driver or memory diagnostics, consider the next step according to the evidence.

• Suspected storage failure: Prioritize data recovery and professional hardware diagnosis.
• Confirmed memory errors: Follow the manufacturer's supported memory troubleshooting or replacement procedure.
• Evidence of Windows corruption without hardware errors: Consider an appropriate Windows recovery or repair installation method for the installed version.
• Repeated startup failure: Use recovery media for the correct Windows version and seek assistance if recovery tools cannot restore startup.

Reinstalling Windows should generally be a later option, after important data is backed up and likely hardware problems have been assessed. A reinstall may not solve the issue if defective hardware continues to corrupt data.

Frequently Asked Questions

Is 0xC0000221 a hardware or software error?

It can involve either. Corrupted Windows system files or drivers are software-related possibilities, while faulty RAM and storage errors are possible hardware-related causes. Diagnostic evidence is needed to distinguish them.

Can SFC fix STATUS_IMAGE_CHECKSUM_MISMATCH?

SFC can repair certain corrupted protected Windows system files. It may resolve the problem when such corruption is responsible, but it cannot repair defective RAM or physically failing storage hardware.

What if Windows cannot start at all?

Enter Windows Recovery Environment using automatic recovery or Windows installation media. Try Startup Repair first, then consider other available recovery options such as System Restore. Protect encrypted data and important files before undertaking recovery operations.

Should I replace the file named in the error message?

No, not as an initial troubleshooting step. The filename helps identify what Windows was attempting to load, but the underlying cause may be file-system corruption, faulty memory, or a storage problem. Use supported repair procedures instead of downloading individual system files from unofficial websites.

Does this error always mean the hard drive is failing?

No. Microsoft lists disk errors as one possible cause, alongside driver and system-file corruption, faulty RAM, and a corrupted paging file. Storage diagnostics and other evidence are needed to determine whether the drive is responsible.

Can reinstalling Windows solve this error?

A repair installation or reinstall may help when Windows corruption is responsible. However, reinstalling should not be the first step, and it may not resolve recurring corruption caused by defective memory or storage hardware.

Sources

• Microsoft Learn: Bug Check 0xC0000221 — STATUS_IMAGE_CHECKSUM_MISMATCH
• Microsoft Learn: SFC command reference
• Microsoft Learn: Fix Windows Update corruption and installation failures
• Microsoft Learn: Windows Recovery Environment
• Microsoft Learn: Windows startup troubleshooting