Why do I keep getting BSOD MEMORY_MANAGEMENT after a RAM upgrade?

After a RAM upgrade, MEMORY_MANAGEMENT BSODs almost always mean incompatibility or improper configuration. First, reseat the new RAM firmly. Test each stick individually with MemTest86. If using XMP/EXPO profiles in BIOS, disable them and run at default JEDEC speeds to test stability. Check your motherboard's QVL (Qualified Vendor List) — not all RAM kits work with all motherboards even if the specs match. Mixed RAM brands or different-generation kits in dual-channel mode are a common culprit. If errors appear in MemTest86, the RAM is faulty or truly incompatible — return it.

How do I find which driver is causing my BSOD in Windows 10 or 11?

Open Event Viewer (eventvwr.msc), go to Windows Logs → System, and filter for Event ID 1001 (BugCheck). The event details will often name the faulting module. For deeper analysis, navigate to C:\Windows\Minidump\ and open the most recent .dmp file in WinDbg — run '!analyze -v' to get the full call stack and faulting driver. The free tool WhoCrashed can parse minidumps in plain English without needing WinDbg expertise. The BSOD QR code on Windows 11 also links to Microsoft's stop code documentation for the specific error.

Can antivirus software like CrowdStrike, Avira, or Kaspersky cause BSOD?

Yes — antivirus and endpoint security tools run kernel-mode drivers that can cause BSODs if they conflict with Windows updates, GPU drivers, or each other. The high-profile CrowdStrike BSOD incident in July 2024 demonstrated this at global scale. If your BSOD started after installing or updating security software, boot into Safe Mode (which prevents most third-party kernel drivers from loading) and uninstall the security tool. Common culprits include CrowdStrike Falcon sensor, Carbon Black, Sophos, McAfee, Avira, and Norton. After removal, test stability before reinstalling. Always run only one real-time antivirus product at a time.

What does BSOD stop code 0xC000021A mean and how do I fix it?

Stop code 0xC000021A (STATUS_SYSTEM_PROCESS_TERMINATED) means a critical Windows system process — either winlogon.exe or csrss.exe — crashed fatally. This is commonly caused by corrupt system files (ntoskrnl.exe, win32k.sys, smss.exe), a failed Windows Update, or malware. Fix steps: (1) Boot from a Windows USB drive, open Recovery → Command Prompt. (2) Run 'sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows' to repair files offline. (3) If that fails, run 'DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim' where D: is your Windows installation USB. (4) Try System Restore to a point before the issue started.

Why do I get a BSOD only while gaming but not during normal use?

Gaming-only BSODs point to GPU driver issues, overheating, or RAM instability under load. At idle, these problems don't manifest because the system isn't stressing the GPU, VRAM, or thermal envelope. Diagnostic steps: (1) Monitor GPU and CPU temperatures with HWiNFO64 or MSI Afterburner while gaming — temperatures above 90°C (GPU) or 95°C (CPU) indicate thermal throttling. (2) Note the exact stop code — nvlddmkm.sys or dxgkrnl.sys BSODs are GPU driver-related; clean reinstall with DDU. (3) Run MemTest86 for 4+ hours to rule out RAM. (4) Try running the game at lower graphics settings or lower GPU clock speeds using MSI Afterburner to confirm thermal/power causes. (5) Check GPU power connectors are fully seated.

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.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,523 words

Key Takeaways

Root cause #1 — Faulty or incompatible RAM: Physical memory errors, bad RAM sticks, or an incompatible RAM upgrade trigger the MEMORY_MANAGEMENT stop code (0x0000001A) by corrupting kernel-level page tables.
Root cause #2 — Corrupt or outdated drivers: GPU drivers (nvlddmkm.sys, atikmdag.sys, amdkmpfd.sys), storage drivers (iastora.sys, storport.sys), and network drivers (netio.sys, ndis.sys) frequently cause memory corruption leading to BSODs.
Root cause #3 — Corrupt Windows system files or bad Windows Update: A failed or partial Windows Update can corrupt ntoskrnl.exe, win32kbase.sys, or other kernel components, producing memory management crashes.
Root cause #4 — Overheating or hardware failure: Thermal throttling, a failing hard drive, or a defective GPU (0x00000116, nvlddmkm.sys) can manifest as memory management BSODs under load or while gaming.
Quick fix summary: Run Windows Memory Diagnostic or MemTest86 to test RAM, execute SFC /scannow and DISM to repair system files, update or roll back suspect drivers using Event Viewer BSOD logs, and verify RAM seating and compatibility after any RAM upgrade.

