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.
- 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.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| SFC & DISM Scan | Corrupt or missing Windows system files suspected | 15-30 min | Low |
| Windows Memory Diagnostic | MEMORY_MANAGEMENT or random BSODs suggest bad RAM | 10-60 min | Low |
| Driver Rollback / Update | BSOD started after a Windows Update or new hardware install | 5-15 min | Low-Medium |
| Startup Repair (WinRE) | System won't boot past BSOD loop | 10-20 min | Low |
| System Restore | BSOD appeared after a recent change and restore point exists | 20-40 min | Medium |
| RAM Replacement | Memory Diagnostic finds errors, reseating doesn't help | 30-60 min | Medium |
| Clean Windows Install | All other methods fail; hardware tests pass | 1-2 hrs | High (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:
- Note the stop code text (e.g., MEMORY_MANAGEMENT) and any listed 'Failed module' (e.g., ntfs.sys, nvlddmkm.sys).
- 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.
- 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).
- Press
Step 2: Boot into Safe Mode (If BSOD Loops on Startup)
If your system cannot boot normally:
- Force-shutdown the PC 3 times in a row (hold power button) — Windows will enter Automatic Repair mode.
- Click 'Advanced options' → 'Troubleshoot' → 'Advanced options' → 'Startup Settings' → 'Restart'.
- Press F4 for Safe Mode or F5 for Safe Mode with Networking.
- 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:
- Press
Win + R, typemdsched.exe, press Enter. - Choose 'Restart now and check for problems'.
- The tool will run in two passes by default. Press F1 to access extended test options and enable the 'Extended' test for thoroughness.
- 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:
- Press
Win + X→ Device Manager. - Expand the relevant category (e.g., Display adapters, Network adapters).
- Right-click the device → Properties → Driver tab → 'Roll Back Driver'.
To update a driver:
- Right-click the device → 'Update driver' → 'Search automatically for updated driver software'.
- 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:
- Download WinDbg from the Microsoft Store or Windows SDK.
- Open WinDbg → File → Open Crash Dump → navigate to
C:\Windows\Minidump\and open the latest.dmpfile. - In the command window, type:
!analyze -v - 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:
- Back up all important data to an external drive.
- Download the Windows 11 or Windows 10 Media Creation Tool from Microsoft.
- Create a bootable USB drive.
- 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
# ============================================================
# 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.mscError 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
- https://support.microsoft.com/en-us/windows/windows-stop-code-errors-troubleshooting-83d2e3a6-b6e7-4b7e-ba7f-df5c08a5e3d9
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management
- https://learn.microsoft.com/en-us/windows/client-management/windows-10-support-solutions
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc
- https://stackoverflow.com/questions/tagged/bsod
- https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-of-death-memory-management-error/c32c4f9a-a8d5-4b10-8b33-4c7c0a8b9c6e