How to Fix Windows Bug Check 0x8B: MBR_CHECKSUM_MISMATCH

Quick Answer

Windows bug check 0x0000008B (MBR_CHECKSUM_MISMATCH) indicates that the checksum calculated for the Master Boot Record (MBR) does not match the checksum supplied by the operating-system loader. Microsoft identifies a virus, including boot-sector malware, as a typical cause.

Investigate possible malware, protect important data, and use trusted Windows recovery tools if the computer cannot start. Do not immediately rewrite the MBR, modify partitions, or reinstall Windows. The appropriate repair depends on the system's boot configuration and the underlying cause. See Microsoft's official documentation for bug check 0x8B.

What Is MBR_CHECKSUM_MISMATCH?

The Master Boot Record is a disk structure used by systems that boot from a disk partitioned with the traditional MBR scheme. It contains boot code and partition-table information. During startup, Windows checks the MBR checksum against the value supplied by the operating-system loader.

When the values do not match, Windows raises bug check 0x8B. A checksum mismatch indicates an inconsistency in boot-related data; it does not, by itself, prove that the disk has failed or that malware is definitely present.

Modern computers may use UEFI firmware and GUID Partition Table (GPT) disks instead of legacy BIOS and MBR. Identify the actual boot configuration before following any manual boot-repair procedure.

Common Causes

• Boot-sector malware: Malware may modify the MBR or other boot-related components. Microsoft identifies a virus as a typical cause of this stop code.
• Changes to boot information: Disk cloning, partitioning utilities, or boot-management software may be relevant if the error started immediately after their use.
• Data corruption: Corruption affecting boot-related information may require further investigation.
• Storage problems: A failing disk can cause data-access problems, although this bug check alone does not establish a hardware failure.
• Recent configuration changes: Changes to firmware settings, boot devices, or system software may provide useful diagnostic clues.

These are possible causes, not a definitive diagnosis. Investigate the evidence before choosing a repair.

Symptoms

• A blue screen displays MBR_CHECKSUM_MISMATCH or stop code 0x0000008B.
• The computer restarts unexpectedly during startup.
• Windows cannot complete the boot process.
• The problem appears after a disk, boot-configuration, or security-related change.
• The computer repeatedly fails to start normally.

These symptoms can overlap with other startup failures. Record the exact stop code and any additional error information.

Before You Begin

• Back up important files if the disk remains accessible.
• If BitLocker or device encryption is enabled, locate the recovery key before starting recovery operations.
• Record recent disk changes, software installations, malware alerts, and firmware modifications.
• Use trusted recovery media obtained from Microsoft or a reputable security vendor.
• If the disk reports hardware errors or appears to be failing, prioritize data recovery instead of repeatedly attempting repairs.

How to Fix MBR_CHECKSUM_MISMATCH

1. Check the Boot Device and Recent Changes

1. Disconnect nonessential USB storage devices and removable media.
2. Check whether the error started after connecting a new drive, cloning a disk, or changing the boot configuration.
3. If necessary, open the computer's firmware setup using the manufacturer's instructions.
4. Confirm that the intended Windows boot device is selected.
5. If a recent boot-order change is clearly responsible, restore the previous known-correct selection.

Do not randomly switch between UEFI and legacy BIOS/CSM modes or change storage-controller settings. Incorrect settings may introduce additional startup problems.

2. Scan for Malware

Because malware is a documented possible cause of bug check 0x8B, investigate the system for boot-related threats.

If Windows Starts

1. Open Windows Security.
2. Select Virus & threat protection.
3. Update security intelligence if a safe internet connection is available.
4. Run a full scan and review the results.
5. If persistent malware is suspected, consider Microsoft Defender Offline when supported by the installed system.

Microsoft Defender Offline restarts the computer and scans outside the normal Windows environment. Save open work before starting it. Availability and interface details can vary by Windows version.

For additional guidance, see Microsoft's malware detection and removal troubleshooting guidance.

If Windows Cannot Start

1. Use a separate, trusted computer to obtain appropriate recovery or antivirus media from its official vendor.
2. Create the media according to the vendor's instructions. The creation process may erase the USB drive.
3. Start the affected computer from the recovery media using its boot menu or documented firmware procedure.
4. Run a malware scan that supports examining relevant boot areas, if that capability is available.
5. Follow the security tool's documented instructions for handling detected threats and recovering the system.

Microsoft Safety Scanner is a malware-removal utility for compatible Windows systems, not a bootable rescue environment. It cannot replace recovery media when Windows will not start.