BSOD Memory Management Fix Approaches Compared
Method	When to Use	Time Required	Risk Level
Windows Memory Diagnostic / MemTest86	First step after any memory-related BSOD, especially after RAM upgrade	30 min – 8 hrs	None
SFC /scannow + DISM	After Windows Update BSOD or corrupt system files (ntoskrnl.exe, win32k.sys)	15–30 min	None
Driver rollback / update (DDU clean install)	GPU/driver BSODs: nvlddmkm.sys, atikmdag.sys, amdkmpfd.sys, dxgkrnl.sys	20–45 min	Low
Check Event Viewer & analyze minidump	Identify exact failing driver or module before making changes	10–20 min	None
Reseat or replace RAM / test sticks individually	After RAM upgrade BSOD or MemTest86 errors found	15–30 min	Low
System Restore or Rollback Windows Update	BSOD started after a specific Windows Update or software install	20–40 min	Low
Startup Repair / Bootrec (unmountable boot volume)	Cannot boot into Windows at all (0xc0000098, 0xc0000185, unmountable boot volume)	20–60 min	Medium
Full Windows Reset or Reinstall	All other methods failed, persistent BSOD on every boot	1–3 hrs	High (data loss risk)

Understanding BSOD Memory Management (0x0000001A)

The MEMORY_MANAGEMENT Blue Screen of Death (stop code 0x0000001A) is one of the most common — and misunderstood — Windows crashes. The error message you see on screen will read:

Your PC ran into a problem and needs to restart.
STOP CODE: MEMORY_MANAGEMENT

or in older Windows versions:

STOP: 0x0000001A (parameter1, parameter2, parameter3, parameter4)

Despite its name, this BSOD is not always caused by RAM. It means the Windows kernel encountered a fatal inconsistency in its own memory management subsystem — which can be triggered by bad RAM, corrupt drivers, corrupt system files, or even a failing storage device. Related stop codes you may encounter include 0x0000003B (SYSTEM_SERVICE_EXCEPTION), 0x0000007A (KERNEL_DATA_INPAGE_ERROR), 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL), 0x00000139 (KERNEL_SECURITY_CHECK_FAILURE), and 0xC000021A (STATUS_SYSTEM_PROCESS_TERMINATED).

Step 1: Read the BSOD and Collect Crash Data

Before touching any settings, collect diagnostic data. Every BSOD writes a minidump file to C:\Windows\Minidump\ and logs an event in Windows Event Viewer.

Find BSODs in Event Viewer:

Press Win + R, type eventvwr.msc, press Enter.
Navigate to Windows Logs → System.
Filter by Event ID 41 (unexpected shutdown) and 1001 (BugCheck).
The BugCheck event will show the stop code and faulting module (e.g., ntoskrnl.exe, nvlddmkm.sys).

Read minidump files with WinDbg: Download WinDbg from the Microsoft Store or Windows SDK. Open a .dmp file from C:\Windows\Minidump\ and run !analyze -v to get the exact faulting driver and stack trace.

The QR code on modern Windows 11 BSODs links to Microsoft's stop code documentation — scan it or note the stop code before your PC reboots.

Step 2: Test Your RAM

This is the most critical step for MEMORY_MANAGEMENT, BAD_POOL_HEADER, BAD_POOL_CALLER, PFN_LIST_CORRUPT, and BSOD after RAM upgrade scenarios.

Windows Memory Diagnostic (quick test):

Press Win + R, type mdsched.exe, press Enter.
Choose Restart now and check for problems.
Results appear in Event Viewer under Windows Logs → System (Event ID 1201).

MemTest86 (thorough — recommended):

Download MemTest86 from memtest86.com.
Flash to a USB drive and boot from it.
Run a minimum of 2 full passes (ideally overnight). Any errors = replace or reseat that RAM stick.

If you recently upgraded RAM: Remove the new stick and test with the original configuration. Test each stick individually in slot 1. Check your motherboard's QVL (Qualified Vendor List) for compatibility. Enable XMP/EXPO profile in BIOS only after confirming stability at default speeds.

Step 3: Run SFC and DISM to Repair System Files

If the BSOD is caused by corrupt Windows files — common after a failed Windows Update, a crash during patching, or malware — System File Checker and DISM can restore them.

Open Command Prompt as Administrator and run the following commands in order:

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

Restart after each command completes. If SFC reports it could not fix some files, run DISM first to restore the component store, then run SFC again.

