Constant kernel panics after macOS High Sierra upgrade

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/DiagnosticReports

<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)

.

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.

javiquil wrote:

I'm having same issue with the same macbook model since I upgraded to High Sierra...

Every 20 minutes or so... kernel panic and It's restart.

Any advice?

Try a clean install on a separate drive. You will probably find that it works just fine.

Problems are almost always due to other software that was there but is not compatible with the new OS.

One should always have two backups before doing a major upgrade.

One of those should be a full bootable clone, so in case of crisis you can immediately run the old system just as before.

Installing on to a clean drive almost always ensures a stable system.

One can then use Migration Assistant to bring back user accounts.

Applications can be easily redownloaded fresh from the App Store (gone are the days of sifting through discs and looking for serial numbers, when a clean install was really painful).

I have the same computer and a very similar problem.

After the High Sierra upgrade, I was getting kernel panics at the rate of 1-2/day. Have been debugging with Apple tech support with assist from Apple Engineering.

They too suggested third party kernel extensions - and the only way to remove them was erase and install and then intentionally NOT using Migration Assistant and copying relevant data manually from backup. I found some ancient extensions (some going back a decade to previous machines and ancient versions of the OS). Good opportunity to clear out cruft.

Until - I got a kernel panic on the install. Clearly NOT a problem with third party extensions.

This first install was from the recovery disk. Advised to do a network recovery.

That worked. Clean drive. New OS.

Until started copying data from backup to clean new file system - immediate kernel panic.

Clearly NOT third party extensions.

Took to local Apple service location for hardware diagnostics. None found. Somehow this service location convinced Apple to replace logic board and SSD.

New OS. Copied ~.8TB of data back.

No kernel panics. Now ~ 4 days using many of my standard Mac apps and Win10 VM apps. No kernel panics.

I am convinced there is some low level hardware/firmware (intermittent) incompatibility with (some?) SSD drives and APFS in High Sierra. My pattern of kernel panics was correlated to high volume I/O involving the SSD. Swapping to virtual memory. DropBox and iCloud syncing. File copy. The third party kernel extensions was (likely) a red herring.

Although most KP events are caused by defective hardware including aftermarket modifications, non-Apple device drivers and kernel extensions can also cause them to occur.

If you want to identify possible problematic kernel extensions, use System Information. It is in your Mac's Utilities folder.

The System Information app will open. From the left column select Software > Extensions. Wait for it to populate, then select "Obtained from" to sort the list by source. It is normal to see several kernel extensions that are not obtained from Apple. They may be from an "Identified Developer", "Unsigned", or "Unknown". None of those categories necessarily imply anything amiss, but those are the ones deserving of scrutiny. If you are uncertain, provide their names in a reply to this Discussion.

Other ways of launching System Information:

• Select  (Apple menu) > About This Mac > System Report...
• Or, hold an option key while clicking the  menu, and select System Information...

Could you please post some of your 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.

It might also be interesting if you post the EtreCheck output as a "Reply" to this thread

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

Use the EtreCheck "Share" button to "Copy Report" (See the image below)

And then Paste in 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.

I'm also having kernel panics after upgrading to High Sierra.

Yes, it appears you are and you actually have third-party kernel extensions loading. So, you need to uninstall those products following the developer's instructions. If the panics cease, install one-at-a-time until you find the one causing the problems:

com.vmware.kext.vmci 90.8.1

com.webroot.driver.WebrootSecureAnywhere 126

com.epson.driver.EPSONProjectorAudio 1.40

com.logitech.manager.kernel.driver 6.70.1

My guess would be WebRoot as all of that ill-designed and useless crap always causes problems.

Logitech would be my second guess as it always has issues when you update the OS.

panic(cpu 1 caller 0xffffff801732e72a): "_MALLOC: kalloc returned NULL (potential leak), size

Yours panic indicates a memory issue, so it could be your RAM. If you still have panics after uninstalling all of that software, then you should check the RAM.

I don't know if this will help anyone but it was a 100% solution for me, so I'll report.....

I have an iMac running High Sierra 10.3.2 and I was getting one or two kernel panics a day since going to High Sierra.

Tried a bunch of stuff that did not work. Called AppleCare, they were nice but of no help except to tell me to bring it to Genius Bar.

But reading that wacky crash report, it had the following line: "BSD process name corresponding to current thread: virusbarrierd"

So I uninstalled my Intego Virus Barrier X6, and have not had a single kernel panic, going on 15 days now.

The kernel panic backtrace says you are in the audio stack and EXPLICITLY mentions YamahaSteinbergUSBAudio as the bit of code running when the panic occurred.

Kernel Extensions in backtrace:

jp.co.yamaha.driver.YamahaSteinbergUSBAudio(1.9.22)[5B137C01-2AF1-34FF-062C-02E 2C7CFD6E8]@0xffffff7fa46f3000->0xffffff7fa470cfff

dependency: com.apple.iokit.IOAudioFamily(206.5)[2F090399-C028-3F14-AE4F-BF49A3D602E5]@0xff ffff7fa4506000

dependency: com.apple.iokit.IOUSBFamily(900.4.1)[FD04D3BC-D376-36FD-924C-DD5DF51B0509]@0xff ffff7fa4646000

jp.co.yamaha.driver.YamahaSteinbergUSBAudio 1.9.22

Us the YamahaSteinbergUSBAudio vendor's uninstaller to remove the code, and especially the kernel extension that is causing your panic.

I'd say you have old stuff that came from previous versions, including kernel extensions.

Please run Etrecheck and post its report here. For mere mortals like me and others on this forum, the information of the Etrecheck report is far more ellucidating the the KP report. I believe you will see that too.

Had the same problems. Turns out for me it where Chrome plugins (trusted ones) in combination with High Sierra!

Never ever had any problems with Sierra and never had any kernel panic in four years on my macbook.

Turns out it caused problems before:

https://www.reddit.com/r/osx/comments/55rcuk/google_chrome_causing_a_kernel_pani c/

https://www.tonymacx86.com/threads/opening-google-chrome-causes-instant-kernel-p anics.210265/

https://discussions.apple.com/thread/6631528

https://productforums.google.com/forum/#!topic/chrome/NcKFPnppV_s

Maybe it's even the hardware-accelerated-css which kills the GPU...

https://apple.stackexchange.com/questions/285146/gpu-panic-cpp-143-macos-sierra- 10-12-5-stability-issues-and-spontaneous-restarts/287511

panic(cpu 0 caller 0xffffff7f857f7f95): nvme: "InitializeNVMe error = 0xE00002D7\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONV MeFamily-356.50.26/AppleNVMeController.cpp:389

If you are getting this panic repeatedly, I think maybe your solid state storage is failing. the NVMe is bus attached SSD storage.

You should make a Genius Bar appointment at your local Apple store and have them evaluate your system.

The only 3rd party kernel extension you have is

com.malwarebytes.mbam.rtprotection 3.2.36

While the long time forum contributers often recommend MalwareBytes (as the Mac verison was written by a long time forum contributor), it is still a kernel extension, and as such can get into trouble when a new macOS version is released.

I would suggest uninstalling MalwareBytes for now, and see if the problems continue

<https://support.malwarebytes.com/docs/DOC-1928>

Since the only current forms of malware affecting macOS are ones where the user is tricked into installing it, you can always re-install MalwareBytes after you have installed something to make sure whatever you installed in not carrying a malware side-package.

If removing MalwareBytes does not stop the system panics, you might consider whether your 3rd party RAM is causing problems.

You could run

Rember

<http://www.kelleycomputing.net/rember/>

.

Quit as many apps and background tasks as you can (such as menu bar items) so more RAM is available for testing. Booting into Safe mode <http://support.apple.com/kb/ht1564> can also free up more RAM for testing, by not loading any 3rd party additions you may have installed.

.

Set Loops: [X] Maximum

and run overnight

You could also move the 8GB DIMMs into the slots currently used by the 2GB DIMMs, and put the 2GB DIMMs in the previous 8GB DIMM slots.

You could also try removing the DIMMs one at a time to see if the problem goes away.

Start by uninstalling the following three 3rd party kernel extensions usng the vendor's uninstall utility or instructions.

com.techsmith.TACC 1.0.3

com.Apowersoft.driver.AudioDevice 1.6.7

at.obdev.nke.LittleSnitch 4740

If they are not the cause, you can always re-install them.

Is the RAM original, or have you replaced the factor RAM with 3rd party RAM? I ask, because it is common for 3rd party RAM to introduce kernel panics.

Do you have any USB devices plugged into your Mac? I ask because broken USB devices or just a broken USB cable have been known to cause kernel panics.

com.cisco.kext.acsock 4.5.0

org.virtualbox.kext.VBoxNetAdp 5.2.18

org.virtualbox.kext.VBoxNetFlt 5.2.18

org.virtualbox.kext.VBoxUSB 5.2.18

org.virtualbox.kext.VBoxDrv 5.2.18

com.paragon-software.filesystems.ntfs 319.2.15

com.Apowersoft.driver.AudioDevice 1.6.7

com.logmein.driver.LogMeInSoundDriver 4.1.84f17

at.obdev.nke.LittleSnitch 5187

Potential candidates.

The backtrace was in the APFS file system driver. Paragon NTFS driver is also file system related. That is a slightly more likely candidate. Not a lock in, as any of the other ones listed are still candidates until you have resolved this.

Did you migrate everything after that clean install?

You may want to run the diagnostic tool Etrecheck and post its report here.