What does BSOD stop code MEMORY_MANAGEMENT (0x0000001A) mean on Windows 10?

Stop code 0x0000001A means the Windows kernel detected a severe inconsistency in its memory management subsystem. It can be triggered by defective RAM, corrupt page tables written by a buggy driver, a corrupt Windows system file, a failing SSD/HDD, or memory overclocking instability. The four parameters logged in Event Viewer (BugCheck source) narrow down the exact sub-cause. Parameter 0x41790 indicates PFN list corruption; 0x41284 usually points to a driver overwriting protected memory.

My BSOD shows ntoskrnl.exe as the faulting module — does that mean my CPU or RAM is broken?

Not necessarily. ntoskrnl.exe (the Windows NT OS Kernel) is a common 'catch-all' module in crash dumps because it manages memory on behalf of every driver. When a third-party driver corrupts memory and the kernel later accesses that region, ntoskrnl.exe takes the blame in the dump. Use WinDbg's !analyze -v and examine the full stack trace (!thread, !stack) to find the real originating driver. That said, if MemTest86 flags errors and ntoskrnl.exe is blamed, defective RAM is the likely cause.

How do I fix BSOD PFN_LIST_CORRUPT on Windows 10?

PFN_LIST_CORRUPT (0x0000004E) and MEMORY_MANAGEMENT share root causes and fixes. Start with MemTest86 to test RAM. Then run SFC /scannow and DISM /Online /Cleanup-Image /RestoreHealth. Update or roll back drivers using WinDbg to identify the faulting module. Check the system drive with chkdsk C: /f /r /x. If the BSOD appeared after a Windows Update, uninstall the latest cumulative update from Settings → Update History → Uninstall Updates.

My PC gets BSOD KERNEL_SECURITY_CHECK_FAILURE on Windows 10 — is this the same issue?

KERNEL_SECURITY_CHECK_FAILURE (0x00000139) is a related but distinct stop code. It fires when a kernel-mode data structure fails a security integrity check — most often caused by an incompatible or corrupt driver, a stack-smashing bug, or antivirus software that hooks kernel APIs incorrectly. Run the driver verifier (verifier.exe) to stress-test drivers: open an elevated CMD, type 'verifier', select 'Create standard settings', check all drivers, and reboot. The system will BSOD faster and name the guilty driver. Fix: update the flagged driver or uninstall the offending software.

Windows 10 got a BSOD after a 2022/2023 update and now it loops at boot — how do I recover?

Boot from Windows 10 installation media (USB). At the setup screen choose 'Repair your computer' → Troubleshoot → Advanced Options → Startup Repair. If that fails, choose 'Command Prompt' and run: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows (replace C: with your actual Windows drive letter). Then try: DISM /Image:C:\ /Cleanup-Image /RestoreHealth. To uninstall the bad update offline: dism /Image:C:\ /Get-Packages — find the KB number, then: dism /Image:C:\ /Remove-Package /PackageName: . Reboot normally afterward.

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, and registry repairs.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,219 words

Key Takeaways

Root Cause 1: Faulty or incompatible RAM modules — the most common trigger for stop code 0x0000001A (MEMORY_MANAGEMENT). Bad memory cells corrupt kernel page tables, crashing the OS.
Root Cause 2: Corrupt or outdated drivers (ntoskrnl.exe, nvlddmkm.sys, fltmgr.sys) overwrite protected memory regions, triggering KERNEL_SECURITY_CHECK_FAILURE or PFN_LIST_CORRUPT alongside MEMORY_MANAGEMENT.
Root Cause 3: Corrupted Windows system files or a botched Windows Update can trash the memory manager's data structures, producing stop codes 0x0000001A, 0x0000007E, or UNEXPECTED_KERNEL_MODE_TRAP.
Quick Fix Summary: Run Windows Memory Diagnostic or MemTest86 to rule out hardware faults, update or roll back GPU/chipset drivers, execute SFC /scannow and DISM to repair system files, and check Event Viewer (System log, source BugCheck) for the exact stop code before attempting deeper repairs.

