Your screen just turned blue with a sad face and a cryptic error code — and now you're wondering if your computer is dying. Take a breath. The Blue Screen of Death on Windows 11 is one of the most alarming-looking errors in computing, but in the majority of cases it is completely fixable without replacing any hardware.
This guide covers everything: what the blue screen actually means, every major error code and what causes it, and a full step-by-step repair process from the simplest fixes to advanced recovery tools. Follow these steps in order and you will almost certainly resolve the issue.
Before you start: take a photo of the error screen
The stop code shown on the blue screen (e.g. IRQL_NOT_LESS_OR_EQUAL) is the single most useful piece of information for diagnosis. If the screen disappears before you can read it, don't worry — we'll show you how to find it in Event Viewer later in this guide.
What Is a Blue Screen of Death?
A BSOD (Blue Screen of Death) is Windows' emergency stop mechanism. When the operating system detects a critical error it cannot safely recover from — a driver writing to the wrong memory address, a hardware component returning corrupted data, a kernel process crashing — it halts everything immediately rather than allowing the damage to spread.
Think of it like a circuit breaker. When there's a dangerous electrical fault, the breaker trips rather than letting a fire start. The BSOD does the same: it crashes the entire system to prevent data corruption or hardware damage.
On Windows 11, the blue screen shows:
- A large sad face :( and the message "Your PC ran into a problem and needs to restart"
- A stop code (e.g. KERNEL_DATA_INPAGE_ERROR) — this is the key to diagnosis
- A QR code linking to Microsoft's support page for that error
- A percentage counter showing Windows collecting crash data
- Sometimes: the name of the file that caused the crash (e.g. ntfs.sys, nvlddmkm.sys)
The 5 Most Common BSOD Error Codes on Windows 11
| Stop Code | Most Likely Cause | Severity |
|---|---|---|
| IRQL_NOT_LESS_OR_EQUAL | Faulty or incompatible driver accessing protected memory | Medium |
| KERNEL_DATA_INPAGE_ERROR | Failing hard drive or SSD, corrupted page file, bad RAM | High — back up data immediately |
| PAGE_FAULT_IN_NONPAGED_AREA | Defective RAM, corrupted system file, bad driver | Medium-High |
| CRITICAL_PROCESS_DIED | Corrupted Windows system files, failed update, malware | High |
| SYSTEM_SERVICE_EXCEPTION | Incompatible driver (often GPU or antivirus), software conflict | Medium |
KERNEL_DATA_INPAGE_ERROR: back up your files right now
If you see this specific stop code repeatedly, your hard drive or SSD may be physically failing. Do not wait — plug in an external drive and copy your important files before continuing any troubleshooting. Once a drive starts failing, it can become completely unreadable within hours.
What Actually Causes a Windows 11 Blue Screen?
1. Faulty or Incompatible Drivers (responsible for ~40% of BSODs)
Drivers are software that allow Windows to talk to hardware — your GPU, network card, printer, USB devices. A driver that writes to the wrong memory address, or one that's incompatible with Windows 11's stricter memory management, will cause an immediate crash.
The most common driver culprits:
- GPU drivers (NVIDIA, AMD) — especially right after a driver update
- Network drivers — WiFi adapters and Ethernet controllers
- Storage drivers — NVMe and SATA controllers
- USB peripheral drivers — gaming keyboards, webcams, drawing tablets
- Antivirus kernel drivers — third-party security software runs deep in the system
2. Defective RAM
RAM is volatile memory — every byte written to it should be readable back perfectly. When a RAM chip develops a fault, data stored in that memory cell becomes corrupted. Windows reads back garbage instead of valid instructions, and crashes. RAM-related BSODs often produce different stop codes each time — IRQL_NOT_LESS_OR_EQUAL one day, PAGE_FAULT the next — because the corrupted data keeps ending up in different places.
3. Failing Hard Drive or SSD
When Windows needs to read a file from storage and gets back corrupted data or a read error, it can crash. This is especially common with older mechanical hard drives developing bad sectors. Signs: the computer has been slowing down gradually, files occasionally disappear or won't open, you hear clicking sounds from the drive.
4. Overheating
CPUs and GPUs have thermal protection: when they exceed safe temperature thresholds, the system crashes rather than sustaining physical damage. Common causes: years of dust accumulation blocking airflow, dried thermal paste between the CPU and heatsink, a failing fan, or running demanding software in a hot room.
5. Corrupted Windows System Files
Windows 11 maintains thousands of critical system files. If a Windows Update fails mid-installation, if power is cut during a write, or if malware modifies protected files, the OS can become unstable and crash. The SFC and DISM commands (covered below) are specifically designed to detect and repair this.
6. Problematic Windows Updates
Microsoft occasionally ships updates that break specific hardware configurations. If your BSOD started immediately after a Windows Update, there's a high chance the update itself is the problem. The fix is to uninstall that specific update — which you can do safely without losing any personal files.
Step-by-Step: How to Fix Blue Screen of Death on Windows 11
Work through these steps in order. Each step eliminates one possible cause. Start with the software fixes before touching any hardware.
Boot into Safe Mode
Safe Mode loads Windows with only essential drivers. If your PC runs without crashing in Safe Mode, the problem is a third-party driver or software — not hardware. Hold Shift and click Restart from the Start menu. Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press F5 for Safe Mode with Networking. If Windows won't boot at all: force shut down 3 times in a row (hold the power button during startup) — Windows will automatically enter the Recovery Environment (WinRE).
Find the Exact Stop Code with Event Viewer or BlueScreenView
Press Win + R, type eventvwr, press Enter. Navigate to Windows Logs > System. Look for Critical events (red icon) at the time of the crash. Alternatively, download BlueScreenView (free, from nirsoft.net) — it reads minidump files automatically and shows the exact stop code, the driver that caused the crash, and the memory address. To prevent automatic restart so you can read the screen: right-click This PC > Properties > Advanced system settings > Startup and Recovery > Settings, uncheck "Automatically restart."
Roll Back the Most Recent Driver Update
Right-click the Start button > Device Manager. Expand the category for the suspect device (Cartes graphiques for GPU, Network Adapters for WiFi). Right-click the device > Properties > Driver tab > Roll Back Driver. If "Roll Back Driver" is greyed out, the driver has no previous version stored — you'll need to uninstall and reinstall manually from the manufacturer's website (nvidia.com, amd.com, intel.com, realtek.com). Restart after rolling back.
Run SFC (System File Checker)
Open Command Prompt as Administrator: press Win + X, select Terminal (Admin). Type exactly: sfc /scannow and press Enter. SFC scans all protected Windows system files and replaces corrupted ones from a cached copy. This takes 10–20 minutes. Do not interrupt it. After it finishes, restart and test. If SFC reports "Windows Resource Protection found corrupt files but was unable to fix some of them," run DISM next.
Run DISM to Repair the Windows Image
DISM repairs the Windows component store that SFC uses. In the same admin terminal, run these three commands in sequence:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
The RestoreHealth command downloads replacement files from Windows Update, so you need an internet connection. It can take 20–45 minutes. After it completes, run sfc /scannow one more time, then restart.
Uninstall a Problematic Windows Update
If the BSOD started right after a Windows Update: go to Settings > Windows Update > Update history > Uninstall updates. Find the most recent Cumulative Update and click Uninstall. This removes just that update — your personal files and other software are not affected. Windows will try to reinstall the update later, so you may need to pause updates temporarily (Settings > Windows Update > Pause updates).
Run Windows Memory Diagnostic
Press Win + R, type mdsched.exe, press Enter. Choose "Restart now and check for problems." Windows will reboot and run a memory test before loading the OS. The basic test takes about 10–15 minutes. For a thorough test, boot into the Advanced options (F1 during the test) and choose the "Extended" test — this takes 1–2 hours but catches subtle RAM faults. Any errors found mean your RAM needs to be replaced. For a deeper test, use MemTest86 (free, bootable from USB — runs for 8+ hours for comprehensive coverage).
Check Your Hard Drive or SSD for Errors
Open an admin Command Prompt and run: chkdsk C: /f /r /x. The /f flag fixes errors, /r locates bad sectors, and /x forces the volume to dismount. Since the C: drive is in use, Windows will schedule the check for next boot. Restart and let it run — on a large HDD this can take 1–3 hours. For SSDs, also check the manufacturer's diagnostic tool (Samsung Magician, Crucial Storage Executive, WD Dashboard). S.M.A.R.T. status "Reallocated Sectors Count" above zero on an HDD is a serious warning sign.
Check for Overheating
Download HWMonitor (free from cpuid.com). Run it while using your computer normally. Watch the CPU temperature — it should stay below 85°C under load. If it's hitting 90°C+ regularly, overheating is likely causing the crashes. Fix: open the case and clean out dust with compressed air (PC unplugged). If you have a laptop, replace the thermal paste on the CPU — on a 3-4 year old laptop this alone can drop temperatures by 20-30°C. Never use your laptop on a soft surface (bed, couch) that blocks the vents.
Scan for Malware in Safe Mode
Some malware installs rootkit drivers that run in kernel mode — the same space where BSOD-causing crashes happen. Boot into Safe Mode (Step 1), then run a full scan with Windows Defender (Settings > Privacy & Security > Windows Security > Virus & threat protection > Full scan) or download Malwarebytes Free. In Safe Mode, most malware is inactive, making it easier to detect and remove.
Reset or Reinstall Windows 11 (Last Resort)
If nothing else works: Settings > System > Recovery > Reset this PC. Choose "Keep my files" — this reinstalls Windows but preserves your personal documents, photos, and desktop files (apps will need to be reinstalled). This resolves virtually all software-caused BSODs. If the BSOD happens even during the reinstall process, that almost certainly indicates a hardware problem (RAM or drive) that needs physical repair.
Pro tip: Use Startup Repair from WinRE
If Windows won't boot at all, force shut it down 3 times during startup (hold power button). On the fourth boot it enters the Recovery Environment. Go to Troubleshoot > Advanced options > Startup Repair. This automatically scans for and fixes boot-related BSOD causes — often resolving issues without any manual steps.
Specific Fix by Stop Code
IRQL_NOT_LESS_OR_EQUAL
This stop code almost always means a driver is accessing memory it shouldn't. The most reliable fix: boot to Safe Mode, open Device Manager, right-click each device that was recently updated and roll back its driver. The usual suspects are GPU drivers (NVIDIA/AMD) and network adapters. If you can't identify which driver: in Safe Mode, go to Settings > Apps, sort by install date, and uninstall anything installed around when the crashes started.
KERNEL_DATA_INPAGE_ERROR
This code almost always points to a storage problem. Run chkdsk C: /f /r /x immediately (Step 8). Also run Windows Memory Diagnostic — occasionally bad RAM causes this code too. Check your SATA or NVMe cables are fully seated (desktop PCs). If chkdsk finds and reports bad sectors, the drive is physically failing and needs replacement before you lose data permanently.
CRITICAL_PROCESS_DIED
A critical Windows process (like csrss.exe, winlogon.exe, or services.exe) terminated unexpectedly. This is most often caused by corrupted system files or a failed Windows Update. Run SFC then DISM (Steps 4-5). If that doesn't fix it, uninstall the most recent Windows Update (Step 6). Malware that targets system processes can also cause this — scan in Safe Mode.
PAGE_FAULT_IN_NONPAGED_AREA
Windows tried to access memory that was supposed to be always-available in RAM but wasn't there. Run the Memory Diagnostic (Step 7). Also check if the error filename (shown on the blue screen below the stop code) is a driver file — if so, reinstall or roll back that specific driver.
SYSTEM_SERVICE_EXCEPTION
Commonly caused by GPU drivers, antivirus software, or recently installed system utilities. The driver filename shown on the blue screen is the key clue. Common culprits include nvlddmkm.sys (NVIDIA GPU driver), dxgkrnl.sys (DirectX), and win32k.sys (core Windows). For NVIDIA: use DDU (Display Driver Uninstaller) in Safe Mode to fully remove the driver, then reinstall the latest version from nvidia.com.
When to Call a Professional
Some BSOD situations genuinely require professional tools and hands-on diagnosis:
- BSODs with a different stop code every time — this pattern strongly suggests defective RAM or a failing motherboard
- The PC won't boot at all, even into Safe Mode or WinRE
- chkdsk or MemTest86 report hardware errors — component replacement requires physical access
- BSODs occur during Windows reinstallation — the hardware itself is faulty
- Clicking or grinding noises from a mechanical hard drive — this is a medical emergency for your data, stop using the computer immediately
- The computer gets hot enough to burn before crashing — the cooling system needs service
IT Cares technicians diagnose BSODs remotely (via AnyDesk) and on-site in Montreal. We use professional tools to identify the exact faulty component and fix it with a result guarantee. Remote diagnosis takes under 30 minutes — we'll tell you honestly if it's software (fixable remotely) or hardware (needs physical repair).
Still Getting Blue Screens?
IT Cares diagnoses and fixes BSODs remotely and on-site in Montreal. We'll identify the exact cause — driver, RAM, drive, or system file — in under 30 minutes.
Prevention: How to Stop Blue Screens From Coming Back
- Update drivers carefully — use only official sources (nvidia.com, amd.com, intel.com). Never use "Driver Updater" software — they frequently install incorrect drivers
- Wait 1-2 weeks after major Windows Updates before installing them — let others discover the bugs first. You can pause updates in Settings > Windows Update
- Clean out dust every 6 months — use compressed air with the PC powered off and unplugged
- Use a UPS (uninterruptible power supply) — sudden power cuts during write operations corrupt system files
- Keep at least 15% of your drive free — a near-full drive causes Windows to mismanage the page file
- Enable System Restore — gives you a quick rollback option after a bad update
Frequently Asked Questions
Does the blue screen damage my computer?
The BSOD itself does not cause hardware damage — it's a protection mechanism. However, the underlying cause (overheating, failing drive) can cause damage if left untreated. Repeated BSODs during disk write operations can also corrupt files.
Can I fix a BSOD without losing my files?
Yes — the vast majority of fixes (driver rollback, SFC, DISM, Windows Update uninstall) do not touch personal files at all. Even "Reset this PC" has a "Keep my files" option. The only risk is if the BSOD is caused by a physically failing drive — in that case the drive itself is the threat, not the fix.
Why do I keep getting different BSOD error codes?
Changing stop codes typically point to defective RAM. When RAM chips fail, they corrupt data randomly, producing different crash signatures each time. Run MemTest86 for 8 hours — if it finds errors, replace the faulty RAM stick(s).
How do I fix BSOD if I can't boot into Windows?
Force shut down 3 times in a row during startup (hold power button when Windows logo appears). On the 4th attempt, Windows enters Recovery Environment automatically. From there: Troubleshoot > Advanced options, then try Startup Repair first, then System Restore, then Command Prompt to run SFC and DISM offline.
My laptop is brand new — why is it blue screening?
A new computer should never BSOD. If it does, it's almost certainly a manufacturing defect (defective RAM or SSD). Do not try to fix it yourself — contact the retailer or manufacturer and get it replaced under warranty. Document every crash with a photo of the error screen.
Comments (3)
Step 3 saved me. Had IRQL_NOT_LESS_OR_EQUAL every day for a week. Rolled back my NVIDIA driver in Device Manager and it's been completely stable for 5 days. I never would have known to look there. Thank you for the clear instructions.
The BlueScreenView tip was a game changer. Found out it was nvlddmkm.sys causing my SYSTEM_SERVICE_EXCEPTION crashes. Ran DDU in safe mode, reinstalled the driver from nvidia.com — no more blue screens. The article is genuinely detailed and actually worked.
KERNEL_DATA_INPAGE_ERROR was terrifying me. Ran chkdsk and it found 4 bad sectors on my old HDD. IT Cares replaced the drive and cloned everything over. Lost zero files. The advice to back up immediately before doing anything else was spot on — don't skip that step.
Leave a Comment