How to Fix the Memory Management Blue Screen Error
Published 2026-10-16 · Marion Remote Fix
Your computer crashes with a blue screen showing the stop code MEMORY_MANAGEMENT. Windows displays a frowning face emoticon and the message Your PC ran into a problem and needs to restart, with MEMORY_MANAGEMENT as the error code. The crash may happen during specific activities (gaming, video editing, running multiple applications) or seemingly at random. After the restart, Windows may work normally for minutes, hours, or days before crashing again. The MEMORY_MANAGEMENT stop code means Windows detected a severe memory handling error — the system attempted to access memory that was invalid, corrupted, or managed incorrectly. The causes are faulty RAM hardware, corrupted or incompatible drivers, disk errors, virtual memory configuration problems, or software that leaks memory until the system becomes unstable.
Run Windows Memory Diagnostic
The first step is testing the physical RAM in your computer:
- Press Windows Key plus R, type mdsched.exe, press Enter
- Select Restart Now and Check for Problems. The computer will restart and run a memory test before Windows loads
- The test runs in two passes by default. Let it complete — it takes 15 to 45 minutes depending on how much RAM you have. The screen shows a progress bar and reports any errors found
- After the test completes, Windows restarts and shows the results in a notification. If the notification disappears too fast, open Event Viewer (type eventvwr in Start), go to Windows Logs, System, and look for MemoryDiagnostics-Results entries
- If the diagnostic finds errors, you have faulty RAM. The defective module needs to be identified and replaced. See the hardware section below
- If the diagnostic shows no errors, the RAM hardware may still be faulty — the Windows tool is basic. For a more thorough test, use MemTest86 (free) — create a bootable USB and let it run for at least 4 passes
Update drivers
Driver bugs are the second most common cause of MEMORY_MANAGEMENT crashes after RAM issues:
- Display drivers: Graphics card drivers are the single most frequent driver cause of blue screens. Update to the latest driver from NVIDIA (GeForce Experience or nvidia.com), AMD (AMD Software or amd.com), or Intel (intel.com/support). If the crashes started after a driver update, roll back: Device Manager, Display Adapters, right-click the GPU, Properties, Driver tab, Roll Back Driver
- Network drivers: Wi-Fi and Ethernet drivers can cause memory management crashes, especially after Windows updates that change the kernel network stack. Update these from Device Manager or the manufacturer website
- Chipset drivers: Update chipset drivers from Intel or AMD depending on your processor. Chipset drivers manage the communication between the CPU, RAM, and other components. Outdated chipset drivers can mismanage memory allocation
Check disk errors
Disk errors can cause MEMORY_MANAGEMENT crashes because Windows uses disk storage for virtual memory (the page file). If the page file area on disk has corruption, memory operations that use virtual memory fail catastrophically:
- Open Command Prompt as administrator (search CMD, right-click, Run as Administrator)
- Run: chkdsk C: /r — this scans the entire disk for file system errors and bad sectors. It will ask to schedule the scan for the next restart — type Y and restart
- The scan runs during startup before Windows loads. It can take 30 minutes to several hours. Let it complete fully
- After the scan, check the chkdsk results in Event Viewer (Windows Logs, Application, look for Wininit source). If it repaired errors or found bad sectors, the disk corruption may have been causing the blue screens
- If chkdsk finds many bad sectors on a hard drive, the drive is physically failing and should be replaced. An SSD reporting bad sectors is unusual and indicates the drive is near end of life — back up data immediately
Adjust virtual memory
Windows uses a page file on disk as an extension of physical RAM. Incorrect page file settings can cause memory management errors:
- Open System Properties: right-click This PC, Properties, Advanced System Settings
- Under Performance, click Settings, then the Advanced tab, then Change under Virtual Memory
- If Automatically Manage Paging File Size for All Drives is unchecked, custom settings are in use. These may be set incorrectly — either too small (causing out-of-memory conditions under load) or pointing to a drive with errors
- The safest fix: check the Automatically Manage box and click OK. This lets Windows set the page file size based on your RAM and usage patterns. Restart the computer
- If you previously set the page file to zero (No Paging File) to save disk space, this is very likely causing the MEMORY_MANAGEMENT crash. Windows needs a page file even with large amounts of RAM — certain system functions require it. Restore automatic management
- If the page file is on a drive with bad sectors, move it to a healthy drive: uncheck Automatically Manage, select the healthy drive, click System Managed Size, click Set. Then select the bad drive, click No Paging File, click Set
System File Checker and DISM
- Corrupted Windows system files can cause memory management errors when the OS tries to execute corrupted code:
- Open Command Prompt as administrator
- Run: dism /online /cleanup-image /restorehealth — this scans the Windows component store and repairs corruption using Windows Update as a source. Takes 10 to 30 minutes
- After DISM completes, run: sfc /scannow — this scans all protected system files and replaces corrupted ones. Takes 10 to 20 minutes
- If SFC finds and repairs files, restart and monitor for blue screens. If DISM reports it could not find sources for repair, you may need to run it from a Windows installation USB: dism /image:C:\ /cleanup-image /restorehealth /source:D:\sources\install.wim (where D: is the USB drive letter)
Check for software memory leaks
- A memory leak occurs when a program allocates RAM but never releases it, consuming more and more memory over time until the system runs out. This can trigger MEMORY_MANAGEMENT when the leaked memory exhausts available RAM and page file
- Open Task Manager (Ctrl plus Shift plus Escape) and sort the Processes tab by Memory. Watch over time — if a specific application Memory usage continuously grows without leveling off (increasing by hundreds of megabytes or gigabytes over hours), that application has a memory leak
- Common leak sources: web browsers with many tabs and extensions (especially Chrome), antivirus real-time scanners, backup software running continuously, and poorly optimized applications. Restarting the leaking application reclaims the memory
- If the leak is in a system process (svchost.exe, Runtime Broker, etc.), the cause is usually a driver or Windows component bug. Updating Windows and all drivers is the fix
Faulty RAM hardware
If memory diagnostic tools find errors, or if the blue screens continue after all software fixes:
- Identify the bad module: If you have two or more RAM sticks, test them individually. Remove all sticks except one, run the computer and test for stability. Swap to the next stick and repeat. The stick that produces crashes or memory test errors is defective
- Test the slots: A motherboard RAM slot can also be the problem. Test each stick in each slot to determine whether the error follows the stick (bad RAM) or stays in the same slot regardless of which stick is in it (bad slot)
- Check RAM compatibility: Mixing RAM sticks of different speeds, timings, or manufacturers can cause memory management errors even if each stick is individually functional. Check your motherboard QVL (qualified vendor list) on the manufacturer website to confirm your RAM kit is listed as compatible
- XMP profiles: If you enabled an XMP (Extreme Memory Profile) in BIOS to run RAM above its default speed, disable it and test at default speed. XMP overclocks the RAM, and not all RAM and motherboard combinations are stable at XMP speeds. Running at default JEDEC speed eliminates overclocking as a cause
- Reseat the RAM: Power off, remove each RAM stick, clean the gold contacts with a pencil eraser if they look tarnished, and reinsert firmly until both retention clips snap closed. A RAM stick that is not fully seated causes intermittent memory errors
Windows Update
- Install all pending Windows updates: Settings, Windows Update, Check for Updates. Microsoft regularly patches memory management bugs in Windows and in the kernel drivers shipped with Windows. A specific Windows version may have a known MEMORY_MANAGEMENT bug that is fixed in a cumulative update
- If the crashes started immediately after a Windows update, the update itself may be the cause. Go to Settings, Windows Update, Update History, Uninstall Updates, and remove the most recent update. Monitor for stability before allowing the update to install again
BIOS update
- Motherboard BIOS updates frequently include memory compatibility and stability fixes. Check your motherboard manufacturer support page for the latest BIOS version. Read the changelog — entries mentioning memory stability, RAM compatibility, or AGESA updates (for AMD systems) indicate fixes relevant to MEMORY_MANAGEMENT crashes
Memory management crash diagnosis in Marion
If the MEMORY_MANAGEMENT blue screen keeps happening and you cannot identify the cause, Marion Remote Fix can analyze your crash dump files to pinpoint the exact driver or component causing the failure, test memory remotely where possible, walk you through hardware diagnostics, and implement the specific fix to stop the crashes.