Help interpreting Kernel Panic report (possible FireWire/audio problem)

A conclusion to this thread for anyone who might encounter a similar problem…

Firstly, connecting my FireWire audio interface using a FireWire>Thunderbolt adapter has fixed the problem of repeated kernel panics (i.e. connecting the audio interface via the Thunderbolt port on my Mac, rather than via the FireWire port). I’ve had no crashes in 40+ hours of ‘stress testing’, running various RAM-hungry audio apps. So if you’re suffering kernel panics from connecting a FireWire audio interface, this would seem to be a viable workaround. The adapter I’m using is this one:

https://www.apple.com/uk/shop/product/MD464ZM/A/thunderbolt-to-firewire-adapter

Secondly, I haven’t been able to locate the exact cause of the previous kernel panics, but I have a good hunch. Prior to testing the FireWire>Thunderbolt adapter, I tried:

- Using a different FireWire cable: kernel panics continued

- Removing Sonarworks and Sophos software: kernel panics continued

So I suspect the fault lies with how my FireWire audio interface driver is ‘talking’ to my macOS or vice-versa. Which is curious, because the driver has otherwise been rock solid since 2017 (no updates since then) and is working fine when ‘talking’ via Thunderbolt. So that particular mystery continues.

Regardless, I now have a working audio interface. And given that my system is thankfully stable, I’ve decided to stop updating my Mac Mini altogether and am going to run it in a ’fossilised’ state using a separate laptop for Internet and running apps that do require updating. Job done. Back to making music :)

Thanks again to BDAqua and Barney-15E who helped with this thread. Appreciated!

It could be a RAM issue as it is a Page Fault.

Interesting... this is helping me piece together some understanding of how to interpret the error reports. Thanks!

However, you should confirm that it is not one of the system modifications you have installed... Uninstall each following the instructions provided by the developer of the apps you installed. After each uninstall, check to see if the panics continue or cease.

I'll try this as my next step.

I would start by uninstalling Sophos--most likely and completely unnecessary.

The other two I've never heard of.

I noticed those system mods in the error report yesterday, so good to know my intuition isn't too far off :)

Being at the top of the list I assumed they might be the likely culprits, so I've already uninstalled Sophos and Sonarworks (the latter is a systemwide EQ software for controlling external loudspeakers, which I no longer use). I left the 'AllenAndHeath' driver running as it's needed to link up my external audio interface (a mixing desk).

The AllenAndHeath driver might still be the cause. It's a discontinued product, but the driver was last updated in 2017 and it's been rock solid, well at least to date (and I haven't knowingly installed any other macOS/app updates that I would suspect might conflict with it... but I'm far from knowledgable on this topic).

I haven't yet re-connected my audio interface using the FireWire port - I'm still 'stress testing' using the FireWire>Thunderbolt adapter and so far I've had no further kernel panics after ~5 hours of testing with various apps running. Now that Sophos and Sonarworks have been uninstalled, I'll try again using the FireWire cable direct - and also try another FW cable as suggested by BDAqua - and see what happens.

Be good to identify the cause of this, but reassuring to know that connecting via Thunderbolt seems to offer a workaround.

I'll report back in due course. In the meantime, thanks for your input - very helpful.

Thanks for clarifying re. possibility of a problem with the RAM.

I’m currently ‘stress testing’ the Mac Mini, running various RAM-hungry apps (including those that were live during the initial kernel panics), all whilst connected to the audio interface via FireWire>Thunderbolt adapter. So far so good - ie. no crashes - though perhaps too early to call for sure.

I’m going to continue testing and will try a different FW cable as suggested. I’ll report back here in case my findings help anyone else who encounters the same error.

In the meantime, it appears as though bypassing the FireWire port via Thunderbolt may be a viable (if not ideal) workaround.

Thanks for the quick reply!

I have another FireWire cable that I can try out; good idea.

Re. your answer to my first question "Yes, or RAM"... is there something in the Panic Report that indicates a RAM issue, or is the suggestion of RAM based on this being a likely culprit generally? (curious as I'm keen to better understand the crash reports myself).

Thanks again.

PS: in case relevant, here's a link o the Allen & Heath mixer product page and some blurb about its FireWire i/o and chipset...

https://www.allen-heath.com/ahproducts/zed-r16/

The internal soundcard features 18 FireWire inputs and 18 outputs plus 16 ADAT I/O. Each channel on the mixer has its own independent soundcard channel so instruments can be recorded simultaneously (pre or post EQ) and into the sequencer separately. To minimise clock jitter and provide synchronicity between the ZED-R16 and other devices, the mixer is equipped with the professional JetPLL™ digital audio chipset.

Here's a full copy of the Panic Report...