Error Medic

Microsoft Windows Stop Code Errors: Complete Troubleshooting Guide (Including MEMORY_MANAGEMENT & More)

Fix Windows Stop Code (BSOD) errors including MEMORY_MANAGEMENT. Step-by-step commands and solutions to get your PC running again fast.

Last updated:
Last verified:
2,032 words
Key Takeaways
  • Windows Stop Code errors (Blue Screen of Death) are triggered by critical kernel-level failures — common culprits include faulty RAM, corrupt drivers, hardware conflicts, and damaged system files.
  • The MEMORY_MANAGEMENT stop code (0x0000001A) specifically indicates a severe error in the Windows memory management subsystem, often caused by bad RAM sticks, outdated drivers, or malware.
  • Quick fix summary: Boot into Safe Mode, run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' to repair system files, use Windows Memory Diagnostic to test RAM, update or roll back recently installed drivers, and check Event Viewer for the exact failing component.
Fix Approaches Compared
MethodWhen to UseTimeRisk
SFC & DISM ScanCorrupt or missing Windows system files suspected15-30 minLow
Windows Memory DiagnosticMEMORY_MANAGEMENT or random BSODs suggest bad RAM10-60 minLow
Driver Rollback / UpdateBSOD started after a Windows Update or new hardware install5-15 minLow-Medium
Startup Repair (WinRE)System won't boot past BSOD loop10-20 minLow
System RestoreBSOD appeared after a recent change and restore point exists20-40 minMedium
RAM ReplacementMemory Diagnostic finds errors, reseating doesn't help30-60 minMedium
Clean Windows InstallAll other methods fail; hardware tests pass1-2 hrsHigh (data loss risk)

Understanding Windows Stop Code Errors

A Windows Stop Code — colloquially called a Blue Screen of Death (BSOD) — is Windows' last resort safety mechanism. When the kernel detects an unrecoverable error that could corrupt data or cause hardware damage, it halts all processes and displays a blue screen with a stop code and QR code linking to https://www.microsoft.com/en-us/windows/stop-code for guidance.

The screen you see typically reads:

Your PC ran into a problem and needs to restart.
We're just collecting some error info, and then we'll restart for you.

Stop code: MEMORY_MANAGEMENT

Or for other variants:

Stop code: SYSTEM_SERVICE_EXCEPTION
Stop code: PAGE_FAULT_IN_NONPAGED_AREA
Stop code: IRQL_NOT_LESS_OR_EQUAL
Stop code: CRITICAL_PROCESS_DIED

Every stop code maps to a hexadecimal bug check code. For example, MEMORY_MANAGEMENT = 0x0000001A, PAGE_FAULT_IN_NONPAGED_AREA = 0x00000050, and IRQL_NOT_LESS_OR_EQUAL = 0x0000000A.


Step 1: Collect the Stop Code and Crash Dump

Before fixing anything, record exactly what you see:

  1. Note the stop code text (e.g., MEMORY_MANAGEMENT) and any listed 'Failed module' (e.g., ntfs.sys, nvlddmkm.sys).
  2. Find the minidump file after reboot: Navigate to C:\Windows\Minidump\. If empty, enable crash dumps:
    • Right-click 'This PC' → Properties → Advanced system settings → Startup and Recovery → Settings.
    • Set 'Write debugging information' to 'Small memory dump (256 KB)'.
    • Restart and reproduce the crash.
  3. Check Event Viewer for the critical error:
    • Press Win + X → Event Viewer → Windows Logs → System.
    • Filter by 'Critical' and 'Error' events near the crash timestamp.
    • Look for Event ID 41 (Kernel-Power) or Event ID 1001 (BugCheck).

Step 2: Boot into Safe Mode (If BSOD Loops on Startup)

If your system cannot boot normally:

  1. Force-shutdown the PC 3 times in a row (hold power button) — Windows will enter Automatic Repair mode.
  2. Click 'Advanced options' → 'Troubleshoot' → 'Advanced options' → 'Startup Settings' → 'Restart'.
  3. Press F4 for Safe Mode or F5 for Safe Mode with Networking.
  4. All subsequent diagnostic steps can be run from Safe Mode.

Alternatively, boot from Windows installation media and choose 'Repair your computer'.


Step 3: Run SFC and DISM to Repair System Files

Open Command Prompt as Administrator (search 'cmd', right-click, 'Run as administrator'):

sfc /scannow

Wait for the scan to complete. If it reports 'Windows Resource Protection found corrupt files but was unable to fix some of them,' run DISM:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run sfc /scannow again. Restart the PC when done.


Step 4: Test RAM with Windows Memory Diagnostic

For MEMORY_MANAGEMENT (0x0000001A) stop codes especially:

  1. Press Win + R, type mdsched.exe, press Enter.
  2. Choose 'Restart now and check for problems'.
  3. The tool will run in two passes by default. Press F1 to access extended test options and enable the 'Extended' test for thoroughness.
  4. After reboot, results appear in the system tray or in Event Viewer under 'Windows Logs → System' (Event Source: MemoryDiagnostics-Results).

If errors are found:

  • Power off, open the case, and reseat the RAM sticks.
  • Test each stick individually by removing all but one and cycling through slots.
  • Replace any stick that shows errors.

Step 5: Update or Roll Back Drivers

