Synchro3
macrumors 68000
Exactly, as 'C: drive', only I'm not using an USB-Stick, but regular SATA flash drives or hard disks in an USB enclosure: http://www.raidsonic.de/en/standards/searchresults.php?we_objectID=3395
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
High Sierra killed memory slot
- Thread starter bened
- Start date
- Sort by reaction score
Exactly, as 'C: drive', only I'm not using an USB-Stick, but regular SATA flash drives or hard disks in an USB enclosure: http://www.raidsonic.de/en/standards/searchresults.php?we_objectID=3395
Trusteft
macrumors 65816
Synchro3
macrumors 68000
Direct App Store link for the full 10.12.6 installer: https://itunes.apple.com/us/app/macos-sierra/id1127487414?mt=12
Santiagocamara
macrumors newbie
First of all, what Mini do you have - 2011?
I looked to see if there were any other reported instances of similar problems in the Mac Mini. The one I could find was:
https://forums.macrumors.com/threads/16gb-upgrade-issues-with-mid-2011-on-high-sierra.2102934/
So both this and the instance linked above involve the 2011 Mini with OWC memory. In the case reported in the link above, it was solved by replacing the OWC memory. In this thread, the OP did not report back results of trying different memory so we don't know what happened or even if the OP ultimately tried that. If you have replaced the memory, I would try the original memory if you have it. If you don't have it, you can try different memory (although it's possible that it's just coincidence that both these cases involved OWC memory, I would avoid that as a candidate for replacement memory). If you don't want to spend the money for a solution which might not work, if you can get to an Apple Store, you can call Apple to see if they'll test different memory at an Apple Store in your Mini.
I looked to see if there were any other reported instances of similar problems in the Mac Mini. The one I could find was:
https://forums.macrumors.com/threads/16gb-upgrade-issues-with-mid-2011-on-high-sierra.2102934/
So both this and the instance linked above involve the 2011 Mini with OWC memory. In the case reported in the link above, it was solved by replacing the OWC memory. In this thread, the OP did not report back results of trying different memory so we don't know what happened or even if the OP ultimately tried that. If you have replaced the memory, I would try the original memory if you have it. If you don't have it, you can try different memory (although it's possible that it's just coincidence that both these cases involved OWC memory, I would avoid that as a candidate for replacement memory). If you don't want to spend the money for a solution which might not work, if you can get to an Apple Store, you can call Apple to see if they'll test different memory at an Apple Store in your Mini.
Santiagocamara
macrumors newbie
Sorry I forgot that. Mine is a MacBook Pro late 2011 13inch 🙂 Its really strange, always works fine, with all MacOS since 2013 (yr that I upgrade to 16gb Corsair), after update do high sierra stop working the superior slot.
I think the problem in this thread and the other one I referenced are specific to the 2011 Mac Mini, the RAM modules used and the firmware. So you might get a better answer in either the MacBook Pro or the High Sierra forum.
Have you tried the SMC reset suggested in post #6? (You can also try the NVRAM reset but I think it's almost not worth it for this type of problem.)
https://support.apple.com/en-us/ht201295
Also, have you tried swapping the RAM modules between the two banks?
When did you start having this problem? High Sierra just had the 10.13.5 update on May 29 (I think it was the 29th). Did you start having the problems after this update?
Santiagocamara
macrumors newbie
Have you tried the SMC reset suggested in post #6? YES
Also, have you tried swapping the RAM modules between the two banks? YES
After the update start to get Kernel Panic, shutdown by himself, and than 3beeps so I try to find some tips on here and realized that might be High Sierra Bug or something...
I tryied to make a cleanup contacts, cleanup mems, both mems work on down slot. :/
Since you have gone through the steps that would typically be suggested for people with RAM issues, I think (as I mentioned in my post #31), you should try getting different RAM (make sure it's the proper RAM for the 2011 MBP) and see if it works. It's possible you have a similar problem - an incompatibility between the memory you have and the EFI firmware. There probably was an EFI firmware upgrade as part of the High Sierra 10.13.5 update so that's why you're having the problem now - unless you were able to use 16GB after the update and then started having problems later. (On my 2014 Mini, it looks like there was a firmware update.) You can't downgrade the EFI. You can try to see if a previous OS build would work but for a lot of people, that's not easy to do and from what I've read, it's not likely to solve the issue. It also doesn't appear to affect a lot of people - I don't see anybody else having this issue in the MacBook Pro forum or the High Sierra forum in the 2011 MBP since the 10.13.5 update.
I just updated my Mac Mini mid-2011 with 16GB (2 x 8GB) Crucial memory that I had added soon after I bought it years ago. The MacOS update was from Sierra 10.12.6 to High Sierra 10.13.5. Everything updated smoothly and the Mac Mini is running perfectly.
Therefore this issue is not about High Sierra having a problem with 16GB (2 x 8GB) RAM and the RAM slots. It has to be another issue causing the problem for some people. It could specific to a type of RAM, a particular configuration or any other problem that has been proposed in this thread.
Note: Ideally use a matched pair (or equivalent spec) of RAM sticks that are fully compatible with the specs of your year and model of Mac or you could run into problems. I can't verify for other brands of RAM. I myself can only confirm that 2 x 8GB Crucial brand designated for my model of Mac does work.
Therefore this issue is not about High Sierra having a problem with 16GB (2 x 8GB) RAM and the RAM slots. It has to be another issue causing the problem for some people. It could specific to a type of RAM, a particular configuration or any other problem that has been proposed in this thread.
Note: Ideally use a matched pair (or equivalent spec) of RAM sticks that are fully compatible with the specs of your year and model of Mac or you could run into problems. I can't verify for other brands of RAM. I myself can only confirm that 2 x 8GB Crucial brand designated for my model of Mac does work.
Last edited:
Santiagocamara
macrumors newbie
Hi there, thanks for your time.
I got some progress in my problem, I did those all resets ( NVRAM, SMC ) and starts with one DIMM (8gb), runs great, so I felt lucky and tried to put the second DIMM, voilá no Beeps, but stucks on login screen, after put my password, 10 secs later, loops on apple logo and came back to login screen... Took one DIMM out and runs great, I get notified about apdate of high sierra, I did. I need to go out of my home and left the MBP on doing the update, later I upgrade with news.... Both MEMs I am 100% sure that are working great. Could be some problem with EFI firmware, crossing my fingers LOL
I'm glad that your 2nd memory module is working again. I had thought that you had problems after the 10.13.5 update but you were having problems with an earlier update and the latest update appears (hopefully) to have solved the issue. As you mentioned and I have guessed, there probably is a problem with certain recent EFI updates and specific RAM modules. Thanks for reporting back. Keep us updated if there are any further issues.
Hmmmm. Coincidentally I got one 8gb rail wind up going bad after I went from Mavericks to Sierra last summer. I had immediate issues. However it wasn't till a few months ago that I did a ram check out of desperation and discovered it, lol. My Mini gave no obvious warnings of it, 'just' lots of infuriating USB connectivity problems and resulting oddball software behavior tied to that.
The bottom ram shot in my 2012 Mini failed recently so I'm down to 8GB from 16GB ram. It's Crucial ram but i think it' a hardware fault probably heat related as it's the bottom slot - there are a few pointers to this I read. It was running High Sierra Ok and still is.
You could have the same issue as in post #37. Check your EFI version (look in the "System Information" app, select "Hardware", look at "Boot ROM Version". On my 2012 Mini with High Sierra, it's MM61.010E.B00 (this is the latest version for El Capitan, Sierra and High Sierra).
I don't know about heat causing the problem - the RAM is on the opposite side of the logic board from the CPU and HM77 (the main helper chip) which are the main heat generators. There's a "SMSC 1428-7 system management bus temperature sensor" fairly close to the memory modules so I would expect that if there were a heat issue, it would shut down the system before damage would happen to that area of the logic board.
Last edited:
easbahr
macrumors newbie
Hello everyone ... I have the same problem a few years after I made the upgrade to the High Sierra my second slot (bank1) stopped working on my MacBook Pro 2011, during the upgrade I was using 16Gb of Ram CorSair, and now I can only use 8Gbps in the first slot slot (Bank0). I've tried the original memory and the problem persists. I took Apple at the time and wanted to exchange my motherboard. Someone in the end managed to solve?
As I replied to post #40, there is a poster who said, in post #37 that their problem seemed to be solved when an EFI upgrade was done (the date of the that post - #37 also coincides to the time I noticed a EFI firmware upgrade on my 2012 Mac Mini). Check your EFI firmware version (instructions in my post #41) and see if you have the latest version. I don't know what the latest version would be since I don't have a 2011 MBP, but you can search the web with the EFI version you have and see if it is the latest (should be early June 2018). If you can't find what the latest EFI version is (Apple doesn't seem to publish this anymore), go to the MacBook Pro forum and post your EFI version and ask people if that's the latest - you need to specify whether or not you have a early or late 2011 MBP and what size monitor you have - 13", 15" or 17".
If that doesn't work, have you tried:
1) SMC reset https://support.apple.com/en-us/ht201295
2) Apple Hardware Test https://support.apple.com/en-us/ht201257
Last edited:
easbahr
macrumors newbie
Yes, I've already done all the nvram and smc cleanup issues. I've also run diagnostics and no error. however when entering the 2nd module of memory happens the 3 beeps.
cobracnvt
macrumors 6502
How do you know both RAM chips are good, have you put the 2nd module in the first slot and booted successfully?
Also, your RAM may still be under warranty from Corsair as some of their memory has lifetime warranties.
easbahr
macrumors newbie
yes either of the two modules normally work in slot 1 and do not work in slot 2. so does the original modules. already had given up thinking that it was just a super coincidence that exactly after the update boot the slot "burned".
is the lower slot? I think the OS upgrade is a coincidence - mine went after a few months on High Sierra. But we are now talking about a 6 year old machine. Googling around it does seem to be a fault that's happened to quite a few people.
easbahr
macrumors newbie
Ues it is in the lower slot, it happened exactly at the time of the boot of the version upgrade. currently the equipment still caters to me, even with 7 years of age works very well. I had 16Gb of ram and now I only use 8.
gikirima
macrumors newbie
this was also happened to my macbook pro mid 2012 i5 processor.
I upgraded my RAM to 16gb, and worked very well with high sierra until recent updates on june/july (i forgot).
both of my RAM and the slots are working, and if I switch one of my RAM to 2gb, it'll work. but not if both are 8gb's.
I tried to downgrade to Yosemite, and there was no problem until I upgraded it back to recent version of High Sierra. so recently I'm sticking with Yosemite and turn off any updates AppStore's pulling via Settings.
probably one of Apple's trick to kill old macbook pros and force consumer to buy a new one.
I probably better be sticking with the working OSX instead of updating it recklessly.
I upgraded my RAM to 16gb, and worked very well with high sierra until recent updates on june/july (i forgot).
both of my RAM and the slots are working, and if I switch one of my RAM to 2gb, it'll work. but not if both are 8gb's.
I tried to downgrade to Yosemite, and there was no problem until I upgraded it back to recent version of High Sierra. so recently I'm sticking with Yosemite and turn off any updates AppStore's pulling via Settings.
probably one of Apple's trick to kill old macbook pros and force consumer to buy a new one.
I probably better be sticking with the working OSX instead of updating it recklessly.
RyanXM
macrumors 6502a
I have updated/upgraded no less than 20, 2011 & 2012, Mac mini to 10.13.5 and all have been ok. All of them are using Apple OE (SK Hynix, Micron) RAM in a 2x8GB configuration and I have yet to have a single one fry a SO-DIMM or a RAM slot. Apple isn't purposely causing a RAM slot to stop working.
As of yesterday, I updated a 2012 Mac mini (MD387LL/A configuration) from 10.9.5 to 10.13.6 without a single issue related to the EFI update that occurred. It went from MM61.0105.B03 to MM61.010E.B00 so most of what is being mentioned in this thread has to be pure coincidence and/or hardware was failing and the OS update pushed it over the edge.