Windows blue screen: capture the stop code, fix it, or call a pro

A blue screen (BSOD, or stop error) means Windows deliberately halted itself to stop a critical fault from corrupting your system or data. The screen shows a stop code and sometimes a module name, both worth noting before you do anything else. Write it down or snap a photo, then work through the quick checklist below. One crash is rarely a disaster; the same stop code showing up repeatedly is what tells you it's time to dig deeper or call in help.

Fixing a blue screen in Windows: 8 steps to try right now

Before you touch drivers or run diagnostics, work through the basics in order. Most single stop errors clear up without any of the advanced steps further down this page, and Microsoft's own troubleshooting guidance confirms most one off restarts resolve on their own.

1. Capture the stop code. Photograph the screen or write down the stop code name (something like INACCESSIBLE_BOOT_DEVICE) and any module name listed underneath it.
2. Unplug anything new. Disconnect any USB device, external drive, dock, or peripheral you've added recently, then restart normally.
3. Watch what happens on restart. If the PC boots fine, keep using it as normal. If it crashes again, move to safe mode.
4. Boot into safe mode. Hold Shift while clicking Restart, or interrupt the boot process twice to trigger the recovery environment, then choose Safe Mode.
5. Check your free disk space. Aim to keep at least 10 to 15% of your main drive free. A nearly full drive causes update failures and file system errors that mimic hardware faults.
6. Run Windows Update. Microsoft patches known stop-code bugs regularly, and an outdated driver package is one of the most common triggers.
7. Run an SFC scan and a quick antivirus check. Open Command Prompt as administrator and type sfc /scannow, then let your antivirus run a fast scan in the background.
8. Know when to stop troubleshooting yourself. If the same code returns after two or three attempts, or you notice missing files, unusual noises from the drive, or the PC won't boot at all, that's your cue to escalate rather than keep guessing.

Pro Tip: Keep your phone next to the desk for a week after your first blue screen. If it happens again, you want that stop code photo from last time to compare against the new one. A matching code is the clearest sign you're dealing with the same unresolved fault.

Microsoft Learn's stop code reference sets out this same core sequence: remove new hardware, boot to safe mode, check Device Manager, confirm disk space, and install updates. It's the same order technicians follow, just condensed for a five minute check.

What does the stop code on a blue screen actually mean?

The stop code is the name Windows gives the specific failure it hit, and it's the single most useful piece of information on that screen. Codes like MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA describe the category of fault, not necessarily the exact component responsible. Underneath the code, Windows sometimes lists a hexadecimal value and a module name, and this is where people often draw the wrong conclusion.

A module name identifies the code that was running when the crash happened. That's a subtle but important distinction: a driver named in the crash isn't automatically the cause. It might simply be the file that happened to be executing when a fault triggered elsewhere in the system, which is why Microsoft's bug-check documentation stresses corroborating any suspected driver with dump analysis or a hardware test before assuming it's guilty.

A few practical points worth knowing:

• Windows 10 and Windows 11 both use the same underlying stop code system, though Windows 11's screen styling and QR code link differ slightly from earlier versions.
• The stop code name (e.g. DRIVER_IRQL_NOT_LESS_OR_EQUAL) is more useful to search and report than the hex value alone.
• Module names ending in .sys almost always point to a driver file, which narrows your troubleshooting significantly.
• Some crashes show no module name at all, which usually means the fault happened at a level Windows couldn't trace to a specific file.

Practitioner estimates suggest roughly 75% of stop code errors trace back to third-party drivers or driver interactions rather than Windows itself. That single figure should shape how you triage: check drivers before you start suspecting your RAM or motherboard.

To capture this information reliably, take a photo of the full screen including the QR code, or open Event Viewer afterwards and check the System log around the crash timestamp. Windows also writes a memory dump automatically in most default configurations, which becomes useful further down the troubleshooting path.

What causes blue screens, and how do you test for each one?

Most blue screens trace back to one of five categories, and each has a fast, low-risk test you can run before assuming the worst.

