How to Fix a Blue Screen Error in Windows 11?

Overview

A blue screen error in Windows 11 means the system hit a problem it could not recover from safely, so it stopped rather than risk damage or data loss. Annoying as it is, the crash is a protective measure.

The mistake most people make is trying random fixes. Blue screens almost always come from one of four things, and each has a different fix:

  1. A driver — by a wide margin the most common
  2. Failing hardware, usually RAM or a drive
  3. Corrupted system files
  4. Overheating or an unstable overclock

Work through this in order and you will usually find it. Skipping to the drastic steps wastes a day and often does not help.

Step 1: Read the stop code

The blue screen shows a stop code — something like SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA or CRITICAL_PROCESS_DIED.

Write it down, exactly. It narrows the cause more than anything else you can do.

If the PC restarts too fast to read it:

  1. Press Windows + R, type sysdm.cpl, press Enter
  2. Go to Advanced > Startup and Recovery > Settings
  3. Untick Automatically restart
  4. Click OK

The next blue screen will stay on screen.

Sometimes the screen names a file, like nvlddmkm.sys or ntoskrnl.exe. A named .sys file is usually a driver, and that is a strong lead.

Step 2: Think about what changed

Blue screens rarely start for no reason. Ask yourself:

  • Did you install a driver, Windows update or new program recently?
  • Did you add hardware — RAM, a drive, a graphics card, a USB device?
  • Did it start after a power cut or an unexpected shutdown?
  • Does it happen at a particular moment — gaming, waking from sleep, plugging something in?

A pattern is worth more than any tool. If it only crashes when a specific game runs, you are looking at graphics drivers or heat. If it only crashes waking from sleep, that is usually a driver power-management issue.

Step 3: Update or roll back drivers

Drivers cause most blue screens, and graphics drivers cause most of those.

To update:

  1. Right-click Start > Device Manager
  2. Expand the category (start with Display adapters)
  3. Right-click the device > Update driver > Search automatically

Better for graphics: download directly from Nvidia, AMD or Intel rather than relying on Windows. Use their clean-install option if offered.

If crashes started right after a driver update, roll it back:

  1. Device Manager > right-click the device > Properties
  2. Driver tab > Roll Back Driver
  3. If the button is greyed out, there is no previous version stored

Look for warning triangles in Device Manager while you are there — a device with a problem is flagged.

Step 4: Check your RAM

Faulty memory causes blue screens that look random and change stop codes between crashes. That inconsistency is itself a clue.

Run Windows Memory Diagnostic:

  1. Press Windows + R, type mdsched.exe, press Enter
  2. Choose Restart now and check for problems
  3. Let it run — it takes a while

For a more thorough test, MemTest86 run from a USB stick is the tool technicians use. Several passes over several hours catch faults the quick test misses.

If you have more than one RAM stick, try running with one at a time. If crashes stop with one stick removed, you have found it.

Also worth doing on a desktop: power off, unplug, and reseat the RAM — press each stick firmly back into its slot. Loose memory is a surprisingly common cause.

Step 5: Repair system files

Corrupted system files cause crashes that no driver update fixes.

Open Command Prompt as administrator (right-click Start > Terminal (Admin)) and run these in order, letting each finish:

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

Running sfc again after DISM is deliberate — DISM repairs the source that sfc repairs from.

Then check the drive:

chkdsk C: /f /r

This one asks to schedule at the next restart. Say yes, then reboot. It takes a long time on a large drive — leave it alone.

Step 6: Check temperatures

Overheating causes crashes that cluster under load — gaming, video export, long exports.

  • Install a monitoring tool and watch CPU and GPU temperatures while working
  • Clean dust out of fans and vents
  • On a laptop, make sure vents are not blocked by a soft surface
  • If you have overclocked anything, set it back to default and see whether crashes stop

Step 7: Read the crash dump

When Windows crashes it writes a minidump file to C:\Windows\Minidump. Those files name the driver that failed.

Tools like BlueScreenView or WhoCrashed read them in plain language and will often point straight at a specific .sys file.

If one driver name keeps appearing across several crashes, that is your culprit — update it, roll it back, or uninstall the device it belongs to.

Step 8: If it crashes before Windows loads

Boot into Safe Mode:

  1. Hold Shift and click Restart from the Start menu
  2. Troubleshoot > Advanced options > Startup Settings > Restart
  3. Press 4 or 5 for Safe Mode

If Safe Mode is stable, the problem is a driver or a startup program, not the hardware. That is useful to know and it narrows the search a lot.

From Advanced options you can also try Startup Repair, or System Restore to roll back to a point before the crashes started.

Frequently asked questions

Is one blue screen something to worry about?
A single crash after months of stability is usually a one-off. Repeated crashes mean something needs fixing.

Will reinstalling Windows fix it?
It fixes software causes and tells you nothing about hardware ones. Try the steps above first — a reinstall that does not fix it has cost you a day for nothing.

What if it only happens in one game?
Graphics drivers or heat. Update the drivers from the manufacturer directly and watch temperatures during play.

Can a Windows update cause blue screens?
Yes. If it started right after one, uninstall it in Settings > Windows Update > Update history > Uninstall updates.

Can a USB device cause it?
Yes. Unplug everything except keyboard and mouse and see whether it stops.

Is the stop code enough to find the problem?
Not by itself, but it narrows it enormously. Search the exact code with the file name if one is shown.

Work it in this order

Write down the stop code and any file name on the screen, then think about what changed on the machine in the days before it started. Those two pieces of information solve more blue screens than any tool.

Then take it in order: drivers first, because that is where most of them come from; then memory, because a bad stick produces exactly this kind of random crash; then system files. The minidump reader is worth reaching for early if the crashes are frequent — a driver name that keeps appearing across several crashes is as close to a direct answer as this gets.

Stop codes, tool names and menu paths change between Windows versions and updates. Back up anything important before running disk repairs or reinstalling, and if the PC is under warranty, check whether opening it affects that before touching the hardware.

Leave a Comment