Constant kernel panics after macOS High Sierra upgrade

I have a MacBook Pro (Retina, 13-inch, Late 2013, 250 GB SSD, 16 GB RAM). I have experienced constant kernel panics after macOS High Sierra upgrade, from Sierra. (Under Sierra 10.12.5 the Mac was as stable as one would expect.)


In High Sierra the OS would boot and almost immediately go into kernel panic. I reinstalled the OS from OS X Recovery (having run Disk First Aid, which revealed no problem) and it worked OK for a couple of days.


I restarted (having noticed an odd behaviour in Contacts) and the problem recurred. Again I had a kernel panics 60-120 seconds after restart, or immediately the Finder started to load.


I again reinstalled the OS from OS X Recovery but the panics continued. I ran Disk First Aid again, which revealed no problem. The kernel panics occurred when booted in Safe Mode too. However, if I logged into a 'plain vanilla' user account the problems didn't occur. This would, I believe, indicate there isn't a problem with the hardware or RAM.


I suspected an rogue extension, and have been trying to uninstall apps that load code or extensions at startup, such as FullContact, Skitch, Yoink, CleanMyMac, and Things. To no avail.


I contacted Apple Support for advice on how to disable or remove other third party extensions but they said there was no method for doing this. They advised backing up, erasing the drive, reinstalling macOS, and restoring the backed up data but if the problem is extension-related it would likely recur.


The closest related post I have found is Kernel panic after latest osx Sierra update, but that only gets me so far. Any advice would be welcomed.

MacBook Pro (Retina, 13-inch, Late 2013), macOS High Sierra (10.13)

Posted on Oct 5, 2017 3:25 PM

Reply
Question marked as Top-ranking reply

Posted on Apr 30, 2018 7:14 PM

RJHMUSIC,


We need to see the panics you are getting to be helpful. As this is a user-to-user technical support fourm, we need information.


Please post the most recent kernel panic report(s). If you have more than one, it would be useful to see a few, as whether they are consistant or change will give us useful information.

Kernel Panic reports: Finder -> Go -> Go to Folder -> /Library/Logs/DiagnosticReportsUser uploaded file

<http://support.apple.com/kb/ht2546>

<http://support.apple.com/en-us/HT200553>

The panic report should have "panic" in the file name.


It would also be useful to see what, if any, 3rd party additions have been installed. This too can help diagnose your system.

Please post the EtreCheck output as a "Reply" to this thread

<https://discussions.apple.com/docs/DOC-6174> or <https://etrecheck.com>

Use the EtreCheck -> Edit -> Copy Report (See the image below)

User uploaded file

.

And then Paste the report as a "Reply" to this thread.

If, AND ONLY IF, you get the error:

"The message contains invalid characters"

then try posting to PasteBin.com, and give us a PasteBin URL link.

<http://pastebin.com/>

.

EtreCheck is a tool that helps Apple Support Community volunteers debug problems without any access to the troubled computers. Debugging problems can be a difficult task even when the machine is in front of you. Attempting it via a discussion forum is extremely difficult. EtreCheck is a great help that regards.


It is possible you have a hardware issue, but we can only look at the information you give us, and then may recommendataions.

137 replies

Oct 9, 2017 4:01 PM in response to Nico Macdonald

panic(cpu 2 caller 0xffffff7f814f8c42): "ino 387353215 you must have an extent covering the alloced size 370049024 (fsize 353271808) orig_pos 370049024:0 err 2\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/apfs/apfs-748.1.46/nx/jobj .c:12043

com.apple.filesystems.apfs(748.1.46)[CA424079-AA66-370B-A9AB-D80ED4C92667]@0xff ffff7f81493000->0xffffff7f81569fff

The new APFS file system is panic'ing your kernel.


Congratulations, you have reported a new kind of kernel panic, which I'm not sure anyone knows what to do with.


I would start with booting into the Recovery partition (Boot holding Command-R, or Internet Recoverey by booting holding Command-Option-R).


Use the Disk Utility when booted from the recovery partition and run Disk Firstaid against your boot disk. Hopefully it will clear up any problems.


