Ad Space — Top Banner

MEMORY_MANAGEMENT

Microsoft Windows

Severity: Critical

Source: OnlyErrorCodes.com — Every error code. One place.

Windows MEMORY_MANAGEMENT BSOD — Stop Code 0x1A Fix

What it means

Windows BSOD 'MEMORY_MANAGEMENT' is the bug check with stop code 0x0000001A, documented on Microsoft Learn at learn.microsoft.com/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management.
Microsoft's exact description: 'a severe memory management error occurred.'
Parameter 1 of the bug check tells the specific violation — the !analyze -v command in WinDbg decodes it precisely.
Most common real-world causes: failing RAM, a buggy driver that wrote to memory it shouldn't have, or a corrupted page file.
Unlike CRITICAL_PROCESS_DIED, MEMORY_MANAGEMENT genuinely does point at RAM hardware in a meaningful percentage of cases.

Affected Models

  • Windows 11 (every version)
  • Windows 10 (every version)
  • Windows Server 2016 / 2019 / 2022 / 2025
  • Common after RAM upgrade, BIOS update, or driver update that changed memory behaviour
  • Same Microsoft fix sequence applies across all versions

Common Causes

  • Failing RAM module — the most likely hardware cause (test with Memory Diagnostic or MemTest86)
  • Buggy device driver writing to invalid memory addresses
  • Page file corrupt or sized too small for current workload
  • Overclocked RAM running outside stable frequency or timings
  • Failing power supply causing memory access errors

How to Fix It

  1. Run Windows Memory Diagnostic.

    Press Win+R, type mdsched.exe, Enter.
    Choose 'Restart now and check for problems'.
    The system reboots into the diagnostic tool.
    The basic scan takes 10-15 minutes; press F1 in the tool to switch to Extended mode for a more thorough 30-60 minute scan.
    Results appear in the system log after Windows boots back — type 'Event Viewer' in Start > Windows Logs > System > look for MemoryDiagnostics-Results events.

  2. Run MemTest86 for a deeper RAM check.

    Windows Memory Diagnostic is decent but MemTest86 (from memtest.org) is more thorough.
    Make a bootable USB on another PC, boot the failing PC from it, let MemTest86 run for at least 4 hours (or overnight).
    Any errors at all mean RAM is faulty — try one stick at a time to identify which is bad, or contact your RAM manufacturer for warranty replacement.
    RAM modules usually have a lifetime warranty.

  3. Disable RAM overclocking / XMP profiles in BIOS.

    If you have XMP or EXPO enabled in BIOS (the profile that runs RAM at advertised speeds like DDR4-3600 or DDR5-6000), MEMORY_MANAGEMENT BSODs sometimes appear because the system isn't actually stable at those timings.
    Enter BIOS during boot, find the XMP/EXPO setting, set it to Disabled.
    The RAM runs at the slower JEDEC default but with rock-solid stability.
    If the BSODs stop, the XMP profile is too aggressive for your specific RAM kit — try a slower XMP profile or manual timings.

  4. Run System File Checker and DISM RestoreHealth.

    Open Command Prompt as Administrator:
    sfc /scannow
    DISM /Online /Cleanup-Image /RestoreHealth
    If either reports and repairs corruption, restart.
    Corrupt system files can cause MEMORY_MANAGEMENT when the kernel memory routines themselves are damaged.

  5. Identify the bad driver with Driver Verifier.

    If RAM tests clean and the BSOD persists, a driver is writing to invalid memory.
    In normal mode, run: verifier.exe
    Choose 'Create standard settings' > 'Automatically select unsigned drivers' > Finish > restart.
    The system runs with extra driver checks and BSODs again pointing at the specific bad driver.
    Note the driver name from the BSOD, then in Safe Mode run: verifier.exe /reset.
    Uninstall the named driver.

  6. Reset or expand the page file.

    If the page file (swap) is too small or corrupt, MEMORY_MANAGEMENT can fire when Windows tries to swap.
    Open System Properties > Advanced tab > Performance Settings > Advanced > Virtual memory > Change.
    Untick 'Automatically manage paging file size'.
    Select your C: drive, choose 'System managed size' (or Custom with at least 1x your RAM as initial and 2x as maximum).
    OK, restart.
    This rebuilds the page file with fresh sizing.

When to Call a Professional

MEMORY_MANAGEMENT genuinely can be a RAM hardware fault, more often than other BSODs.
Always run Windows Memory Diagnostic or MemTest86 early in the troubleshooting sequence.
If RAM tests clean, a driver is the next suspect — Driver Verifier and Reliability Monitor will identify it.
If you recently overclocked the RAM or applied XMP/EXPO timings in BIOS, reset to defaults — unstable RAM timings cause MEMORY_MANAGEMENT bug checks that look exactly like hardware faults but are actually a settings issue.

Frequently Asked Questions

Should I just replace my RAM if Windows Memory Diagnostic finds errors?

Yes — but try a few things first.
Re-seat the RAM modules: power off, unplug, open the case, take RAM out, blow dust out of the slots, push the modules back in firmly until both clips click.
Sometimes RAM 'errors' are actually a marginal contact in the slot, not a bad module.
If re-seating doesn't help and errors persist, test each stick individually — that tells you which specific stick is bad.
Most RAM has a lifetime warranty (Corsair, G.Skill, Crucial all do); RMA the bad stick to the manufacturer for free replacement instead of buying new.