Getting Bluescreen from MEMORY_MANAGEMENT ntoskrnl.exe

The MEMORY_MANAGEMENT blue screen with ntoskrnl.exe indicates a severe memory management error. Even if Windows Memory Diagnostic and sfc /scannow show no issues, this type of bug check is commonly related to:

• Faulty or marginal RAM or memory slots
• Other hardware problems (CPU, motherboard)
• Faulty or incompatible drivers corrupting memory

For a home Windows 11 system without access to kernel debugging tools, use the supported troubleshooting paths:

1. Remove or roll back recent changes
   • If any new hardware (RAM sticks, expansion cards, USB devices) was added around the time the BSODs started, shut down the PC, physically remove that hardware, and test again.
   • If any new device drivers or system utilities were installed or updated (chipset, GPU, storage, antivirus, tuning/overclock tools), uninstall or roll back them and test.
2. Boot in Safe Mode and observe
   • Start Windows 11 in Safe Mode (see “Start your PC in safe mode in Windows 10/11” from the basic troubleshooting steps).
   • Use the PC in Safe Mode for a while. If BSODs stop in Safe Mode, that strongly suggests a third‑party driver or software is corrupting memory.
3. Check Device Manager for driver issues
   • Right‑click Start → Device Manager.
   • Look for any devices with an exclamation mark (!).
   • For any such device, choose Update driver. If that does not help, disable or uninstall the device and test.
4. Run a deeper hardware check
   • Run Windows Memory Diagnostics again, but choose the extended test (press F1 at startup of the tool, set Test Mix to Extended, then F10). Let it complete fully.
   • If any memory errors are reported, test with one RAM module at a time and/or different motherboard slots to isolate a bad stick or slot.
   • If RAM passes but MEMORY_MANAGEMENT persists, consider other hardware: CPU or motherboard can also cause memory corruption, as shown in similar cases where replacing a faulty CPU or updating BIOS resolved BSODs.
5. Check Event Viewer around the crash time
   • Press Win+R → eventvwr.msc → Enter.
   • Under Windows Logs → System, look for critical or error events that occur at the same time as the blue screens. These may point to a specific driver or device.
6. General bug check troubleshooting
   • Ensure all Windows Updates are installed (Settings → Windows Update → Check for updates).
   • Confirm there is sufficient free disk space (at least 10–15%) on the system drive so Windows can manage paging and crash dumps correctly.
   • If overclocking (CPU, RAM, GPU, XMP/DOCP profiles) is enabled, return all settings to default and test.
7. If the problem continues
   • Follow the general bug check guidance: remove or update any recently added drivers or services, run hardware diagnostics from the system or motherboard vendor, and verify hardware compatibility with the installed Windows version.
   • If repeated MEMORY_MANAGEMENT bug checks persist after all driver and hardware checks, consider a hardware RMA path (RAM, motherboard, or CPU), as similar cases have been resolved only by replacing faulty components.

If none of the above resolves the issue, use the standard Windows recovery options (such as System Restore or a repair install) as a last software step, but given the nature of MEMORY_MANAGEMENT, focus primarily on RAM and other hardware.

References:

• Bug Check 0x1A: MEMORY_MANAGEMENT
• Bug checks (stop code errors)
• Troubleshooting Windows unexpected restarts and stop code errors
• Bug Check 0x154: UNEXPECTED_STORE_EXCEPTION
• Constant BSOD - Microsoft Q&A
• Trying to figure out this Windows Error Reporting 1001 event (Event Name: Bluescreen) - Microsoft Q&A
• Kernel_Security_Error BSOD. Driver Verifier causing bootloop. - Microsoft Q&A
• BSODs caused by ntkrnlmp.exe - Microsoft Q&A