Halloween DealsAmazon USHalloween week deals: useful picks before month-endAmazon US: current deals, useful picks and tech finds.Check DealsClean PCRecommendedOne scan can reveal what keeps slowing WindowsLook for cleanup and repair opportunities.Run ScanHalloween DealsAmazon USOctober picks are moving - compare before checkoutAmazon US: current deals, useful picks and tech finds.See Picks×
VGSOURCES
Get listed

blue screenPATCH 2026.10.18

How to Fix a Windows Stop-Code Error (Blue Screen)

By VGSources Team 8 min read

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A Windows stop-code error is a serious crash, commonly shown as a blue screen (BSOD), that forces Windows to shut down or restart to protect the system. Write down the exact stop-code name, hexadecimal code, and any “What failed” module first. Then use this order: remove recently added hardware, try Safe Mode, install Windows updates, and undo or update the change that appeared before the first crash. If the computer cannot start even in Safe Mode, the same code keeps returning, or hardware errors are suspected, preserve the crash information and get qualified technical help.

What a Windows stop code means

A stop code is Windows’ name for a protective shutdown after the operating system detects a condition that could make normal operation unsafe or lead to operating-system or user-data corruption. You may also see the terms bug check, kernel error, blue-screen error, or BSOD. The screen can show a readable name such as PAGE_FAULT_IN_NONPAGED_AREA or MEMORY_MANAGEMENT, a hexadecimal value, and sometimes the driver or module involved.

As an Amazon Associate I earn from qualifying purchases.

The code is a symptom, not a complete diagnosis. Microsoft states: “An unexpected restart might be caused by a hardware device, its driver, or software.” A single restart can be an isolated event; repeated crashes require a methodical search for the change or component that is triggering the failure.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Capture the evidence before changing anything

The blue-screen display can disappear quickly after an automatic restart. Before attempting repairs, record what Windows showed.

#1 Best Overall
5-in-1 Win Repair & Reinstall Bootable USB Flash Drive – Fix, Recover, or Reinstall Windows 11 (amd64 + arm64) / 10/7 - Includes PE Tools, Driver Pack, Antivirus, Data Recovery & Password Reset
  • Dual USB-A & USB-C Bootable Drive – compatible with nearly all Windows PCs, laptops, and tablets (UEFI & Legacy BIOS). Works with Surface devices and all major brands.
  • Fully Customizable USB – easily Add, Replace, or Upgrade any compatible bootable ISO app, installer, or utility (clear step-by-step instructions included).
  • Complete Windows Repair Toolkit – includes tools to remove viruses, reset passwords, recover lost files, and fix boot errors like BOOTMGR or NTLDR missing.
  • Reinstall or Upgrade Windows – perform a clean reinstall of Windows 7 (32bit and 64bit), 10, or 11 (amd64 + arm64) to restore performance and stability. (Windows license not included.). Includes Full Driver Pack – ensures hardware compatibility after installation. Automatically detects and installs drivers for most PCs.
  • Premium Hardware & Reliable Support – built with high-quality flash chips for speed and longevity. TECH STORE ON provides responsive customer support within 24 hours.
  • Write the stop-code name exactly, including underscores.
  • Copy the hexadecimal code if one appears.
  • Record any What failed driver, file, or module name.
  • Note what you were doing: starting a game, waking from sleep, connecting a device, installing software, or performing another task.
  • Record whether this was the first crash or whether the same code has appeared repeatedly.

If Windows restarted normally and this happened only once, continue to monitor it rather than immediately making several unrelated changes. Changing many things at once makes it harder to identify the cause if the stop code returns.

