Microsoft Windows Stop Code Errors: Complete Troubleshooting Guide (Including MEMORY_MANAGEMENT Fix)

Understanding Microsoft Windows Stop Code Errors

A Windows Stop Code — commonly called a Blue Screen of Death (BSOD) — appears when the Windows kernel encounters a condition so severe it cannot safely continue running. Microsoft surfaces these at https://www.microsoft.com/en-us/windows/stop-code and through the Windows Error Reporting portal. The blue screen displays a human-readable stop code name (e.g., MEMORY_MANAGEMENT) alongside a hexadecimal code (e.g., 0x0000001A) and, when available, the name of the offending driver or module.

Common Stop Codes and What They Mean

• MEMORY_MANAGEMENT (0x0000001A) — A severe memory management error; most often faulty RAM, corrupt page file, or a driver accessing invalid memory addresses.
• PAGE_FAULT_IN_NONPAGED_AREA (0x00000050) — System tried to access memory that doesn't exist; linked to bad RAM, corrupt drivers, or antivirus conflicts.
• IRQL_NOT_LESS_OR_EQUAL (0x0000000A) — A driver attempted to access memory at an illegal IRQL; almost always a driver bug.
• SYSTEM_SERVICE_EXCEPTION (0x0000003B) — An exception occurred while executing a routine that transitions from non-privileged to privileged code.
• CRITICAL_PROCESS_DIED (0x000000EF) — A critical system process (e.g., lsass.exe, csrss.exe) terminated unexpectedly.
• DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1) — Network or storage driver accessing paged memory at elevated IRQL.
• KERNEL_SECURITY_CHECK_FAILURE (0x00000139) — Data structure corruption detected; often caused by overclocking or faulty RAM.

Step 1: Read the Stop Code and Gather Information

When a BSOD occurs, Windows briefly displays the stop code before rebooting. If the system reboots too quickly:

1. Disable automatic restart on failure:

   • Right-click This PC → Properties → Advanced system settings → Startup and Recovery → Settings.
   • Uncheck Automatically restart under System failure.
   • Click OK.

2. Check Event Viewer for crash details:

   • Press Win + R, type eventvwr.msc, press Enter.
   • Navigate to Windows Logs → System.
   • Filter by Critical and Error events around the crash time.
   • Look for Event ID 41 (unexpected shutdown) and Event ID 1001 (BugCheck).
   • The BugCheck event contains the exact stop code and parameters.

3. Read the minidump file:

   • Minidumps are stored at C:\Windows\Minidump\.
   • Use WinDbg (Windows Debugger, available from Microsoft Store or Windows SDK) to analyze them.
   • After opening WinDbg, run: !analyze -v to get a full analysis of the most recent dump.

Step 2: Run System File Checker and DISM

Corrupt Windows system files are a frequent but easily overlooked cause of stop code errors.

Open an elevated Command Prompt (Run as Administrator) and execute:

sfc /scannow

Wait for the scan to complete (it may take 10–20 minutes). If it reports violations that it could not fix, run DISM to repair the Windows component store:

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

After DISM completes, run sfc /scannow a second time and then reboot.

Step 3: Test Your RAM

For MEMORY_MANAGEMENT and related stop codes, RAM is the primary suspect.

Using Windows Memory Diagnostic (quick test):

1. Press Win + R, type mdsched.exe, press Enter.
2. Choose Restart now and check for problems.
3. The tool runs automatically on reboot and reports errors in Event Viewer under Windows Logs → System (search for source MemoryDiagnostics-Results).

Using MemTest86 (thorough test — recommended):

1. Download MemTest86 from https://www.memtest86.com/.
2. Create a bootable USB using the provided image tool.
3. Boot from the USB and let it run for at least two full passes (ideally overnight).
4. Any errors reported indicate faulty RAM. Note which slot/module fails.
5. Remove and replace the failing module. Test each stick individually to isolate the bad one.

Step 4: Update, Rollback, or Remove Problematic Drivers

Driver bugs are responsible for a large percentage of stop codes. Use the following approach:

1. Identify the faulting driver from WinDbg output — look for lines like Probably caused by: nvlddmkm.sys (NVIDIA display driver) or ntoskrnl.exe.
2. Update drivers via Device Manager:
   • Press Win + X → Device Manager.
   • Right-click suspect devices (especially Display Adapters, Network Adapters, Storage Controllers) → Update driver.
3. Roll back a recently updated driver:
   • In Device Manager, right-click the device → Properties → Driver tab → Roll Back Driver.
4. Use DDU (Display Driver Uninstaller) for GPU driver issues — boot into Safe Mode and run DDU to completely remove the current GPU driver before installing a fresh copy.

Step 5: Reset the Virtual Memory / Page File

A corrupted or misconfigured page file can cause MEMORY_MANAGEMENT crashes.

1. Right-click This PC → Properties → Advanced system settings.
2. Under Performance, click Settings → Advanced tab → Change (under Virtual memory).
3. Check Automatically manage paging file size for all drives.
4. Click OK and restart.

Alternatively, to delete and recreate the page file:

1. Uncheck automatic management, select No paging file, click Set, and reboot.
2. After reboot, re-enable automatic management and reboot again.

Step 6: Check for Overheating and Hardware Issues

Thermal throttling and hardware faults can cause intermittent stop codes:

• Use HWMonitor or Core Temp to check CPU and GPU temperatures under load.
• Inspect Event Viewer for WHEA (Windows Hardware Error Architecture) events — Event Source: WHEA-Logger, Event ID: 17 or 18 indicate hardware errors.
• Run chkdsk on the system drive to rule out storage issues:

  chkdsk C: /f /r /x
  

  (Schedule for next reboot if drive is in use.)

Step 7: Perform a Clean Boot to Isolate Software Conflicts

1. Press Win + R, type msconfig, press Enter.
2. On the Services tab, check Hide all Microsoft services, then click Disable all.
3. On the Startup tab, open Task Manager and disable all startup items.
4. Click OK and restart.
5. If the BSOD stops, re-enable services/startup items in batches to find the culprit.

Step 8: Use Startup Repair or System Restore (Last Resort Before Reinstall)

1. Boot from Windows installation media (USB or DVD).
2. Select Repair your computer → Troubleshoot → Startup Repair.
3. If Startup Repair fails, try System Restore to revert to a known-good restore point.
4. As a final option before clean install, use Reset this PC (keep files option available) from Settings → System → Recovery.