How To Fix MEMORY_MANAGEMENT Blue Screen Error?

As you know, we often refer to the solutions for blue screen errors. We recently resolved the DRIVER_PNP_WATCHDOG blue screen error. Today, we will try to solve the frequent MEMORY_MANAGEMENT blue screen error.

If you wish, let’s look at what the MEMORY_MANAGEMENT (0x0000001A) error is. This error occurs when a problem occurs in memory management. Memory (RAM), as it is known, is the temporary storage center used by the operating system and applications. Problems in this context can cause crashes in the system. Today, we will discuss exactly this problem and its solution.

Again, we start by analyzing our minidump file. Minidump files are files that keep track of the crashes that occur in the system during the blue screen and are used to solve the errors. To obtain these files, you must navigate to the C:WindowsMinidump file path. The minidump file will appear with the .DMP extension.

To use the file, you must also take ownership of the file. For this, you can go to our guide here and get detailed information.

Analysis of the minidump file

As usual, we start with the !analyze -v command to examine the minidump file we opened with WinDbg.

2: kd> !analyze -v ********************************************* ************************************* * * * Bugcheck Analysis * * * ***** ************************************************** ************************ MEMORY_MANAGEMENT (1a) # Any other values ​​for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. Arg2: ffffb180f5b7cfe0 Arg3: 0000000008000000 Arg4: 0000000000000000 Debugging Details: —————— KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 6655 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 21200 Key : Analysis.Init.CPU.mSec Value: 1140 Key : Analysis.Init.Elapsed.mSec Value: 2717 Key : Analysis.Memory.CommitPeak.Mb Value: 82 Key : MemoryManagement .PFN Value: 8000 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 FILE_IN_CAB: 012322-46796 -01.dmp BUGCHECK_CODE: 1a BUGCHECK_P1: 41792 BUGCHECK_P2: ffffb180f5b7cfe0 BUGCHECK_P3: 8000000 BUGCHECK_P4: 0 MEMORY_CORRUPTOR: ONE_BIT BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME : chrome.exe STACK_TEXT: ffff850f`6888b0f8 fffff804`666440ca : 00000000`0000001a 00000000`00041792 ffffb180`f5b7cfe0 00000000`08000000 : nt!KeBugCheckEx ffff850f`6888b100 fffff804`6669e556 : 00000000`00000000 ffffc888`b21e7980 00000000`0000000d ffffb180`f5b7cfe0 : nt!MiDeleteVa+0x153a ffff850f`6888b200 fffff804`6669e66b : ffffb1d8`c07adbe0 ffffc888`b21e7980 ffff850f`00000000 ffff850f`6888b670 : nt !MiWalkPageTablesRecursively+0x776 ffff850f`6888b2a0 fffff804`6669e66b : ffffb1d8`ec603d68 ffffc888`b21e7980 ffff850f`00000001 ffff850f`6888b680 : nt!MiWalkPageTablesRecursively+0x88b ffff850f`6888b340 fffff804`6669e66b : ffffb1d8`ec603000 ffffc888`b21e7980 ffff850f`00000002 ffff850f`6888b690 : nt !MiWalkPageTablesRecursively+0x88b ffff850f`6888b3e0 fffff804`66604f4b : 00000000`00000000 ffffc888`b21e7980 00000000`00000003 ffff850f`6888b6a0 : nt!MiWalkPageTablesRecursively+0x88b ffff850f`6888b480 fffff804`66642961 : ffff850f`6888b620 ffffc888`00000000 ffffb180`00000002 00000000`00000000 : nt !MiWalkPageTables+0x36b ffff850f`6888b580 fffff804`66612aa0 : 00000000`00000001 ffff850f`00000000 ffffc888`b21e77d0 ffffc888`b1de7080 : nt !MiDeletePagablePteRange+0x4f1 ffff850f`6888b890 fffff804`66a01149 : 00000000`00000000 00000000`00000000 aaaaaaaa`00000000 00000000`00000000 : nt!MiDeleteVad+0x360 ffff850f`6888b9a0 fffff804`66a00f22 : ffffc888`b989c2a0 00000000`00000000 ffffc888`b21e7300 00000000`00000000 : nt !MiUnmapVad+0x49 ffff850f`6888b9d0 fffff804`66a00d99 : 00000000`00000000 000001eb`6e4d0000 aaaaaaaa`aaaaaaaa 00000000`00000000 : nt!MiUnmapViewOfSection+0x152 ffff850f`6888bab0 fffff804`66808cb8 : ffffc888`b1de7080 000001eb`6f9e0000 ffff850f`6888bb80 ffffc888`b21e7300 : nt !NtUnmapViewOfSectionEx+0x99 ffff850f`6888bb00 00007ff9`0c2f06e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 00000000`0c2f06e4 : 00000000`00000000 00000000`000000000000`0000`0000`0000`0000`0000`0000`0000`0000`0000`0000` nt! `0c2f06e4 MODULE_NAME: hardware IMAGE_NAME: memory_corruption STACK_COMMAND: .cxr; .ecxr ; kb FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {e3faf315-c3d0-81db23-819a-6cOwner

