How to avoid to use faulty Ram Areas with EfiUnusableMemory

Hi, ive a macbook with soldered Ram and some are faulty so i want to tell Macos not to use this Areas.


ive installed Ubuntu and thers a kernel option memmap to go around faulty ram


but how do i get this done for macos?


ive heard of EfiUnusableMemory command, but where can i put this in?


maybe this will help many with faulty soldered Ram to use their MacBooks a bit longer

Posted on Sep 17, 2023 7:37 AM

Reply

Similar questions

27 replies

Sep 17, 2023 11:34 AM in response to John Galt

Apple diagnostic said all is ok

bigsur is supported.


you wasting time, answer the question how to blacklist Ram areas on macos


with maxmem=1800M i could install bigsur but i need the rest of the ram.


i figured out that 1848M till 1850M is the area i need to blacklist


the efi command should be the best one but i im thankful of any other software solution

Sep 18, 2023 12:19 AM in response to John Galt

John Galt wrote:


Aikawa24 wrote:

Memtest86+ is the Best app to test Ram and its highly accurate,

It appears you have been misled.

It is not possible to reliably test memory on the system in which the app performing the test is running.


A memory test on the system in which the app is performing the test is running might produce false negatives. False assurances that "everything is OK."


However, if the application has enough control over memory mapping that it can direct all reads/writes to real RAM, and avoid overwriting the RAM out of which it is running, there is no reason to believe that any problems discovered would be false positives.


When the OP says, "maybe this will help many with faulty soldered Ram to use their MacBooks a bit longer," I believe he is making faulty assumptions about what causes most Macs to be retired or scrapped. The usual causes are almost surely things like hard drive or SSD failure, inability to upgrade hardware or software – and user-caused damage (dropping laptops). RAM that is good, later going bad, is probably WAY, WAY down the "cause of death" list.


But I'm not going to make a blanket pronouncement that RAM failures never happen to anyone. Or that a third party RAM testing tool must be wrong just because it finds RAM failures where Apple Diagnostics found none.

Sep 18, 2023 2:28 AM in response to Servant of Cats

@Servant of Cats

yes you are right that topic is far away of my skills but I am not willing to give up this machine because of 4MB BadRam.


with MAxmem = 1844 and open core Ventura installs on that old one, if I set back the Ram limitation it runs flawless but with the knowing of BadRam it feels not good.


I thought that macOS and Linux have more in common and that I can adapt the Commands to MacOs.


so that discussion may end here.


thank you for the Conclusion

Sep 20, 2023 7:34 AM in response to Aikawa24

I was not completely doubting the memory issue, I was just suggesting caution with trusting a utility that has been dormant for a decade. I do plan to start using Memtest86+ at some point since it is open source and at one time it was the better app until it went dormant, but I would want to compare the results with another utility which has proven itself to me for the last decade.


Looking at the memory addresses, I do see a commonality in the addresses which are listed as failing. I had overlooked it due to the low resolution of the picture as it was hard to read.


FYI, when posting pictures, please make sure the are in the proper orientation. It is frustrating to see pictures sideways or upside down. You should not make the people helping you work so hard to view them. It is easy to rotate the pictures on your iPhone/iPad:

https://www.iphonelife.com/blog/5/tip-day-how-rotate-photo

Oct 7, 2023 2:46 PM in response to 0nelight

0nelight wrote:

I run rEFInd Boot Manager to execute a very small EFI-Script which disables the faulty RAM-Area before I boot MacOS (works on Big Sur on MacBook Pro Late 2013).
...
I use this solution for years now, but at this moment I don't remember where the Source Code (with the hardcoded area) is. I will check tomorrow and will update you here as soon as I found it.


I'm glad to hear that it worked out for you.


One question: How have you used this solution "for years now" when your original post (from before when you applied it) isn't even one month old?


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

How to avoid to use faulty Ram Areas with EfiUnusableMemory

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.