Constant kernel panics after macOS High Sierra upgrade

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/

Everything in the Loaded kexts section of the report may have caused the panic.

You can uninstall all and reinstall one-at-a-time, or remove one at a time. Since it appears to be file system related, I’d start with paragon.

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.

I'm just going to repeat what happened to me. I was getting kernel panics everyday. I uninstalled Intego Virus Barrier X6 and haven't had a kernel panic in the last 6 weeks.

Sorry I have no idea what VPN is, but my case shows that kernel panics can happen because of software conflicts, not just hardware.

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.

In addition to Bob's advice, you may also run the diagnostic tool Etrecheck and post its report here.

It may well

bernadettefromleiden wrote:

I have Finder, but no option to Go -> Go to Folder -> /Library/Logs/DiagnosticReports.

Sure you do.

This brings up a window, where you are supposed to type the folder path.

Is there a panic log in /Library/Logs/DiagnosticReports/?

The name will start with kernel and end with .panic.

If there is, open it, copy the text and post here.

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.

"thread_call group 'high' reached max thread cap (500): active: 1, blocked: 499, idle: 0"

Interesting. This is not a typical kernel panic.

You do not have any 3rd party kernel additions. It appears to be the original 4GB of RAM.

I other words, the common ways to experience kernel panics do not appear in your panic report.

I said the panic message was interesting, as it seems to indicate that software you were running, attempted to create too many threads of execution.

I would suspect the software you were running at the time of the panic as being suspect.

Unless you can narrow it down to running a specific app, this could be a messy problem to diagnose.

Just in case this helps too: noticed @Bob Harris mentioned it in first few threads.

EtreCheck version: 4.1 (4A162)

Report generated: 2018-03-06 23:46:36

Download EtreCheck from https://etrecheck.com

Runtime: 2:37

Performance: Excellent

Problem: Computer is restarting

Description:

Kernel panics

Major Issues: None

Minor Issues:

These issues do not need immediate attention but they may indicate future problems.

Small backup drive - Time Machine backup drive is too small.

32-bit Apps - This machine has 32-bits apps that may have problems in the future.

Hardware Information:

MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports)

MacBook Pro Model: MacBookPro14,1

1 2.3 GHz Intel Core i5 (i5-7360U) CPU: 2-core

8 RAM Not upgradeable

BANK 0/DIMM0

4 GB LPDDR3 2133 ok

BANK 1/DIMM0

4 GB LPDDR3 2133 ok

Battery: Health = Normal - Cycle count = 58

Video Information:

Intel Iris Plus Graphics 640 - VRAM: 1536 MB

Color LCD 2880 x 1800

Drives:

disk0 - APPLE SSD SM0256L 251.00 GB (Solid State - TRIM: Yes)

Internal PCI-Express 8.0 GT/s x4 NVM Express

disk0s1 - EFI [EFI] 315 MB

disk0s2 250.69 GB

disk1s1 - Macintosh HD (APFS) 250.69 GB 32.49 GB

disk1s2 - Preboot (APFS) [APFS Preboot] 250.69 GB 23 MB

disk1s3 - Recovery (APFS) [Recovery] 250.69 GB 510 MB

disk1s4 - VM (APFS) [APFS VM] 250.69 GB 1.07 GB

Mounted Volumes:

disk1s1 - Macintosh HD 250.69 GB (216.45 GB free)

APFS

Mount point: /

Encrypted

disk1s4 - VM [APFS VM] 250.69 GB (216.45 GB free)

APFS

Mount point: /private/var/vm

Network:

Interface en0: Wi-Fi

802.11 a/b/g/n/ac

One IPv4 address

Interface en3: Bluetooth PAN

Interface bridge0: Thunderbolt Bridge

System Software:

macOS High Sierra 10.13.3 (17D102)

Time since boot: About an hour

System Load: 1.91 (1 min ago) 1.25 (5 min ago) 1.16 (15 min ago)

Security:

32-bit Applications:

System Launch Agents:

System Launch Daemons:

User Launch Agents:

User Login Items:

iTunesHelper Application (Apple, Inc. - installed 2018-02-09)

(/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)

Internet Plug-ins:

QuickTime Plugin: 7.7.3 (installed 2018-01-19)

Time Machine:

Skip System Files:

Mobile backups:

Auto backup: Yes

Volumes being backed up:

