Windows 10 2004 update breaks BCDedit method. Can you update BadMemory?

[mkbehbeh]

I tried your driver and it does not appear to be working correctly. It is loaded according to systeminfo, but it is not loaded at the memory address that I specified in the badmemory application.

Here are the questions I had and the steps I tried.

1. Do you need to remove existing badmemory instance? i.e. if the same memory address that the driver asks for is in the {badmemory} list will it crash. ---- I removed the badmemory object before I started
2. Need to run BadMemoryManager as admin (goes without saying, but if you forget it does not give you an error). ----- I got this running but I was not able to confirm as the registry location is locked and I cannot access it to check if it registered with the driver or not.

3.  When the memory is locked it shows up as locked by shell32.dll  is this correct?   ----- This does not appear to be correct as it loaded something else on the next boot
   

Do you have time to look into this driver again? It would be great timing now that Microsoft has broken the BCDedit method.

[HenkPoley]

@mkbehbeh Do you happen to know if (windows kernel handling of) bcdedit /set {badmemory} badmemorylist still broken in Windows 10 2004 / 20H2 / 21H1?

[prsyahmi]

@mkbehbeh
1: Personally I haven't tried this, but the software will try to allocate memory address at that region and if the region is listed on {badmemory} it may failed to do that as it was blocked by windows in the first place.
2: This software may need an update
3: You can use RAMmap, it should show system PTE on the region

@HenkPoley I got an email saying this:

Also by the way, starting from Windows 10 version 2004, the Badmemory in Bcdedit is no longer excluded. The commands still show as if they're working but the bad memory is still used by the system anyway. Your solution still works even after updating to 20H2 which makes your program the only solution I know for version 2004 and later.

[HenkPoley]

Interestingly the Windows live background memory scrubber still seems to run from time to time in 2004-21H1. You can sometimes notice it when on an idle computer System suddenly uses ~40%+ CPU. A debugger would be able to tell you it's MiScrubMemoryWorker/RtlpGenericRandomPatternWorker (It's run from Windows Task Scheduler: Microsoft > Windows > MemoryDiagnostic > RunFullMemoryDiagnostic).

Does the tester write its test result to a new place? Or does it now simply cause a Bug Check (BSOD) akin to "replace your hardware"?