safety – Disabling Thunderbolt-related kernel extensions within the SSV on Large Sur (Random Crashes 2015 Retina MacBook Professional)

EDIT: Don’t do that. This created a startup error that has now compelled me to reinstall my OS from Web Restoration.

I am certainly one of a variety of MacBook Professional customers sadly affected by a longstanding concern apparently associated to defective energy chips on the motherboard of my 2015 Retina MacBook Professional (most notably documented right here in addition to on a variety of Macrumors threads and AD questions). It is my understanding that this concern impacts the the 820-3662 and 820-3787 logic boards. For readability’s sake, I’ve methodically assessed and eradicated most different potential causes for the crashes, and once I initially identified the issue, I went by means of all the everyday steps together with a number of contemporary installs, EtreCheck, and an Apple {hardware} and software program diagnostic (all unremarkable).

This drawback has been reliably solved previously by disabling a number of Thunderbolt-related kernel extensions on the SSV (and reportedly as nicely by this app, although I have not tried it myself), which I have been doing each time I replace the OS.

Most likely towards my higher judgment, I up to date to Large Sur, and after a little bit of discussion board trawling (I’m not a developer and far of that is over my head), my understanding is that Large Sur has, within the means of changing into safer, made it way more tough to put in writing the SSV.

On recommendation from a number of threads and weblog posts, together with the next:

I’ve finished the next:

1. Boot into the Terminal in Restoration Mode (reboot holding Command-R and open Terminal underneath Utilities within the menu bar).
2. mount -uw /Volumes/Macintosh HD (on my Mac, I perceive nomenclature can range).
3. Navigate to the related folder with cd /Methods/Library/Extensions/
4. Rename the related kernel extensions from the suffix .kext to .kext.BAK (disabling them) with mv AppleThunderboltNHI.kext AppleThunderboltNHI.kext.BAK, for instance
5. Repeating the above with every of the related kernel extensions – many customers have been capable of get by with simply disabling the above, others have needed to disable practically all thunderbolt-related kernel extensions. Fortuitously I do not really use these features on my MacBook. The record that I used this time comes from right here and contains:
   • AppleThunderboltDPAdapters.kext
   • AppleThunderboltIP.kext
   • AppleThunderboltPCIAdapters.kext
   • AppleThunderboltEDMService.kext
   • AppleThunderboltUTDM.kext
   • and at last, the above-mentioned AppleThunderboltNHI.kext
6. Disabled protections with csrutil authenticated-root disable
7. “Blessed” the adjustments I’ve made within the snapshot I have been working with with sudo bless --folder /Volumes/Macintosh HD/System/Library/CoreServices --bootefi --create-snapshot
8. Rebooted into regular mode.

To date, looks like it is working (I’ve had no crashes) however I will want to make use of the laptop computer for every week or so to inform – the crashes are pretty unpredictable.

I’ve posted this for 2 functions:

1. I hope that if this works, it is a helpful useful resource for others which are much less savvy, like myself.
2. As talked about, that is nicely above my head and I am hoping somebody can verify my work and ensure I have not finished something fully egregious. For instance, do I must re-enable the techniques protections that I’ve disabled, or does that occur mechanically once I reboot into regular mode?

Thanks a lot on your time, I actually recognize this group.