Windows Stop Codes: How to Check and Fix the Causes of BSODs?

This guide walks you through the various stop codes, what they mean, and their causes.

You have probably heard recent news stories about the thousands of Windows PCs booting up with a blue screen of death, disrupting the operation of supermarkets, banks, airlines, and many other businesses worldwide. Even though it wasn’t Microsoft’s fault, it shows how problematic BSODs can be. 

Data loss, system instability, and serious work disruption are some of the issues that can result from BSODs. Fortunately, BSOD errors usually come with a Windows stop code, which can help you identify the problem and resolve it before it gets worse. 

I’ll walk you through everything important you need to know about stop codes and how to use them to resolve various BSODs issues. 

Let’s begin.

What Is a Windows Stop Code?

A Windows stop code is an error ID number that shows up when your computer has a serious problem. The code usually starts with “0x” followed by eight characters, like “0xc000021a.” Sometimes, these codes may come in a shorter way by removing the zeros, so “0xc000021a” becomes “0x21a.”

Regardless of how the code appears, each Windows stop code has its own special meaning and points to a specific problem with your computer. These problems usually come from device drivers, RAM, or other hardware and software issues. When you see a stop code, you can use it to figure out what’s wrong and how to fix the error.

Different Microsoft Stop Codes and What They Mean

The first step to fixing a blue screen of death issue is to understand the stop code you are seeing and the potential cause of the error. Different stop codes warn you about different things and have different severity levels. The following is a list of some of the Windows stop codes and what they mean:

Method 1: Using the Event Viewer to check stop codes

While Windows stop codes can be helpful, they often don’t provide a complete picture. To truly understand the causes of the BSOD, you need to dig a bit deeper. This is where the Event Viewer comes in. 

It’s a built-in log viewer that records everything under your system’s hood. Event Viewer is your first stop when deciphering what causes the BSOD. Follow these steps to check stop codes: 

• Press the Windows key to open the Start menu, type “Event Viewer,” and select it.

• In the Event Viewer, look at the left panel and click Windows Logs category.

• Under Windows Logs, click on System. System logs carry detailed records of your system’s operations, including Microsoft stop code occurrences.

• In the top right, find Filter Current Log.

• In the dialogue box, check the boxes with the tags Critical and Error. Then, click OK.

• Look through the items on your screen and observe if there are any items labeled BugCheck in the Source tab. Any item like this is the error you are looking for. Click on it to see the stop error code.

Method 2: Using the Reliability Monitor to identify issues

The Reliability Monitor provides a clear view of your system’s stability, making it easier to troubleshoot issues that may lead to a BSOD. It logs critical events, including memory, hard disk, application, and operating system failures, which are common causes of BSOD errors.

Additionally, it tracks significant system changes, like new software installations or updates, that could impact stability. This can help you identify patterns or recent changes that may be linked to the BSOD error and take specific actions to correct it.

How to access the Reliability Monitor

• Type “Reliability Monitor” into the search bar in your Start menu.

• Once you click the application, you will see a graph showing the stability index of your system over time.

• On the horizontal axis, you have dates. On the vertical axis, you will see numbers 1, 5, and 10. Those numbers indicate how stable your computer was on the dates displayed. Usually, the higher the number, the better. For the computer above, we can tell its most stable day was on the 11th of November. 
• For a more detailed view, you can change from days to weeks. This gives you more details from previous weeks instead of just the week in view.

Identifying critical events in the Reliability Monitor

Below the graph is a list of errors. Each error on the Reliability Monitor timeline has an icon that denotes its type. Here, you’re primarily looking for critical events or instances that have led to the BSOD.

These events provide key insights into what can cause a blue screen. Examining them closely can lead to identifying the Windows stop code responsible for your woes.

Method 3: Analyzing dump files

Even with tools like the Event Viewer and the Reliability Monitor, the causes of the error can sometimes remain elusive. This is where dump files come in. They can provide a deeper understanding of the Windows blue screen of death you’re facing.

Dump files are essentially snapshots of your system at the moment of the crash. They contain detailed information about your system’s actions when encountering the blue screen of death in Windows 10 and 11.

How to generate dump files

Before you analyze the dump files, you need to generate them first. Here’s how to do it: 

• Go to Windows Explorer (Windows + E), right-click on This PC, and select Properties.

• Click on Advanced system settings.

• Under Startup and Recovery, click Settings.

• Ensure Write an event to the system log is checked in the new window. Choose the dump file type you want under Write debugging information.

• Click OK and then Apply.

After a BSOD occurs, you can locate these dump files in the C:\Windows\Minidump folder.

Analyzing dump files using WinDbg

The simplest and easiest way to read the dump files is to use WinDbg. Microsoft developed this tool, so you have nothing to worry about. 

To use it, follow these steps:

