Kernel Panic

I'm having this same issue (MBP 13' 2017, macOS 12.2.1). Been having it since the year began. Please, where can I find this panic report so I can look through it myself? I have EtreCheck and I've used it multiple times (and followed it's recommendations), no solution. Been have this problem since upgrading to Monterrey at the beginning of the year. Just about sick of it all. I can go days without anything, then in 10 minutes, I can have up to 4 panics consecutively. I read in a separate thread that it could be RAM-related, but everything in this mac is OEM. I haven't replaced any parts, never even opened it.

It should be part of a kernel panic report. A kerne panic report layout is similar to the following:

• panic message (which you show)
• registers
• kernel backtrace
• running task (which you show)
• misc system information in 2 paragraphs
• list of loaded kernel extensions

Panic reports are in Finder -> Go (menu) -> Go to Folder -> /Library/Logs/DiagnosticReports

Was there a kernel backtrace with any useful information in it.

The fact that it is different current running task would tend to say they have noting directly to do with it.

All the traps appear to happen at 0xnnnnnnnnnnn73918. The earlier address differences are mostly due to kernel address randomization, but the 73918 means it is coming from the same bit of kernel code.

A kernel backtrace with function names and drives would be most helpful. That might indicate what subsystem is involved.

Is this from an iMac with 3rd party RAM installed? 3rd party RAM is a common cause of kernel panics. And yes, a new version of the operating system can trigger this as stuff moves around in a new operating system version, and sometimes new algorithms hammer harder on a segment of memory that exposes a memory weakness. I'm not saying it is a RAM issue, just that it has been known to happen.

Sometimes when there is a kernel trap is can be RAM related. Sometimes the kernel registers can give a clue (not often, but sometimes I've found a gem, like it shows a misspelling of 0xdeadbeef which is a memory value used to poison free'ed memory in case a process attempts to continue using it after it was freed. It is not often the registers will tell me that kind of information, but when it does, it is invaluable.

If you would care to post a few (not all; but a few) of the entire panic reports, that might help (or not). Reading panic reports is a lot like reading "Tea Leaves". Sometimes it helps, sometimes not.

As BobHarris has pointed out, it looks like the culprit may be a Sony Camera(?) driver.

last started kext at 18989458201: >driverkit.serial	6.0.0 (addr 0xffffff7fb4527000, size 28672)
loaded kexts:
com.sony.driver.dsccamDeviceInfo00	1

3rd party kernel extensions have been a kernel panic focal point. One of the reasons Apple is pushing them out and making users use System Extensions.

So as Tesserax says, suggest removing the com.sony.driver.dsccamDeviceInfo00 kernel extension from your system.

If the panics continue after it is removed, then it was something else 😀

No external backups, Apple security disabled, fan control tools (which you really don’t want to use to throttle down fans), what might be a firewall app. seriously overloaded memory and storage, and the storage write speed is way too low.

Yeah, this Mac has problems.

Start by freeing up some storage and some processor time. The Google apps tend to be resource- and processor-intensive, so they’re an option to remove, among various others here. If that Lulu app is the firewall, I’d remove that. Get your Time Machine backups going again too, so that macOS is not trying to use snapshots and occupying that storage. Re-enable Apple security, as well.

When this Mac gets replaced (as it’s not upgradable), your replacement Mac will best want substantially more memory (given what is shown here, go 16 GB minimum) and your storage is probably due to at least double or maybe quadruple.

Check for updates from Google for Chrome, or remove the Google apps as a workaround.

I’d also look for updates for whatever Sony app is loaded here that needs a kernel extension, too.

The kernel backtrace is not being helpful. Sometimes they actually list then kernel extensions involved in the panic. This one does not.