Why am I experiencing kernel panics and restarts when adjusting settings in OBS?

The kernel panic you’re encountering on your M2 Mac mini involves the DCPEXT (Display Controller Pipeline Extension) subsystem, suggesting an issue related to graphics, display hardware, or associated drivers. The error details, particularly axi_rd_err (AXI read error), hint at a problem with memory access or a miscommunication between the system's graphics controller and its resources.

What are some potential causes of these panics?

• A bug in macOS Sonoma could be causing the panic. The error might be related to a recent update or compatibility issue in the display subsystem. The currently latest version of Sonoma is 14.7.2. The report shows that your Mac is still running 14.7.1. I suggest you update as the first step.
• When using external displays, especially with those with high resolutions or refresh rates, they could be triggering the issue. Certain adapters or cables (e.g., USB-C to HDMI) might also contribute to this.
• Faulty GPU hardware or display components on the M2 Mac mini logic board.
• Some third-party software that modifies display settings or graphics performance (e.g., display calibration tools) might conflict with macOS.
• Connected peripherals, especially those involving video or audio, might cause issues.
• Prolonged high GPU usage might lead to overheating, triggering kernel panics.

I second Barney-15E's suggestion to remove all external peripherals other than your keyboard and mouse to see if the panics stop. If they do, you can add them back, one-at-a-time, until they start again to narrow down the culprit.

balcobops wrote:

I noticed that the Acer monitor's refresh rate was 75hz and the LG TV's refresh rate was 60hz. Both have a 1920x1080 resolution. I use the Acer to display my applications (including two GPU-intensive ones in veadotube mini and Ferromagnetic), and I display OBS on the LG TV.

• Could that mismatch in refresh rates be significant?

Potentially, but it's too early in the troubleshooting game to know for sure.

* Further, would reducing the resolution on my monitor/TV help reduce resource usage?

It should, but again we'd be concentrating on only one area. It is a better troubleshooting strategy to remove all potential elements (aka, removing all of the peripherals) to verify that your Mac, itself, is not the culprit.

* I wasn't able to get a straight answer on this, but what is considered a "high" kernel_task CPU%? Should I be looking for a spike in resources used when looking for the source of the kernel panic?

CPUs are multi-core. Each core can run up to 100%. Typically, the CPU% is an average of all of the cores. So, for example, if you have a four-core CPU, the value can reach 400% to be considered "maxed out." Using the Activity Monitor would be very helpful here, especially the CPU tab.

The M2 has 8-cores; whereas the M2 Pro, has either 10- or 12-cores.

* Are there adapters or cables that have a specific tendency to cause issues or is this just a general suggestion?

The general rule here is: "You get what you pay for." Always use high quality cables and adapters, whenever possible.

Again, I would suggest that you start with the following steps:

1. Update macOS Sonoma to 14.7.2 OR upgrade to macOS Sequoia. At this point, I suggest the former.
2. Remove all peripherals except the keyboard and the single Acer monitor. Leave them all disconnected for the time being. Run in this configuration for 24-48 hours to see if the panics return. If they do, go on to the next step. If they don't, go on to step 4.
3. Boot up your Mac into Safe Mode. Run in this configuration for, at least, 24 hours. Again look to see if the panics continue. If they do continue, then most likely, there is a potential hardware issue with your Mac, and your next step would be to make a Genius Bar appointment at your local Apple Store.
4. Boot up your Mac normally. Add back one of your peripherals. Run in this configuration for 2-4 hours. If the panics reoccur, you identified (at least) one of the culprits. Go ahead and disconnect this peripheral, and then, add back another one. For each one, run for 2-4 hours to look for any issues. If found, that would be another culprit. If adding back all of your peripherals does not end up with any panics, then you're done troubleshooting.

Try disconnecting the external devices and see if the panics occur.

Having Google Chrome and its keystone background tasks in the same machine as any video application is a formula for disaster. They are known to hog the system videotoolbox and cause video applications to malfunction and crash. This looks like it could well be the case here.

Uninstall Chrome and especially its background minions, and see how things go.

See https://chromeisbad.com

How are the external drives connected to your Mini? If by dock is the dock self powered?

balcobops wrote:

I have only one more question, when running in these different configurations, should I run the programs that I'm intending to use when streaming to replicate the conditions?

Yes. but give each configuration a chance to stabilize a bit before doing so. Maybe, an hour or so.

Having a particular configuration run for a period of time is to fully verify if that configuration helps or not. The times I provided you are based on my experience with troubleshooting. You're free to choose when a particular configuration has run for enough time. Sometimes the failure will happen quickly; other times, it may not manifest itself for many hours.

That shoots down that idea. Nest please download and run Etrecheck.  The free version is sufficient.

Copy the report as shown in this animated screenshot

and use the Additional Text button to paste the report in your reply.

Then we can examine the report and see if we can determine the cause of the problem.