Just in case, hopefully you have a current backup, just in case you have to restore the disk from a backup.

Oct 10, 2017 7:06 AM in response to Nico Macdonald

I managed to get my high sierra disk to boot again.


I've move all my *.kext file from /Library/Extensions/ to an other directory.

My system started up just fine and everything seems to work as it should, Although I would believe that it would need the kext files I have removed.


The /Library/Extensions stays empty though, I am not sure if I can figure out which *.kext was causing the system to panic. As far as I know they should be in /System/Library/Extensions.


What I don't understand is that the timestamps have not changed, which I would expect if the system fails after a reboot on a (corrupt) kext driver.


Here's my list in case someone wants to know, only the GeForce and NVDA kext files are in my /System/Library/Extensions directory.


User uploaded file

Mar 29, 2018 6:12 AM in response to bernadettefromleiden

Reply to bernadettefromleiden

Both panic reports are more or less identical "overflow detected" in the networking stack

panic(CPU 3): "overflow detected"


Kernel Extensions in backtrace:

com.apple.iokit.IO80211Family(1200.12.2)

dependency: com.apple.driver.corecapture(1.0.4)

dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)

dependency: com.apple.kec.corecrypto(1.0)

dependency: com.apple.iokit.IONetworkingFamily(3.4)

com.apple.driver.AirPort.BrcmNIC(1220.28.1a3)

dependency: com.apple.driver.corecapture(1.0.4)

dependency: com.apple.driver.mDNSOffloadUserClient(1.0.1b8)

dependency: com.apple.iokit.IO80211Family(1200.12.2)

dependency: com.apple.iokit.IOPCIFamily(2.9)

dependency: com.apple.iokit.IONetworkingFamily(3.4)

However, I do not have a clue what "overflow detected" refers to.


I did some Google searches and I did not find anything that seems to be related.


Since you keep getting these panics, and the panic (at least in 2 instances) is consistent, I would take 2 approaches.


A) maybe do a re-install of macOS overtop of your existing install (always make a backup first, "Just In Case".


B) consider making a Genius Bar appointment, and have them test your hardware. MAKE sure you show them the kernel panic reports.


C) spend a lot more time doing your own web searches to see if you can find other instances of this kernel panic. I only spent a few minutes in a coffee shop searching, so my results are not conclusive.

Jul 18, 2018 5:35 AM in response to Nico Macdonald

i recently had this same kernal panic crash/reboot issue going on. after a few weeks of dealing with it, i saw someone suggested running software called etrecheck. its free, and gives you some further details about issues going on with your system. min happened to be mdworker using 175% of my CPU. learned that it had to do with spotlight indexing (something i have literally never used in 8 years of using mac) so i disabled it (spotlight). you will have to command+R during reboot and disable SIP in terminal, reboot, then disable spotlight, then command+R reboot again and reenable SIP. since doing that, i have not had another crash... yet... im starting to think that High Sierra is complete garbage.

https://www.macworld.co.uk/how-to/mac/how-turn-off-mac-os-x-system-integrity-pro tection-rootless-3638975/



http://recomhub.com/blog/how-to-turn-off-and-on-spotlight-in-mac-os-sierra/

Dec 2, 2017 7:24 PM in response to Troglos

panic: "vnode_put(0xffffff804508bf80): iocount < 1"@/.../vfs/v fs_subr.c:4507

This panic is file system related. A vnode is an internal OS data structure used to keep track of an open file. A put is what the OS does when the thread using that file is releasing it. The iocount is used to make sure the OS does not free the data structure and use the memory for something else, or associate it with a different file.


The iocount < 1 means the vnode was released more times than it was reserved.


This is generally a bug in the kernel software or a kernel extension that was using the file.


Since this is High Sierra the question is, do you have an SSD on your Mac mini or a rotating hard disk. An SSD would have been converted to APFS, which is rather new software, so there is always a chance it is at fault.


But if you have a rotating hard disk, then you would have HFS+ which is very stable software.


And regardless of whether APFS or HFS+ is the file system, ANY "Kernel Extension" could mess up accessing the file system, so yes the VirtualBox Kernel Extensions would use vnode_put() just like any other kernel extension to access files, and VirtualBox needs to access files as part of its normal operations.