According to what is written in the detail of parameter 1 (Arg1) in the analysis, a broken PTE was detected. PTE (Page Table Entry) ie page table entry; maintains the mapping between the virtual address of a page and the address of a physical frame. For more details, you can proceed to our article on virtual memories here.

Additionally, you can see nt!MiWalkPageTablesRecursivelyand similar statements in STACK_TEXT output. Again, these show us that there is a problem with the page tables.

Virtual memory corruption can occur in this blue screen error, as seen above. As a solution, we turn off the virtual memory and turn it back on.

1) To turn off virtual memory, we first right-click on This PC and select Properties.

pc oezellikler png
Right click and select Properties.

2) Select the “Advanced system settings” option from the Settings window that opens.

gelismis sistem ayarlari png
We select advanced system settings.

3) In the “System Properties” window that opens, we click on the Performance settings from the Advanced tab.

sistem oez png
From the Advanced tab, we enter the performance settings.

4) If the items in the window that opens cannot be clicked, disable the “Automatically manage paging file size on all drives” option at the top.

sanal bellek png

5) We select the option “No paging file” and save the settings. Then Windows says we need to reboot the system and we reboot the system. After the reboot, we open this window again and select the “System managed size” option as before. After saving and exiting this process, we restart the computer. In this way, virtual memory file formation is finished.

Test your RAMs with Memtest86

Memtest86 is a USB print-run program that does not require or use any operating system to run. Also, although the Windows Memory Diagnostic tool can be used instead of Memtest86, we recommend using Memtest86 for precise results. If you don’t have a USB stick, you can use Windows’ tool or MemTest64.

You can watch our video guide below to learn more about the use of Memtest86.

Note: In order to get more stable results, we recommend that you reset the additional settings you applied to your RAMs in the BIOS to default.

If there is a problem with the disk on which you installed the system and this affects the virtual memory, it is possible that you will get the MEMORY_MANAGEMENT blue screen error. Of course, let’s not go without saying, if you put the virtual memory file on a different disk, there may be an error on that disk. If there is a bad sector formation on the disk and the virtual memory file is on one of these bad sectors, you will get a blue screen.

You can use HD Tune or CrystalDiskInfo to check the health of the disks. You can also proceed to our detailed guide here for more detailed information.

As it is known, RAMs can work with high performance by opening XMP/DOCP settings via BIOS. Sometimes the default frequency and voltage ratios of the motherboards are not enough for the memory, and in this case, a blue screen occurs. In this case, resetting memory overclocking to default will solve the problem.

In addition, if you want to use your memory at high frequencies and you are encountering an error when you open the default settings, you can try to increase the voltage manually. However, we recommend that you do not do it if you do not have any information about the exact values ​​you need to give, because the memory can be permanently damaged with the overload.

RAM performance improvements can be released with BIOS updates on motherboards. Of course, there are some situations that should be considered when updating the BIOS. First, make sure you’ve selected your motherboard correctly. If you do not know the model of your motherboard, you can find out by typing system information in the search bar.

sistem bilgisi

Then search for your motherboard model from the support section of the manufacturer’s page and scroll to the category with BIOS versions.

BIOS surum bilgisi
BIOS tab on the motherboard’s support page.

As you can see, there is an update for memory stability in version 0702 of the motherboard, but our motherboard’s BIOS is at the latest version. So we don’t need to do anything to the BIOS.

When RAMs are incompatible, they may not work with each other. For example, a RAM with 3200 MHz and CL16 and a RAM with 2800 MHz CL15 may have compatibility issues. In order not to experience this, you can buy your RAMs in kit form.

Check your motherboard manual for RAM mounting

Some motherboards have 4 or more RAM slots, in which case it is a common mistake to repeatedly install RAMs. If you are going to place 2 RAMs in 4 slots, you should install your RAMs according to the booklet.

For example, ASUS offers the following configuration suggestions for the TUF Gaming X570-Plus model.

tavsiye edilen ram konfigurasyonu
ASUS memory configuration recommendation for TUF Gaming X570-Plus motherboard.

When cascaded, the memories do not operate in dual channel, making you unable to use the potential performance. Therefore, it is useful to look at the motherboard’s booklet and insert your RAMs.

As it is known in LGA socket structure, the memory management unit is on the processor. An error occurs during memory management if the processor is not seated or if there is a problem with its pins. You can examine your processor and motherboard to determine the problem.

A break may also occur in the data paths to the RAMs, and the damage to these paths will directly prevent the RAMs from working.


If your problem is not solved even though you have tried all the solution suggestions so far, you can create your own topic in the Blue Screen Error Analysis category in Technopat Social and get technical support from our members. We wish you trouble-free days.

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *