I read the bcdedit documentation and hoped to find something there, but I only found truncating memory and burning memory settings. I hate it when something from Microsoft has useful features and they don't care about documenting them.
The corrupted RAM module is at bank 4. I could put it even further away, but I then I would need to run memtest again to find out the new location, so I'm sticking with this where I already know the bad memory address.
"bcdedit /set badmemorylist" will not work, the correct syntax would be "bcdedit /set {badmemory} badmemorylist".
So now I'm hoping to see no more corrupted files or random crashes in the future.
|