3

So I have blocked some bad memory range from RAM memory. My Question is the next one, I have done it right?

Here you have the info:

C:\Windows\system32>bcdedit /set badmemorylist 0xFC 0xFD 0xFE 0xFF
The operation completed successfully.

C:\Windows\system32>bcdedit /enum

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {d9b18246-6fc0-11e8-aa41-d80cde060b56}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
displaymessageoverride  Recovery
recoveryenabled         No
testsigning             Yes
badmemorylist           0xfc
                        0xfd
                        0xfe
                        0xff
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {d9b18246-6fc0-11e8-aa41-d80cde060b56}
nx                      OptIn
numproc                 8
bootmenupolicy          Standard
usefirmwarepcisettings  No

C:\Windows\system32>bcdedit /set badmemoryaccess no
The operation completed successfully.

And the memtest will be shown:

Memtest

  • 1
    -1 ram has locations not sectors. hard drives have sectors – barlop Jun 18 '18 at 2:35
  • 1
    +1 I did not know BCDedit could map out bad RAM segments. I suppose there are limitations depending on word boundaries – Sunnyskyguy EE75 Jun 18 '18 at 3:05
  • I don't think there's any problem with the question except for the incorrect term usage. I didn't know that Windows can also block fault memory ranges like grub Running windows with faulty memory which can not be replaced – phuclv Jun 18 '18 at 3:40
  • +1 for this undocumented feature. You seem to have done it right,as far as the non-documentation goes. You will can know the answer just by using the computer. – harrymc Jun 18 '18 at 8:11
  • No, I didn't. Anyway, the FIX for this is it on my profile. – Ștefan Furtună Jun 18 '18 at 8:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.