• Third-party drivers. This is the most common cause by a wide margin. Open Device Manager, look for any device with a yellow warning triangle, and check whether you've updated a graphics, network, or peripheral driver recently. Rolling back a driver you installed in the last two weeks resolves a surprising share of crashes.
• Faulty RAM. Search "Windows Memory Diagnostic" in the Start menu and let it run a standard scan, or download memtest86 for a more thorough overnight test. Random crashes with different stop codes each time often point here.
• Storage faults. INACCESSIBLE_BOOT_DEVICE and similar codes usually mean Windows lost contact with its boot drive. Check the drive's SMART status through its manufacturer's tool, and confirm SATA or NVMe cables and slots are seated properly if you've recently opened the case.
• Overheating and power faults. Codes beginning with WHEA_UNCORRECTABLE_ERROR often point to thermal issues or unstable power delivery. Check that fans are spinning, vents aren't blocked with dust, and consider resetting overclocked settings in BIOS or UEFI back to default.
• Software conflicts and corrupted system files. A recent Windows update, a new application, or a corrupted system file can all trigger blue screens that look hardware related but aren't. Running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth catches a large share of these.

Testing in this order matters. It's far easier to disable a driver than to replace a stick of RAM, so start cheap and reversible, then work towards anything that requires opening the case or swapping parts.

How do you troubleshoot a Windows blue screen step by step?

Once you've run the quick checklist and identified a likely category from the section above, it's time for a structured pass. This flow moves from the safest, most reversible steps through to recovery options, and it mirrors the order technicians use when a PC lands on the bench.

1. Boot into safe mode and observe. Safe mode loads Windows with only essential drivers, so if your PC runs fine there but crashes normally, a third-party driver or startup application is almost certainly involved. If it still crashes in safe mode, the fault is more likely hardware or a core system file, which changes your next move.

2. Work through Device Manager methodically. For any device showing a warning icon, right click and choose Update Driver first. If that doesn't help, use Roll Back Driver if the option is available. Failing that, disable the device temporarily to confirm whether crashes stop, which tells you definitively whether that hardware is involved before you commit to replacing anything.

3. Check storage health and BIOS defaults. Run chkdsk /f /r from an elevated Command Prompt (this needs a restart to complete) and check your drive's SMART data using its manufacturer's diagnostic tool. If you've changed any BIOS or UEFI settings recently, particularly around RAM timings, voltage, or overclocking profiles, reset them to default and retest. If you're planning to clone a failing drive rather than repair it, do this before running further repair tools, since some repair processes can make a failing drive harder to image cleanly afterwards.

4. Run SFC and DISM together. sfc /scannow checks and repairs core system files, while DISM repairs the underlying Windows image that SFC draws from. Run DISM first if SFC reports it can't fix something, since a damaged image needs repairing before SFC has anything reliable to check against.

5. Use System Restore or Reset This PC when the fault started after a specific change. If you can pinpoint roughly when the crashes began, a System Restore to a point beforehand is faster than reinstalling anything. If restore points aren't available or the corruption is deeper, Reset This PC with the "keep my files" option preserves your documents while replacing the Windows installation itself.

6. Handle a PC that won't boot at all. If Windows can't reach the desktop, it should drop into the Windows Recovery Environment automatically after two failed boot attempts. From there, Startup Repair diagnoses common boot faults automatically, while Command Prompt access lets you run chkdsk or bootrec commands manually. Having a recovery USB prepared in advance makes this stage far less stressful, since you're not trying to build one while the machine you need it for is the one that's broken.

If you've been through this whole sequence and the crashes persist, that's a strong signal you're dealing with either a genuine hardware fault or something that needs dump analysis. A related guide on PCs that won't boot walks through the recovery environment steps in more detail if you're stuck at that stage.

How do technicians analyse crash dumps for a blue screen?

When the standard troubleshooting flow doesn't resolve the fault, the next layer of evidence is the crash dump Windows writes automatically at the moment of failure. This is where casual troubleshooting ends and technician level debugging begins, and it's genuinely worth understanding even if you never run the tools yourself.

