Windows 10: How to add to Predictive Failure Analysis PFA Memory List via Registry

Hi I trying to blacklist some areas of RAM soldered onto MB, replacement not an option. I tried to use this command based on the output I got from Memtest86. bcdedit /set {badmemory} badmemorylist 0x382E3C 0x396DE5 0x43D2BA 0x24B03E 0x35634E 0x3D38F5 0x418B0F 0x48E2FF 0x28B72C 0x201546 0x284AB9 0x2DBFCB 0x32BE71 0x3E8CFD 0x49D5E8 0x15C6BE 0x19F7AC 0x1A3D6C 0x281450 0x382CD8 0x437FE3 0x437148 0x38F00 0x3B9D2 0x3A16B 0x3CC3D 0x1C1581 0x1C3581 0x20476A 0x20676A 0x2C1E9E 0x2C3E9E 0x38CB46 0x38EB46 0x39D1E4 0x39F1E4 0x2C0EFA 0x2C5A95 0x31C434 0x378633 0x28E5C8 0x2C1D47 0x2DE4FE 0x2D3C79 0x2D71CA

:)

 

Bsod " irql_not less or equal"

The badmemory command in the bat file is used to see whether Windows had predicted RAM failure.
If Windows predicts RAM failure it can block memory addresses.

https://docs.microsoft.com/en-us/win...analysis--pfa-
https://docs.microsoft.com/en-us/win...fa-memory-list
https://docs.microsoft.com/en-us/win...of-pfa-results


The image was Memtest86.
Did you report running Memtest86+ ?

Memtest86+ - Advanced Memory Diagnostic Tool
MemTest86 - Official Site of the x86 Memory Testing Tool

 

BSOD MEMORY_MANAGEMENT once or twice a week

You are very welcome.

Please mark as solved.


Post #9 displayed the defective RAM area detected by Windows. (badmemory)

For academic interest:
When you have replacement RAM it would be interesting and educational to unblock the RAM region on the malfunctioning RAM, reboot, and see the impact.

Windows memory testing then could be ran to see if it finds again the bad area (confirmation test)

C:\Windows\system32>bcdedit /deletevalue {badmemory} badmemorylist

https://docs.microsoft.com/en-us/win...analysis--pfa-
https://docs.microsoft.com/en-us/win...-on-ecc-memory
https://docs.microsoft.com/en-us/win...of-pfa-results
https://docs.microsoft.com/en-us/win...fa-memory-list

 

Starting with Windows 10 2004 the PFA memory list is no longer recognized

Starting with Windows 10-2004 the PFA memory list, as described for example here How to Manage the PFA Memory List - Windows drivers , is no longer recognized.

How to test:
1) Start „regedit.exe“, and export „ Computer\HKEY_LOCAL_MACHINE\HARDWARE\RESOURCEMAP\System Resources” as _text_ to a file A.
2) Choose a memory address to test the functionality. For example 32MB (=0x2000000 page number = 0x2000000 / 0x1000 {page size} = 0x2000).
3) Now open file A and ensure the chosen address (0x2000000) is part of a descriptor below “Physical Memory”, but neither part of “Loader Reserved” nor “Reserved”. Typically 0x2000000 should be fine.
4) Open an administrator command prompt and execute these commands to add the memory at 0x2000000 to the bad memory list by adding its page number 0x2000:
“bcdedit /set {badmemory} badmemorylist 0x2000”
To ensure Windows does not ignore the list this setting is also required:
“bcdedit /set {badmemory} badmemoryaccess no”
To be sure there is no override in the current settings also call:
“bcdedit /set {current} badmemorylist 0x2000”
“bcdedit /set {current} badmemoryaccess no”
The settings can be verified calling:
“bcdedit /enum {badmemory}”
“bcdedit /enum {current}”
5) Reboot the PC
6) Again start „regedit.exe“, and export „ Computer\HKEY_LOCAL_MACHINE\HARDWARE\RESOURCEMAP\System Resources” as text to another file B.
7) Compare file A and B.

Before Windows 10-2004 files A and B were different, because in file B the faulty page was excluded from usable memory, as you can see in the attached files.

Using Windows 10-2004 the only differences are the timestamps.

We also succeeded in reserving a memory range containing such a bad memory entry by calling “MmAllocateContiguousMemorySpecifyCache” (MmAllocateContiguousMemorySpecifyCache function (wdm.h) - Windows drivers).