Dec 3, 2017 7:39 AM in response to Troglos

Keep your virtual machine image, and just temporarily remove VirtualBox. If the system still failed, it is NOT VirtualBox and you can reinstall and continue to use your saved virtual image.


And if having NO 3rd party kernel extensions and it still panics, you should file a bug report with Apple

BugReporter (Free ADC (Apple Developer Connection)) account needed for BugReporter

<http://bugreporter.apple.com>

Anyone can get a free ADC account at:

<https://developer.apple.com/register/index.action>

Dec 30, 2017 6:37 PM in response to AppleMac1990

AppleMac1990 wrote:

Here's my kernel panic:

.

.

.

Most likely this is what caused your panic

com.webroot.driver.WebrootSecureAnywhere 64

Suggest uninstalling whatever this 3rd party kernel extension is, an do not install it again.


If this is part of an anti-virus package, do not install it nor any other anti-virus package. Generally on the Mac, all anti-virus packages do is waste your Mac's resources looking for Windows malware, while making your Mac unstable, consuming electricity, and slowing down your Mac, all the while allowing annoying adware have free rain on the Mac.


If you are just plan paranoid, then look at the free version of MalwareBytes, and ONLY run it when you want to check, and do not have it running all the time.

Feb 7, 2018 12:16 PM in response to dovad

Kernel Extensions in backtrace:
com.apple.driver.AirPort.BrcmNIC(1220.28.1a3)[816C62A1-7F51-35B7-8F71-9936D56657 7C]@0xffffff7f8944b000->0xffffff7f89c00fff
dependency: com.apple.driver.corecapture(1.0.4)[F0C23182-01CA-3C3D-BA00-A39C4BED75AE]@0xfff fff7f89313000
dependency: com.apple.driver.mDNSOffloadUserClient(1.0.1b8)[EE7B82F9-F4B1-39F5-9CE8-02661C0 18C68]@0xffffff7f89345000
dependency: com.apple.iokit.IO80211Family(1200.12.2)[DBDAB567-E27E-3387-8FA8-AA5ACC6DA48E]@ 0xffffff7f8934c000
dependency: com.apple.iokit.IOPCIFamily(2.9)[8E6C654E-4A8F-3C6B-BBFE-BA8A68C9C146]@0xffffff 7f88694000
dependency: com.apple.iokit.IONetworkingFamily(3.4)[17D64D9A-AE76-391D-8C42-6DBC6686333B]@0 xffffff7f88a08000

This panic is happening in the WiFi stack.

Mar 28, 2018 5:52 PM in response to bernadettefromleiden

bernadettefromleiden wrote:


I have noticed that I have no kernel panic when I am connected with the internet. When my MacBook Air is nog able to find my personal hotspot, my laptop goes in kernel panic. The moment my laptop finds my personal hotspot, everything is ok. Also, my wifi at home: no problem. So apparently it seems to have something to do with a internet connection...

It would be interesting to see the kernel panic reports

Kernel Panic reports: Finder -> Go -> Go to Folder -> /Library/Logs/DiagnosticReports

<http://support.apple.com/kb/ht2546>

<http://support.apple.com/en-us/HT200553>

The panic report should have "panic" in the file name.

Oct 10, 2017 1:06 PM in response to BobHarris

It's easy to gun down someone who runs OS X High Sierra on an unsupported system, even when its a full Mac. Nevertheless I had the same issue, system panics after High Sierra upgrade.The cause might be different. Graphics or whatever, both systems failed and panicked. I was just trying to run down the problem and help others. I should have know better, instead of trying to fix the problem I should have known I would get answers like this.


Maybe Nico is still willing to look if his system will boot when he moves the /Library/Extensions/*.kext files to an other place, narrowing it down to 3th part extensions. At least his system will boot if the problem would be there, still beats a total re-install.


I'll step out and sort out my own things, at least I have my system up an running, smoothly, even though its abandoned.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Constant kernel panics after macOS High Sierra upgrade

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.