Fix Approaches Compared
Method	When to Use	Time	Risk
Windows Memory Diagnostic	First step when BSOD is random or RAM-related	15–30 min	None
MemTest86 (bootable USB)	Deep RAM validation — multiple passes after WMD flags errors	2–8 hrs	None
SFC /scannow + DISM	System files corrupt after bad Windows Update	20–40 min	Low
Driver rollback / DDU uninstall	BSOD started after GPU or chipset driver update	10–20 min	Low
Update drivers via Device Manager	Outdated ntoskrnl, nvlddmkm.sys, fltmgr.sys suspected	10–30 min	Low
Windows Update rollback	BSOD appeared immediately after a cumulative update	15–30 min	Medium
Reseat / replace RAM stick	MemTest86 confirms hardware errors on a specific slot	5–15 min	Low
System Restore	BSOD is recent and restore points exist	20–40 min	Medium
In-place Upgrade Repair	Persistent BSOD, all software fixes exhausted	1–2 hrs	Medium
Clean Install Windows 10	Hardware confirmed good, OS irreparably corrupt	2–4 hrs	High (data loss)

Understanding the MEMORY_MANAGEMENT BSOD (Stop Code 0x0000001A)

When Windows 10 displays the blue screen message "Your PC ran into a problem and needs to restart. Stop code: MEMORY_MANAGEMENT", it has detected a fatal inconsistency in its own memory manager. The full stop code is 0x0000001A. Unlike many BSODs that stem from a single driver, this one sits at the intersection of hardware integrity, driver correctness, and OS file health — making systematic diagnosis essential.

You may also encounter these closely related stop codes during the same troubleshooting session:

0x0000007A — KERNEL_DATA_INPAGE_ERROR (disk or RAM I/O failure)
0x0000004E — PFN_LIST_CORRUPT (Page Frame Number list damaged)
0x00000139 — KERNEL_SECURITY_CHECK_FAILURE
0x0000007F — UNEXPECTED_KERNEL_MODE_TRAP

All of these can appear alongside or instead of MEMORY_MANAGEMENT depending on which kernel subsystem catches the corruption first.

Phase 1: Collect the Crash Evidence

Before touching any settings, gather forensic data so you fix the right thing.

Step 1.1 — Read Event Viewer

Press Win + X → Event Viewer → Windows Logs → System. Filter by Source = BugCheck. Each BSOD writes an entry here containing the raw stop code and four parameter values, for example:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a
(0x0000000000041790, 0xfffff6fb40000000, 0x000000000000ffff, 0x0000000000000000).

The first parameter (e.g., 0x41790) narrows the sub-cause inside MEMORY_MANAGEMENT. Common sub-codes:

0x41201 — Physical page is corrupt
0x41284 — Page table is corrupt (often a driver bug)
0x41790 — PFN (Page Frame Number) list is corrupt
0x1 — Page pool corruption

Step 1.2 — Analyze the minidump file

Minidumps live at C:\Windows\Minidump\. Install **WinDbg Preview** from the Microsoft Store, then open the most recent .dmp file. Run:

!analyze -v

This prints the faulting module. If it shows ntoskrnl.exe as the culprit, the fault is in the core kernel — RAM or system files. If it shows nvlddmkm.sys (NVIDIA GPU driver), fltmgr.sys (filter manager), or a third-party driver, you have a software target.

Phase 2: Test Your RAM Hardware

Faulty RAM is responsible for the majority of genuine MEMORY_MANAGEMENT crashes. Do not skip this step.

Step 2.1 — Windows Memory Diagnostic (quick test)

Press Win + R, type mdsched.exe, choose Restart now and check for problems. After reboot, results appear in Event Viewer → Windows Logs → System, Source = MemoryDiagnostics-Results.

Step 2.2 — MemTest86 (thorough test)

