Troubleshooting the Blue Screen of Death (BSOD) Issue on Windows 10

Encountering the Blue Screen of Death (BSOD) on your Windows 10 computer can be frustrating and disruptive. In this comprehensive guide, we will walk you through the process of troubleshooting BSOD errors, providing step-by-step instructions in a conversational style. By following these exact settings, tools, and methods, you’ll be equipped to diagnose and resolve BSOD issues on your Windows 10 system.

What is BSOD on Windows 10?

BSOD stands for “Blue Screen of Death.” It is an error screen that appears on Windows operating systems, including Windows 10, when the system encounters a critical error or encounters a problem it cannot recover from. The screen turns blue, hence the name “Blue Screen of Death,” and displays an error message along with a stop code.

When a BSOD occurs, it usually indicates a severe system error or hardware failure. Common causes of BSODs include incompatible or faulty hardware drivers, faulty hardware components, memory issues, system file corruption, or software conflicts.

The purpose of the BSOD is to prevent further damage to the system by halting its operation and displaying the error information. It provides diagnostic information and a stop code that can help users or IT professionals identify the cause of the error and take appropriate actions to resolve it.

When a BSOD occurs in Windows 10, the system collects information about the error and may automatically restart. It is also possible to configure Windows 10 to create a “minidump” file that can be analyzed later to determine the cause of the error.

If you encounter a BSOD on Windows 10, it is recommended to note down the error message and stop code displayed on the screen. This information can be helpful when seeking assistance or troubleshooting the issue.

How to enable minidump file generation on Windows 10?

To enable minidump generation on Windows 10, follow these steps:

  1. Open the Start menu and type “Control Panel.” Open the Control Panel application from the search results.

  2. In the Control Panel, change the view to “Small icons” or “Large icons” to see all the available options.

  3. Locate and click on the “System” or “System and Security” option.

  4. In the System window, click on the “Advanced system settings” link on the left side.

  5. The System Properties window will appear. Go to the “Advanced” tab.

  6. In the Advanced tab, click on the “Settings” button under the “Startup and Recovery” section.

  7. Another window titled “Startup and Recovery” will open. In the “System failure” section, you’ll see options related to dump files.

  8. To enable minidump generation, make sure the following settings are configured:

    • Check the box next to “Write an event to the system log.”

    • Select “Small memory dump (256 KB)” from the “Write debugging information” dropdown menu.

  9. Optionally, you can choose the location where the minidump files will be saved. By default, they are stored in the %SystemRoot%\Minidump folder.

  10. Click “OK” to save the changes and close the windows.

Once you’ve enabled minidump generation, the system will create minidump files when a BSOD occurs. These files can be useful for analyzing the cause of the error or providing them to technical support for assistance.

Parsing a minidump file with WinDbg Preview

To parse a minidump file and find the cause of a BSOD (Blue Screen of Death) on Windows 10 using the WinDbg Preview app, follow these steps:

  1. Install WinDbg Preview: WinDbg Preview is available on the Microsoft Store. Visit the Microsoft Store, search for “WinDbg Preview ”, and install the application on your Windows 10 system.

  2. Launch WinDbg Preview: Open the WinDbg Preview app from the Start menu or by searching for “WinDbg Preview” in the Windows search bar.

  3. Load the Minidump File: In WinDbg Preview, select “File” and then “Open Dump File.” Locate and select the minidump file you want to analyze.

  4. Analyze the Minidump: Once the minidump file is loaded, WinDbg Preview will display information about the crash. You can use various commands and options to examine the call stack, identify the faulting module, and investigate the cause of the BSOD. Some useful commands include:

    • ‘!analyze -v’ : This command automatically analyzes the current minidump file and provides a summary of the crash. It displays information about the error code, faulting module, and stack trace.

    • ‘!process’ : This command displays information about the running processes in the current debugging session. It provides details such as process IDs, parent process IDs, and module information.

    • ‘!thread’ : This command displays information about the threads in the current debugging session. It shows details like thread IDs, stack traces, and the current thread context.

How to troubleshoot BSOD with event viewer

