Monterey 12.2 Kernel panics and restarts

It's been more than 2 days now with no issues for me, so my problem was definitely in the bluetooth communication with my keyboard (3rd Gen Apple Wireless Keyboard). I have since removed my keyboard entirely in the settings and turned bluetooth back on with no issues. I'm going to start putting the rest of my settings back to normal, one by one. Then I will try to reinstall my keyboard and see what happens. I read somewhere that they totally rewrote the bluetooth in Monterey and I just found this as well -

https://macpaw.com/how-to/bluetooth-issues-macos-monterey

Adjusting Energy Saver settings and such were great workarounds, but they don't solve the actual problem. Pretty confident most of us can solve our troubles by going in to bluetooth settings, removing and reconnecting each device as new. These issues occurred for all of us after updating to Monterey. Clearly not hardware. I've included a screenshot of the start of one of my crash reports so you can all see that mine were very similar to the OPs. My problem appears to be solved. Good luck.

The report says you installed this:

2022-01-31 Bitdefender Virus Scanner (3.16)

However, I do not see it listed elsewhere in the report?

Have you subsequently uninstalled Bitdefender? If yes do you have the restarts after removal?

You said:

I've even wiped the hard drive and installed Monterey 12.2 clean

Did it have restarts before restoring anying or did you just download/install app and setup things vice restore things from backup. If you restored things what did you restore?

User?Settings?

Apps?

I will test this but I think that is not the problem as I was using caffeinate -i in the terminal at the time.

I do seem to remember reading somewhere about not having the firewall enabled. So I will do a 2 step test 1st disable sleep, then enable firewall.

I've been dealing with this same issue for weeks as well. I keep seeing Mdnsresponder listed in my report on the fourth line where yours shows pid 83: fseventsd. I've tried everything as well. I even downloaded recent drivers for everything connected to this Mac. I have a Magic Mouse on order now because I'm being pulled toward the possibility that it has something to do with my Logitech mouse. Do you happen to have one as well?

I translated a German forum thread and that's where I found the suggestion to adjust energy saver settings. Before you posted this, that was the only thread I could find for this exact issue. I guess my 2018 Mac mini was restarting so frequently, when I'd come home from work it would be completely shut down. Someone on that German thread had success by launching in safe mode, going in to the library folder on the main HD, and deleting 2 folders - Launchdeamons and Launchagents. 3 files in each folder on my computer and they were for Adobe, Logitech (mouse), and Brother (printer/scanner). For me, this definitely seemed to help, as my computer would now be sleeping when I get home, but would still show a kernel panic report restart report when I would log in...It seems to me though, that this has to do with one of those 3 things. Maybe if we have one of them in common we could figure this out :)

This is very frustrating. Please report back if you find a better solution than changing energy saver preferences, as will I.

I have a Magic Mouse on order now because I'm being pulled toward the possibility that it has something to do with my Logitech mouse. Do you happen to have one as well?

I have been having this problem (2108 Mac mini) after installing 12.2, and have a Logitech usb mouse as well. I never installed drivers/the system prefs pane for it after I did a clean install of Monterey last fall.

I noticed that it seemed like it was panicking when the machine would go to sleep, so I tried disabling that last night before I logged off. But sure enough, it crashed overnight.

The crash reports seem to point toward something about a USB bus, but those reports are generally too cryptic. I have a Magic Trackpad that I use secondary to the mouse. I will unplug the mouse and see if it's still doing this throughout today.

Great, thanks. If you have a crash report to look at, can you please look at this line from the OP and tell me if yours is the same or different?

Process name corresponding to current thread (0xffffff8b6b528aa0): fseventsd

Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mine has mdnsresponder listed instead of fseventsd. This makes me believe that we all have 3rd party software that is not jiving with Monterey. These programs both interact with multiple Apple and 3rd party software and devices. Everyone seems to have had these problems start after an OS update, so it's very highly unlikely to be hardware causing this issue imo. Also, everyone, including myself, who has run diagnostics to check hardware, has reported no issues.

I have yet to see a wipe and reinstall work as well (I've tried that too!). In the OP's case, he even tried to set up as new, but I'm sure he is still using the same monitor, printer, keyboard, mouse, external, etc.

Wow, great! I hope we’re getting somewhere…I don’t have a spare mouse or alternate option to try until my new one arrives. I will also add that the current iOS driver that I installed for my mouse only listed compatibility up to 11.0. I suppose the older your mouse, the more unlikely they are to keep up with the ever-changing iOS.

That panic log indicates a memory problem (element modified after free). That could be RAM or it could be something in the logic board that passes chunks of memory around.

I have seen some Anti-virus software cause memory corruption, but you don’t have any third-party kernel extensions loaded at the time of the panic.

The last loaded kext was the ExFAT driver. fseventsd monitors and logs all file system events, but I don’t think it does so for non-Mac drive formats.

If it is a hardware fault, the only way to figure it out is to take it to an Apple Store or Authorized Repair center. Apple Diagnostics will not likely find anything that might cause a kernel panic except for the RAM checks.

Update:

So, I realized that my external hdd was spinning up and down constantly when I put my mini to sleep as well. How about you guys? I have also been reading every crash report and noticed that mdnsresponder wasn’t always the culprit for me. I’ve had symptomsd and bluetoothd since I’ve been looking as well.

I also realized (duh) that I could unplug my mouse when putting the computer to sleep to test my theory there - no change. Then I tried an old monitor - no change. Finally, I tied disconnecting my Apple keyboard by turning Bluetooth off, and voila…I have had no restarts or sleep cycling external hard drives since. These were the only 3 items I left connected (as instructed) when I first started troubleshooting…There used to be an option to disallow Bluetooth devices to wake your Mac, but this is apparently gone in Monterey. It’s been a few hours now with no troubles, but I’ll update if that changes. This is definitely not a hardware issue. Hopefully this will be fixed in the next update, but please try turning off Bluetooth if you haven’t already and lmk if it works for you.

I have a fairly clean install, I just used rsync to copy a few files from my external HD. I have an apple blue tooth key board and the latest Magic Mouse. I've followed the previous discussions and the following settings had no panics restarts over the weekend.

I had previously put the firewall on, this is now off, and I set power-nap to off. Bluetooth was left with all the input devices connected.

Last update:

My new Magic Mouse showed up right after my last post. Turned it on and my problems returned. Tried disconnecting and setting up as new multiple times to no avail. Even tried resetting my bluetooth with terminal command - sudo pkill bluetoothd. Nothing. Plug usb mouse and keyboard back in, turn bluetooth off, and everything is perfect again. Stuck waiting for a fix from Apple now. Here's another article link...

https://www.macworld.com/article/610175/macos-monterey-12-2-battery-drain-bluetooth.html

Are there any 3rd party kernel extensions installed?

"element modified after free"

is generally caused by kernel software that frees some memory but still continues to use the pointer.

This generally happens when there are 3rd party kernel extensions installed, as they are often times not as well debugged.

While this could happen with 3rd party RAM, that change from 0 to 0x6247 is not typical. Generally failing RAM just changes a single bit. This is more like some code actually write 0x6247 into the offending memory location, which is 99.9999999% a software error.