What is the stop code MEMORY_MANAGEMENT in Windows 10?

The stop code MEMORY_MANAGEMENT (0x0000001A) means the Windows kernel detected a critical error in the memory management subsystem. It is triggered by bad RAM, faulty drivers, corrupted page tables, or damaged Windows system files. Check Event Viewer (Event ID 1001) and your minidump files in C:\Windows\Minidump\ to identify the specific sub-code and faulting module.

My BSOD dump shows ntoskrnl.exe — what does that mean?

ntoskrnl.exe is the Windows kernel itself, so seeing it in a crash dump does not always mean the kernel is faulty. It often means the root cause module unloaded before the crash, leaving ntoskrnl.exe holding the stack. Run !analyze -v in WinDbg and look at the full STACK_TEXT section. Faulty RAM, outdated chipset drivers, or overclocked memory are the most common underlying causes when ntoskrnl.exe appears.

How do I fix nvlddmkm.sys BSOD on Windows 10?

nvlddmkm.sys is NVIDIA's kernel-mode graphics driver. To fix it: (1) Boot into Safe Mode, (2) Use Display Driver Uninstaller (DDU) to fully remove the current NVIDIA driver, (3) Download and install the latest stable driver from nvidia.com. If the crash persists after a clean driver install, test your GPU in another PCIe slot or system to rule out hardware failure. Also check that your PSU can supply sufficient wattage to the GPU under load.

Can a Windows 10 update cause a MEMORY_MANAGEMENT BSOD?

Yes. Certain cumulative updates have caused BSOD loops, notably KB5009543 (January 2022) and KB5010793. If your BSOD started immediately after an update, go to Settings → Update & Security → View Update History → Uninstall Updates, find the most recent update, and uninstall it. You can also use System Restore to revert to a pre-update restore point via Advanced Startup Options.

What is PFN_LIST_CORRUPT and how is it related to MEMORY_MANAGEMENT?

PFN_LIST_CORRUPT (stop code 0x0000004E) is a closely related BSOD that specifically indicates corruption in the Page Frame Number database, which Windows uses to track physical memory pages. Like MEMORY_MANAGEMENT, it is most commonly caused by faulty RAM sticks or drivers that write beyond allocated memory buffers. The fix steps are identical: run MemTest86 to test RAM, update drivers, and run SFC/DISM to repair system files.

BSOD MEMORY_MANAGEMENT Windows 10: Stop Code 0x0000001A Fix Guide

Fix BSOD MEMORY_MANAGEMENT (0x0000001A) on Windows 10. Step-by-step guide covering RAM tests, driver fixes, ntoskrnl.exe, nvlddmkm.sys, and registry repairs.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,019 words

Key Takeaways

The MEMORY_MANAGEMENT BSOD (stop code 0x0000001A) is caused by corrupt RAM, faulty drivers (ntoskrnl.exe, nvlddmkm.sys, fltmgr.sys), or damaged Windows system files.
A Windows Update gone wrong, overclocked memory (XMP/DOCP profiles), or a failing SSD/HDD can all trigger this crash loop.
Quick fix path: run 'sfc /scannow' and 'DISM /RestoreHealth' first, then run Windows Memory Diagnostic, update or roll back GPU/chipset drivers, and reseat RAM sticks if software fixes fail.

Fix Approaches Compared
Method	When to Use	Time	Risk
SFC + DISM System File Repair	Corrupted Windows system files, post-update BSOD	10-30 min	Low
Windows Memory Diagnostic / MemTest86	Suspected faulty RAM or PFN_LIST_CORRUPT errors	30 min – 8 hrs	None
Driver Rollback / Update (GPU, Chipset)	BSOD after driver update, nvlddmkm.sys or ntoskrnl.exe in dump	15-30 min	Low
Disable XMP/DOCP in BIOS	Overclocked RAM causing instability	5 min	None
Reseat or Replace RAM	MemTest86 reports errors, multiple sticks installed	15-30 min	Low (static risk)
System Restore / Rollback Update	BSOD started after a specific Windows Update	20-40 min	Medium
Clean Windows 10 Reinstall	All other fixes failed, persistent crash loop	1-2 hrs	High (data loss)

Understanding the MEMORY_MANAGEMENT BSOD Error

When Windows 10 encounters a fatal inconsistency in its memory management subsystem, it throws a Blue Screen of Death with the stop code 0x0000001A and the text MEMORY_MANAGEMENT. You may also see related variants including:

STOP 0x0000001A: MEMORY_MANAGEMENT
Your PC ran into a problem and needs to restart. Stop code: MEMORY MANAGEMENT
PFN_LIST_CORRUPT (0x0000004E)
KERNEL_SECURITY_CHECK_FAILURE (0x00000139)
UNEXPECTED_KERNEL_MODE_TRAP (0x0000007F)

