Help Blacklisting Ram via Registry Windows 11

[Monty_Droppings]

Hi I'm working on a laptop with soldered ram, trying to blacklist the bad areas per the memtest instructions but I'm having trouble. The output from Memtest is

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 0x4994B1 0x115293 0x21FDE5 0x237B6D 0x237A17 0x255528 0x30970C 0x3C6CD2 0x45B7C9 0x47CE95 0x1CD0D9 0x1CF0D9

but per https://docs.microsoft.com/en-us/win...fa-memory-list "Starting in Windows version 19042, bad memory pages are stored in the registry under HKLM\SYSTEM\CurrentControlSet\Control\WHEA\BadPage s. In previous versions of Windows, this information is stored in the BCD system store." The example given shows the output as

C:\Windows\system32>reg query "HKLM\SYSTEM\CurrentControlSet\Control\WHEA" /v BadPages

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WHEA
BadPages REG_BINARY 000000000000000058140280000000005C1B0280000000007C30038000000000E2BBFC8000000000AF52188000F00F00

This makes it look like the addresses are in a different format than those outputed by memtest, does anyone have experience blacklisting RAM using the reg editor in Windows 11?

[David (PassMark)]

That is a long list of bad pages.
I would think it is likely that there are more pages with problems than what is in he list as it doesn't appear to be an isolated fault.
If you run MemTest86 again, does it return exactly the same output or is it a bit random?

Doesn't make sense to me to place a bad page list in the Windows registry. As by the time the registry is available, Windows has already booted and software has already potentially made use of the bad pages. The article seems to imply that the registry entry is just for ECC RAM with single bit correctable failures (i.e. not laptop RAM). The article also continues to suggest BCDEdit is used as well, but I agree Microsoft hasn't done a great job of making the interaction between the registry and BCD store clear.

As far as we know BCD still works.

[Monty_Droppings]

bcdedit /set {badmemory} badmemorylist 0x24DA73 0x3D9A7D 0x4829A3 0x292299 0x2C1839 0x3D8030 0x4640F1 0x20EBEE 0x24D4D3 0x24A109 0x10D7EB 0x10F7EB 0x29927F 0x29B27F 0x2D156A 0x2D356A 0x2D881A

This is what I got running it again, it looks a lot of these are different.

[Monty_Droppings]

I was reading this page linked from the blacklisting ram page which is why I was under the impression the BCD method no longer worked. https://answers.microsoft.com/en-us/...1-d785d802c8c7 I'm not sure how to verify it is working, the total ram amount doesn't look different in task manager, and with RAMMAP I'm not sure what I'm looking for "reserved"?

[David (PassMark)]

We don't know if that Microsoft bug report you linked to is true nor if it got corrected if it was true.

But what I am sure about is that those RAM errors aren't consistent. So black listing those pages isn't likely to fix the problem.