Help! Updated to macOS 10.12.4, MBP randomly shuts off

Hollie

macrumors newbie
Dec 4, 2019
1
0
Belgium
Hello,

I registered at this forum just to post a thank you for this tip.

Story: replaced the battery in my 6 years old late 2013 15" Macbook Pro Retina with a replacement battery from iFixit. The device is running High Sierra with latest updates. After stress testing the battery to calibrate it (8 terminals with `yes > /dev/null`, display on high brightness) all was looking fine.

That is, unless the next day when I tried to use the laptop for regular work. It was shutting down multiple times at the most inconvenient times, without storing the work I was doing first... Bummer.

I could not believe the device got broken by carefully replacing the battery. After going through the regular SMC + NVRAM resets, and some more advanced troubleshooting trying to find the cause for the halting, luckily I found this thread.

The first workaround with the Python script rang a bell. Remember I had no issues with the device shutting down while running the battery calibration test when the CPUs were being stressed. Sounded quite like the reports from people who told their computer was running fine as long as the CPUs did not throttle down.

Yesterday my device that had been working for the last 6 years without a hickup, was shutting down all the time. After removing the thunderbolt kext as instructed in this thread yesterday evening and recharging the battery to 100%, my laptop has been running without issues again all day.

So: a big thanks to all the people contributing to this thread. Really appreciated very much!

Lieven.
 

JRD-

macrumors newbie
Dec 7, 2019
1
0
My 2003 MacBook Pro has been shutting down so frequently, have not been able to work with it. I finally found a super quick solution that worked so far for me here as have listed below ...


Disable FireWire & Thunderbolt Networking
This optimization can help free up bandwidth in the firewire bus and allow Digidesign FireWire devices to work more efficiently.
  1. Open System Preferences.
  2. Click ‘Network’.
  3. On the left hand sidebar, click on FireWire/Built-In FireWire/Thunderbolt FireWire/Thunderbolt Bridge (may not be present depending on computer model).
  4. Click on the drop-down menu for ‘Configure IPv4’ and choose Off.
  5. Click Apply and restart your computer.



    thunderbolt.png
 

Gokuvsfish

macrumors newbie
Feb 10, 2019
1
0
Hi Everyone,

Wanted to share my thanks for this thread, it’s been keeping me productive for almost a year. However…

I updated my 2014 MacBook Pro to 10.15.2 yesterday, and the terminal trick no longer seems to be working. I’ve tried renaming all of the thunderbolt kexts and my MacBook still shuts down randomly. Not sure if I’m doing something wrong this time or if it’s something new with 10.15.2, but just wanted to share my new issue.

I did decide to go back to Mojave, which was easier since I made a seperate APFS partition just in case. Happily back on 10.14.6 and so far no problems.

Thanks again and good luck!
 

amnesia106

macrumors newbie
Jun 5, 2018
12
0
Harzvier
Hi Everyone,

Wanted to share my thanks for this thread, it’s been keeping me productive for almost a year. However…

I updated my 2014 MacBook Pro to 10.15.2 yesterday, and the terminal trick no longer seems to be working. I’ve tried renaming all of the thunderbolt kexts and my MacBook still shuts down randomly. Not sure if I’m doing something wrong this time or if it’s something new with 10.15.2, but just wanted to share my new issue.

I did decide to go back to Mojave, which was easier since I made a seperate APFS partition just in case. Happily back on 10.14.6 and so far no problems.

Thanks again and good luck!
Yes same problem here...
 

amnesia106

macrumors newbie
Jun 5, 2018
12
0
Harzvier
 

des011

macrumors newbie
Jan 24, 2012
3
0
I'm getting shutdowns again on Catalina 10.15.2 (19C57).
I've successfully used the kext deletion / renaming trick for over a year last successful on 10.15.1.

Can people please report in, as I assume I'm not alone here.
 

MWJ

