The fastest solution for most blue screen errors is to boot into Safe Mode and run the System File Checker. Press F8 during startup, select Safe Mode, then run sfc /scannow in an elevated Command Prompt to repair corrupted system files.

Fix Windows Blue Screen Errors – Windows 10/11 2026
Comprehensive guide to diagnose and fix Windows Blue Screen of Death (BSOD) errors on Windows 10 and 11 using proven troubleshooting methods.
Understanding Windows Blue Screen Errors
The Windows Blue Screen of Death (BSOD) represents one of the most critical system failures in Windows operating systems. When Windows encounters a fatal error that it cannot recover from, it displays a blue screen with diagnostic information and automatically restarts the system to prevent data corruption.
Blue screen errors have evolved significantly in Windows 10 and 11, providing more user-friendly error messages and QR codes for quick troubleshooting. However, the underlying causes remain consistent: hardware failures, driver conflicts, corrupted system files, or incompatible software installations.
Modern Windows systems include enhanced crash dump analysis and automatic recovery features, but manual intervention is often required to identify and resolve the root cause. The error codes displayed during a blue screen provide valuable diagnostic information that can pinpoint specific components or processes causing the failure.
This comprehensive guide addresses the most effective methods for diagnosing and fixing blue screen errors, from simple Safe Mode troubleshooting to advanced crash dump analysis. Each method is designed to target different potential causes, ensuring a systematic approach to resolution.
Related: Fix Windows Update Error 0x80070020 – Windows 10, Windows
Related: Fix Windows Error 0x8024402c – Windows 10/11 2026
Related: Fix Windows Update Error 0x80070003 – Windows 10, Windows
Related: Fix Windows KB5004945 Update Error – Windows 10, Windows 11
Related: How to Fix Windows Update Errors on Windows 11 (2026
Symptoms
- Computer suddenly crashes with a blue screen displaying error codes
- System automatically restarts after displaying the blue screen
- Error messages like SYSTEM_SERVICE_EXCEPTION, MEMORY_MANAGEMENT, or DRIVER_IRQL_NOT_LESS_OR_EQUAL
- Computer becomes unresponsive and requires manual restart
- Frequent crashes during specific activities or randomly
- Stop codes displayed in hexadecimal format (0x0000001E, 0x0000003B, etc.)
Root Causes
- Corrupted or incompatible device drivers
- Hardware failures including RAM, hard drive, or motherboard issues
- Overheating components causing system instability
- Corrupted Windows system files or registry entries
- Incompatible software or recently installed programs
- Power supply issues or electrical problems
- Malware infections affecting critical system processes
- Windows Update conflicts or incomplete installations
Solutions
Boot into Safe Mode and Run System File Checker
Safe Mode allows Windows to start with minimal drivers, helping isolate the cause of blue screen errors.
- Restart your computer and immediately press F8 repeatedly during startup
- Select Safe Mode with Command Prompt from the Advanced Boot Options menu
- Once in Safe Mode, right-click the Start button and select Windows Terminal (Admin)
- Run the System File Checker to repair corrupted files:
sfc /scannow- Wait for the scan to complete (this may take 15-30 minutes)
- If corrupted files are found, run DISM to repair the Windows image:
DISM /Online /Cleanup-Image /RestoreHealth- Restart your computer normally to test if the blue screen issue is resolved
Update and Roll Back Device Drivers
Incompatible or corrupted drivers are the leading cause of blue screen errors. This method addresses driver-related issues.
- Right-click This PC and select Properties
- Click Device Manager from the left panel
- Look for devices with yellow warning triangles or red X marks
- Right-click problematic devices and select Update driver
- Choose Search automatically for drivers
- If updating doesn't work, try rolling back recent driver updates:
- Right-click the device and select Properties
- Go to the Driver tab and click Roll Back Driver
- For graphics drivers, download the latest version directly from manufacturer websites:
- NVIDIA: GeForce Experience or nvidia.com
- AMD: AMD Software or amd.com
- Intel: Intel Driver & Support Assistant
To identify which driver caused the blue screen, check the crash dump:
Get-WinEvent -FilterHashtable @{LogName='System'; ID=1001} | Select-Object -First 5Run Windows Memory Diagnostic and Check Hardware
Faulty RAM is a common cause of blue screen errors. This method tests your system memory and other hardware components.
- Press Windows + R and type
mdsched.exe - Click Restart now and check for problems
- Your computer will restart and run a memory test (this takes 10-20 minutes)
- After the test completes, check results in Event Viewer:
- Press Windows + X and select Event Viewer
- Navigate to Windows Logs → System
- Look for events from source "MemoryDiagnostics-Results"
For additional hardware testing, run these commands in an elevated Command Prompt:
chkdsk C: /f /r
wmic diskdrive get status
wmic memorychip get capacity,speed,memorytype,devicelocator- Check system temperatures using built-in tools:
Get-WmiObject -Namespace "root/OpenHardwareMonitor" -Class Sensor | Where-Object {$_.SensorType -eq "Temperature"}- If memory errors are found, physically reseat RAM modules or replace faulty memory
- Ensure all internal connections are secure and components are properly seated
Disable Automatic Restart and Analyze Crash Dumps
Analyzing crash dump files provides detailed information about what caused the blue screen error.
- Disable automatic restart to see the full blue screen error:
- Right-click This PC → Properties → Advanced system settings
- Under Startup and Recovery, click Settings
- Uncheck Automatically restart under System failure
- Set Write debugging information to Small memory dump (256 KB)
- Note the crash dump location:
%SystemRoot%\Minidump - Download and install Windows Debugging Tools (WinDbg) from Microsoft Store
- Open WinDbg and load the most recent dump file:
windbg -z C:\Windows\Minidump\[latest_dump_file].dmp- Run the analyze command to get crash details:
!analyze -v- Look for the "PROBABLE_CAUSE" and "MODULE_NAME" in the output
- Search for the specific error code and module name to find targeted solutions
- Common stop codes and their meanings:
- 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED (driver issue)
- 0x0000003B: SYSTEM_SERVICE_EXCEPTION (system service error)
- 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (thread exception)
- 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL (driver memory access)
Perform System Restore or Reset Windows
If other methods fail, restoring Windows to a previous working state or performing a reset can resolve persistent blue screen issues.
- System Restore Method:
- Press Windows + R and type
rstrui.exe - Click Next and select a restore point from before the blue screens started
- Click Scan for affected programs to see what will be changed
- Click Next and then Finish to start the restore process
- Windows Reset Method (if System Restore fails):
- Go to Settings → Update & Security → Recovery
- Under Reset this PC, click Get started
- Choose Keep my files to preserve personal data
- Select Remove everything only if keeping files doesn't resolve the issue
- Choose Just remove my files for faster reset
- Click Reset to begin the process
For advanced users, you can also use DISM to repair the Windows image from installation media:
DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim:1 /LimitAccess- Replace
D:with your Windows installation media drive letter - After reset, reinstall essential programs and restore data from backups
Verification
To verify that blue screen errors have been resolved, monitor your system for at least 48-72 hours of normal use. Run these verification commands:
Get-WinEvent -FilterHashtable @{LogName='System'; Level=1,2,3} -MaxEvents 20
Get-EventLog -LogName System -EntryType Error -Newest 10Check the Windows Reliability Monitor for system stability:
- Press Windows + R and type
perfmon /rel - Review the reliability chart for critical events or application failures
- Ensure no new blue screen events appear in the timeline
Run a final system health check:
sfc /verifyonly
DISM /Online /Cleanup-Image /ScanHealthIf these commands return no errors and your system runs stable for 72 hours without crashes, the blue screen issue has been successfully resolved.
Advanced Troubleshooting
If the above methods didn't resolve your blue screen errors, try these advanced troubleshooting steps:
Hardware Testing: Use manufacturer diagnostic tools like Dell SupportAssist, HP Hardware Diagnostics, or Lenovo Diagnostics to test all hardware components. Consider running stress tests with tools like Prime95 for CPU and FurMark for GPU to identify unstable hardware.
Clean Boot: Perform a clean boot to eliminate software conflicts. Run msconfig, go to the Services tab, check Hide all Microsoft services, then Disable all. Restart and test for blue screens.
Registry Repair: Use the Registry Editor to check for corruption in critical registry hives. Back up the registry first, then run sfc /scannow followed by chkdsk /f on the system drive.
Professional Diagnosis: If blue screens persist, the issue may be hardware-related requiring professional diagnosis. Document all error codes, timestamps, and activities that trigger crashes for technical support.
Data Recovery: Before attempting more aggressive fixes, ensure all important data is backed up. Use Windows Backup or third-party tools to create full system images.
Frequently Asked Questions
What causes Windows blue screen errors?+
How do I read blue screen error codes?+
Can I prevent blue screen errors from happening?+
Is it safe to continue using my computer after a blue screen?+
When should I seek professional help for blue screen errors?+
Emanuel DE ALMEIDA
Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.
Further Intelligence
Deepen your knowledge with related resources
Discussion
Share your thoughts and insights
You must be logged in to comment.


