How to fix random Memory Management (0x1a) Crash

Question

How to fix random Memory Management (0x1a) Crash

Connor Votava 0

Recently I did nothing to my computer then all of a sudden it gives me this error. I think its nothing important and reopen windows but then it keeps happening, I've done everything online has told me from running the Windows Memory Diagnostic which it says its fixed then a few minutes later it crashes. Done file checker which it finds corrupted files but never fixes them or tells me what needs to be fixed. Reinstalled windows and updated all drivers and bios. And still nothing has fixed it. Any way to fix it all?

0 comments

2 answers

Your answer

Answer 1

DaveM121 934.5K Independent Advisor

Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Please do not upload a very large Memory.dmp file.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.

Connor Votava 0 Reputation points

2026-09-16T11:25:18.5333333+00:00

https://1drv.ms/u/c/22833ddaea89646f/IQCO517Rk4T2RoCCdNVaoaE9AU67F9poTb0bsq7xw448eNQ?e=MS2kpm would this be the possible files you would be looking for?
DaveM121 934.5K Reputation points Independent Advisor

2026-09-16T11:34:55.86+00:00

1

Your minidump files do not indicate any specific driver as the cause of the crashes.

However, I do notice an Nvidia process is listed in all your minidump files, do you have the Nvidia Broadcast app installed on your PC?

If so, uninstall that, restart your PC and wait to see if your system is stable.

2

If not, to try to force Windows to show any faulting drivers... etc., the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

Before you run Driver Verifier, please create a new System Restore Point

https://learn.microsoft.com/en-us/answers/questions/4377096/(article)-driver-verifier-tracking-down-a-mis-beha?forum=windows-windows_10-update&referrer=answers

.

.

.

Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

Do this twice

On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

Upon restart, press 4 to enter Safe Mode

Open Command Prompt as Administrator and run these two commands, then restart your PC.

verifier /reset

verifier /bootmode resetonbootfail
Connor Votava 0 Reputation points

2026-09-16T14:48:45.5166667+00:00

Now everything is breaking, My nvidia drivers arent installing and windows doesnt trust the drivers and when I try to get the MiniDump files to go into a zip I dont have access to them and changing who owns them doesnt fix it either
DaveM121 934.5K Reputation points Independent Advisor

2026-09-16T14:53:41.58+00:00

Have you disabled DriverVerivier once your PC has crashed a couple of times?

To upload the minidump files, in the Minidump files, right click and copy the files, then on your Desktop press Ctrl + V to paste a copy of the minidump files, you should then be able to upload the copied files for analysis.
Connor Votava 0 Reputation points

2026-09-16T14:57:01.22+00:00

I never could do DriverVerivier I wanted to see if it was Nvidia Broadcast first, And ive been getting different errors instead of Memory_Management
DaveM121 934.5K Reputation points Independent Advisor

2026-09-16T15:01:23.74+00:00

Are you able to use that process to upload any new minidump files you may have for analysis.

For the Nvidia drivers not installing, please provide a screenshot of ay error you may be seeing and where are you downloading the drivers from.
Connor Votava 0 Reputation points

2026-09-16T15:08:13.1566667+00:00

No I wasn't able to upload the dump and the other screenshot tells me I dont have owner of the file
DaveM121 934.5K Reputation points Independent Advisor

2026-09-16T15:11:45.4333333+00:00

If you are downloading the drivers from the official Nvidia website, you can safely choose 'Install this driver software anyway'.

The error on the minidump file indicates you are trying to open the file, are you just copying them to your Desktop using Ctrl + C and Ctrl + V?
Connor Votava 0 Reputation points

2026-09-16T15:14:32.17+00:00

Ok Ill try that,

This is what ive been getting trying to put into zip
DaveM121 934.5K Reputation points Independent Advisor

2026-09-16T15:20:20.2366667+00:00

If you changes security permissions on the minidump files that may be causing that problem, run Disk Cleanup on your drive, to delete the minidump files, then wait for your PC to crash again and please upload any new minidump files you may get for analysis.
Connor Votava 0 Reputation points

2026-09-16T16:41:44.6433333+00:00

https://1drv.ms/u/c/22833ddaea89646f/IQAyCCdArQqbTLwEdaPdkefCAZnb97Zinj2oM4prMvF9N1A?e=1lI8vg Ive now tired to install a different drive that has windows installed and now its doing the same thing as well
DaveM121 934.5K Reputation points Independent Advisor

2026-09-16T16:50:08.99+00:00

The new minidump files just indicate generic errors, nothing specific as the cause of the crashes.

If the System File Checker finds corrupted files and does not fix them, the best option is to open the Settings App.

Go to System - Recovery

Click the Reinstall Now' button in the 'Fix problems with Windows Updates' section and wait for that process to complete.

This process should fix any system corruption and will not affect your files, settings or installed apps.
Connor Votava 0 Reputation points