All of these share a common thread: the Windows kernel detected that a critical memory structure was corrupted or accessed illegally. The crash dump file (usually at C:\Windows\Minidump\) will point to the offending module — most commonly ntoskrnl.exe, nvlddmkm.sys (NVIDIA GPU driver), or fltmgr.sys (Filter Manager).

Step 1: Read the Crash Dump in Event Viewer

Before touching anything, pull the diagnostic data.

Press Win + R, type eventvwr.msc, press Enter.
Navigate to Windows Logs → System.
Filter for Event ID 41 (Kernel-Power, unexpected shutdown) and Event ID 1001 (BugCheck).
The BugCheck entry will show the exact stop code and the four parameters, e.g.: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041790, 0xfffff6fb40000000, 0x000000000000ffff, 0x0000000000000000).

The first parameter after the stop code is the sub-code that narrows the root cause:

0x41201 – Page frame number (PFN) database error (bad RAM)
0x41284 – Driver mapped invalid memory
0x41790 – Page table corruption
0x8884 – Driver freed pool memory it did not own

Step 2: Run System File Checker and DISM

Corrupted Windows system files are the most common software-side cause, especially after a bad Windows Update.

Open an elevated Command Prompt (right-click Start → Windows PowerShell (Admin)):

sfc /scannow

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

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

Reboot after DISM completes and monitor for crashes.

Step 3: Test Your RAM with Windows Memory Diagnostic and MemTest86

Faulty physical RAM is responsible for a large percentage of MEMORY_MANAGEMENT BSODs.

Windows Memory Diagnostic (quick test):

Press Win + R, type mdsched.exe, press Enter.
Choose Restart now and check for problems.
The tool will run automatically on reboot. Results appear in Event Viewer under Windows Logs → System with source MemoryDiagnostics-Results.

MemTest86 (thorough test — recommended):

Download MemTest86 from https://www.memtest86.com/ and burn it to a USB drive.
Boot from the USB before Windows loads.
Run a minimum of two full passes (each pass covers all test algorithms). Any errors at all indicate faulty RAM.

If you have two or more RAM sticks, test each stick individually in slot 1 to isolate the faulty module.

Step 4: Disable XMP/DOCP Memory Overclocking

Many modern systems ship with XMP (Intel) or DOCP (AMD) profiles enabled in BIOS, pushing RAM beyond its rated JEDEC specifications. This can cause memory instability without technically being a hardware defect.

Reboot and enter BIOS (usually Delete, F2, or F10 during POST).
Navigate to the AI Tweaker, OC, or Memory section.
Set the XMP/DOCP profile to Disabled or set memory frequency manually to its stock JEDEC speed (typically 2133 or 2400 MHz).
Save and exit.

Monitor for 24-48 hours. If crashes stop, your RAM cannot reliably handle the XMP speed.

Step 5: Update or Roll Back GPU and Chipset Drivers

The file nvlddmkm.sys in a crash dump identifies NVIDIA's kernel-mode GPU driver as the culprit. Similarly, atikmdag.sys points to AMD GPU drivers.

To roll back a driver:

Right-click Start → Device Manager.
Expand Display adapters, right-click your GPU → Properties.
Click the Driver tab → Roll Back Driver.

To update drivers cleanly (NVIDIA):

Download DDU (Display Driver Uninstaller) from https://www.guru3d.com/files-details/display-driver-uninstaller-download.html
Boot into Safe Mode (hold Shift while clicking Restart → Troubleshoot → Advanced options → Startup Settings → Safe Mode).
Run DDU and choose Clean and restart.
After reboot, install the latest stable driver from https://www.nvidia.com/Download/index.aspx

For fltmgr.sys crashes, the Filter Manager is typically called by a third-party antivirus or backup software. Check if a security product update coincided with the BSOD onset and temporarily disable or uninstall it to confirm.

Step 6: Roll Back a Problem Windows Update

If the BSOD started after a Windows Update (a particularly common complaint in 2022 with updates KB5009543 and KB5010793), roll it back:

Press Win + I → Update & Security → View Update History → Uninstall Updates.
Locate the recently installed update (sort by Installed On date).
Right-click and Uninstall.

Alternatively, via Command Prompt:

wusa /uninstall /kb:XXXXXXX /quiet /norestart

Replace XXXXXXX with the KB number shown in update history.

To pause future updates temporarily: Settings → Update & Security → Advanced Options → Pause Updates.

Step 7: Use Startup Repair and Recovery Tools

If Windows fails to boot into the desktop:

Force three hard shutdowns during boot (hold power button) to trigger Automatic Repair mode.
Click Advanced options → Troubleshoot → Advanced options → Startup Repair.
If that fails, choose Command Prompt and run:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
chkdsk C: /f /r /x