• Download the WinDbg tool from Microsoft’s website and install it.
• Open WinDbg and click File, then Open Crash Dump.
• Navigate to C:\Windows\Minidump and open the dump file.
• Once the file is open, type “!analyze -v” in the command line at the bottom of the WinDbg window and press Enter.
• Wait while WinDbg analyzes the file. It will then display the Windows stop code and other information about what caused the crash.

Navigating dump files might feel like a complicated task. However, these files contain the key to understanding the Windows 11/10 stop codes and the root of the Windows blue screens of death. With the information you gather, you’ll be better prepared to solve and prevent further BSOD occurrences.

How to Fix Windows Stop Code Errors on Windows 11/10

Now that you found the Windows stop codes, what is the next thing to do? The answer to that will depend on the severity of the problem you are facing.

The following are general solutions that should work for most problems. Think of them as first-aid solutions. However, you should know that every stop code error has a unique solution, like you saw in the table above. If, after trying these solutions, the error still persists, you should check this article on how to fix a BSOD for more detailed solutions.

Fix 1: Restart your computer

Even though the BSOD looks like a big issue, simple fixes like restarting your computer might solve the problem. A computer restart acts like a complete refresh button for your system, addressing various technical hiccups in one simple action. 

Simply press the power button of your computer for about 10 seconds until it shuts down. Once it is off, you can turn it on again and see if the problem is resolved.

Fix 2: Update Windows

If the problem was from a bad update from Windows, there is a huge possibility that Windows is already working to fix the issue. Therefore, updating your OS in such cases will likely fix the problem.

To do that, simply check for available Windows updates, and if there are any available, download and install them.

Fix 3: Scan for malware

Viruses and malware can also cause BSOD issues. Some of these malicious software can delete or corrupt critical system files, making it difficult for Windows to boot properly.

If you are dealing with malware, this is probably the beginning of many other problems. To be safe, consider scanning your PC with a trusted malware tool. Run a full scan of your computer and promptly delete any malware you find in the process.

Fix 4: Uninstall any updates, apps, or drivers that are incompatible or recently installed

BSOD errors may appear due to apps, drivers, or even Windows updates that may be incompatible. If you recently installed an app, a driver, or updated Windows before you saw the BSOD error, this might be the cause of the problem.

Try uninstalling these applications to see if that resolves the problem.

Fix 5: Check your computer’s RAM using the Windows Memory Diagnostic tool

Issues with your computer’s RAM can lead to the BSOD. If that is the case, you can run the Windows Memory Diagnostic tool to identify and potentially fix the issue. 

Remember that the tool will run after your computer restarts and give you its results. The results are usually stored in the Event Viewer, just in case you need them again.

Fix 6: Run SFC, DISM, and CHKDSK utilities

When you see Windows stop code errors, you could be dealing with corrupted system files or disk errors. 

You can fix some of these issues by running Windows’ built-in system repair utilities like the SFC, DISM, and CHKDSK.

These powerful tools can scan for, detect, and repair corrupted files and disk errors that might be triggering these stop codes. 

To run these tools, open the Command Prompt with administrative privileges and execute the following commands: 

• sfc /scannow 
  

• DISM /Online /Cleanup-Image /RestoreHealth 

• chkdsk x: /f /r 

Run these commands one after the other and, if possible, back up your data before proceeding.

Fix 7: Perform a system restore

If the problem persists, restore Windows to a previous version when it was working well. The process only tries to fix Windows by restoring it to a saved restore point and may roll back your operating system settings and application files but will not affect your personal data. 

Remember that the restore point you want to use should be from a time when your PC was not showing the error. If you choose a restore point that was saved after you started experiencing the BSOD, you may be restoring the problem instead of fixing it.

To perform a system restore:

• Type “create a restore point” into the Windows search box and open the application.

• In the System Properties window, click on System Restore.

• Click on Next to see the available restore points.

• Choose any of the restore points you think were created before the problem started and click Next > Finish.

Fix 8: Reinstall Windows as a last resort

If you have tried everything above and nothing worked, you should consider reinstalling Windows. Sadly, this process will remove all your installed programs and system settings, essentially giving you a clean slate.

However, it is a good way to ensure that your system returns to a stable, error-free state by removing any deep-rooted problems that might be causing the recurring blue screen errors.

Here’s a detailed guide to help you: How to Factory Reset a Computer Running Windows 10/11

Windows Stop Codes: Explained

We hope that you have found a solution from the above steps. However, it does not end there. Once you’ve resolved the Windows stop code error, it’s essential to take proactive steps to prevent the BSOD from recurring.

One of the best things to do is keep a regular system maintenance schedule. This will help keep your computer running smoothly. To avoid stress, you can use third-party tools like Auslogics BoostSpeed or similar software to optimize and manage your system. 

Also, keep your machine updated, perform regular scans, and monitor your system performance. All of these steps will go a long way in preventing future errors.

By the way, we would like to hear from you! Drop a comment below and let us know how this guide helped you or if you have any additional questions!

FAQ