Exetools

Exetools (https://forum.exetools.com/index.php)
-   General Discussion (https://forum.exetools.com/forumdisplay.php?f=2)
-   -   Mark memory page as invalid (https://forum.exetools.com/showthread.php?t=17878)

Kerlingen 08-29-2016 12:57

Mark memory page as invalid
 
Does anybody know a way to mark a physical page of memory as invalid or bad somehow on Windows x64?

One of my RAM modules sometimes has a single-bit error at the same fixed address (found by memtest86+). The memory page is located in higher RAM, so it will be unused right after a reboot, but eventually Windows will use it for programs (unexpected crashes) or caching (corrupted files). I want to make sure Windows never tries to store anything on that memory page.

I can't get a single RAM replacement module, I would need to buy 6 new modules. I would like to prevent that if there was an easier fix.

nulli 08-29-2016 14:11

You can mark memory as bad.

But first I would move the defected RAM module far away from Memory Bank 0 (first slot that's going to be used) and then tell Windows _not_ to use that part of the RAM module using bcdedit commands:
bcdedit /set badmemorylist xxx xx
bcdedit /set badmemoryaccess No

For more information see:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff728891(v=vs.85).aspx
http://superuser.com/questions/420051/running-windows-with-defective-ram
http://www.passmark.com/forum/memtest86/5146-memtest86-results-assistance-required-please

Kerlingen 08-29-2016 15:46

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.

nulli 08-29-2016 19:49

Sorry, I haven't used that command before. I just did some quick googling.

Anyways, hopefully it works as expected.


All times are GMT +8. The time now is 21:48.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2026, vBulletin Solutions, Inc.
Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX