Error Medic

BSOD MEMORY_MANAGEMENT (0x0000001A) & Related Stop Codes: Complete Troubleshooting Guide

Fix BSOD MEMORY_MANAGEMENT (0x0000001A) and related stop codes on Windows 10/11. Step-by-step diagnosis with commands, driver fixes, and RAM repair tools.

Last updated:
Last verified:
2,561 words
Key Takeaways
  • The MEMORY_MANAGEMENT BSOD (stop code 0x0000001A) is almost always triggered by faulty RAM, corrupted drivers, overclocked memory, or damaged system files — not software bugs alone.
  • Related stop codes like 0x0000007E, 0x000000D1 (IRQL), 0x00000116 (GPU driver), 0xC000021A, BAD_POOL_CALLER, PFN_LIST_CORRUPT, and KERNEL_SECURITY_CHECK_FAILURE often share the same root causes: memory corruption, driver conflicts, or hardware failure.
  • Quick fix path: Run Windows Memory Diagnostic or MemTest86 to rule out bad RAM, then use SFC /scannow and DISM to repair system files, update or rollback suspect drivers (ntoskrnl.exe, nvlddmkm.sys, atikmdag.sys), and check Event Viewer for the faulting module before reinstalling Windows as a last resort.
Fix Approaches Compared
MethodWhen to UseTimeRisk
Windows Memory Diagnostic (mdsched.exe)First step — suspect RAM after crash10–30 minLow
MemTest86 (bootable USB)Thorough RAM test when mdsched fails to catch errors2–8 hoursLow
SFC /scannow + DISM RestoreHealthCorrupted system files, post-Windows-Update BSODs15–45 minLow
Driver rollback or update (Device Manager)BSOD after driver/Windows update, GPU or NIC-related stop codes5–15 minLow-Medium
DDU (Display Driver Uninstaller) + clean reinstallnvlddmkm.sys, atikmdag.sys, atikmpag.sys, 0x00000116 BSODs20–40 minLow
XMP/DOCP profile disable in BIOSBSOD after RAM upgrade, overclocked memory instability5 minLow
Reseat / replace RAM stickMemTest86 errors on specific slot or stick10–20 minLow
System Restore / Windows ResetAll software fixes exhausted, BSODs persist30–120 minMedium-High
Chkdsk /f /rBSOD NTFS.sys, Unmountable Boot Volume, hard-drive-related codes30–90 minMedium

Understanding BSOD MEMORY_MANAGEMENT and Related Stop Codes

A Blue Screen of Death (BSOD) with stop code MEMORY_MANAGEMENT (0x0000001A) means the Windows kernel detected a fatal violation of memory management integrity. This is a broad catch-all that can stem from physical RAM defects, corrupt page tables, misbehaving kernel-mode drivers, or damaged NTFS metadata. Dozens of related stop codes share these root causes:

  • 0x0000001A — MEMORY_MANAGEMENT (direct memory subsystem fault)
  • 0x0000007E — SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (driver exception in kernel)
  • 0x000000D1 — DRIVER_IRQL_NOT_LESS_OR_EQUAL (driver accesses invalid memory address at elevated IRQL)
  • 0x00000116 / 0x00000133 — VIDEO_TDR_FAILURE / DPC_WATCHDOG_VIOLATION (GPU driver hang)
  • 0x00000139 — KERNEL_SECURITY_CHECK_FAILURE (stack corruption, often a driver or malware)
  • 0xC000021A — STATUS_SYSTEM_PROCESS_TERMINATED (critical user-mode process like winlogon or csrss crashed)
  • BAD_POOL_CALLER / BAD_POOL_HEADER — Driver or app wrote outside its allocated pool
  • PFN_LIST_CORRUPT — Page Frame Number list is corrupted, almost always bad RAM or a driver bug
  • APC_INDEX_MISMATCH — Kernel APC state mismatch, often a third-party driver or antivirus (Avira, Kaspersky, McAfee, Sophos, CrowdStrike) conflict
  • 0x000000F4 — CRITICAL_OBJECT_TERMINATION (usually a failing hard drive or SSD)

Common faulting modules you will see in crash dumps or Event Viewer: ntoskrnl.exe, ntkrnlmp.exe, nvlddmkm.sys (NVIDIA GPU), atikmdag.sys / atikmpag.sys (AMD GPU), amdkmpfd.sys, amdppm.sys, dxgkrnl.sys, dxgmms1.sys, dxgmms2.sys, netio.sys, tcpip.sys, ndis.sys, ndu.sys, ntfs.sys, fltmgr.sys, win32k.sys, win32kbase.sys, win32kfull.sys, wdf01000.sys, usbxhci.sys, storport.sys, acpi.sys, intelppm.sys, igdkmd64.sys, ksecdd.sys, mouclass.sys, lvuvc64.sys (Logitech webcam), hardlock.sys (Sentinel dongle driver).

Step 1: Collect Crash Dump Information

Use Event Viewer first:

  1. Press Win + R, type eventvwr.msc, press Enter.
  2. Navigate to Windows Logs → System.
  3. Filter by Event ID 41 (Kernel-Power — unexpected shutdown) and 1001 (BugCheck — BSOD details).
  4. The BugCheck event shows the stop code and the faulting module path.

Read minidump files with WinDbg: Minidumps are saved in C:\Windows\Minidump\. Install WinDbg from the Microsoft Store or Windows SDK, then run:

windbg -z C:\Windows\Minidump\<filename>.dmp

In WinDbg type !analyze -v to get the full analysis including the faulting driver and stack trace.

Free alternative — WhoCrashed or BlueScreenView: Both tools read minidumps without needing WinDbg expertise and display the faulting driver name plainly.

Step 2: Test Your RAM

Before touching drivers or reinstalling Windows, eliminate physical RAM as the cause. Bad RAM causes the majority of MEMORY_MANAGEMENT, PFN_LIST_CORRUPT, and BAD_POOL_HEADER crashes.

Quick test (Windows built-in):

  1. Press Win + R, type mdsched.exe, press Enter.
  2. Choose Restart now and check for problems.
  3. Windows runs two passes. If errors appear, proceed to MemTest86.

Thorough test (MemTest86):

  1. Download MemTest86 from memtest86.com and create a bootable USB.
  2. Boot from USB and run at least 2 full passes (4+ passes recommended).
  3. Any errors indicate defective RAM. Isolate by testing one stick at a time in different slots.

If you recently upgraded RAM:

  • Enter BIOS/UEFI and disable XMP / DOCP / EXPO profiles to run RAM at stock JEDEC speeds.
  • Confirm the RAM is on your motherboard's QVL (Qualified Vendor List).
  • Try each stick individually to find a faulty module.

Step 3: Repair Windows System Files

Corrupted system files (especially after a Windows Update gone wrong) cause MEMORY_MANAGEMENT, 0xC000021A, BAD_SYSTEM_CONFIG_INFO, and CRITICAL_PROCESS_DIED.

Run these commands as Administrator in sequence:

# Step 3a: Check and repair system files
sfc /scannow

# Step 3b: If SFC reports unrepairable corruption, use DISM to restore the Windows image
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# Step 3c: Run SFC again after DISM completes
sfc /scannow

# Step 3d: Check disk for errors (schedule for next reboot if C: is in use)
chkdsk C: /f /r /x

Reboot after each stage. If chkdsk finds and fixes errors, run MemTest86 next — a corrupting drive often means a failing SSD/HDD controller.

Step 4: Identify and Fix the Faulting Driver

Once you have the faulting module name from Event Viewer or a dump analysis, apply the targeted fix:

GPU drivers (nvlddmkm.sys, atikmdag.sys, atikmpag.sys, 0x00000116, dxgkrnl.sys):

  1. Boot into Safe Mode (hold Shift while clicking Restart → Troubleshoot → Advanced Options → Startup Settings → Safe Mode with Networking).
  2. Download Display Driver Uninstaller (DDU) from wagnardsoft.com.
  3. Run DDU in Safe Mode to completely remove the GPU driver.
  4. Download the latest stable driver directly from nvidia.com or amd.com.
  5. Install with a clean install option checked.

Network drivers (netio.sys, tcpip.sys, ndis.sys, ndu.sys, netwtw10.sys):

  • Update your NIC/Wi-Fi adapter driver from Device Manager or manufacturer site.
  • For ndu.sys (Network Diagnostics): disable via Registry — set HKLM\SYSTEM\CurrentControlSet\Services\Ndu\Start to 4 (disabled).

Antivirus-caused BSODs (Avira, Kaspersky, McAfee, Sophos, Norton, CrowdStrike, Carbon Black): Security software kernel drivers (mini-filters, hypervisor hooks) frequently cause APC_INDEX_MISMATCH, KERNEL_SECURITY_CHECK_FAILURE, and SYSTEM_SERVICE_EXCEPTION. Boot into Safe Mode, uninstall the security product using its dedicated removal tool (e.g., ESET Uninstall Tool, Kaspersky Kavremover), then reinstall the latest version.

For CrowdStrike (which caused a massive global outage in July 2024):

  1. Boot into Safe Mode or Windows Recovery Environment.
  2. Delete C:\Windows\System32\drivers\CrowdStrike\C-00000291*.sys.
  3. Reboot normally.

