Key takeaways
- Searching only for the hex number. Codes are shared by many causes, so context matters.
- Skipping the memory test. Many of the most common codes can come from bad memory.
- Installing driver packs from unofficial sites. They can make crashes worse.
- Overclocking while troubleshooting. Go back to default settings first.
- Ignoring a failing drive. Repeated file system codes call for a backup first.
A blue screen error code, also called a stop code or bug check, names the kind of failure Windows detected, and the fastest first move is to write down the code shown on screen, boot normally or into Safe Mode, then update or roll back the most recent driver, run the system file repair tools and test memory and storage. Most codes point to one of four causes: a faulty driver, bad memory, a failing drive or unstable hardware settings.
How to Read a Stop Code
Microsoft describes a bug check as the halt Windows performs when it detects a condition it cannot safely continue from. The screen shows a text name such as CRITICAL_PROCESS_DIED and a hexadecimal value. Microsoft’s code reference lists each value, for example 0x0000000A for IRQL_NOT_LESS_OR_EQUAL and 0x000000EF for CRITICAL_PROCESS_DIED. Recent Windows 11 releases show the crash screen in black rather than blue, with the same stop code information. A QR code on the screen leads to Microsoft’s troubleshooting page.
The code itself is a clue, not a verdict. The same stop code can come from different faults, so use it together with the driver named on screen, if any, and with recent changes to the PC.
Common Codes at a Glance
| Hex | Name | Usual direction |
|---|---|---|
| 0x0A | IRQL_NOT_LESS_OR_EQUAL | Driver or memory problem |
| 0xD1 | DRIVER_IRQL_NOT_LESS_OR_EQUAL | A device driver touched memory incorrectly |
| 0x1E | KMODE_EXCEPTION_NOT_HANDLED | Driver or software fault |
| 0x3B | SYSTEM_SERVICE_EXCEPTION | Driver, security software or graphics driver |
| 0x50 | PAGE_FAULT_IN_NONPAGED_AREA | Bad memory, driver or corrupted file system |
| 0x7E | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED | A driver crashed, often named on screen |
| 0x1A | MEMORY_MANAGEMENT | Memory fault or memory settings |
| 0xEF | CRITICAL_PROCESS_DIED | Corrupted system files, driver or drive |
| 0x124 | WHEA_UNCORRECTABLE_ERROR | Hardware fault, heat or overclocking (per Microsoft) |
| 0x116 | VIDEO_TDR_FAILURE | Graphics driver or GPU stability |
| 0x133 | DPC_WATCHDOG_VIOLATION | A driver stalled, often storage or network |
| 0x9F | DRIVER_POWER_STATE_FAILURE | Driver failing during sleep or wake |
| 0x7B | INACCESSIBLE_BOOT_DEVICE | Storage driver, boot configuration or drive |
| 0xED | UNMOUNTABLE_BOOT_VOLUME | File system or drive problem |
| 0x139 | KERNEL_SECURITY_CHECK_FAILURE | Corrupted data, driver or memory |
| 0x101 | CLOCK_WATCHDOG_TIMEOUT | A processor core stopped responding |
This table is a starting map. Microsoft’s per-code pages list the parameters and remarks for each bug check, aimed at developers.
Step-by-Step Troubleshooting
1. Record the Details
Note the stop code, any file named such as a driver ending in .sys, and what you were doing. If the PC restarts too fast to read, open Settings, search for advanced system settings, and under Startup and Recovery turn off automatic restart. Windows normally also stores a small dump in the Minidump folder under the Windows directory, which tools such as WinDbg or free analyzers can read.
2. Undo Recent Changes
If the crashes began after a driver, update or new hardware, remove or roll back that item. In Device Manager, the driver’s properties offer a Roll Back option if a previous version exists. Use System Restore if you created a restore point before the change.
3. Boot to Safe Mode if Needed
If Windows crashes at startup, use the recovery environment, which appears after repeated failed boots, and choose Startup Settings to reach Safe Mode. Safe Mode loads minimal drivers, so if the PC is stable there, a driver or startup program is the likely cause.
4. Repair System Files
Open Terminal as administrator and run sfc /scannow. If it reports problems it cannot fix, run DISM /Online /Cleanup-Image /RestoreHealth and then run the scan again. These are Microsoft’s own tools and are generally safe.
5. Check the Drive
Run chkdsk on the system drive to find file system errors, and look at the drive’s health with the maker’s utility. Codes such as 0xED and 0x7B suggest a storage problem. Back up important data before running repairs on a drive you suspect is failing.
6. Test the Memory
Run the Windows Memory Diagnostic, or a bootable test such as MemTest86, for several passes. Memory-related codes such as 0x1A and 0x50 often respond to this. Turn off memory profiles such as XMP or EXPO to test at default speed, since BIOS changes and overclocking can cause instability and may void the warranty, so keep settings conservative.
7. Update Key Drivers
Install the latest graphics driver directly from the GPU maker, the chipset driver from the CPU or board maker, and the network and audio drivers from the board or laptop maker. For graphics crashes like 0x116, a clean graphics driver install is a common step. Avoid driver updater utilities of unknown origin.
8. Check Heat and Power
Overheating can produce several codes, especially 0x124 and 0x101. Make sure fans spin, dust is cleared with the PC unplugged, and the cooler is seated. Do not open a power supply. If you suspect the supply is failing, contact the maker or a technician.
Symptom, Cause and Fix Quick Table
| Symptom | Likely cause | Fix |
|---|---|---|
| Crash during games, graphics code | Graphics driver or GPU instability | Clean driver install, remove GPU overclock, check temperatures |
| Crash at boot, boot device code | Storage driver or drive fault | Check BIOS storage mode, chkdsk, drive health |
| Random crashes with varied codes | Faulty memory or unstable settings | Memory test, default BIOS settings |
| Crash after waking from sleep | Driver power state failure | Update chipset, network and graphics drivers |
| Crash right after a Windows update | Incompatible driver or update | Roll back driver, uninstall the update, use restore point |
| Crash after installing hardware | Incompatible or loose component | Reseat or remove the part and test |
Advanced Options
Driver Verifier is a Windows tool that stresses drivers to expose faulty ones. Microsoft documents it for developers and advanced users, but it can itself cause repeated crashes, so back up data and know how to turn it off in Safe Mode before using it. A clean reinstall of Windows is a last resort after hardware tests pass. If crashes continue with a fresh install, hardware is the likely cause and the maker or a technician should look at it.
Common Mistakes
- Searching only for the hex number. Codes are shared by many causes, so context matters.
- Skipping the memory test. Many of the most common codes can come from bad memory.
- Installing driver packs from unofficial sites. They can make crashes worse.
- Overclocking while troubleshooting. Go back to default settings first.
- Ignoring a failing drive. Repeated file system codes call for a backup first.
Frequently Asked Questions
What does a blue screen error code mean?
It identifies the type of fatal error Windows detected, shown as a name and a hexadecimal bug check value. It tells you the category of fault, such as a driver, memory or hardware error, rather than the exact part at fault.
How do I find out which driver caused the crash?
The screen sometimes names a .sys file. Otherwise, open the minidump with WinDbg or a dump analyzer, which can point to the module involved. Treat the result as a lead and confirm by rolling back or updating that driver.
Is a blue screen dangerous for my PC?
The screen itself is a protective halt, but repeated crashes can corrupt files and signal failing hardware. Back up your data and work through the fixes, and contact a technician if the problem persists at default settings.
Why did Windows 11 show a black screen instead of a blue one?
Recent Windows 11 releases changed the crash screen colour to black while keeping the stop code and the QR code. The troubleshooting steps are the same.
Can a bad Windows update cause a blue screen?
Yes, an update can introduce a driver incompatibility. Uninstalling the update from the update history or using a restore point is a standard way to test this.
When should I reinstall Windows?
Only after repair tools, driver updates and hardware tests have not solved it. If crashes continue after a fresh install, suspect hardware.
FAQ
What does a blue screen error code mean?
How do I find out which driver caused the crash?
Is a blue screen dangerous for my PC?
Why did Windows 11 show a black screen instead of a blue one?
Can a bad Windows update cause a blue screen?
When should I reinstall Windows?
More from Amazon
Programs that pair well with the guide above. Offers and eligibility are set by Amazon and may change.
Free shipping on eligible items, Prime Video and more. Eligible new members can start with a free trial.
Start a Prime free trialAd-free music streaming. Eligible new subscribers can start with a free trial.
Try Music Unlimited freeA Prime membership for ages 18-24 with a trial period. Eligibility is set by Amazon.
See Prime for Young AdultsAudiobooks and podcasts to listen to on the go. Eligible new members can start with a free trial.
Try Audible freeAs an Amazon Associate we earn from qualifying purchases.