- Thunderbolt 1.2.1 Update Resolves Kernel Panic Issue For Mac Download
- Thunderbolt 1.2.1 Update Resolves Kernel Panic Issue For Mac 2017
Screenshot: Macbook Pro Kernel Panic My 15″ Macbook Pro with TouchBar had it’s first ever Kernel Panic since I bought it in 2016. It was waking from sleep when it froze/locked up completely before showing the kernel panic grey screen of death. I’ve included the full logs from the Panic Report at the end of this post. If anybody can spot the cause or is having similar kernel panic issues please leave a comment below. My system was up to date (at the time of writing) running macOS High Sierra version 10.13.3 (17D47). Screenshot: About This Mac Initial research mentions third party extensions can cause such issues; below shows the three third party extensions I have installed on this Macbook Pro, all of which were up to date at the time of the kernel panic.
Thunderbolt 1.2.1 Update Resolves Kernel Panic Issue For Mac Download
Screenshot: Currently installed 3rd party extensions I’ve run a full disk first aid check in “Disk Utility” which didn’t find any problems, I’ve also rebooted into single user mode (Command+S during boot) and run. I never had this problem until High Sierra (MBP 15” c.2013, 8Gb RAM 500GbSSD). All software is up to date, and OSX up to date. Other problems unique to High Sierra have included overheating, not shutting down properly, and not waking up after sleep. With the latter, sometimes it recognises that a kernel panic has occurred and other times there’s no evidence of a kernel panic despite not being able to wake it up. In the unix/linux world, and OSX sits on top of BSD, such crashes are unheard of.
Thunderbolt 1.2.1 Update Resolves Kernel Panic Issue For Mac 2017
It’s scandalous that the richest corporation on earth has dragged such a venerable OS as unix/linux through the mud like this.
Every time I start my MacBook, everything works fine. For around 3 minutes.
Afterwards, it crashes with a kernel panic. I am forced to write this question in safe mode, as booting normally will make it crash again. Sounds like you're on the right track with how you've started troubleshooting.
Without knowing exactly what you've already tried, and for the benefit of others, I've outlined how I would normally proceed (keeping in mind that troubleshooting is a process of elimination and does require patience!). Since you've already established the problem is not occurring when booted into Safe Mode then it's time to investigate login items, fonts, and kernel extensions. Investigating login items, fonts, and kernel extensions Let's start with Login Items:. Startup normally.
Go to System Preferences Users & Groups. Select the Login Items tab. Take a note of your Login Items.
Now remove all of them by highlighting them and clicking on the - button below. Restart your computer Now your Mac will boot up without those login items loading. Test to see if you can use your Mac without it crashing:. If you can, you know one (or more) of the Login items were causing the problem. You can then add them back in one by one until you've identified the culprit. Problem solved.
If the problem does persist, it's either a problem with fonts you've installed yourself or with a 3rd party kernel extension. A little more info below: Fonts:- You can remove any of the fonts you've installed yourself to see if this makes a difference. Kernel Extensions:- You can open Terminal (found within your Utilites folder) and enter the following command: kextstat grep -v com.apple The above command will list 3rd party kernel extensions (you may need to stretch the Terminal window so it's easier to read). Look for anything you don't remember installing, or something that belongs to software you've removed, or just anything that looks out of place.
Remember though, this is a list of 3rd party kernel extensions and therefore any of them could be causing the problem. If your Mac continues to crash once you've gone through the above process, I would suggest that continuing to troubleshoot this will cause more frustration and take more time than just cutting your losses and doing a fresh installation of macOS.