MEMORY_MANAGEMENT (bug check 0x1A) means Windows’ memory manager hit a severe error: usually its own bookkeeping (page tables, page frame lists or working sets) no longer adds up, and sometimes a driver asked it to do something illegal. The causes and fixes for a memory management BSOD are the same on Windows 11 and Windows 10; on Windows 11 version 24H2 and later the crash screen may be black instead of blue, with the same stop code at the bottom.
Microsoft’s reference lists dozens of variants, and the first parameter tells you which one you hit. That makes this code easier than most: several values are ones Microsoft flags as probably hardware, a few point at a driver misusing memory, and one points at the page file on your drive. Read it before you buy RAM or reinstall anything.
If you can’t get the parameter, use the pattern. MEMORY_MANAGEMENT mixed with other codes, such as PAGE_FAULT_IN_NONPAGED_AREA or IRQL_NOT_LESS_OR_EQUAL, at random times usually means RAM or memory settings. The same code with the same driver in every dump points to software.
Try these first
- Find Parameter 1 in Reliability Monitor’s crash details and match it in the table below to see whether RAM, a driver or the drive is the suspect.
- If you recently added RAM, remove the new module and see whether the crashes stop.
- If XMP/EXPO or another memory overclock is on (common on custom and gaming desktops), turn it off in the BIOS and retest.
- If every dump names the same third-party driver, update or roll back that driver.
- Run Windows Memory Diagnostic (mdsched.exe) with the Extended test; it can take hours, so start it when you can leave the PC.
Read parameter 1 first
In Reliability Monitor, open the crash’s technical details (problem event name BlueScreen) and read Parameter 1. Windows shows it without the 0x or leading zeros, for example 41790. In WinDbg it’s Arg1; our blue screen of death guide shows both methods. These are the values most worth knowing from Microsoft’s much longer list.
| Parameter 1 | What it means | Where to look |
|---|---|---|
| 0x403 | Page tables and page frame numbers are out of sync. Microsoft says this is probably hardware, especially if parameters 3 and 4 differ by a single bit. | RAM |
| 0x31 | A loaded image’s relocation table or code is corrupted; Microsoft says probably hardware. | RAM, then storage |
| 0x41790 | A page table page is corrupted. | RAM first, then a driver writing into memory it doesn’t own |
| 0x41792 | A corrupted page table entry was detected. | RAM first, then drivers |
| 0x61941 | The paging hierarchy is corrupted. | RAM or driver: test RAM, then look for a repeating module |
| 0x3F | A page read back from the page file failed its checksum. | The drive holding the page file, then RAM |
| 0x1233, 0x1236, 0x1240 | A driver mapped or described memory pages that weren’t locked or resident. | Driver bug: find the module in the dump |
| 0x5305, 0x41286 | Code tried to free an invalid memory pool address. | Driver bug |
| 0x5003 (older Windows) | The working set free list is corrupted; probably hardware. | RAM |
The one-bit test
For 0x403, open Calculator in Programmer view, select HEX, enter parameter 3, choose XOR from Bitwise, enter parameter 4 and press equals. If the result is a single power of two (1, 2, 4, 8, 10, 20, 40, 80 and so on in hex), exactly one bit differs, the classic signature of a bad memory cell.
Test the RAM after a 0x1A crash
- Save your work, then run
mdsched.exe(or search Windows Memory Diagnostic) and choose Restart now and check for problems (recommended). - When the test screen appears, press F1, set Test Mix to Extended (press Tab to move between settings), raise the Pass Count if you can leave it running, and press F10 to apply.
- After Windows starts, the result appears as a notification. If you miss it, open Event Viewer > Windows Logs > System and filter by the source MemoryDiagnostics-Results.
Microsoft has been testing a Windows 11 prompt that offers a quick memory scan at the next restart after a crash. If you see it, accept it, but at about five minutes it’s a first look, not a substitute for the Extended test.
Read the result honestly. If XMP/EXPO or another memory overclock was on during the test, turn it off and test again before buying anything, because an unstable profile can make good memory report errors. A single error at default settings means a module or slot is bad (occasionally the board).
A clean pass doesn’t fully clear the RAM, because intermittent faults can take many passes or a warm machine to show up. A longer bootable tester such as MemTest86, run overnight, is the stronger test.
Find the bad module
On PCs with removable memory, shut down and unplug the PC first, then test one module at a time in the slot your PC or motherboard manual recommends for a single module, keeping that slot the same for each test. If every module passes alone but errors return in one particular slot, the slot or board is the problem.
Laptops vary. Many thin models have all their memory soldered to the board, and some combine soldered memory with one removable slot. On those, remove the slotted module and test again: if the errors stop, replace only that module. If errors continue with the slot empty, or all the memory is soldered, the PC maker’s diagnostics (Dell SupportAssist, HP PC Hardware Diagnostics, Lenovo Diagnostics) confirm the fault, and the fix is a board repair under warranty or service.
If it crashes at startup or before you can sign in
When 0x1A hits during startup or within minutes of signing in, the Windows-based checks above may not be available. Work through these instead, quickest first.
- Undo memory changes. If the crashes began after you enabled XMP/EXPO or changed memory settings, turn them back off in the BIOS/UEFI setup. On a desktop, also remove any module you just added.
- Try Safe Mode. Windows opens its recovery environment by itself after two failed starts in a row. There, choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 or F4. Safe Mode loads a minimal set of drivers, so if the PC stays up there, roll back or remove the suspect driver; if it crashes even in Safe Mode, hardware becomes the likelier cause. If the PC keeps returning to the repair screen instead, follow our automatic repair loop guide.
- Test memory without Windows. On another PC, put a bootable memory tester such as MemTest86 on a USB drive, then start the crashing PC from it. It runs before Windows loads, so drivers and a damaged Windows install can’t affect the result.
A crash or spontaneous restart inside the bootable tester points to hardware, because none of your installed drivers are running there.
Memory settings: XMP, EXPO and mixed kits
XMP (Intel) and EXPO (AMD) profiles run memory faster than its default standard speed. Most kits handle it, but an unstable profile is a frequent reason a desktop throws 0x1A along with other memory-related codes. Turn the profile off in the BIOS/UEFI setup (menu names vary by board maker) and use the PC for a few days. If the crashes stop, leave it off or pick a lower speed.
Mixed memory is the other trap. Microsoft’s guidance for unexplained restarts is to verify that all memory modules run at the same speed and are configured correctly. Modules added years apart, from different brands or with different timings, can fail together even when each passes on its own. The PC maker’s support site lists compatible memory for your model.
A BIOS update from your PC or board maker can also improve memory compatibility, but a failed or interrupted update can leave the PC unable to start. Back up your files first, install only the update listed for your exact model, keep a laptop plugged in, and don’t restart or power off while it runs. Suspend BitLocker first so the update doesn’t trigger a recovery prompt, and check that protection is back on afterward; see where your BitLocker recovery key is kept.
Rather have a technician sort it out?
With your approval, a technician can connect remotely, read parameter 1 from your crash dumps, check drivers, the drive and the page file, and tell you whether RAM, a driver or the disk is the most likely cause. A GoProIT technician can connect remotely, with your permission, and fix it while you watch. $59 per fix, Mon–Fri 8am–8pm ET.
When it’s a driver, not the RAM
Suspect software when parameter 1 is one of the driver values above, memory tests pass at default settings, and the same third-party module appears in every dump. The usual suspects are kernel drivers that manage memory heavily: graphics drivers (NVIDIA’s is nvlddmkm.sys), virtualization and emulator software, security agents, and disk caching or RAM disk utilities.
- Update or reinstall the named driver from the PC or device maker, or roll it back if the crashes started after an update.
- Uninstall virtualization, caching or “memory optimizer” tools you don’t need.
- If no driver repeats, Driver Verifier with Special Pool can catch a driver writing into memory it doesn’t own. Microsoft warns that it can crash the computer and says to run it only on test machines, so on a work PC back up first and know how to turn it off:
verifier /resetand a restart (from Safe Mode if the PC crashes at startup, since Verifier doesn’t run there). The Driver Verifier section of the blue screen of death guide linked above has the full steps.
If your crashes alternate between 0x1A and 0xA, our IRQL_NOT_LESS_OR_EQUAL guide shows how to separate a driver’s bad pointer from memory corruption.
The page file side: parameter 0x3F and disk errors
With 0x3F, data Windows wrote to the page file came back different when it was read. The page file lives on your system drive by default, so a failing SSD, a loose connection or file system errors can cause it, and so can RAM that corrupted the data before it was written.
- Run
chkdsk C: /scanin an administrator terminal, and check the drive’s health withGet-PhysicalDiskin PowerShell or the drive maker’s tool. - Reset the page file to defaults: System Properties > Advanced > Performance Settings > Advanced > Virtual memory Change, then tick Automatically manage paging file size for all drives, select OK, and restart when Windows asks.
- Don’t disable the page file to make the crash go away. Windows writes crash dumps through it by default, so without one you lose the evidence for the next crash.
Match the symptom to the cause
| Symptom | Likely cause | Next step |
|---|---|---|
| Crashes began after adding or swapping RAM | New module faulty or mismatched | Remove it and retest; replace with a matched kit |
| Crashes stop with XMP/EXPO off | Unstable memory profile | Leave it off or lower the speed |
| Memory test reports errors at default settings | Bad module or slot | Test modules one at a time; replace the faulty part |
| Tests pass; same driver in every dump | That driver | Update, roll back or uninstall it |
| Parameter 1 = 0x3F, slow disk or chkdsk errors | Drive or page file | Back up, check drive health, reset the page file |
| Many different stop codes, random restarts, heat | RAM, power or overheating | Memory test, then check cooling and the power supply |
| PC freezes solid with no blue screen and no new dump | A hang, heat or power problem rather than a bug check | Follow our guide to a computer that keeps freezing |
| Desktop with a 13th or 14th Gen Intel Core processor, mixed stop codes | Possibly the instability Intel has confirmed in some 13th and 14th Gen desktop chips | Install the maker’s latest BIOS (back up and suspend BitLocker first); our clock watchdog timeout guide covers Intel’s current microcode and warranty guidance |
When it’s hardware, and when to stop
Bad memory doesn’t only crash Windows. It can silently damage files as they’re saved and corrupt the system files Windows depends on. Once a test shows errors, stop editing important documents on that PC until the RAM is replaced, and check that your backups were taken before the crashes started.
Once replacement memory is in and the PC has run a day without crashes, repair any Windows files the bad RAM damaged: run DISM /Online /Cleanup-Image /RestoreHealth and then sfc /scannow in an administrator terminal. Running them earlier is wasted effort, because they don’t fix the crash and faulty RAM can corrupt their results. Then open recently saved documents and spreadsheets, and restore any damaged file from a backup taken before the crashes began.
Replace rather than reseat when a module fails testing on its own. If the memory is soldered or the PC is under warranty, contact the maker with the diagnostic result.
If you’d rather not do the diagnosis yourself, it’s a typical $59 remote fix: with your approval, a technician reads the dumps, fixes driver and page file problems, and tells you which part is most likely at fault if it’s hardware. Changing BIOS settings and swapping memory need someone at the PC, and replacement parts aren’t included. See how remote support works.
Common questions
Does MEMORY_MANAGEMENT always mean bad RAM?
No. Several parameter 1 values are ones Microsoft marks as probably hardware, but others point at a driver misusing memory, and 0x3F points at the page file on your drive. RAM is the first suspect when memory tests fail, crashes stop with XMP or EXPO turned off, or other memory-related stop codes appear as well.
How long should I run Windows Memory Diagnostic?
Use the Extended test mix and at least one full pass, which can take hours on a PC with lots of memory. If crashes continue and it passes, run more passes or an overnight bootable test such as MemTest86. One error at default memory settings is enough to treat the memory as faulty; a clean result doesn’t prove the RAM is perfect.
Can XMP or EXPO cause a memory management blue screen?
Yes. These profiles run memory above its default speed and often at higher voltage, and a profile that isn’t stable on your board and processor can corrupt memory under load. Disable the profile in the BIOS/UEFI setup and use the PC for a few days. If the crashes stop, leave it off or choose a slower speed.
Can a failing SSD cause MEMORY_MANAGEMENT?
It can, through the page file. When parameter 1 is 0x3F, a page Windows read back from the page file didn’t match what was written. Check the drive with chkdsk C: /scan and the maker’s health tool, back up, and reset the page file to automatic. If the drive is healthy, test the RAM next.
I added RAM and now get memory management errors. Why?
The new module may be faulty, or it may not match the existing ones in speed, timings or type, and mixed modules can fail together even when each passes alone. Remove the new module and test. If that’s stable, replace the set with a matched kit from your PC maker’s compatibility list.
Can a graphics card cause a memory management blue screen?
Usually through its driver rather than the card. Graphics drivers manage large amounts of memory, so a faulty one can trigger 0x1A, often under graphics load such as games or video editing; reinstall it from the PC or GPU maker. A dedicated card’s video memory is separate from system RAM, and Windows Memory Diagnostic doesn’t test it. Visual glitches such as colored blocks or lines point at the card itself.