Download MemTest86 and create a bootable USB. Boot from it and run at least 2 full passes (4+ passes recommended). Any error count > 0 means the RAM stick is defective.

Step 2.3 — Physical reseat

Shut down, disconnect power, open the case. Remove each RAM stick, clean the gold contacts with a dry cloth, and reseat firmly. If you have two sticks, test each slot individually to isolate a bad module or slot.

Phase 3: Repair Windows System Files

Corrupt Windows files — especially those modified by a failed Windows Update — are the second most common cause.

Step 3.1 — SFC scan

Open an elevated Command Prompt (right-click Start → 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.

Step 3.2 — DISM repair

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

After DISM completes, re-run sfc /scannow to confirm repairs.

Step 3.3 — Check disk health

chkdsk C: /f /r /x

Schedule on next reboot. Bad sectors on the OS drive can corrupt the page file and trigger MEMORY_MANAGEMENT.

Phase 4: Fix Driver Issues

nvlddmkm.sys (NVIDIA display driver), fltmgr.sys (Windows Filter Manager), and ntoskrnl.exe are the three most frequently blamed modules in Windows 10 memory BSODs.

Step 4.1 — GPU driver (nvlddmkm.sys / BSOD nvlddmkm sys Windows 10)

Use Display Driver Uninstaller (DDU) in Safe Mode to completely remove the current GPU driver:

Boot into Safe Mode (hold Shift, click Restart → Troubleshoot → Advanced → Startup Settings → 4).
Run DDU, select GPU vendor, click Clean and restart.
After reboot, install the latest WHQL-certified driver from nvidia.com or amd.com.

Step 4.2 — Roll back a recent driver update

Device Manager → expand Display Adapters → right-click GPU → Properties → Driver tab → Roll Back Driver. If greyed out, the previous version is unavailable; use DDU + older known-good installer.

Step 4.3 — fltmgr.sys (BSOD fltmgr sys Windows 10)

fltmgr.sys crashes often stem from third-party antivirus or backup software installing a filesystem filter driver. Check the WinDbg stack trace for the third-party driver name. Uninstall or update the offending security software.

Phase 5: Windows Update Issues

If the BSOD appeared after a Windows Update:

Step 5.1 — Uninstall the problematic update

Settings → Update & Security → View Update History → Uninstall Updates. Sort by Installed On descending and remove the most recent cumulative update (KB number visible). Restart and monitor.

Step 5.2 — Pause updates temporarily

Settings → Windows Update → Advanced Options → Pause Updates (up to 35 days) while investigating.

Phase 6: Recovery Options

System Restore: Settings → Control Panel → Recovery → Open System Restore. Choose a restore point dated before the BSODs began.

Startup Repair: Boot from Windows 10 installation media → Repair your computer → Troubleshoot → Advanced Options → Startup Repair.

In-place Upgrade Repair: From a running Windows 10 (even if intermittently stable), mount the ISO, run setup.exe, choose Keep personal files and apps. This reinstalls core OS components without data loss.

BIOS/UEFI settings: Disable XMP/EXPO memory overclocking profiles in BIOS. Running RAM faster than its rated speed without stability testing is a documented cause of 0x0000001A on Windows 10.

Frequently Asked Questions

powershell

# ============================================================
# Windows 10 BSOD MEMORY_MANAGEMENT Diagnostic & Repair Script
# Run in an elevated PowerShell (Admin) window
# ============================================================

# --- 1. Export last 10 BugCheck events from Event Viewer ---
Write-Host "[*] Fetching BugCheck events from System log..." -ForegroundColor Cyan
Get-WinEvent -LogName System -MaxEvents 500 |
    Where-Object { $_.ProviderName -eq 'BugCheck' } |
    Select-Object TimeCreated, Id, Message |
    Format-List | Out-File "$env:USERPROFILE\Desktop\BugCheck_Events.txt"
Write-Host "[+] Saved to Desktop\BugCheck_Events.txt" -ForegroundColor Green

# --- 2. List minidump files ---
Write-Host "`n[*] Minidump files found:" -ForegroundColor Cyan
$dumpPath = "$env:SystemRoot\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)}} |
        Format-Table -AutoSize
} else {
    Write-Host "[-] No minidump directory found. Enable Small Memory Dump in System Properties." -ForegroundColor Yellow
}