BSODs caused by drivers account for a large percentage of stop code occurrences. The failed module listed on the BSOD screen (e.g., nvlddmkm.sys = NVIDIA driver, ntfs.sys = file system, ataport.sys = storage driver) points you in the right direction.

To roll back a driver:

  1. Press Win + X → Device Manager.
  2. Expand the relevant category (e.g., Display adapters, Network adapters).
  3. Right-click the device → Properties → Driver tab → 'Roll Back Driver'.

To update a driver:

  1. Right-click the device → 'Update driver' → 'Search automatically for updated driver software'.
  2. Or visit the manufacturer's website for the latest stable driver.

For GPU drivers specifically (frequent culprit):

  • NVIDIA: Download DDU (Display Driver Uninstaller), boot into Safe Mode, run DDU to cleanly remove old drivers, then install fresh from nvidia.com.
  • AMD: Use AMD Cleanup Utility before reinstalling from amd.com.

Step 6: Check Disk Health

Corrupt sectors or a failing drive can cause stop codes like NTFS_FILE_SYSTEM or PAGE_FAULT_IN_NONPAGED_AREA.

chkdsk C: /f /r /x

This command requires a reboot to run on the active partition. Schedule it and restart. For SSDs, also check manufacturer diagnostic tools (Samsung Magician, CrystalDiskInfo, etc.).


Step 7: Analyze the Minidump File (Advanced)

For persistent BSODs where the cause isn't obvious:

  1. Download WinDbg from the Microsoft Store or Windows SDK.
  2. Open WinDbg → File → Open Crash Dump → navigate to C:\Windows\Minidump\ and open the latest .dmp file.
  3. In the command window, type:
    !analyze -v
    
  4. Look for the 'STACK_TEXT' and 'MODULE_NAME' fields — these identify the exact driver or component that triggered the crash.

Step 8: Use Startup Repair or System Restore

If the above steps don't resolve the issue:

  • Startup Repair: Boot from Windows media → Repair your computer → Troubleshoot → Startup Repair. Windows automatically attempts to fix boot and system issues.
  • System Restore: Boot from media → Troubleshoot → Advanced options → System Restore. Choose a restore point from before the BSODs began.

Step 9: Perform a Clean Windows Install (Last Resort)

If hardware passes all tests and software fixes fail:

  1. Back up all important data to an external drive.
  2. Download the Windows 11 or Windows 10 Media Creation Tool from Microsoft.
  3. Create a bootable USB drive.
  4. Boot from USB and choose 'Custom: Install Windows only (advanced)' for a clean install.

This resolves any deep OS corruption or incompatible software conflicts that survive all repair methods.

Frequently Asked Questions

bash
# ============================================================
# Windows Stop Code Diagnostic & Fix Script
# Run all commands in Administrator Command Prompt or PowerShell
# ============================================================

# --- Step 1: Check System File Integrity ---
sfc /scannow

# --- Step 2: DISM Image Repair (run if SFC finds unfixable errors) ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# --- Step 3: Re-run SFC after DISM ---
sfc /scannow

# --- Step 4: Check Disk for Errors (schedules on next reboot for C:) ---
chkdsk C: /f /r /x

# --- Step 5: View recent BugCheck events in Event Viewer via PowerShell ---
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001} | Select-Object -First 10 | Format-List TimeCreated, Message

# --- Step 6: View Memory Diagnostic Results ---
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-MemoryDiagnostics-Results'} | Format-List TimeCreated, Message

# --- Step 7: Launch Windows Memory Diagnostic ---
mdsched.exe

# --- Step 8: List all installed drivers with dates (find recently changed ones) ---
driverquery /v /fo csv | ConvertFrom-Csv | Sort-Object 'Driver Start Mode' | Select-Object 'Module Name','Display Name','Driver Type','Start Mode','State','Driver Start Mode' | Format-Table -AutoSize

# --- Step 9: Export minidump list for analysis ---
dir C:\Windows\Minidump\ /od

# --- Step 10: Open WinDbg to analyze latest minidump (requires WinDbg installed) ---
# Replace the filename below with your actual .dmp file name
# windbg -z C:\Windows\Minidump\Mini010125-01.dmp

# --- Step 11: Disable automatic restart on BSOD (to read the stop code) ---
wmic recoveros set AutoReboot = False

# --- Step 12: Check RAM slots and details ---
wmic memorychip get BankLabel,Capacity,DeviceLocator,MemoryType,Speed

# --- Step 13: Export System Info for full hardware report ---
msinfo32 /report C:\SystemInfo.txt

# --- Step 14: Check for pending Windows Updates ---
# PowerShell - requires PSWindowsUpdate module
# Install-Module PSWindowsUpdate -Force
# Get-WindowsUpdate

# --- Step 15: Roll back a specific driver via PowerShell (example: Display adapter) ---
# Get-PnpDevice | Where-Object {$_.Class -eq 'Display'}
# Use Device Manager GUI for rollback: devmgmt.msc
devmgmt.msc
E

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows system administrators with 10+ years of experience diagnosing and resolving critical system failures across enterprise and consumer environments. Our guides are built from real incident post-mortems, Microsoft documentation, and hands-on lab testing — so every fix we recommend actually works.

Sources

Related Articles in Microsoft Windows Stop Code

Explore More windows Guides