The chkdsk command will check for and repair file system errors and bad sectors on your drive, which can also cause memory management faults through corrupted page file activity.

Step 8: Analyze Minidump Files with WinDbg

For advanced diagnosis, use Microsoft's debugging toolkit:

Install WinDbg Preview from the Microsoft Store.
Open WinDbg → File → Open Crash Dump → navigate to C:\Windows\Minidump\ and open the most recent .dmp file.
In the command window, type: !analyze -v
Look for the MODULE_NAME, IMAGE_NAME, and STACK_TEXT fields to identify the exact faulty driver or process.

This output will tell you definitively whether the crash originates from a driver, a hardware fault, or a Windows kernel component.

Frequently Asked Questions

powershell

# ============================================================
# Windows 10 BSOD MEMORY_MANAGEMENT Diagnostic & Fix Script
# Run as Administrator in PowerShell
# ============================================================

# --- Step 1: System File Checker ---
Write-Host "[1/7] Running System File Checker..." -ForegroundColor Cyan
sfc /scannow

# --- Step 2: DISM Image Repair ---
Write-Host "[2/7] Running DISM RestoreHealth..." -ForegroundColor Cyan
DISM /Online /Cleanup-Image /RestoreHealth

# --- Step 3: Check Disk for errors (schedules on next reboot) ---
Write-Host "[3/7] Scheduling CHKDSK on C: at next reboot..." -ForegroundColor Cyan
echo Y | chkdsk C: /f /r

# --- Step 4: Export recent BSOD events from Event Viewer ---
Write-Host "[4/7] Exporting BugCheck events from Event Log..." -ForegroundColor Cyan
$crashEvents = Get-WinEvent -FilterHashtable @{
    LogName   = 'System'
    Id        = 1001
    StartTime = (Get-Date).AddDays(-7)
} -ErrorAction SilentlyContinue

if ($crashEvents) {
    $crashEvents | Select-Object TimeCreated, Message | Format-List
    $crashEvents | Export-Csv -Path "$env:USERPROFILE\Desktop\BugCheck_Events.csv" -NoTypeInformation
    Write-Host "Crash events saved to Desktop\BugCheck_Events.csv" -ForegroundColor Green
} else {
    Write-Host "No BugCheck events found in the last 7 days." -ForegroundColor Yellow
}

# --- Step 5: List minidump files ---
Write-Host "[5/7] Listing minidump files..." -ForegroundColor Cyan
$dumpPath = "$env:SystemRoot\Minidump"
if (Test-Path $dumpPath) {
    Get-ChildItem -Path $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. Small Memory Dump may not be configured." -ForegroundColor Yellow
    Write-Host "Configuring system to save minidumps..." -ForegroundColor Yellow
    # Enable small memory dumps
    Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl' -Name 'CrashDumpEnabled' -Value 3
    Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\CrashControl' -Name 'MinidumpDir' -Value '%SystemRoot%\Minidump'
    Write-Host "Minidump collection enabled. A dump will be saved on the next BSOD." -ForegroundColor Green
}

# --- Step 6: Check RAM configuration and speed ---
Write-Host "[6/7] Checking installed RAM modules..." -ForegroundColor Cyan
Get-CimInstance Win32_PhysicalMemory | Select-Object `
    @{N='Slot';E={$_.DeviceLocator}}, `
    @{N='CapacityGB';E={[math]::Round($_.Capacity/1GB,2)}}, `
    @{N='SpeedMHz';E={$_.Speed}}, `
    Manufacturer, PartNumber, SerialNumber

# --- Step 7: List top drivers by date (find old/unsigned drivers) ---
Write-Host "[7/7] Listing kernel drivers (oldest first -- suspect outdated drivers)..." -ForegroundColor Cyan
Get-WmiObject Win32_SystemDriver | Where-Object {$_.State -eq 'Running'} | `
    Sort-Object @{Expression={$_.PathName}} | `
    Select-Object Name, State, PathName | `
    Format-Table -AutoSize

# --- Bonus: Verify Page File settings ---
Write-Host "`n[BONUS] Page File Configuration:" -ForegroundColor Magenta
Get-CimInstance Win32_PageFileSetting | Select-Object Name, InitialSize, MaximumSize

Write-Host "`n=== Diagnostic complete. Review output above and BugCheck_Events.csv on your Desktop. ===" -ForegroundColor Green
Write-Host "Next steps: Run MemTest86 for RAM, and use WinDbg to open .dmp files for driver analysis." -ForegroundColor Green

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, Windows systems administrators, and SRE professionals with over 15 years of combined experience diagnosing kernel panics, Blue Screens of Death, and system-level failures across enterprise Windows environments. Our guides are built from real incident postmortems, Microsoft documentation, and hands-on lab testing. We don't just quote fixes — we verify them.

Sources

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.