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

  • Question

  • Please explain the badmemorylist when:

    a) third party or Windows memory testing is used (does it evaluate or reevaluate the prior reads or reports)

    b) does re-seating or replacing one or more RAM modules reset the badmemorylist?

    c) see the specific questions below with the Microsoft link


    C:\Windows\system32>bcdedit /enum {badmemory} RAM Defects ----------- identifier {badmemory}



    displays one or more entries in the badmemory this / these addresses are blocked.

    This enables Windows to continue working with bad RAM.


    1) If third party RAM testing is performed (Memtest86+ or Memtest86)

    are the addresses blocked or should errors be found when tested?

    2) There is a command to clear the badmemorylist with

     /deletevalue {badmemory} badmemorylist

    Should this be used when testing the RAM or should the third party RAM testing

    be able to find the bad memory addresses without clearing the badmemorylist?

    3) If Windows memory diagnostics is ran instead of third party software please

    indicate whether the badmemorylist has to be cleared to find an updated


    (if there were prior entries on the badmemorylist that were false positives are

    they rechecked with each run of Windows memory diagnostics or do they remain

    until cleared?)

    4) If there are multiple RAM modules that are removed and re-seated into

    different DIMM does this reset the badmemorylist?

    5) If one or more RAM modules are replaced does this reset the badmemorylist?

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

    Monday, March 30, 2020 8:32 PM