Kernel panics on mid 2016 MacBook Pro (Monterey 12.7.6)

Question

Level 1

10 points

Kernel panics on mid 2016 MacBook Pro (Monterey 12.7.6)

I began getting some frequent kernel panics a few weeks back. I ran diagnostics and all of my hardware came back fine.

In DiskUtility, running First Aid can't complete on my Data drive because it gets stuck at fsroot tree. When I run first aid in recovery mode, it suggests making a data back up (which I have). I also am unable to reinstall OS from recovery mode because I get "com.apple.BuildInfo.preflight.error 21".

At this point, I've just completed a PRAM reset before approaching a full erase and reinstall. I've included an Etre report and two panic logs if anyone can examine them to see if something else is causing this that I can uninstall or address before going down the erase/reinstall route. I also want to make sure the kernel error won't migrate over on a restore if I need to do that.

The one "change" that occurred around the time the panics began that I can point to is I removed my external Time Machine hard drive from my MacBook while it was sleeping (I had properly ejected it before putting the computer to sleep). I am also finding the Time Machine back up can not complete now, so I'm wondering if that could be a possible culprit.

MacBook Pro 15″

Posted on Jun 2, 2025 8:06 AM

Reply

Answer 1

Jun 2, 2025 12:24 PM in response to favre1fan93

<< In DiskUtility, running First Aid can't complete on my Data drive because it gets stuck at fsroot tree. >>

That item, the File System Root Tree is the origin of the File system. unless that can be repaired properly, you will need to completely ERASE your Mac and all its files, which you said was a concern because Time Machine would not run, so your copies are not up-to-date.

restart your Mac in Recovery, where the drive is Completely free for a Deep repair.

launch disk Utility.

set the tiny view menu to 'show all devices'.

select the boot DEVICE, by its immutable manufacturer-given name, and repair the Device.

if any errors, run again.

then repair the container-disk

then repair each Volume.

if any errors, run the repair again until it comes clean or is hopelessly stuck.

let readers know how you fare.

Reply

Answer 2

Jun 2, 2025 1:12 PM in response to favre1fan93

get rid of This junk, and never re-install.

[Loaded] com.macpaw.CleanMyMac4.Agent.plist (MacPaw Inc. - installed 2024-10-22)

Executable: /Library/PrivilegedHelperTools/com.macpaw.CleanMyMac4.Agent

Also you have:

Automatic updates disabled - Automatic updates are disabled. This computer is at risk of malware infection.

[...]

Apple security disabled - Apple security software is disabled. This computer is at risk of malware infection.

Reply

Answer 3

Jun 2, 2025 1:14 PM in response to favre1fan93

VPN:

A virtual private network, or VPN, is a private connection over the Internet from a device to a specific network. VPN technology is widely used in corporate environments. If you need to be "present" on an institutional network, a VPN is a great tool for accomplishing this. it is generally issued and controlled by the institution.

Almost all other uses are a SCAM. There is generally no need for you to have a private connection to a VPN vendor's Network, except to make it easier for them to harvest your data to sell. There is NO security advantage whatsoever in using a VPN. Your connections are already encrypted in most cases.

If VPN vendors just stopped there, it would be bad. But many of these packages also insist on scanning all your files, non-stop, -- nominally looking for viruses, but who knows for sure what data they are harvesting. Their non-stop file reading punishes your computer's performance in the process.

Some also break into your other secure connections so they can be FIRST to examine your data, often leaving your Mac MORE vulnerable to attack.

https://gist.github.com/joepie91/5a9909939e6ce7d09e29

Launchd: /Library/LaunchDaemons/com.cisco.anyconnect.vpnagentd.plist

Command: /opt/cisco/anyconnect/bin/vpnagentd -execv_instance

Reply

Answer 4

favre1fan93 Author

Level 1

10 points

Jun 2, 2025 2:55 PM in response to Grant Bennet-Alder

Thanks for the notes about these extra steps in Disk Utility. Unfortunately since my post and before your response another kernel panic happened so I went through with erasing the computer and trying to restore from my Time Machine.

Sadly not all user files were migrated over in my most recent Time Machine (from May 15 when this first started happening), and I'm realizing now from your comment that it's likely my back ups were not fully backing up if the File System Root tree had been corrupted. I was able to salvage what I could from prior back ups but not everything. And despite this, running Disk Utility now shows no issues with my data drive and I haven't experience any panics in the hours since the restore.

I wish in my internet searches had brought up about the "show all devices" for Disk Utility so I could have tried that sooner, though I can't know if it would have solved the issue.