To troubleshoot a BSOD (Blue Screen of Death) issue on Windows 10 using the Event Viewer, you can follow these steps:

  1. Open Event Viewer: Press the Windows key + R to open the Run dialog box. Type “eventvwr.msc” and press Enter. This will open the Event Viewer application.

  2. Navigate to the System Event Log: In the Event Viewer window, expand the “Windows Logs” folder on the left side. Click on “System” to view the System Event Log, which contains information about system events and errors.

  3. Filter the Event Log: In the middle pane of the Event Viewer window, click on the “Filter Current Log” option. This will open a dialog box where you can specify the filter criteria.

  4. Set the Filter Criteria: In the filter dialog box, select “By Source” in the “Event sources” drop-down menu. Then, choose “BugCheck” as the source. This will filter the event log to display only events related to BSODs.

  5. View and Analyze Events: After applying the filter, the Event Viewer will display the events related to BSODs in the system. Look for events with the “BugCheck” source and note the Event ID and other details.

  6. View Event Details: Double-click on a specific event to view its details. Pay attention to the “Bugcheck code” and “Bugcheck parameter” sections, as they provide important information about the BSOD error.

  7. Research the Error Code: Take note of the Bugcheck code (e.g., 0x0000001A) and search for it online. Many websites and forums provide information and possible solutions related to specific BSOD error codes. This can help you understand the cause of the issue and find potential solutions.

  8. Check for Related Events: While viewing the Event Viewer, check for any other events or errors that occurred around the time of the BSOD. Sometimes, other events or warnings can provide additional context or clues about the cause of the BSOD.

  9. Take Action: Based on the information gathered from the Event Viewer and research, you can take appropriate actions to troubleshoot the BSOD issue. This might involve updating drivers, checking for hardware issues, running diagnostic tools, or seeking further assistance from technical support.

Keep in mind that BSODs can have multiple causes, and analyzing the Event Viewer alone may not always provide a definitive solution.

Advanced Troubleshooting Methods

  1. Run Windows Memory Diagnostic:

    Use the built-in Windows Memory Diagnostic tool to check for memory-related issues that can cause BSOD errors. Follow these steps:

    • Press the Windows key + R to open the Run dialog box.

    • Type “mdsched.exe” and hit Enter.

    • Choose to restart now and check for problems immediately or schedule the test for the next restart.

  2. Perform System File Check (SFC) and DISM Scan:

    Run the System File Check (SFC) and Deployment Image Servicing and Management (DISM) tools to repair corrupted system files that may contribute to BSOD errors. Execute the following commands in an elevated Command Prompt or PowerShell:

    • Open an elevated Command Prompt or PowerShell by right-clicking the Start button and selecting the corresponding option.

    • Type “sfc /scannow” and hit Enter to run the System File Check. Wait for the scan to complete and follow any instructions provided.

    • After the SFC scan finishes, type “DISM /Online /Cleanup-Image /RestoreHealth” and hit Enter to run the DISM scan. Allow the scan to complete, which may take some time.

  3. Use Safe Mode and Clean Boot:

    Boot your Windows 10 system into Safe Mode or perform a Clean Boot to isolate software or driver conflicts causing the BSOD. Follow the appropriate steps based on your preferred method.

Seeking Additional Assistance

  1. Online Forums and Communities:

    Engage with online forums and communities dedicated to Windows troubleshooting to seek guidance and assistance from experienced users and professionals.

  2. Contacting Microsoft Support:

    If all else fails, reach out to Microsoft Support for further assistance in resolving persistent BSOD issues. Provide them with detailed information about your system, error messages, and steps you’ve already taken.


By following this detailed guide, you now have the tools and knowledge to troubleshoot and resolve BSOD issues on your Windows 10 computer. Remember to analyze error messages, utilize diagnostic tools, and explore advanced troubleshooting methods. Don’t let the Blue Screen of Death hinder your productivity—tackle it head-on and get your system back to optimal performance. Happy troubleshooting!

comments powered by Disqus

Related Posts

Resolves an issue where the system frequently prompts ‘Intel Optane(tm) Memory Pinning’

Users using Windows 10 may encounter this problem, and a prompt often pops up in the lower right corner, titled Intel Optane (tm) Memory Pinning, which reads:

Read more

How to find back Bitlocker Recovery key?

Some Win10 computers prompt for Bitlocker keys after restoring the system, resetting the computer, entering safe mode, and replacing hardware, which caught many friends by surprise and did not know where to get the key.

Read more

How do I fix the problem that Windows 10 has an internet connection, but says it can’t connect to the internet, and the little globe sign is displayed?

Recently, some Windows 10 users have encountered networking problems, and the network icon on the taskbar is marked with an exclamation mark or shows a small globe sign, which is manifested:

Read more