Macintosh HD: Disk size: 250.69 GB - Disk used: 34.23 GB

Destinations:

B********p [Local] (Last used)

Total size: 0 B

Total number of backups: 8

Oldest backup: 2017-11-19 15:04:42

Last backup: 2018-02-08 23:01:20

Top Processes by CPU:

Top Processes by Memory:

Top Processes by Network Use:

Top Processes by Energy Use:

Virtual Memory Information:

Diagnostics Information (past 7 days):

2018-03-04 19:34:55 findmydeviced Crash

2018-02-09 20:28:14 Kernel Kernel Panic

End of report

Internal PCI-Express 8.0 GT/s x4 NVM Express

panic(cpu 0 caller 0xffffff7f9640da3c): nvme: "Fatal error occurred. CSTS=0xffffffff

Combining the kernel panic report with the EtreCheck output, the nvme from the panic report is your NVM Express storage.

Since you have a 2017 Mac, I suspect it might still be under full warranty. Make a Genius Bar appointment at your local Apple store and see about getting your Mac repaired.

Basically I agree with Luis Sequeira1

Reply to janet99x

Kernel Extensions in backtrace:

com.apple.kext.AMDRadeonX4000(1.6)[1069DE07-9A4D-3E0D-8664-1906A6A08124]@0xffff ff7f8f02d000->0xffffff7f8f8affff

dependency: com.apple.iokit.IOSurface(209.2.2)[AE58720D-7079-388F-AD95-FD2366F98F8D]@0xffff ff7f8ef6b000

dependency: com.apple.iokit.IOPCIFamily(2.9)[8E6C654E-4A8F-3C6B-BBFE-BA8A68C9C146]@0xffffff 7f8cc94000

dependency: com.apple.iokit.IOGraphicsFamily(517.22)[2AEA02BF-2A38-3674-A187-E5F610FD65B7]@ 0xffffff7f8d435000

dependency: com.apple.iokit.IOAcceleratorFamily2(376.6)[5F8F39B4-41AB-3263-9867-D0FAF9BBD2A E]@0xffffff7f8ef87000

I suspect you have a graphics card issue

RJHMUSIC wrote:

To simply say to uninstall the products that are causing the problem is a cop out. By the way, those products all ran fine on OSX 10.12. SO if they cause kernel panics on OSX 10.13 then in my opinion OSX 10.13 should not have been brought to the market before it was perfectly stable. I thought only Microsoft did things like that. And.... if i uninstall all of the products that cause a kernel panic, then i would not need the computer would I?

Wow, that is simply not how computers work.

You are correct if an app is just a user space app, it should never cause any issues with the kernel, but today many apps install kernel extensions ("kext"s). The kernel changes between OS releases, and if Apple changes things between releases an extension that directly manipulated kernel information some way in one release may well cause a panic in another, and it's the fault of the app developer simply because Apple always gives developers ample notice of these changes (and generally goes through at least six months of a beta program where the app developer could have watched their app crash and burn.)

To use a "Fast and Furious" analogy, if you buy a Chevy then immediately bolt on a supercharger and a nitrous system, when the engine blows up it's not necessarily because Chevy made a bad engine to begin with.

Uninstalling products is a tool; if you find out a particular app causes macOS to fall over, yes, Apple should fix it but they will have greater impetus to do so if say Adobe complains about it than if you do, but Adobe would never know if you didn't track down that it's occurring because you have Photoshop CC installed.

If you've had "nothing but panics" for weeks now, why haven't you been back to the Apple Store to diagnose what's wrong with your new machine? It may be defective as well - even balls on roulette wheels can land on the same number twice in a row. High Sierra is stable for the vast majority of users, faster too. That doesn't, however mean there isn't someone with just the right configuration to make it unstable, and odds are an install of Sierra will if anything be more unstable than High Sierra.

There's no reason why it should take you weeks to get everything up and running nor why a machine out of the box should fail or have other issues, but the latter cases do happen, these are machines made by humans.

Try this and see if it turns up anything:

How to use Apple Diagnostics on your Mac - Apple Support

mbk216 wrote:

So what does this mean to someone who doesn't understand all of this tech talk? 🙂

Do you have an external WiFi device plugged into a USB or Thunderbolt slot?

Do you have any external devices plugged in. Bad USB devices have been known to put bad things on the internal data bus.

It could also be failing hardware.

It could be a corrupt file system giving wrong bits for programs.