Separate names with a comma.
Discussion in 'macOS Sierra (10.12)' started by mokhan23, Mar 30, 2017.
It seems to be working for me also. I'll keep testing it. Thank you!!
Thank you so much!
You did what Apple Support and two different New York Apple Store Genius Bars couldn't do, you figured this out!
I had the same twisted random shut down problem which rendered my $3000 macbook completely unusable. I disabled AppleThunderboltNHI.kext per your instructions and I"VE GOT MY MAC BACK.
Yeah, it works. But I don't think is a definitive solution, during this week I've had two reboots (one of them was not waking up from sleep and the other one a kernel panic)... at least both of them showed me the error report at startup.
I thought it work for me too, but it's not Mac still freezing, not as often as before, but it's not a solution for me, so I'm using python script again.
Thanks @OlegK0! I can confirm that this solution seems to fix the issue (even though it's still a mystery what actually is the issue).
Full details: I'm running 10.12.6. I turned off the Python script and disabled AppleThunderboltNHI.kext 6 days ago. I have not experienced any shutdown yet.
It's been 4 days and I haven't had a shut down yet. FYI When I disabled the thunderbolt ktext file I also upgraded to the newest version of High Sierra.
I copied it somewhere else, but now it's "can’t be modified or deleted because it’s required by macOS."
To others: easy way to reach the folder is open Spotlight Search and paste the path "/System/Library/Extensions" (took me a few minutes to get this after trying other options)
Did you disable csrutil?
Yes, it's working perfectly! Thank you!
Guys nicoguzman as found the grail.
One week of constant use now without a single shutdown.
Is it not strange that all these people started having problem at the same time?
The theory is that it is related with one of latest upgrades BUT somebody was experiencing the problem back in July: https://apple.stackexchange.com/que...ns-and-shuts-off-after-a-few-minutes-use?rq=1
Is this the symptom of some new stealthy spyware that is spreading?
What if it is something that lives in the firmware for Thunderbolt Ethernet adapters and it does not work with this new driver?
My MBP15" late 2015 is also running stable for 2 weeks now since i deleted "AppleThunderboltNHI.kext"
I did not test if my thunderbolt eth adapter is still working but since i got a bunch of usb eth adapter this would be a big deal. My external thunderbolt displays still work so far.
Hi guys, I have MBP Late 2013, running High Sierra 10.13.2 and if I remove "AppleThunderboltNHI.kext", my thunderbolt is not loaded at all. It's interesting that for some of you, thunderbolt is still working.
But yes, this fix works for my model as well, but for the price of a non-working thunderbolt.
Since removing "AppleThunderboltNHI.kext" my Mac is still running perfectly as far as shutdowns go, but I havent tried Thunderbolt yet so can't testify to that.
Any idea why this is happening:
$ sudo /usr/libexec/firmwarecheckers/ethcheck/ethcheck --integrity-check
Could not find any BCM5701Enet devices or device driver is not supported
I haven't removed: AppleThunderboltNHI.kext
Hi guys, I have signed up to thank you for helping me. I have a late-2013 MacBook Pro 15" and having the same shut down issues, I have deleted AppleThunderboltNHI.kext and it works a treat now.
I have notified apple via bug reporter so hopefully they look in to it for all of us.
Has anyone looked in to the kext file to see if it is a software fault or could it be a hardware fault and when that kext file is trying to work it’s caurseing the shut down?
Has anyone tested reinstalling Yosemite to see if the problem is still present? I have spoke to a few people and every who are not having any problems are on Yosemite. Maybe the kext file from Yosemite can be substituted in sierra and high sierra?
Scrap that, I have just tried a fresh install of Yosemite off external drive and it still happens, soon as the installer has finished and first boot it shuts down.
Hi all, I am experiencing all of the same issues with my mid-2014 15in rMBP. Random shutdowns when not connected to my Thunderbolt Cinema Display.
I attempted the fix disabling the AppleThunderboltNHI but my display wouldn't work after. This unfortunately is a tough place to be in as I split my work time between coffee shops and my home office.
Does anyone know the fix here? Thanks so much. I'm desperate.
Also mid 2014 15 inch rMBP, having the same issues. Python script lets me use my computer but at a significant battery loss.
I used automator to automatically start the script upon startup and hide it, which helps. Submitted a bug request with apple linking to this forum with other people having the same problem. I think this started when updating to 10.13
I posted a note back in April 2017 (see comment #19, quoted at the bottom of this post). The Python script stabilized the system. THANK YOU jerry008 FOR FIGURING THAT ONE OUT!!!
Since my post in April, I've found a few things.
I tried to get my company's Desktop Support Center to open a case with Apple in August of 2017, at the time I was on Sierra (the most-current release at that time). As High Sierra was just around the corner, I was told they couldn't open a case.
<editorialize> Evidently 10.12 wasn't sexy enough for Apple anymore by then? </editorialize>
Apple has discontinued hardware support of my model MBP (late 2013 15" retina). Or, perhaps it's just that Desktop Support has allowed the support contract to lapse. Either way, I can't get hardware support from Apple at all, nor hardware replacement unless there's a recall of some kind, even though I'm now running 10.13.
Having said that, there is evidently a recall on the display. If you have one, I'd take it to an Apple Store and see if they'll at least do that much.
There is another... "something," I'll just copy what Desktop Support wrote in the ticket: "So I did some more research and there is a care program (OP1400) for your model machine, one of symptoms is 'Unexpected system restarts'."
There's evidently a test that a certified support team can run - my Desktop Support Center is certified by Apple to at least the same level (perhaps higher given our volume) as an Apple Store. The test can validate if the issue is related to the care program.
In my specific case, my MBP pro passed the test, so I'm not subject to the care program. However, in the process of running the test, they opened the case and found that my heatsink had actually broken off the mount. I'm due for regular technology refresh in a month anyway, so I'm just riding it out at this point until I get my new circa-2017 MBP.
Desktop Support had absolutely no idea why either running the Python script or attached the Thunderbolt-to-wired-Ethernet dongle stabilized the system. At least in the Python case, you would think that the additional load, however minor, would actually cause the system to heat faster and destabilize it more quickly... but whatever, it worked for the past year and I'm getting a new laptop now, so there's not much more I can do to figure things out.
25% of all MBP at my company are this particular model, I estimate that makes for around 2,000 units. I'm the *only* one exhibiting these symptoms, though my local support technician said that there's some kind of gremlin running around giving off weird artifacts here and there, much more than you would expect (though he didn't have specific numbers).
Upgraded my MacOS to 10.13.3 today and immediatelly had an unexcpected reboot after login, so I checked the /System/Library/Extensions folder and noticed that the AppleThunderboltNHI.kext got restored. deleted it again, rebooted. during the reboot the "install new software" screen showed up again.. after 2 more reboot i was able to login and so far no shutdowns.
Mid-2014 15in MBP reporting in with the same "bug"
Never updated my MBP since 10.12.1
It began to shut off randomly the day after I installed LogMeIn....
Hope it helps
Same here. Worked fine after removing AppleThunderboltNHI.kext, but faced shutdowns immediately after upgrading to MacOS 10.13.3. After removing AppleThunderboltNHI.kext, which was installed again with MacOS 10.13.3, everything is running smoothly for the past week ...
There are anyone who have this problem, but removing thundherboltnhi didn't help them? For my only python script works, so maybe it's a hardware problem. Apple support told me that I should wait for system update, but I have this problem for a year now...