• Minidumps save to C:\Windows\Minidump by default and contain a condensed snapshot of the crash, usually a few hundred kilobytes.
• Full memory dumps capture everything in RAM at the time of failure and need to be enabled manually in advance through System Properties, since they aren't the default setting.
• WinDbg, Microsoft's free debugging tool, opens a dump file and the !analyze -v command produces a detailed breakdown of the likely faulting module and call stack.
• The output often names a specific driver file, but as with the module name on the blue screen itself, that's a lead to corroborate, not a confirmed verdict.
• Common false leads include generic system files like ntoskrnl.exe appearing in the stack simply because they're involved in almost every crash, regardless of the true cause.
• Disabling a suspected driver to confirm the theory is a reasonable step for a technician; casual users should stop at gathering the dump file and let a professional run the analysis, since disabling the wrong driver on business hardware can cause its own problems.

Pro Tip: If you're planning to hand your PC to a technician, enable full memory dumps beforehand if you can still boot normally. A minidump is useful, but a full dump gives WinDbg far more context and often cuts diagnostic time down considerably.

How do you prevent future blue screen errors?

A short, consistent maintenance routine catches most of the conditions that lead to stop errors before they happen.

• Keep Windows Update and drivers current, sourcing driver updates from the manufacturer's site or Windows Update rather than third-party download sites.
• Back up important files regularly, and consider an image-based backup so a full system recovery doesn't mean starting from scratch.
• Keep an eye on internal temperatures, especially if your PC lives in a cabinet or gets dusty, since heat-related WHEA errors build slowly before they become obvious.
• Create a System Restore point manually before installing anything major, like a new graphics driver or a BIOS update.
• Build a recovery USB while your PC is healthy, not after it's already refusing to boot.
• When setting up a new PC or adding new hardware, isolate one change at a time so you can immediately tell what caused a problem if one appears. Our new PC setup checklist covers this in practical detail.

When we get called in for a blue screen, and what to have ready

Most of the recurring blue screen jobs we see fall into three buckets: a driver regression after a Windows Update, a hard drive quietly failing over weeks before it finally throws INACCESSIBLE_BOOT_DEVICE, or a BIOS or UEFI setting that got changed during a hardware upgrade and never reset properly. Each of these is diagnosable, but it takes the right evidence to do it quickly.

Before a technician arrives, or before a remote session starts, it helps enormously to have the stop code written down, a rough timeline of any recent changes, and a note of whether crashes happen randomly or only under specific conditions like gaming or waking from sleep. A remote session usually covers driver checks, event log review, and system file repairs. Onsite visits add hardware testing and physical inspection when the fault looks component related. If you suspect data loss, back up whatever you can access before the visit.

- PC Scientist

How PC Scientist can help when the blue screens won't stop

You have practical options beyond guessing through driver rollbacks and BIOS resets alone, particularly if the crashes involve a business machine you can't afford to have offline for long. Onsite and remote diagnostic sessions are available across New South Wales service areas, and a typical visit starts with exactly the evidence this guide has walked you through: the stop code, a look at recent changes, and a check of crash dump data if one's available.

Our Computer Repair Scientist service handles hardware diagnosis and repair for both laptops and desktops, whether the culprit turns out to be a failing drive, unstable RAM, or a driver conflict that needs a technician's eye rather than another restart. If crashes have already cost you files, our Data Recovery Scientist team can recover data from a drive that's on its way out before it fails completely. For a straightforward next step, book a diagnostic session through PC Scientist and bring your stop code notes with you. It'll save time on both ends.

Sources

For deeper detail beyond this guide, Microsoft's own references are the most reliable starting point: the stop code troubleshooting guide, the bug check reference for WinDbg analysis, and our own Safe Mode test guide for a hands on companion to the steps above.

• Stop code error or bug check troubleshooting - Windows Client | Microsoft Learn
• Troubleshooting Windows unexpected restarts and stop code errors - Microsoft Support

Recommended

• Windows won't boot? Try this fix order first
• PC keeps freezing? Try this 20-minute Safe Mode test
• Computer running slow? Here's what to try first
• Laptop won't turn on? Here's what to check first