Repeated Kernel Panics

No 3rd party kernel extensions.

2017 13" Macbook Pro has fixed RAM and SSD, so no 3rd party options here.

It does not appear you have any USB devices plugged in (I could be wrong about this last part).

So if Booting into Safe Mode, which clears some kernel caches, and then booting normally does not clear things up.

And doing an NVRAM and SMC reset does not help (mostly these 2 are like comfort food)

Reset the System Management Controller (SMC) on your Mac - Apple Support

https://support.apple.com/en-us/HT201295

How to reset NVRAM on your Mac - Apple Support

https://support.apple.com/en-us/HT204063

If not of the above work, then I might suspect a hardware problem.

You can try the hardware diagnostics

https://support.apple.com/en-us/HT201257

These are not as intensive as the ones Apple can run at the Genius Bar, but is something.

If all of the above does not help, then make a Genius Bar appointment at your local Apple Store (or authorized Apple Service center), and see about having your Mac checked out.

kern-panic wrote:

It has not so far. What does this tell me

Would the panic have happened by now? Or is it too soon to be sure.

Safe mode does 3 things.

1. Safe mode deletes the kernel cache, so that the kernel has to repopulate the cashe.
2. Safe mode does not load 3rd party extensions, launch agents, nor launch daemons
3. Safe mode loads some more conservative drivers. For example the graphics driver is much more conservative and you may see your screen flicker with refresh effects from time to time. Other more conservative drivers may also be loaded.

It has happened that cleaning the kernel cache with a Safe mode boot and the booting into normal mode clears up some problems when something in the kernel cashe gets messed up.

Not loading 3rd party stuff, when it comes to panics is most effective when there are 3rd party kernel extensions. You do not have any 3rd party kernel extensions. Other uses for Safe mode would be if there is a performance issue caused by more than just kernel extensions.

Loading more conservative drives may stress the hardware less, and allow a marginal component to not fail, but the more aggressive drivers may push a marginal component into failing.

And if the system still fails in Safe mode, you have eliminated all of the above as being an issue.

You can do the NVRAM and SMC reset anytime you desire. Mostly those are kind-of comfort food, and it dots the i's and crosses the t's but I'm not sure it will change anything, but it will not hurt anything either.

NotMalwareEXE wrote:

Hey I have the exact same system (MacBook Pro 13-inch, 2017, Two Thunderbolt 3 ports running macOS Mojave version 10.14.6), and I've also experienced the panic report. So whatever the problem is, it's not unique to your system.

Kernel Extensions in backtrace:

com.apple.driver.AirPort.BrcmNIC(1400.1.1)[B02492C7-18DA-31C8-B433-2288A0283367]@0xffffff7f940cb000->0xffffff7f94886fff

dependency: com.apple.driver.corecapture(1.0.4)[693051F0-23A6-3D6D-BC04-F65BFBFBC9B0]@0xffffff7f93633000

dependency: com.apple.driver.mDNSOffloadUserClient(1.0.1b8)[A56BE25A-F8A4-39B3-B0B7-4C01B6D9CEF2]@0xffffff7f931db000

dependency: com.apple.iokit.IO80211Family(1200.12.2)[549E5FBE-327A-398B-9021-7D09DEA39396]@0xffffff7f93fce000

dependency: com.apple.iokit.IOPCIFamily(2.9)[F2C92761-0D41-3490-9646-0C34293AD6DB]@0xffffff7f92095000

dependency: com.apple.iokit.IONetworkingFamily(3.4)[75FA72F4-A0A9-36FD-8EAC-C5A4EC24310B]@0xffffff7f92ac7000

There is more to a kernel panic than the backtrace. Maybe you do and maybe you have something unique in you full panic report. Won't know until we see it.

Look for the Kernel Panic reports at:

Finder -> Go -> Go to Folder -> /Library/Logs/DiagnosticReports

more than one report helps establish if there is a trend or random factors involved. Reading kernel reports is often similar to reading "Tea Leaves" and sometimes uncovers nothing. But until we see the tea leaves, it is hard to give any advice.

Hey I have the exact same system (MacBook Pro 13-inch, 2017, Two Thunderbolt 3 ports running macOS Mojave version 10.14.6), and I've also experienced the panic report. So whatever the problem is, it's not unique to your system.

Kernel Extensions in backtrace:
         com.apple.driver.AirPort.BrcmNIC(1400.1.1)[B02492C7-18DA-31C8-B433-2288A0283367]@0xffffff7f940cb000->0xffffff7f94886fff
            dependency: com.apple.driver.corecapture(1.0.4)[693051F0-23A6-3D6D-BC04-F65BFBFBC9B0]@0xffffff7f93633000
            dependency: com.apple.driver.mDNSOffloadUserClient(1.0.1b8)[A56BE25A-F8A4-39B3-B0B7-4C01B6D9CEF2]@0xffffff7f931db000
            dependency: com.apple.iokit.IO80211Family(1200.12.2)[549E5FBE-327A-398B-9021-7D09DEA39396]@0xffffff7f93fce000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[F2C92761-0D41-3490-9646-0C34293AD6DB]@0xffffff7f92095000
            dependency: com.apple.iokit.IONetworkingFamily(3.4)[75FA72F4-A0A9-36FD-8EAC-C5A4EC24310B]@0xffffff7f92ac7000

Safe Boot from the HD, (holding Shift key down at startup), does the problem occur in Safe Mode?