What does the error code on a blue screen mean?

The error code (e.g., IRQL_NOT_LESS_OR_EQUAL or MEMORY_MANAGEMENT) identifies which part of Windows detected the fatal error. IRQL errors usually point to a driver accessing memory incorrectly. MEMORY_MANAGEMENT often points to faulty RAM. KERNEL_SECURITY_CHECK_FAILURE often points to corrupted system files or a failing drive. Searching the exact code alongside your specific situation (e.g., 'after GPU driver update') narrows the cause far faster than generic troubleshooting.

How do I find out what caused a specific BSOD?

Open Event Viewer (search for it in Start) and navigate to Windows Logs > System. Look for a red 'Critical' or 'Error' entry timestamped around when the crash happened — it usually names the specific driver or file involved (e.g., nvlddmkm.sys for an Nvidia GPU driver). You can also check C:\Windows\Minidump for crash dump files, which can be analyzed with the free WinDbg tool for a more precise diagnosis.

Will System Restore fix a blue screen error?

Yes, if the BSOD started after a specific software change — a driver install, a Windows update, or a new application — System Restore can roll Windows back to a point before that change, often resolving the crash immediately. Search 'Create a restore point' in Start, click System Restore, and choose a restore point dated before the problem began. This doesn't affect personal files, only system settings and recently installed software.

Is a blue screen error a sign my PC is dying?

Not usually. The large majority of BSODs are caused by a software-level issue — a bad driver or corrupted system file — both of which are fully fixable without any hardware replacement. A BSOD is more concerning if it happens repeatedly with the same memory-related error code (suggesting failing RAM) or alongside other symptoms like unusual noises or extreme heat (suggesting failing hardware). Running Windows Memory Diagnostic and checking temperatures, as covered above, will tell you which situation you're in.

Windows Blue Screen Error (BSOD)? Here’s How to Fix It

A recently installed driver is the most common cause. Identify the exact error code and work through these steps to find the real culprit.

Quick Answer

✓Note the error code on the blue screen (e.g., IRQL_NOT_LESS_OR_EQUAL) — it tells you exactly which subsystem failed.
✓Boot into Safe Mode first — if the BSOD doesn't recur there, a recently installed driver is almost certainly the cause.
✓Run 'sfc /scannow' in an elevated Command Prompt to repair corrupted Windows system files automatically.
✓If crashes persist under light use, check CPU/GPU temperatures with HWMonitor — sustained heat above 90°C causes emergency shutdowns that look like BSODs.

Common Causes

A recently installed driver is incompatible or corrupted

Most Likely

Hardware drivers — especially GPU, WiFi, and audio drivers — run with the highest level of system access (kernel mode), so a bug in one of them can crash the entire operating system rather than just the affected app. This is the single most common BSOD cause. If the crashes started right after installing a new GPU driver, a Windows Update, or a new peripheral, the driver is the first place to look.

Faulty or failing RAM

Common

Bad memory modules cause data corruption that can crash Windows with a wide variety of error codes — MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA, and others. Unlike driver crashes, RAM-related BSODs tend to be inconsistent: different error codes, happening at random times rather than during a specific action. Windows Memory Diagnostic (built in) can confirm or rule this out.

Windows system files are corrupted

Common

A failed update, an improper shutdown (holding the power button), or a sudden power loss can leave core Windows system files in a corrupted state. When Windows tries to load a damaged system file, it can trigger a BSOD rather than failing gracefully. The System File Checker tool (sfc /scannow) scans for and automatically repairs these files using a protected cache.

Overheating CPU or GPU triggering an emergency shutdown

Less Common

When a CPU or GPU temperature exceeds its safe operating threshold, some systems force an emergency shutdown to prevent permanent hardware damage — and this can present as a BSOD rather than a clean power-off. This is more common on laptops with clogged cooling vents or desktops with dried thermal paste. It typically happens under load (gaming, video rendering) rather than at idle.

Step-by-Step Fix

Note the exact error code on the blue screen

When the BSOD appears, look for the error code in all caps (e.g., IRQL_NOT_LESS_OR_EQUAL, MEMORY_MANAGEMENT, KERNEL_SECURITY_CHECK_FAILURE). If the screen disappears too fast to read, go to Settings > Windows Update > Windows Insider Program is not needed — instead check Event Viewer (search 'Event Viewer' in Start) > Windows Logs > System and look for a 'Critical' event around the crash time, which will show the same code. Each code points to a different subsystem, so searching the specific code narrows your troubleshooting significantly.

Boot into Safe Mode and check if the crash recurs

Hold Shift while clicking Restart from the Start menu's power options. This boots into the recovery environment. Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 (or F4) to enter Safe Mode. Safe Mode loads only essential drivers. Use the PC normally for a while — if the BSOD doesn't happen in Safe Mode, a third-party driver is almost certainly the cause, since Safe Mode bypasses most of them.

Pro tip: If the PC won't boot normally at all, Windows usually drops into the recovery environment automatically after 2-3 failed boot attempts, giving you the same Troubleshoot menu.

Roll back recently installed drivers

Open Device Manager (Win + X > Device Manager). Look for any device with a yellow warning icon, or think about what you installed or updated recently — GPU drivers and WiFi drivers are the most common culprits. Right-click the device > Properties > Driver tab > Roll Back Driver. If that button is grayed out, instead uninstall the device (right-click > Uninstall device) and let Windows reinstall a basic driver on next restart.

Run Windows Memory Diagnostic

Search 'Windows Memory Diagnostic' in the Start menu and open it. Select 'Restart now and check for problems.' The PC will restart and run a memory test before Windows loads — this takes 10-20 minutes for a standard test. For a more thorough check, press F1 during the test to access extended test options and let it run overnight. Results appear as a notification after Windows finishes booting.

Run System File Checker (sfc /scannow)

Search 'Command Prompt' in the Start menu, right-click it, and select 'Run as administrator.' Type 'sfc /scannow' and press Enter. This scans all protected system files and automatically replaces any that are corrupted using a cached copy. The scan takes 5-15 minutes. If it reports it found and fixed corrupted files, restart and check if the BSODs stop.

Pro tip: If sfc reports it couldn't fix some files, run 'DISM /Online /Cleanup-Image /RestoreHealth' first (also in an elevated Command Prompt) to repair the underlying Windows image, then run sfc /scannow again.

Check CPU and GPU temperatures under load

Download HWMonitor (free, from cpuid.com). Open it while running a normal workload — browsing, or whatever typically triggers the crash. Watch the 'Max' temperature column for your CPU and GPU. Sustained temperatures above 90°C (194°F) indicate a cooling problem. On a laptop, this usually means dust-clogged vents; on a desktop, it can mean a failed fan or dried thermal paste. Cleaning vents with compressed air resolves most cases.