Step 4: Update or Roll Back Drivers

Driver-caused BSODs are extremely common. The most frequent offenders are:

GPU drivers: nvlddmkm.sys (NVIDIA), atikmdag.sys / atikmpag.sys / amdkmpfd.sys (AMD), dxgkrnl.sys, dxgmms1.sys, dxgmms2.sys
CPU drivers: intelppm.sys, amdppm.sys
Network drivers: netio.sys, ndis.sys, ndu.sys, tcpip.sys, netwtw10.sys
Storage drivers: iastora.sys, storport.sys
USB/HID: usbxhci.sys, mouclass.sys, hdaudbus.sys
Security software: Avira, Kaspersky, McAfee, Norton, Sophos, CrowdStrike Falcon (falcon sensor), Carbon Black — antivirus kernel drivers are a frequent hidden cause

Clean GPU driver reinstall using DDU:

Download Display Driver Uninstaller (DDU) from guru3d.com.
Boot into Safe Mode (msconfig → Boot → Safe boot).
Run DDU, select your GPU vendor, choose Clean and restart.
After restart, install the latest stable driver from NVIDIA.com or AMD.com.

Roll back a driver:

Open Device Manager (devmgmt.msc).
Right-click the suspect device → Properties → Driver tab → Roll Back Driver.

Check for third-party driver conflicts: Run verifier /query in an elevated prompt to see if Driver Verifier is active. To enable Driver Verifier for testing (will cause deliberate BSODs if a bad driver is found), run verifier /standard /all and reboot.

Step 5: Address Specific Stop Codes

0x0000007A (KERNEL_DATA_INPAGE_ERROR): Usually indicates a failing hard drive or SSD. Run chkdsk C: /f /r /x from an elevated prompt. Check SMART data with CrystalDiskInfo.

0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL): A driver accessed memory at an improper IRQL. Check Event Viewer for the faulting driver name.

0x00000116 / nvlddmkm.sys / atikmdag.sys: GPU timeout — clean reinstall GPU drivers, check GPU temperatures with GPU-Z or HWiNFO64, reseat GPU, test with integrated graphics.

0x0000009F (DRIVER_POWER_STATE_FAILURE): Power management driver conflict. Run powercfg /energy and check the report.

0xC000021A / 0xC0000001 (Fatal System Error): Critical Windows process (winlogon.exe or csrss.exe) failed. Boot from Windows installation media, open Recovery Console, and run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows.

0xC0000098 / 0xC0000185 / Unmountable Boot Volume: BCD or boot partition corruption. Boot from Windows USB, choose Repair → Command Prompt, then run bootrec /fixmbr, bootrec /fixboot, bootrec /rebuildbcd.

APC_INDEX_MISMATCH / DPC_WATCHDOG_VIOLATION: Often caused by antivirus software, NVMe firmware issues, or audio drivers. Update audio drivers (hdaudbus.sys) and NVMe firmware.

0x0000003B (SYSTEM_SERVICE_EXCEPTION): Check for win32k.sys, win32kbase.sys, win32kfull.sys faults — usually a GPU driver or display driver issue.

Step 6: Check Hardware and Thermals

BSODs that occur under gaming load (BSOD while gaming, BSOD memory management while gaming) are often thermal. Use HWiNFO64 or MSI Afterburner to monitor:

CPU temperature (should stay below 95°C)
GPU temperature (below 90°C)
GPU VRAM temperature (below 95°C)

For Alienware, Razer Blade, Surface, and Samsung laptops — clean vents, repaste the CPU/GPU if the machine is over 2 years old. Thermal throttling under load can corrupt in-flight memory operations.

Test storage health:

chkdsk C: /f /r
wmic diskdrive get status

Step 7: Recovery When You Cannot Boot

If Windows won't start at all:

Boot from a Windows 10/11 USB installation drive.
Select Repair your computer → Troubleshoot → Advanced Options → Startup Repair.
If Startup Repair fails, use Command Prompt and run SFC offline or bootrec commands.
Use System Restore if a restore point exists prior to when BSODs started.

For persistent BSODs after all steps, Reset this PC (keeping or removing files) is the nuclear option. Back up data first using a Linux live USB if Windows won't boot.

Tools and Software Recommendations

