Stop Codes (Blue Screen)

Microsoft gives these steps on Troubleshooting Windows unexpected restarts and stop code errors for any stop code. It is Microsoft's general page for stop codes, so these steps apply to every code of this group.

Microsoft's general page for any stop code. It says a single restart usually fixes the problem; these steps are for a stop code that keeps coming back. Its Windows 10 tab has the same steps with the Windows 10 Settings path.

1. Remove new hardware

   If you added hardware just before the errors started, shut the PC down, take that hardware out, and start the PC again.

2. Use safe mode if Windows won't start

   Changes boot or startup

   If the PC has trouble restarting, start it in safe mode (Microsoft's 'start your PC in safe mode' page explains how). You can do the other steps from safe mode.

   Microsoft advises: Keep track of what you change so you can undo it, and return the PC to a normal startup when you are done. (How to perform a clean boot in Windows)

3. Check Device Manager

   Disables or removes drivers

   Right-click the Start button and choose Device Manager. Look for any device marked with an exclamation point (!).

   Right-click that device and choose Update driver. If a new driver doesn't fix it, disable or uninstall that device as the next try.

   Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

4. Leave enough free disk space

   Windows and some apps need free space for swap files and other work. The exact amount varies, but Microsoft suggests keeping about 10% to 15% of the drive free.

5. Install the latest updates

   Select Start > Settings > Windows Update, then Check for updates.

6. Restore Windows

   Changes the Windows installation

   If none of this helps, restore Windows from a system restore point, or use another option on Microsoft's 'Recovery options in Windows' page - pick the one that best matches your situation.

   Microsoft advises: Back up your important files before you start. If BitLocker is on, you'll need your BitLocker recovery key for most recovery options in Windows RE. (Recovery options in Windows)

Microsoft gives these steps on Bug check 0xA: IRQL_NOT_LESS_OR_EQUAL for 1 code of this group: 0x0000000A. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Note the driver and check the System log

   Examine the name of the driver if it was listed on the blue screen.

   Check the System Log in Event Viewer for other error messages that might help pinpoint the device or driver, especially critical errors from the same time as the blue screen.

2. Faulty hardware

   If hardware was added recently, remove it to see whether the error comes back. If existing hardware has failed, remove or replace it.

   Run the hardware diagnostics supplied by the system manufacturer (see the computer's owner's manual).

Microsoft gives these steps on Bug Check 0x12: TRAP_CAUSE_UNKNOWN for 1 code of this group: 0x00000012. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Check the System log

   Check the System log in Event Viewer for messages that name the device or driver.

2. Disable or update the named driver

   Disables or removes drivers

   If a driver is named in the stop message, disable it or check with the maker for an update.

   Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

3. Check new hardware

   Confirm any newly installed hardware is compatible with this Windows version.

Microsoft gives these steps on Bug Check 0x18: REFERENCE_BY_POINTER for 1 code of this group: 0x00000018. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Check the System log

   Check the System log in Event Viewer for messages that name the device or driver.

2. Disable or update the named driver

   Disables or removes drivers

   If a driver is named in the stop message, disable it or check with the maker for an update.

   Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

3. Check new hardware

   Confirm any newly installed hardware is compatible with this Windows version.

Microsoft gives these steps on Bug check 0x1E: KMODE_EXCEPTION_NOT_HANDLED for 1 code of this group: 0x0000001E. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Remove or disable the faulty driver

   Disables or removes drivers

   If a driver is named, disable or remove it; also disable or remove recently added drivers or services. If it fails during startup on an NTFS system partition, Safe Mode may let you disable the driver in Device Manager.

   Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

2. Check logs and run diagnostics

   Check the System log in Event Viewer; run the hardware diagnostics from the system maker, especially the memory scanner.

Microsoft gives these steps on Bug Check 0x23: FAT_FILE_SYSTEM for 1 code of this group: 0x00000023. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Hardware diagnostics

   Run the hardware diagnostics from the system maker.

Microsoft gives these steps on Bug Check 0x24: NTFS_FILE_SYSTEM for 1 code of this group: 0x00000024. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Free disk space

   Confirm there is enough free space on the hard drive; it is normally a good idea to have 10% to 15% free.

2. Repair system files

   Run the System File Checker to repair missing or corrupted system files: SFC /scannow

Microsoft gives these steps on Bug Check 0x2E: DATA_BUS_ERROR for 1 code of this group: 0x0000002E. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Check logs and scan

   Check the System log in Event Viewer; scan for viruses with software that checks the Master Boot Record.

Microsoft gives these steps on Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION for 1 code of this group: 0x0000003B. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Device Manager

   Look for devices marked with an exclamation point and try to update the related driver.

2. Check the System log

   Check the System log in Event Viewer for messages that name the device or driver.

Microsoft gives these steps on Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA for 1 code of this group: 0x00000050. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Faulty hardware

   If hardware was added recently, remove it to see whether the error comes back; remove or replace failed hardware; run the manufacturer's hardware diagnostics (see the owner's manual).

Microsoft gives these steps on Bug check 0x7A: KERNEL_DATA_INPAGE_ERROR for 1 code of this group: 0x0000007A. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Virus check

   Check the computer for viruses with up-to-date virus-scanning software that also examines the Master Boot Record.

2. Event Viewer and updates

   Check the System Event Viewer for error messages, especially those right before the bug check, and make sure the latest Windows updates are installed.

Microsoft gives these steps on Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED for 1 code of this group: 0x0000007E. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Check the System log

   Check the System Log in Event Viewer for more error messages that might help identify the device or driver that is causing bug check 0x7E.

2. Disable or update the named driver

   Disables or removes drivers

   If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.

   Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

3. Check new hardware

   Confirm that any new hardware that is installed is compatible with the installed version of Windows (for example, the Windows 10 specifications list the required hardware).

Microsoft gives these steps on Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE for 1 code of this group: 0x0000009F. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Recently added drivers or services

   Disables or removes drivers

   If new device drivers or system services were added recently, try removing or updating them, and try to work out what changed before the new bug check code appeared.

   Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

2. Device Manager

   Look in Device Manager for devices marked with the exclamation point (!). Review the events log in the driver properties for any faulting driver, and try updating the related driver.

3. Check the System log

   Check the System Log in Event Viewer for other error messages that might help identify the device or driver that is causing the error; look for critical errors from the same time as the blue screen.

4. Hardware

   If you recently added hardware, try removing or replacing it, or ask the manufacturer about patches. You can also run the hardware diagnostics supplied by the system manufacturer.

5. Firmware

   Changes BIOS or firmware

   Check with the manufacturer whether an updated system ACPI/BIOS or other firmware is available.

   Our advice: Back up your files first, and follow your PC maker's instructions for BIOS or firmware settings and updates. How to: Windows recovery environment

Microsoft gives these steps on Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL for 1 code of this group: 0x000000D1. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Check the System log

   Check the System Log in Event Viewer for other error messages that might help identify the device or driver that is causing this bug check.

2. Disable or update the named driver

   Disables or removes drivers

   If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.

   Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

3. Check new hardware

   Confirm that any new hardware that is installed is compatible with the installed version of Windows (for example, the Windows 10 specifications list the required hardware).

Microsoft gives these steps on Bug check 0xEF: CRITICAL_PROCESS_DIED for 1 code of this group: 0x000000EF. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Hardware and drivers

   Disables or removes drivers

   Remove or replace recently added hardware; remove or update recently added drivers or services.

   Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

2. Check the System log

   Check the System log in Event Viewer for messages that name the device or driver.

3. Firmware and diagnostics

   Changes BIOS or firmware

   Check with the maker for BIOS/firmware updates; run the maker's hardware diagnostics.

   Our advice: Back up your files first, and follow your PC maker's instructions for BIOS or firmware settings and updates. How to: Windows recovery environment

4. Virus scan and SFC

   Run a virus scan (including the Master Boot Record) and SFC /scannow.

5. Device Manager

   Look for devices marked with an exclamation point and try updating the related driver.

Microsoft gives these steps on Bug Check 0x133: DPC_WATCHDOG_VIOLATION for 1 code of this group: 0x00000133. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Disable or update the named driver

   Disables or removes drivers

   If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.

   Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

2. Check the System log

   Check the System Log in Event Viewer for other error messages that might help identify the device or driver that is causing bug check 0x133.

3. Check new hardware

   Confirm that any new hardware that is installed is compatible with the installed version of Windows (for example, the Windows 10 specifications list the required hardware).

Microsoft gives these steps on Bug Check 0x139: KERNEL_SECURITY_CHECK_FAILURE for 1 code of this group: 0x00000139. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Check the event log

   Use the event log to see if there are higher level events that occur leading up to the stop code.

2. Recently added hardware

   If you recently added hardware to the system, try removing or replacing it, or check with the manufacturer whether patches are available.

3. Recently added drivers or services

   Disables or removes drivers

   If new device drivers or system services were added recently, try removing or updating them, and try to work out what changed before the new bug check code appeared.

   Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

4. Check the System log

   Check the System Log in Event Viewer for other error messages that might help identify the device or driver that is causing the error; look for critical errors from the same time as the blue screen.

5. Device Manager

   Look in Device Manager for devices marked with the exclamation point (!). Review the events log in the driver properties for any faulting driver, and try updating the related driver.

6. Virus scan

   Run a virus detection program, and make sure it checks the Master Boot Record for infections.

Microsoft gives these steps on Bug Check 0xC000021A: WINLOGON_FATAL_ERROR for 1 code of this group: 0xC000021A. The page does not give them for every code of the group; check the Microsoft page before you try them on another code.

1. Check the System log

   Check the System Log in Event Viewer for other error messages that might help identify the device or driver that is causing the error; look for critical errors from the same time as the blue screen.

2. Repair system files

   Run the System File Checker to repair missing or corrupted system files: SFC /scannow

3. Virus scan

   Run a virus detection program, and make sure it checks the Master Boot Record for infections.

4. Latest updates

   Verify that the latest updates are installed; to see the installed version, select Start > Run, type winver and press ENTER.

5. Safe Mode

   Changes boot or startup

   Consider Safe Mode to isolate the cause. On Windows 11, open Settings > System > Recovery and select Restart now next to Advanced startup (Microsoft's 'Windows recovery environment' page); on Windows 10, the bug check page's path is Settings > Update and Security > Recovery > Advanced startup. Then choose Troubleshoot > Advanced Options > Startup Settings > Restart, and choose option 4, 5 or 6.

   If the device is encrypted with BitLocker, you need its BitLocker recovery key to change startup settings (Microsoft's 'Windows startup settings' page).

   Microsoft advises: Keep track of what you change so you can undo it, and return the PC to a normal startup when you are done. (How to perform a clean boot in Windows)