Follow this safe first-response procedure

  1. Shut down and remove newly added hardware

    If the crash began after installing a device, expansion card, storage drive, memory module, dock, adapter, or other hardware, turn the computer off completely. Disconnect the newly added item or return the system to its previous hardware configuration, then start Windows again. A change that coincided with the first crash is more informative than a generic repair utility.

  2. Start Windows in Safe Mode when normal startup is unstable

    Safe Mode starts Windows with a limited set of drivers and startup software. If the computer is usable long enough to open Windows, go to Settings > System > Recovery (on Windows 10, the wording may appear under Update & Security > Recovery), choose Advanced startup, select Restart now, then choose Troubleshoot > Advanced options > Startup Settings > Restart. Select the Safe Mode option after the restart.

    Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

    If Windows will not stay running long enough to reach Settings, interrupt startup by holding the power button to turn the PC off, then start it again. After repeated failed starts, Windows may open its recovery environment automatically; from there use Troubleshoot > Advanced options > Startup Settings. Avoid repeatedly cutting power if Windows is performing a repair or update.

  3. Install current Windows updates

    In normal mode or Safe Mode with networking when available, open Settings > Windows Update and select Check for updates. Install available quality and cumulative updates, restart when requested, and check again until no further updates are offered. Updates can correct system software and driver compatibility problems that trigger a bug check.

  4. Undo or update the change associated with the first crash

    If the stop code started after a driver, application, or hardware change, reverse that change first. For a driver, open Device Manager, expand the relevant device category, open the device’s Properties, and use Driver > Roll Back Driver when that option is available. If rollback is unavailable, use the device manufacturer’s current driver for your exact Windows edition and hardware model. For an application, remove the recently installed version from Settings > Apps > Installed apps and restart. Do not install several different driver packages at once.

  5. Test after each change

    Restart normally and use the computer in the situation that previously produced the crash. If the same stop code returns, record the new time and context before trying the next remedy. A fix that stops one symptom but creates a different crash is not a confirmed solution.

    Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Use the pattern of the crash to choose the next step

When several remedies appear plausible, compare four facts instead of guessing:

Question What the answer suggests Practical next move
Did the crash begin immediately after a change? A recently installed driver, application, or hardware item is a leading suspect. Remove, roll back, or uninstall that change, then retest.
Does it reproduce in Safe Mode? A crash that disappears in Safe Mode points toward a third-party driver or startup program; a crash that persists there warrants broader hardware or system investigation. Compare normal and Safe Mode behavior before adding more software.
Does the same stop-code name repeat? A repeated code gives you a stable clue; changing codes can indicate several interacting problems or heavily corrupted memory. Keep the exact names and timestamps together and use the repeated code for code-specific guidance.
Do diagnostics implicate a component? Evidence of a device, memory, storage, or other hardware problem changes the repair path. Stop stressing the machine, back up accessible data, and arrange qualified hardware testing.

Do not treat a registry cleaner, a generic driver updater, or a one-click repair utility as proof that an unspecified stop code has been diagnosed. A tool cannot infer the failed component from the word “blue screen” alone.

Rank #2
SANDISK 128GB Ultra Flair, USB-A Flash Drive, Up to 150MB/s Read Speeds | USB Flash Drive, Up to 15x Faster than standard 2.0, Password Protection, Durable, Sleek Metal Casing, USB 3.0, Silver/Black
  • High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
  • Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
  • Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
  • Sleek, durable metal casing
  • Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9 plus; Software download required for Mac, visit the SanDisk SecureAccess support page]

What the stop-code statistics tell you

Microsoft Learn’s crash-root-cause analysis reports the following distribution: 70% caused by third-party driver code, 10% by hardware issues, 5% by Microsoft code, and 15% unknown because memory is too corrupted to analyze. These are Microsoft’s reported analysis figures, not a universal probability for every computer, Windows release, or crash. They explain why checking drivers and recently changed devices is often productive while leaving room for hardware and system-software causes.

Reported category Share in Microsoft’s analysis How to use it
Third-party driver code 70% Prioritize a driver rollback or an official driver update when the crash follows a device or driver change.
Hardware issues 10% Consider component testing when the crash persists in Safe Mode or follows a physical hardware change.
Microsoft code 5% Keep Windows fully updated and preserve the exact dump and stop-code details.
Unknown because memory is too corrupted to analyze 15% Do not claim certainty from an incomplete dump; escalate if crashes continue.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

How to handle common code names

PAGE_FAULT_IN_NONPAGED_AREA

This name indicates that Windows stopped while handling an invalid memory reference in an area that should remain available. The name alone does not identify whether a driver, software component, or physical memory problem is responsible. Start with the evidence workflow: note any named module, compare normal startup with Safe Mode, and undo the driver, application, or hardware change that preceded the first crash.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

MEMORY_MANAGEMENT

This code points to a failure in Windows memory management, but it is not a guarantee that a memory module is defective. A driver that corrupts memory can produce the same visible code. Repeat the Safe Mode comparison, remove recent changes, install updates, and preserve crash information before replacing hardware.

For any other code, use the exact spelling and the named module when looking for Microsoft’s code-specific guidance. Do not substitute a similar-looking code or rely on a generic “fix all BSODs” checklist.

If Windows will not boot normally

Use the recovery environment

Allow Windows to enter its recovery environment after failed starts, or reach it through Settings > System > Recovery > Advanced startup when possible. Use Troubleshoot > Advanced options > Startup Settings to test Safe Mode. If Safe Mode works, remove the recent change and complete Windows Update from that stable session.

Protect data before repeated experiments

If you can reach the desktop or a recovery command prompt and important files are accessible, copy them to a separate, known-good location before continuing. Repeated crashes and forced shutdowns can make later recovery more difficult. If the storage device is making unusual noises, disappearing, or producing read errors, stop troubleshooting and seek professional data assistance.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

When recovery options do not work

If the machine cannot boot normally or in Safe Mode, do not keep cycling through random drivers and utilities. Photograph the stop screen, record the recovery options tried, and arrange qualified repair help. A technician may need the crash dump, event information, and hardware diagnostics that are difficult to interpret safely without a stable system.

Preserve crash information for advanced analysis

When crashes continue, preserve the stop-code screen, the time of each failure, and any dump or event information Windows created. Keep the original files rather than renaming or deleting them. An advanced user or IT professional can compare dumps, identify a repeatedly named module, and determine whether the memory was too corrupted for a reliable conclusion. Microsoft provides separate advanced troubleshooting guidance for IT professionals and experienced users; follow that material only when you are comfortable changing recovery and diagnostic settings.

When to escalate immediately

  • The computer cannot boot normally or in Safe Mode.
  • The same stop code returns after removing recent hardware, updating or rolling back the relevant driver, and installing Windows updates.
  • Hardware errors are suspected, especially after a component change or when crashes occur under ordinary use.
  • Important data may be at risk or the storage device shows signs of failure.
  • You need crash-dump interpretation and cannot identify a consistent module or trigger.

Give the technician the exact stop-code name, hexadecimal value, “What failed” text, first-crash date, recent changes, Safe Mode result, and the steps already attempted. That history is more useful than reporting only that the PC “got a blue screen.”

As an optional shortcut after the manual checks, Outbyte PC Repair can look for more than 100 common Windows issues, including broken system elements, invalid redirects, and shared DLL problems, while also offering settings adjustments, temporary-file cleanup, privacy warnings, vulnerability checks, a real-time boost, file shredding, and an app-crash log. It runs on Windows 11, 10, 8, and 7; its free trial is offered by category for at least two days and then requires a subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

blue screenBSODstop codetroubleshootingWindows

Leave a reply

Your email address will not be published. Required fields are marked *

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Recommended PC Tool
Recommended PC Tool
Windows Errors? Fix Them Before They SpreadFree repair scan
Crashes, No Sound, or Screen Glitches?Free driver scan

Two free Windows tools

One Free Minute Could Fix That PC

Before you go - each of these free tools takes about a minute and tackles what quietly slows a Windows PC down.

Special offer. View Outbyte info, uninstall instructions, EULA, and Privacy Policy.