A clean scan does not prove that every boot component is intact. Continue with recovery diagnostics if the error persists.

3. Run Windows Startup Repair

Windows Recovery Environment (WinRE) provides tools for diagnosing certain startup failures.

1. Enter Windows Recovery Environment through Automatic Repair or by starting from official Windows installation media.
2. If using installation media, choose the option to repair the computer rather than beginning a new installation.
3. Select Troubleshoot > Advanced options > Startup Repair.
4. Select the Windows installation if prompted and follow the instructions.
5. After the operation finishes, restart the computer and check whether Windows starts normally.

Startup Repair may resolve certain boot-configuration or startup problems, but it is not a guaranteed fix for MBR_CHECKSUM_MISMATCH specifically.

Official references: Startup Repair and Windows Recovery Environment.

4. Check Disk and Storage Health

If malware scanning and Startup Repair do not resolve the problem, investigate whether the storage device has errors.

• Use the storage manufacturer's diagnostic utility, where available, to check drive health.
• Review available hardware diagnostics for storage-related errors.
• If disk problems are reported, prioritize backup or professional data recovery before attempting repairs that write to the disk.
• If the drive appears healthy, investigate boot configuration and recent disk-management changes rather than assuming hardware failure.

Storage diagnostics can help identify hardware problems, but they do not independently determine the cause of the checksum mismatch.

5. Consider Manual Boot-Record Repair

Manual boot-record repair should be considered only after identifying the actual disk layout, firmware mode, and nature of the damage. MBR and GPT systems use different boot structures, and repair procedures are not interchangeable.

Do not automatically run commands that rewrite the MBR, rebuild boot configuration data, mark partitions active, or format partitions just because bug check 0x8B occurred. Microsoft does not document a universal manual command sequence that guarantees resolution of this specific stop code.

If manual repair is necessary, follow the official Windows recovery guidance appropriate to the system or seek assistance from a qualified technician. Ensure important data is backed up and the target disk is positively identified before making changes.

Understanding Bug Check Parameters

Microsoft documents the following parameters for bug check 0x8B. They may help an experienced technician interpret crash information, but they do not independently identify the root cause.

For the authoritative parameter definitions, consult Microsoft's Bug Check 0x8B reference.

How to Verify the Fix

1. Restart the computer and confirm that Windows reaches the sign-in screen or desktop.
2. Check whether the stop error returns during subsequent normal startups.
3. Review antivirus results and confirm that detected threats have been handled.
4. Check storage diagnostics if disk-related symptoms were present.
5. Verify that the correct boot device and firmware configuration remain selected.
6. Back up important data and install appropriate security updates once the system is stable.

If the error recurs, record the diagnostic results and preserve any available crash information. Repeatedly applying unrelated boot repairs can make diagnosis more difficult.

When to Seek Professional Help

Contact a qualified technician or security professional if malware is detected in boot-related components, the computer remains unbootable, the disk reports hardware errors, or you cannot confidently identify the correct boot configuration.

For business systems or computers containing irreplaceable data, avoid destructive recovery attempts. If an infection is confirmed, use a known-clean device to follow appropriate account-security and incident-response procedures.

Frequently Asked Questions

Does MBR_CHECKSUM_MISMATCH always mean a virus is present?

No. Microsoft identifies a virus as a typical cause, but the stop code alone does not prove an infection. Investigate malware alongside other relevant boot and storage issues.

Can Startup Repair fix error 0x8B?

Startup Repair may resolve certain startup problems, but it is not a confirmed universal fix for this particular bug check. Malware and other causes may require separate investigation.

Should I run bootrec commands to fix this error?

Not automatically. The correct repair depends on the boot mode, disk partition style, and actual damage. Identify the configuration and protect important data before considering manual boot-record changes.

Can this error prevent Windows from starting?

Yes. Bug check 0x8B occurs during the boot process and may prevent Windows from starting normally.

What should I do if the error returns after a malware scan?

Review the scan results, confirm that detected threats were handled, and investigate storage health and boot configuration. If the cause remains unclear, obtain professional assistance rather than repeatedly rewriting boot records.

Sources

• Microsoft Learn: Bug Check 0x8B — MBR_CHECKSUM_MISMATCH
• Microsoft Support: Troubleshoot problems with detecting and removing malware
• Microsoft Learn: Microsoft Safety Scanner
• Microsoft Support: Startup Repair
• Microsoft Support: Windows Recovery Environment