Fix 75% of Windows 11 Blue Screens. Read the Stop Code First
If you see a Windows 11 blue screen, first note the stop code, remove any recently added hardware, and try booting to Safe Mode. Most cases trace back to a faulty driver and are fixable without reinstalling Windows. Minidump files that Windows saves during the crash sit in C:\Windows\Minidump if you need a deeper diagnosis later.
TL;DR:
Most blue screens in Windows 11 are caused by faulty drivers, with around 75% linked to specific low-level hardware or software components.
Basic troubleshooting steps such as freeing disk space, disconnecting new hardware, and installing pending updates can resolve many crashes without further diagnostics.
Analyzing stop codes and Event Viewer logs helps identify whether the issue stems from RAM, drivers, or disk problems, guiding targeted fixes.
Safe Mode and Windows Recovery Environment are effective tools to determine if crashes are caused by third-party software or hardware failures.
When troubleshooting fails or hardware issues are suspected, professional on-site diagnosis and repair offer a reliable solution.
Table of Contents
Quick checks to try before deeper troubleshooting
Before running diagnostic tools, rule out the simple causes. These checks take a few minutes each and solve a surprising number of crashes on their own.
Unplug external drives, USB hubs, and any internal hardware you added recently, then restart to see if the crash stops.
Free up at least 10 to 15% of your system drive, since Microsoft’s own troubleshooting guidance lists low disk space among the basic checks before anything more advanced.
Turn off automatic restart on system failure so the screen stays put long enough to read and photograph the stop code.
Open Settings and install any pending Windows updates, since a known driver bug is often already patched.
If the crash returns, restart into Safe Mode to see whether it happens there too.
Doing these five things first means you will not waste an hour on driver rollbacks or memory tests when the real problem was a nearly full hard drive or an update sitting half installed.
What the stop code and Event Viewer are telling you
The blue screen shows a stop code such as MEMORY_MANAGEMENT, CRITICAL_PROCESS_DIED, or DRIVER_IRQL_NOT_LESS_OR_EQUAL, often with a file name like a graphics or storage driver underneath it. That code is your starting point, not just an error to dismiss.
MEMORY_MANAGEMENT usually points to RAM or a driver mishandling memory. CRITICAL_PROCESS_DIED means a core system process closed unexpectedly, which can stem from corrupted system files or a misbehaving driver. A named driver file underneath the code is often the clearest clue you will get.
Microsoft’s stop code troubleshooting guide recommends working through removing new hardware, booting Safe Mode, checking Device Manager, and installing updates in that order, based on what the code points to. If the screen mentions a generic system file rather than naming a specific driver, that often means a third-party driver is the real cause but Windows cannot pin it down directly.
Event Viewer backs this up. Open it, go to Windows Logs > System, and look for a Bugcheck event around the time of the crash. Its details include the same stop code plus four parameter values that describe the exact failure, useful if you end up asking for help or searching the code online. Use what you find to decide your next move: a driver-related code means check Device Manager next, a memory code means test your RAM, and a disk-related code means run a disk check.
Booting to Safe Mode and using Windows Recovery Environment
Safe Mode starts Windows with only essential drivers and services running, according to Microsoft’s Safe Mode guidance. If your PC runs fine there but crashes normally, a third-party driver or app is almost certainly to blame rather than your hardware.
If Windows will not boot normally, force it to fail three times in a row (restart during loading) to trigger Windows Recovery Environment automatically, a method Microsoft documents for boot-looping PCs.
From the recovery screen, go to Troubleshoot, then Advanced options, then Startup Settings, then restart and choose Safe Mode.
If you suspect boot corruption rather than a driver issue, run Startup Repair from the same Advanced options menu instead, which scans for damaged system files, a broken boot configuration, or incompatible drivers.
If the crashes began after a specific update or app install, use System Restore from Advanced options to roll back to a point before the problem started.
A clean Safe Mode session that behaves itself is good news: it means you are chasing a driver or piece of software, not a failing part.
Checking Device Manager and updating or rolling back drivers
Faulty or incompatible drivers cause roughly 75% of stop errors, according to Microsoft Q&A discussion on BSOD causes. That single figure is the reason driver checks come before anything more drastic.
Open Device Manager and look for any entry with a yellow warning triangle. Right-click it, choose Update driver, and let Windows search automatically first. If a driver update happened just before the crashes started, right-click the device instead, choose Properties, then the Driver tab, then Roll Back Driver to undo it.
Work through likely culprits in this order: graphics drivers, storage controllers, chipset drivers, then network adapters. These four categories account for most driver-related BSODs because they run at a low level and touch the system constantly.
When you do need a fresh driver, download it from the manufacturer’s own site (Nvidia, AMD, Intel, or your laptop’s OEM support page) rather than a generic driver tool, and avoid installing anything unsigned. An unsigned or mismatched driver is a common way to trade one blue screen for another.
Running SFC, DISM, and hardware checks in the right order
System file and memory checks catch problems that driver updates cannot fix. Run them in sequence rather than all at once, since each tool assumes the previous layer is sound.
Open Command Prompt as administrator and run sfc /scannow first, which checks and repairs protected system files.
If SFC reports it could not fix everything, run DISM /Online /Cleanup-Image /RestoreHealth, which repairs the underlying component store that SFC draws from, a sequence Microsoft outlines in its recovery options guidance.
Run Windows Memory Diagnostic (search for it in the Start menu) or MemTest86 overnight; any FAIL result points to RAM that needs reseating or replacing.
If the stop code mentioned disk or file system issues, run chkdsk /f and check your drive’s SMART status through its manufacturer’s utility.
Pro Tip: Run these scans after a driver rollback, not before, so you are not chasing file corruption that a bad driver caused in the first place.
If SFC, DISM, and hardware tests all come back clean but the crashes continue, that is a strong sign the fault sits deeper than software, and a full OS reset or reinstall becomes the next reasonable step.
Reading minidumps and using Driver Verifier safely
Windows saves a small crash record, called a minidump, in C:\Windows\Minidump every time it blue screens. Each file names the loaded drivers at the time of the crash and the module that likely triggered it, which is far more specific than the stop code alone.
Install the Windows debugging tools (WinDbg) from Microsoft, open the minidump file, load symbols, then run !analyze -v.
Look for the Probable_Cause and IMAGE_NAME fields in the output, since these usually name the exact driver file responsible.
If several minidumps in a row point to a generic Windows file rather than a named driver, that pattern itself is useful information worth noting before you swap any hardware, as discussed in Microsoft Q&A’s minidump troubleshooting thread.
Driver Verifier built into Windows deliberately stresses drivers to force a crash that names the culprit, but it carries a real risk of causing boot loops on its own, according to Broadcom’s knowledge base on enabling Driver Verifier for BSOD cases. Create a System Restore point before turning it on, enable it against one suspected driver rather than all of them where possible, and remember the command verifier /reset if your PC will not boot afterwards.
If WinDbg output only shows generic system files with no clear driver name, or Driver Verifier sends you into a boot loop you cannot reset, that is the point to stop and hand the dump files to a technician or a knowledgeable forum rather than keep guessing.
When to stop troubleshooting and call in help
Some signs mean DIY has reached its limit: crashes that keep happening after driver rollbacks and full scans, a failed RAM or disk test, or important files you cannot afford to lose sitting on a drive that might be failing.
A technician visiting your home will run the same hardware diagnostics you have already tried, but with tools that go further, alongside data recovery and, where needed, a full OS repair or reinstall. Before booking, back up whatever you can, write down the stop codes you have seen, and note any recent hardware or software changes.
Expect an on-site visit to start with diagnosis before any repair work begins, and remember the promise behind it: No Fix, No Fee.
Why the stop code matters more than most people think
Most Windows 11 troubleshooting advice jumps straight to “reset your PC” far too early. That skips the one piece of evidence that actually tells you what is wrong: the stop code sitting on the blue screen itself. Reading it first, then testing in Safe Mode, turns a guessing game into a short list of likely causes.
The advice that Driver Verifier and WinDbg are “too advanced for normal people” is also overstated. Anyone can open a minidump and read a driver name out of the output. The real risk is not the tool, it is running Driver Verifier without a restore point first and getting stuck in a boot loop with no way back.
What most guides underplay is how often the fix is boring: a graphics driver rollback, a Windows update that was stuck, or 10GB of free space. Chase those before anything that involves a screwdriver or a full reinstall. Save the deep diagnostics for the crashes that survive all the easy fixes, and treat a repeated boot loop or a failed hardware test as the signal to stop doing it yourself.
— Matthew
Getting on-site help when the blue screen won’t quit
Working through stop codes, Safe Mode, and driver rollbacks takes patience, and not everyone has a spare afternoon to spend on it. A technician can be sent to your home to handle the diagnosis and repair directly, covering the hardware checks, data recovery, and OS repair work that a persistent blue screen usually calls for.
The visit runs on a basis where you only pay when the problem is actually resolved, with pricing explained upfront and no jargon.
What to prepare | Why it helps |
A note of the stop codes you have seen | Speeds up diagnosis on arrival |
A backup of important files | Protects data if a drive repair is needed |
A list of recent hardware or software changes | Points the technician to the likely cause faster |
Pro Tip: Leave the PC exactly as it was when it last crashed, don’t uninstall drivers or run resets right before the visit, so the technician can see the same evidence you did.
If your laptop or desktop keeps blue screening after trying the steps above, book a laptop and computer repair visit and get it sorted at home.
FAQ
How to fix Windows 11 blue screen?
Start by noting the stop code, removing any recently added hardware, and installing pending Windows updates. If the crash repeats, boot into Safe Mode, check Device Manager for driver warnings, and run sfc /scannow followed by DISM to repair system files.
Can Windows 11 cause a blue screen?
A blue screen is Windows 11 deliberately stopping itself to prevent data corruption after a critical failure. Faulty or incompatible drivers cause roughly 75% of these stop errors, so the operating system is usually flagging a driver or hardware problem rather than causing one on its own.
How do I fix my PC blue screen?
Work through the same order regardless of Windows version: remove new hardware, free up disk space, update drivers, install Windows updates, and use Safe Mode or Startup Repair if the crash continues. If scans and driver fixes don’t resolve it, the fault is more likely hardware and worth testing directly.
How to find out what caused blue screen in Windows 11?
Check Event Viewer under Windows Logs > System for a Bugcheck event, which records the stop code and four parameter values from the crash. For a more specific answer, open the minidump file saved in C:\Windows\Minidump using WinDbg and run !analyze -v to see the likely driver named in the output.
Recommended
Comments