# --- 3. Run System File Checker ---
Write-Host "`n[*] Running SFC /scannow (this may take 10-20 minutes)..." -ForegroundColor Cyan
$sfcResult = sfc /scannow 2>&1
$sfcResult | Tee-Object -FilePath "$env:USERPROFILE\Desktop\SFC_Results.txt"
Write-Host "[+] SFC output saved to Desktop\SFC_Results.txt" -ForegroundColor Green

# --- 4. Run DISM health restore ---
Write-Host "`n[*] Running DISM RestoreHealth..." -ForegroundColor Cyan
DISM /Online /Cleanup-Image /RestoreHealth | Tee-Object -FilePath "$env:USERPROFILE\Desktop\DISM_Results.txt"
Write-Host "[+] DISM output saved to Desktop\DISM_Results.txt" -ForegroundColor Green

# --- 5. Schedule CHKDSK on next reboot ---
Write-Host "`n[*] Scheduling CHKDSK for next reboot..." -ForegroundColor Cyan
echo Y | chkdsk C: /f /r /x
Write-Host "[+] CHKDSK scheduled. It will run on next restart." -ForegroundColor Green

# --- 6. Check RAM slot usage ---
Write-Host "`n[*] Installed RAM information:" -ForegroundColor Cyan
Get-CimInstance Win32_PhysicalMemory | Select-Object BankLabel, Capacity, Speed, Manufacturer, PartNumber |
    ForEach-Object {
        $_.Capacity = [math]::Round($_.Capacity / 1GB, 2)
        $_
    } | Format-Table -AutoSize

# --- 7. List recently installed drivers (last 30 days) ---
Write-Host "`n[*] Drivers installed or updated in the last 30 days:" -ForegroundColor Cyan
$cutoff = (Get-Date).AddDays(-30)
Get-CimInstance Win32_PnPSignedDriver |
    Where-Object { $_.DriverDate -gt $cutoff } |
    Select-Object DeviceName, DriverVersion, DriverDate, Manufacturer |
    Sort-Object DriverDate -Descending |
    Format-Table -AutoSize

# --- 8. Check Windows Update history for recent installs ---
Write-Host "`n[*] Last 10 Windows Updates installed:" -ForegroundColor Cyan
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10 |
    Format-Table HotFixID, Description, InstalledOn -AutoSize

# --- 9. Quick disk health via SMART (requires admin) ---
Write-Host "`n[*] Disk reliability status:" -ForegroundColor Cyan
Get-PhysicalDisk | Select-Object FriendlyName, MediaType, Size, HealthStatus, OperationalStatus |
    Format-Table -AutoSize

# --- 10. Enable Driver Verifier on non-Microsoft drivers (optional, uncomment to use) ---
# WARNING: This will cause BSODs faster to identify bad drivers. Only use in a test scenario.
# verifier /standard /driver $(Get-CimInstance Win32_SystemDriver |
#     Where-Object { $_.PathName -notlike '*\Microsoft\*' -and $_.PathName -notlike '*system32*' } |
#     Select-Object -ExpandProperty Name) 2>&1

Write-Host "`n[DONE] Diagnostics complete. Review files on your Desktop." -ForegroundColor Green
Write-Host "Next steps: Open WinDbg Preview (Microsoft Store) and load the most recent .dmp file." -ForegroundColor Yellow
Write-Host "In WinDbg run: !analyze -v   to identify the faulting driver." -ForegroundColor Yellow

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, Windows SREs, and system administrators with 10+ years of hands-on experience diagnosing kernel crashes, blue screens, and OS-level failures across enterprise and consumer Windows environments. We specialize in translating low-level crash dump analysis into actionable fixes for developers and power users alike.

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.