USB/Storage drivers (usbxhci.sys, storport.sys, iastora.sys):

  • Update chipset drivers from your motherboard manufacturer (Intel, AMD).
  • Disable USB selective suspend in Power Options.
  • For iastora.sys (Intel RST): update Intel Rapid Storage Technology driver from intel.com.

Driver Verifier — for finding the true culprit: If the dump points to ntoskrnl.exe but no specific driver, enable Driver Verifier to stress-test all third-party drivers:

verifier /standard /all

This forces a BSOD the moment a driver misbehaves, and the crash dump will then clearly name the guilty driver. Only run this temporarily and disable it after finding the culprit:

verifier /reset

Step 5: BIOS/UEFI and Hardware Checks

  • Update BIOS firmware — especially on Alienware, Razer Blade, Surface, and Samsung laptops where vendor firmware updates patch memory controller bugs.
  • Check CPU temperatures — overheating causes random BSODs. Use HWiNFO64 or Core Temp. Thermal paste replacement may be needed.
  • Reseat GPU and RAM — physical connection issues cause intermittent crashes, especially during gaming (BSOD while gaming scenarios).
  • Test with integrated graphics — remove discrete GPU temporarily to rule out GPU hardware failure (0x00000116 persisting after clean driver install = suspect GPU hardware).
  • Check PSU — an underpowered or failing PSU causes random BSODs under load, especially after adding new hardware.

Step 6: Advanced Recovery Options

System Restore: If BSODs started after a specific update or software install, roll back:

  1. Boot to Windows Recovery Environment (WinRE): hold Shift + Restart.
  2. Navigate to Troubleshoot → Advanced Options → System Restore.
  3. Choose a restore point dated before the BSODs began.

Startup Repair (for 0xC000021A, Unmountable Boot Volume, 0xC0000098):

  1. Boot from Windows installation media (USB).
  2. Select Repair your computer → Troubleshoot → Startup Repair.

Reset this PC (last resort before reinstall):

  • Settings → System → Recovery → Reset this PC → Keep my files.
  • This reinstalls Windows while preserving personal data but removes all apps and drivers.

Platform-Specific Notes

  • Windows 11 BSODs: Many users report increased BSOD frequency after upgrading. Ensure all drivers are Windows 11 certified. Check for incompatible apps with Get-AppxPackage and remove legacy kernel-mode drivers.
  • Virtual Machine BSODs (VMware, Hyper-V): Usually caused by incompatible VMware Tools version. Update VMware Tools to match your hypervisor version. Nested virtualization conflicts can also trigger 0x000000D1.
  • Gaming BSODs (Valorant EAC, Lost Ark, Xbox Game Pass): Anti-cheat drivers (EasyAntiCheat, Battleye, Vanguard) are kernel-mode and can conflict with other kernel drivers. Update games to latest version; ensure Windows is fully updated.
  • Nintendo Switch BSOD: The Switch has a distinct blue error screen (not Windows). Recovery involves holding Power for 15 seconds to force reboot, then initiating factory initialization from recovery menu if it persists.

Frequently Asked Questions

powershell
# ============================================================
# BSOD MEMORY_MANAGEMENT Diagnostic & Repair Script
# Run as Administrator in PowerShell
# ============================================================

Write-Host "=== Step 1: Check recent BSODs from Event Log ==" -ForegroundColor Cyan
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001} -MaxEvents 10 |
  Select-Object TimeCreated, Message |
  Format-List

Write-Host "`n=== Step 2: List minidump files ==" -ForegroundColor Cyan
$dumpPath = "C:\Windows\Minidump"
if (Test-Path $dumpPath) {
    Get-ChildItem $dumpPath -Filter "*.dmp" | Sort-Object LastWriteTime -Descending |
      Select-Object Name, LastWriteTime, @{N='SizeMB';E={[math]::Round($_.Length/1MB,2)}}
} else {
    Write-Host "No minidump folder found. Enable small memory dumps:" -ForegroundColor Yellow
    Write-Host "  SystemPropertiesAdvanced -> Startup and Recovery -> Small memory dump (256 KB)"
}

Write-Host "`n=== Step 3: Check RAM for errors (quick test) ==" -ForegroundColor Cyan
Write-Host "Scheduling Windows Memory Diagnostic on next reboot..."
# Uncomment the line below to actually schedule the test:
# Start-Process -FilePath "mdsched.exe" -ArgumentList "/schedule" -Wait
Write-Host "Run manually: Win+R -> mdsched.exe -> Restart now and check for problems"

Write-Host "`n=== Step 4: Scan and repair system files ==" -ForegroundColor Cyan
Write-Host "Running SFC /scannow (this may take 10-20 minutes)..."
sfc /scannow

Write-Host "`n=== Step 5: Repair Windows image with DISM ==" -ForegroundColor Cyan
Write-Host "Running DISM CheckHealth..."
DISM /Online /Cleanup-Image /CheckHealth
Write-Host "Running DISM RestoreHealth (requires internet connection)..."
DISM /Online /Cleanup-Image /RestoreHealth

Write-Host "`n=== Step 6: Check disk for errors ==" -ForegroundColor Cyan
Write-Host "Scheduling chkdsk on C: for next reboot..."
# Uncomment to schedule:
# chkdsk C: /f /r /x
Write-Host "Run manually (elevated CMD): chkdsk C: /f /r"

Write-Host "`n=== Step 7: Check for problematic drivers ==" -ForegroundColor Cyan
Get-WinEvent -FilterHashtable @{LogName='System'; Level=2} -MaxEvents 20 |
  Where-Object { $_.Message -like '*driver*' -or $_.Message -like '*.sys*' } |
  Select-Object TimeCreated, Message |
  Format-List

Write-Host "`n=== Step 8: List third-party kernel drivers (potential BSOD sources) ==" -ForegroundColor Cyan
Get-WmiObject Win32_SystemDriver |
  Where-Object { $_.PathName -notlike '*\system32\*' -and $_.State -eq 'Running' } |
  Select-Object DisplayName, PathName, State |
  Sort-Object DisplayName |
  Format-Table -AutoSize

Write-Host "`n=== Step 9: Check page file configuration ==" -ForegroundColor Cyan
Get-WmiObject Win32_PageFileSetting | Select-Object Name, InitialSize, MaximumSize

Write-Host "`n=== Step 10: Disable Driver Verifier if previously enabled ==" -ForegroundColor Cyan
Write-Host "To ENABLE Driver Verifier (find bad driver): verifier /standard /all"
Write-Host "To DISABLE Driver Verifier after testing:   verifier /reset"
Write-Host "Current Driver Verifier status:"
verifier /query 2>$null

Write-Host "`n=== BSOD Diagnostic Complete ==" -ForegroundColor Green
Write-Host "Next steps:"
Write-Host "  1. If SFC/DISM found and fixed errors -> Reboot and monitor"
Write-Host "  2. If no errors found -> Run MemTest86 from bootable USB (memtest86.com)"
Write-Host "  3. Check Event Viewer (eventvwr.msc) -> Windows Logs -> System -> BugCheck events"
Write-Host "  4. Open latest .dmp file in WinDbg and run: !analyze -v"
Write-Host "  5. Update or rollback the driver identified in the crash dump"
E

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, Windows system architects, and SRE professionals with a combined 40+ years of experience diagnosing kernel panics, crash dumps, and system failures across enterprise and consumer Windows environments. Every troubleshooting guide is validated against real crash dumps and lab-reproduced error conditions before publication.

Sources

Related Articles in Other Bsod

BSOD Memory Management (0x0000001A): Complete Fix Guide for Windows 10 & 11
Fix BSOD MEMORY_MANAGEMENT (0x0000001A) on Windows 10/11. Step-by-step diagnosis with MemTest86, SFC, DISM, and driver rollback commands included.
BSOD Memory Management Error: Complete Troubleshooting Guide for Windows 10 & 11 (Stop Code: MEMORY_MANAGEMENT)
Fix BSOD MEMORY_MANAGEMENT stop code errors on Windows 10/11. Step-by-step guide with real commands to diagnose RAM, drivers, and disk issues fast.
BSOD MEMORY_MANAGEMENT (Stop Code 0x0000001A): Complete Fix Guide for Windows 10 & 11
Fix BSOD MEMORY_MANAGEMENT errors (0x0000001A) on Windows 10/11. Step-by-step diagnosis with MemTest86, SFC, DISM, and driver rollback commands.

Explore More windows Guides

Acer Aspire Blue Screen of Death Fix: How to Stop BSOD Crashes on Acer Laptops
Fix Acer Aspire Blue Screen of Death errors fast. Step-by-step guide covering driver updates, RAM checks, overheating, and Windows repair commands.
Acer Aspire Blue Screen of Death Fix: Step-by-Step Troubleshooting Guide (BSOD Errors Solved)
Fix Acer Aspire blue screen of death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK and more. Step-by-step commands included.
Acer Aspire Blue Screen of Death Fix: Stop Codes, Causes & Complete Solutions
Fix Acer Aspire Blue Screen of Death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK_FAILURE & more with exact commands.