macrumors newbie
Dec 20, 2019
3
0
I was having the same issues with random shutdowns and the thunderbolt trick worked until 15.2. I downgraded to Mojave and the disabling of the thunderbolt no longer worked. After nearly a month with this problem and countless calls to support, Apple replaced my logic board and both of my speakers...I wasn't aware of a problem with the speakers though. I just received my fixed MacBook Pro 15 inch 2014. Im typing this response on it now, and thus far...no shutdowns. This is a hardware issue folks. Renaming/disabling the thunderbolt essentially is delaying inevitable hardware failure. It's a faulty capacitor on the circuit going to the AMD chip on the logic board. Apple did replace both parts for me free of charge(speakers and logic board)...I am grateful for how they responded. However, I'm not certain that the actual defect was addressed. There are known issues with the logic boards manufactured in several MacBook Pro models sold from 2012-2014. My advice is to speak to support...be calm and courteous....they may remedy your problem without cost even though you're far past warranty; at this point, you have nothing to lose.
 
Last edited:

MWJ

macrumors newbie
Dec 20, 2019
3
0
Bootcamp did seem to work fine, but windows uses different driver protocols then does Mac OS. As I shared in my previous post, this is very likely a hardware issue.
 

psychodalien

macrumors newbie
Jul 25, 2018
5
0
Bootcamp did seem to work fine, but windows uses different driver protocols then does Mac OS. As I shared in my previous post, this is very likely a hardware issue.
So if it's a hardware issue then it should also be present in Windows, isn't it?
 

des011

macrumors newbie
Jan 24, 2012
3
0
I'm getting shutdowns again on Catalina 10.15.2 (19C57).
I've successfully used the kext deletion / renaming trick for over a year last successful on 10.15.1.

Can people please report in, as I assume I'm not alone here.

Ok seems the python script is still working fine as an alternative on Catalina 10.15.2 (19C57), I never used this approach before, prefered the kext trick instead.
But now I'm using the python script and this method with automator here (page is sometimes slow to load)
 

eagletg

macrumors newbie
Dec 27, 2019
1
1
Hi Everyone,

This thread has been amazingly helpful in keeping my MacBook Pro 2013 happy. Thanks to all that have contributed up until this point.

Things have been great until the latest Catalina update was applied, 10.15.2 (as indicated above). The problem has returned. Basically, I noticed it most when utilizing Google Chrome, the screen would go black (but was still powered-on/lit), sometimes fans would spin up, after 30 or so seconds, the machine would hard power down. Nothing indicated in any of the system logs/console.

I found information on Reddit regarding removing/renaming the IOThunderboltFamily.kext in addition to AppleThunderboltNHI.kext, but that did not seem to correct the issue for me.

I decided to try the nuclear option and rename everything containing "Thunderbolt" in the /System/Library/Extensions folder.

So far, this seems to have helped. I've been up and running on this machine far longer than I've been previously since installing 10.15.2.

Here's what my /System/Library/Extensions folder looks like now:
Extensions$ ls -ld *Thunderbolt*
drwxr-xr-x@ 3 root wheel 96 Sep 26 00:03 AppleThunderboltDPAdapters_kext.bak
drwxr-xr-x@ 3 root wheel 96 Sep 26 00:10 AppleThunderboltEDMService_kext.bak
drwxr-xr-x@ 3 root wheel 96 Sep 26 00:01 AppleThunderboltIP_kext.bak
drwxr-xr-x@ 3 root wheel 96 Sep 25 23:54 AppleThunderboltNHI_kext.bak
drwxr-xr-x@ 3 root wheel 96 Sep 25 23:58 AppleThunderboltPCIAdapters_kext.bak
drwxr-xr-x@ 3 root wheel 96 Sep 26 00:11 AppleThunderboltUTDM_kext.bak
drwxr-xr-x@ 3 root wheel 96 Aug 24 19:10 IOThunderboltFamily_kext.bak

Naturally, this is probably overkill. If I get some time, I may try to narrow down (likely via trial and error) which exact KEXT is now causing the issue in 10.15.2. For now, it's working for me and seemingly hasn't disabled anything "important" that I've noticed yet. Time will tell.

Edit: Six hours later, not a single crash. Been using the machine basically all day. :)
 
Last edited:

Антон Джига

macrumors newbie
Jan 22, 2020
1
0
Hi Everyone,

This thread has been amazingly helpful in keeping my MacBook Pro 2013 happy. Thanks to all that have contributed up until this point.

Things have been great until the latest Catalina update was applied, 10.15.2 (as indicated above). The problem has returned. Basically, I noticed it most when utilizing Google Chrome, the screen would go black (but was still powered-on/lit), sometimes fans would spin up, after 30 or so seconds, the machine would hard power down. Nothing indicated in any of the system logs/console.

I found information on Reddit regarding removing/renaming the IOThunderboltFamily.kext in addition to AppleThunderboltNHI.kext, but that did not seem to correct the issue for me.

I decided to try the nuclear option and rename everything containing "Thunderbolt" in the /System/Library/Extensions folder.

So far, this seems to have helped. I've been up and running on this machine far longer than I've been previously since installing 10.15.2.

Here's what my /System/Library/Extensions folder looks like now:
Extensions$ ls -ld *Thunderbolt*
drwxr-xr-x@ 3 root wheel 96 Sep 26 00:03 AppleThunderboltDPAdapters_kext.bak
drwxr-xr-x@ 3 root wheel 96 Sep 26 00:10 AppleThunderboltEDMService_kext.bak
drwxr-xr-x@ 3 root wheel 96 Sep 26 00:01 AppleThunderboltIP_kext.bak
drwxr-xr-x@ 3 root wheel 96 Sep 25 23:54 AppleThunderboltNHI_kext.bak
drwxr-xr-x@ 3 root wheel 96 Sep 25 23:58 AppleThunderboltPCIAdapters_kext.bak
drwxr-xr-x@ 3 root wheel 96 Sep 26 00:11 AppleThunderboltUTDM_kext.bak
drwxr-xr-x@ 3 root wheel 96 Aug 24 19:10 IOThunderboltFamily_kext.bak

Naturally, this is probably overkill. If I get some time, I may try to narrow down (likely via trial and error) which exact KEXT is now causing the issue in 10.15.2. For now, it's working for me and seemingly hasn't disabled anything "important" that I've noticed yet. Time will tell.

Edit: Six hours later, not a single crash. Been using the machine basically all day. :)
Thanks for this solution! Stuck into the same problem with 10.15.2 update. Disabling all Thundebolt extensions helped in my case (Macbook pro 2014). Did you have a chance to figure out which Thunderbolt component causing the error?
 

maciek1422

macrumors newbie
Oct 29, 2017
14
1
I was having the same issues with random shutdowns and the thunderbolt trick worked until 15.2. I downgraded to Mojave and the disabling of the thunderbolt no longer worked. After nearly a month with this problem and countless calls to support, Apple replaced my logic board and both of my speakers...I wasn't aware of a problem with the speakers though. I just received my fixed MacBook Pro 15 inch 2014. Im typing this response on it now, and thus far...no shutdowns. This is a hardware issue folks. Renaming/disabling the thunderbolt essentially is delaying inevitable hardware failure. It's a faulty capacitor on the circuit going to the AMD chip on the logic board. Apple did replace both parts for me free of charge(speakers and logic board)...I am grateful for how they responded. However, I'm not certain that the actual defect was addressed. There are known issues with the logic boards manufactured in several MacBook Pro models sold from 2012-2014. My advice is to speak to support...be calm and courteous....they may remedy your problem without cost even though you're far past warranty; at this point, you have nothing to lose.
You were speaking or texting with support? You have official Apple Stores in your country? I have tried many times to get it repair, but they don't fix it. I have Late 2013, so I have it for 5,5 years I think, it's probably too long to get support. But maybe I will try again. It's still a nice laptop, but still having python script running is annoying...