How To Recognize Blue Screen of Death: What Does It Look Like?

The Blue Screen of Death (BSoD) is a serious error on Windows that forces the computer to restart. It is recognized by its distinct blue screen and error message. However, not all blue screens are a BSoD and sometimes the error occurs without an error code.

Let’s take a closer look at what the BSoD looks like on different versions of Windows, how to diagnose the problem, and what you can do to fix BSoD.

What does BSoD look like on Windows 10 and 11?

Windows 10, 8, and the latest version, Windows 11, share the same style of blue screen. The main difference is that in some earlier builds of Windows 11, the screen was black instead of blue.

A typical BSoD includes a sad face icon, followed by a message similar to this: Your PC ran into a problem and needs to restart as soon as we’re finished collecting some error info.

Usually, it is accompanied by a Stop Code at the bottom which can be used to identify the type of problem that caused the crash. However, this isn’t always present.

A BSoD can occur at any time and will immediately freeze everything you are doing, overtaking the screen with the blue window. You will have only a few seconds to note down the Stop Code before the system restarts.

You may also be advised to visit the Windows stop code reference page to learn more about the error.

What does BSoD look like on Windows 7 and Vista?

On Windows 7 and Vista, the blue screen contains a lot more text and no icons. The main message states: A problem has been detected and Windows has been shut down to prevent damage.

This is then followed by an error code, such as UNMOUNTABLE_BOOT_VOLUME.

There is also general guidance about checking your hardware and software, and a technical Stop Code that experts can use to further troubleshoot the problem.

What are BSoD Stop Codes?

Stop codes are error codes/messages that typically accompany the BSoD on all versions of Windows. They are either descriptive or numbered codes and can be used to identify what went wrong with your computer.

This doesn’t always pinpoint the precise cause of the problem, but it gives you a general idea about what failed at the time.

For example, UNMOUNTABLE_BOOT_VOLUME indicates that the computer is unable to access the boot volume, which contains critical system files required to start the operating system.

However, the reason for this problem could be anything from hard drive failure to malware corrupting your system files.

There are endless stop codes, but some of the most common are as follows:

• IRQL_NOT_LESS_OR_EQUAL – When a driver or system process tried to access a memory address that it did not have permission to access.
• CRITICAL_PROCESS_DIED – This indicates that a critical system process has stopped unexpectedly and cannot continue to run.
• PAGE_FAULT_IN_NONPAGED_AREA – The system attempted to access a non-existent or invalid page in memory.
• SYSTEM_SERVICE_EXCEPTION – A system service has failed and caused the system to crash.
• MEMORY_MANAGEMNT – When a RAM module or other aspect of memory malfunctions and causes the BSoD.
• VIDEO_TDR_FAILURE – The graphics card driver has failed or the GPU itself is malfunctioning.
• UNEXPECTED_STORE_EXCEPTION – This stop code indicates that the system has encountered an unexpected error while trying to access the disk or storage device.

Windows 7 and Vista are much more likely to present numbered stop codes, which you can Google to find further information.

What if you missed the BSoD Stop Code?

If you weren’t able to note down the stop code before the blue screen restarted your computer, you can find more information by checking the Windows Event Logs or dump files. In some cases, the BSoD only happens once, but it’s still useful to learn why.

To open the Event Viewer:

1. Press the Windows key + R on your keyboard to open the Run dialog box.
2. Type eventvwr.msc and press Enter or click OK. This will open the Event Viewer.
3. In the left pane, expand the Windows Logs category and select System.
4. In the middle pane, you should see a list of system events. Look for events with the Error level and source BugCheck. These events indicate a BSoD has occurred.
5. Double-click on an event to view more details about the BSoD. In the event details window, you should see information about the stop code, bugcheck code, and other relevant details that can help you diagnose the issue.

To view the BSoD minidump:

1. Press the Windows key + E to start File Explorer and navigate to the C:\Windows\Minidump folder.
2. To analyze a .dmp file, you can use a debugging tool such as WinDbg from Microsoft Store or a third party like BlueScreenView.
3. Open WinDbg and select File and then choose Open Crash Dump. Browse to the location of the .dmp file and select it.
4. WinDbg will analyze the dump file and display information about the crash, including the stop code, error message, and details about the drivers and modules involved.

How do I fix BSoD errors quickly?

Even with additional tools, Stop Codes can still be confusing for the average user. Fortunately, Windows repair software like Fortect can quickly fix the BSoD if it is caused by corrupted system files or registry entries.

1. Download and Install Fortect on your computer.
2. Run in normal or Safe Mode, and perform a system scan.
3. Click ‘Start Repair’ to fix all Windows problems.
4. If prompted, restart your PC.

Although Fortect cannot fix physical hardware problems, its hardware summary can reveal if memory modules aren’t being recognized or your CPU is overheating.

As the name suggests, the blue screen of death is identified by its signature blue background. You will usually get an error code or you can use a BSoD viewer to help with troubleshooting. In many instances, a tool like Fortect can fix the problem automatically, without having to reinstall Windows to solve the BSoD.