WinDbg — Microsoft's official crash dump analyzer (free, Microsoft Store)
WhoCrashed — Beginner-friendly minidump reader (free, resplendence.com)
MemTest86 — Gold standard RAM tester (free, memtest86.com)
CrystalDiskInfo — Hard drive/SSD SMART health (free)
DDU (Display Driver Uninstaller) — Clean GPU driver removal (free)
HWiNFO64 — Real-time hardware sensor monitoring (free)
Autoruns — Find third-party drivers and services loading at boot (free, Microsoft Sysinternals)

Avoid paid "BSOD fixer" or "BSOD repair software" tools marketed online — they provide no value beyond what Windows built-in tools already offer, and some are scareware.

Frequently Asked Questions

powershell

# ============================================================
# BSOD MEMORY_MANAGEMENT DIAGNOSTIC & FIX SCRIPT
# Run PowerShell as Administrator
# ============================================================

# --- 1. View recent BSODs from Event Viewer ---
Write-Host "=== Recent BSOD Events (last 7 days) ==="
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001; StartTime=(Get-Date).AddDays(-7)} |
  Where-Object {$_.Message -like '*BugCheck*'} |
  Select-Object TimeCreated, Message |
  Format-List

# --- 2. List all minidump files ---
Write-Host "`n=== Minidump Files ==="
Get-ChildItem -Path "$env:SystemRoot\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue |
  Sort-Object LastWriteTime -Descending |
  Select-Object Name, LastWriteTime, Length |
  Format-Table -AutoSize

# --- 3. Run System File Checker ---
Write-Host "`n=== Running SFC (this may take 10-15 minutes) ==="
sfc /scannow

# --- 4. Run DISM to repair Windows image ---
Write-Host "`n=== Running DISM Health Check ==="
DISM /Online /Cleanup-Image /CheckHealth
Write-Host "`n=== Running DISM Restore (requires internet) ==="
DISM /Online /Cleanup-Image /RestoreHealth

# --- 5. Check disk health via SMART ---
Write-Host "`n=== Disk SMART Status ==="
Get-WmiObject -Class Win32_DiskDrive | Select-Object Model, Status, MediaType | Format-Table -AutoSize

# --- 6. Schedule CHKDSK on next boot ---
Write-Host "`n=== Scheduling CHKDSK on next reboot ==="
cmd /c "echo y | chkdsk C: /f /r /x"
# Note: CHKDSK will run on next restart

# --- 7. Export list of installed drivers ---
Write-Host "`n=== Non-Microsoft Kernel Drivers Currently Loaded ==="
Get-WmiObject Win32_SystemDriver |
  Where-Object {$_.State -eq 'Running' -and $_.PathName -notlike '*\Windows\System32\*'} |
  Select-Object Name, PathName, State |
  Format-Table -AutoSize

# --- 8. Check for recently installed drivers/updates ---
Write-Host "`n=== Windows Updates Installed in Last 30 Days ==="
Get-HotFix | Where-Object {$_.InstalledOn -gt (Get-Date).AddDays(-30)} |
  Select-Object HotFixID, Description, InstalledOn |
  Sort-Object InstalledOn -Descending |
  Format-Table -AutoSize

# --- 9. Launch Windows Memory Diagnostic ---
Write-Host "`n=== Launching Windows Memory Diagnostic (will require reboot) ==="
$response = Read-Host "Run Windows Memory Diagnostic now? (y/n)"
if ($response -eq 'y') {
  mdsched.exe
}

# --- 10. Enable Driver Verifier (WARNING: will cause deliberate BSODs if bad driver found) ---
# Uncomment only if you want to identify a specific bad driver:
# Write-Host "`n=== Enabling Driver Verifier (standard settings) ==="
# verifier /standard /all
# Write-Host "Driver Verifier enabled. Reboot to activate. Run 'verifier /reset' to disable."

# --- 11. Disable Driver Verifier (run this after testing to turn it off) ---
# verifier /reset

Write-Host "`n=== Diagnostic Complete. Review output above. ==="
Write-Host "For GPU driver issues, download DDU from guru3d.com and clean-reinstall drivers in Safe Mode."
Write-Host "For deep minidump analysis, open WinDbg from Microsoft Store and run '!analyze -v'."

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Windows systems administrators with 10+ years of experience diagnosing kernel-level crashes, BSOD stop codes, and Windows internals. Our guides are based on hands-on troubleshooting of real-world environments — from gaming rigs to enterprise endpoints — and cross-referenced with official Microsoft documentation, Sysinternals tooling, and community-verified fixes. We do not recommend paid 'BSOD fixer' software and always prioritize free, first-party diagnostic tools.

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.