2026-09-16T16:56:47.4533333+00:00

This is what i have gotten from it, and gave me a dism.log as well, Just now too it crashed saying irql_not_less_or_equal https://1drv.ms/u/c/22833ddaea89646f/IQCXWONQvzqlRYxyFJ6FDWTMAZ2gHvxtoHEHaIszzCK8Y3s?e=C6FrTd
DaveM121 934.5K Reputation points Independent Advisor

2026-09-16T17:07:56.37+00:00

That error indicates the file structure on your drive may be corrupted, try running this command to repair the disk, and it would be best to backup your files first.

chkdsk C: /f /r
Connor Votava 0 Reputation points

2026-09-17T09:59:22.31+00:00

Ok I did a fresh install of both my drives I have on my computer and its just basic windows and its still doing the Memory_Management 0x01a, and also irql_not_less_or_equal https://1drv.ms/u/c/22833ddaea89646f/IQBWT0-YaID9Sq3aYb5U3IliAcTrVifdsUr6v8OL4uNKxJA?e=cvNXFr
DaveM121 934.5K Reputation points Independent Advisor

2026-09-17T10:10:47.89+00:00

Your new minidump file just indicates generic errors, nothing specific.

If you have clean installed Windows and a full set of drivers from the support page for your system on the manufacturers website, and that did not result in a stable and responsive system, that usually indicates there is an underlying hardware fault causing the crashes.

You indicate you ran a Windows Memory Diagnostics test and it said it fixed it, that test cannot fix RAM errors, what was the result of that test, did it indicate no problems were found on the RAM?
Connor Votava 0 Reputation points

2026-09-17T10:42:50.0433333+00:00

I got these results from the MemoryDiagnositscs-Results

Answer 2

MEMORY_MANAGEMENT (0x1A) means Windows detected a severe memory management error. Since the crashes continue after reinstalling Windows, updating drivers, and updating BIOS, the next useful step is to identify whether the cause is hardware corruption or a specific driver.

Check the bug check details in the dump files.
- The stop code 0x0000001A is only the top-level bug check.
- Parameter 1 identifies the exact violation. Examples from Microsoft documentation include:
  - 0x3f: in-page operation failed with a CRC error
  - 0x403: page table and PFNs are out of sync, probably hardware error
  - 0x411: a PTE has been corrupted
  - 0x5003: working set free list is corrupted, probably hardware error
  - 0x5200: free pool page corruption, possibly write-after-free in a driver
- Use the !analyze debugger extension on a minidump or memory dump to see which parameter value is being reported and what component is implicated.
Collect the crash dumps if the cause is still unclear.
- For ongoing random crashes, collect the minidump files from C:\Windows\Minidump.
- If deeper analysis is needed, collect a full OS memory dump.
Focus on hardware if the crashes survived a Windows reinstall.
- Microsoft Q&A guidance for similar cases states that BSODs that continue after reinstalling Windows often point to a hardware fault.
- Similar cases also identify RAM or general memory corruption as a common cause.
Check for unstable drivers even if they are updated.
- Similar cases showed MEMORY_MANAGEMENT crashes caused by graphics drivers and anti-cheat or virtual drivers.
- If any third-party anti-cheat, low-level security, motherboard utility, or graphics driver software is installed, test without it where possible.
- For graphics drivers, one accepted resolution in a similar case was to completely remove the current Nvidia driver and install a slightly older stable version.
Recheck RAM and firmware-related stability.
- Microsoft documentation recommends running the Windows Memory Diagnostic tool.
- Similar cases recommend a more thorough RAM test such as MemTest86 with multiple passes when crashes continue.
- If memory overclocking or XMP is enabled, disable it and test at default settings. This is especially relevant when memory corruption appears random.
Check motherboard support software and chipset-level drivers.
- In similar cases, accepted guidance was to install the chipset drivers recommended by the PC or motherboard manufacturer.
- If the system uses motherboard-linked components such as TPM-dependent anti-cheat, reinstalling or updating those components can help.
If dump analysis is inconclusive, use Driver Verifier carefully.
- In a similar case, Driver Verifier was suggested to force Windows to expose a faulty driver.
- Warning: Driver Verifier can intentionally trigger additional crashes while testing. Create a restore point first.
- If Windows becomes hard to start afterward, boot to Recovery, enter Safe Mode, and run:
  - verifier /reset
  - verifier /bootmode resetonbootfail

Most likely next path based on the symptoms:

Analyze the latest minidump with !analyze
Test RAM more thoroughly
Disable XMP or any overclocking
Reinstall chipset drivers from the motherboard or PC manufacturer
Remove or roll back low-level third-party drivers such as GPU drivers or anti-cheat software

If the dump files only show generic memory corruption and the issue still persists after those steps, the remaining likely cause is faulty RAM or another hardware fault on the memory path.

References: