Error Medic

Blue Screen of Death MEMORY_MANAGEMENT (Stop Code 0x0000001A): Complete Fix Guide

Fix the Blue Screen of Death MEMORY_MANAGEMENT error (0x0000001A) on Windows 10/11 with step-by-step diagnostics, commands, and repair tools. Resolve it today.

Last updated:
Last verified:
2,259 words
Key Takeaways
  • Root cause 1: Faulty or failing RAM modules causing memory corruption — the most common trigger of stop code 0x0000001A (MEMORY_MANAGEMENT).
  • Root cause 2: Corrupt or incompatible device drivers (e.g., nvlddmkm.sys, athrx.sys) writing illegal data to protected memory regions.
  • Root cause 3: Corrupted Windows system files or a bad Windows Update introducing kernel instability and memory management failures.
  • Root cause 4: Overclocked CPU/RAM running outside stable voltage or frequency thresholds, causing intermittent memory faults.
  • Quick fix summary: Run Windows Memory Diagnostic or MemTest86 to rule out hardware failure, then use SFC /scannow and DISM to repair system files, update or roll back drivers, and if all else fails perform a Windows repair install.
Fix Approaches Compared
MethodWhen to UseTimeRisk
Windows Memory DiagnosticFirst step — suspect bad RAM causing MEMORY_MANAGEMENT BSOD15–60 minNone
MemTest86 (bootable)RAM passes Windows test but BSODs continue; need thorough hardware test2–8 hoursNone
SFC /scannow + DISMAfter a failed Windows Update or when system files are suspected corrupt15–30 minVery Low
Driver rollback / updateBSOD started after driver install; nvlddmkm.sys or athrx.sys in dump file10–20 minLow
Check Disk (chkdsk)BSODs occur during disk I/O or after power loss; suspect storage errors30–90 minLow
Windows Startup RepairSystem stuck in BSOD boot loop and cannot reach desktop20–40 minLow
Windows Repair Install (in-place upgrade)Persistent BSOD after all software fixes fail; keep files and apps60–120 minMedium
Full Windows ReinstallHardware confirmed good but OS is beyond repair60–180 minHigh (data loss)
RAM replacementMemTest86 reports errors on specific DIMM slot10–30 minNone (hardware swap)

Understanding the MEMORY_MANAGEMENT Blue Screen of Death

The MEMORY_MANAGEMENT stop code (0x0000001A) is one of Windows' most critical kernel-level errors. When the Windows memory manager detects a fatal violation in its own internal data structures — such as a corrupted page table, a double-free, or a bad pool allocation — it has no choice but to halt the system immediately with this BSOD. You'll see a screen that reads:

Your PC ran into a problem and needs to restart.
Stop code: MEMORY_MANAGEMENT

On older Windows versions, this appears as STOP: 0x0000001A with additional parameters like 0x00041284, 0x00000031, or 0x0000041201 that provide more specific context about the failure type.


Step 1: Capture the Crash Dump and Identify the Cause

Before fixing anything, collect evidence. Windows writes a minidump file to C:\Windows\Minidump\ after every BSOD.

Using Event Viewer:

  1. Press Win + XEvent Viewer.
  2. Navigate to Windows Logs → System.
  3. Filter by Critical events and look for Event ID 41 (Kernel-Power) or 1001 (BugCheck).
  4. The BugCheck event shows the stop code and parameter values.

Using WinDbg (Windows Debugger): Download WinDbg from the Microsoft Store, open the latest .dmp file from C:\Windows\Minidump\, and run:

!analyze -v

Look for the MODULE_NAME and IMAGE_NAME fields — they will point to the offending driver (e.g., nvlddmkm.sys for NVIDIA GPUs or athrx.sys for Atheros Wi-Fi).


Step 2: Test Your RAM Hardware

Physical memory failure is the number-one cause. Run both tests:

Windows Memory Diagnostic (quick):

  1. Press Win + R → type mdsched.exe → Enter.
  2. Choose Restart now and check for problems.
  3. Windows reboots and runs two passes. Results appear after the next login in Event Viewer under Windows Logs → System, source MemoryDiagnostics-Results.

MemTest86 (thorough — recommended):

  1. Download MemTest86 from https://www.memtest86.com/.
  2. Flash it to a USB drive using the included installer.
  3. Boot from the USB and let it run at least 2 full passes (4+ passes for thoroughness).
  4. Any red error = faulty RAM. Swap or reseat DIMMs and test each stick individually.

Reseating RAM: Power off, unplug the PC, press the power button to discharge capacitors, then firmly remove and reinsert each RAM stick. Clean the contacts with isopropyl alcohol if dusty.


Step 3: Repair Windows System Files

Corrupted system files — often caused by a bad Windows Update or an abrupt shutdown — can trigger MEMORY_MANAGEMENT BSODs.

Run SFC (System File Checker): Open an elevated Command Prompt (Win + X → **Windows Terminal (Admin)`) and run:

sfc /scannow

Wait for 100% completion. If it reports "Windows Resource Protection found corrupt files but was unable to fix some of them", proceed to DISM.

Run DISM (Deployment Image Servicing and Management):

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

After DISM completes, run sfc /scannow once more to verify all files are repaired. Reboot.


Step 4: Update or Roll Back Drivers

Driver-induced MEMORY_MANAGEMENT BSODs are extremely common. The crash dump will name the offending .sys file.

Common culprits and fixes:

  • nvlddmkm.sys (NVIDIA GPU): Update or DDU-uninstall the NVIDIA driver and reinstall a clean version from https://www.nvidia.com/drivers.
  • athrx.sys (Atheros Wi-Fi): Update the wireless adapter driver from Device Manager or the manufacturer's site.
  • Generic driver rollback: Open Device Manager (devmgmt.msc), right-click the suspect device, choose Properties → Driver → Roll Back Driver.

Using Display Driver Uninstaller (DDU) for GPU drivers:

  1. Boot into Safe Mode (msconfig → Boot → Safe boot).
  2. Run DDU and select Clean and restart.
  3. Reboot normally and install the latest stable driver.

Step 5: Check the Storage Drive

A failing SSD or HDD can corrupt memory page files, causing cascading MEMORY_MANAGEMENT errors.

Run Check Disk:

chkdsk C: /f /r /x

Schedule it to run on next reboot if the drive is in use. This scans for bad sectors and repairs filesystem errors.

Check drive health with SMART data:

wmic diskdrive get status

Or use CrystalDiskInfo (free) for detailed SMART attribute analysis. A Caution or Bad status means drive replacement is imminent.


Step 6: Disable Overclocking and Check BIOS Settings

If you've overclocked your CPU, GPU, or RAM (XMP/EXPO profiles included), instability at elevated frequencies or voltages frequently manifests as MEMORY_MANAGEMENT BSODs.

  1. Reboot into BIOS/UEFI (usually Del or F2 at POST).
  2. Load Optimized Defaults.
  3. If using XMP/EXPO RAM profiles, disable them temporarily and test at stock JEDEC speeds.
  4. Save and exit. Test for stability.

Step 7: Use Windows Startup Repair (For Boot Loops)

If you're stuck in a BSOD loop and cannot reach the desktop:

  1. Force-shutdown the PC 3 times during boot to trigger Windows Recovery Environment (WinRE).
  2. Go to Troubleshoot → Advanced Options → Startup Repair.
  3. Let Windows attempt automatic repair.

Alternatively, boot from a Windows 10/11 installation USB and choose Repair your computer to access WinRE.


Step 8: Perform a Windows Repair Install (In-Place Upgrade)

If all software fixes fail and hardware tests pass, a repair install replaces all Windows system files while preserving your personal files and installed applications.

  1. Download the Media Creation Tool from https://microsoft.com/software-download/windows11.
  2. Run it and choose Upgrade this PC now.
  3. Select Keep personal files and apps.
  4. Complete the installation. This replaces all core OS files.

BSOD on Non-PC Devices (Android, Samsung, Nintendo Switch, etc.)

Note that many modern devices display "blue screen" style error screens that are not the Windows MEMORY_MANAGEMENT error:

  • Android / Samsung phones (Samsung S21, Motorola): A blue error screen usually indicates a firmware crash or bootloader issue. Factory reset via Recovery Mode or flash stock firmware using Odin (Samsung) or manufacturer tools.
  • Nintendo Switch / Switch Lite: A blue error screen typically means corrupted system software. Hold Power for 12 seconds to force-off, then reboot. If persistent, perform a factory reset from Recovery Mode (hold Vol+ and Power).
  • iPads: Force restart (Vol Up + Vol Down + hold Power) and restore via iTunes/Finder if the issue persists.
  • TVs (Samsung, LG, Sony Bravia, Vizio, Roku): A blue or blank screen usually indicates a signal loss, firmware crash, or HDMI handshake failure — not a true BSOD. Power cycle the TV, check input sources, and update firmware via the TV's settings menu.
  • Ender 3 3D Printer: A "blue screen" on the Ender 3 touchscreen typically indicates a corrupted firmware on the display board. Reflash the display firmware using the manufacturer's SD card procedure.

When to Seek Professional Repair

If MemTest86 confirms RAM failure and replacing the RAM (or reseating it) does not resolve the issue, the memory controller on the CPU or motherboard may be damaged. At this point, professional diagnosis is warranted. Typical repair costs for BSOD diagnosis range from $50–$150 at most repair shops, with hardware replacement costs on top.

Frequently Asked Questions

bash
:: ============================================================
:: MEMORY_MANAGEMENT BSOD Diagnostic & Fix Script (Run as Admin)
:: Compatible with Windows 10 and Windows 11
:: ============================================================

:: Step 1: Check system file integrity
echo [1/7] Running System File Checker...
sfc /scannow

:: Step 2: Repair the Windows image with DISM
echo [2/7] Running DISM health check...
DISM /Online /Cleanup-Image /CheckHealth
echo Running DISM RestoreHealth (requires internet)...
DISM /Online /Cleanup-Image /RestoreHealth

:: Step 3: Schedule Check Disk on next reboot (C: drive)
echo [3/7] Scheduling CHKDSK for next reboot...
echo Y | chkdsk C: /f /r /x

:: Step 4: Export recent BSOD crash events from Event Log
echo [4/7] Exporting BugCheck events to Desktop...
wevtutil qe System /q:"*[System[Provider[@Name='Microsoft-Windows-WER-SystemErrorReporting'] and (EventID=1001)]]" /f:text /rd:true /c:10 > "%USERPROFILE%\Desktop\BSOD_Events.txt"
echo BugCheck events saved to Desktop\BSOD_Events.txt

:: Step 5: List recently installed drivers (sorted by date)
echo [5/7] Listing recently installed drivers...
driverquery /FO TABLE /SI > "%USERPROFILE%\Desktop\Drivers_List.txt"
echo Driver list saved to Desktop\Drivers_List.txt

:: Step 6: Check RAM with Windows Memory Diagnostic
echo [6/7] Launching Windows Memory Diagnostic (will reboot)...
echo ** Close this window if you want to run MemTest86 instead **
timeout /t 10
start mdsched.exe

:: Step 7: Display drive SMART status
echo [7/7] Checking disk SMART health...
wmic diskdrive get Model,Status,Size

:: Step 8: List minidump files for WinDbg analysis
echo.
echo [INFO] Minidump files available for WinDbg analysis:
dir C:\Windows\Minidump\*.dmp /B /O:-D 2>nul || echo No minidump files found.

:: Step 9: Check for pending Windows Updates (PowerShell)
powershell -Command "Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5 | Format-Table HotFixID,InstalledOn,Description"

echo.
echo === Diagnostic complete. Review Desktop output files and reboot. ===
pause
E

Error Medic Editorial

Error Medic Editorial is a team of senior DevOps engineers, SREs, and Windows system administrators with 15+ years of combined experience diagnosing kernel crashes, BSOD stop codes, and system-level failures across enterprise and consumer environments. Our guides are built from real crash dump analysis, Microsoft documentation, and hands-on hardware testing. We cover everything from Windows stop codes and driver failures to firmware issues on embedded devices.

Sources

Related Articles in Other Blue Screen Of Death

Explore More windows Guides