Mac Pro 2019 Kernel Panic only when Logic X is running

My Mac Pro 2019 running Ventura 13.4 is suffering from Kernel Panic on a regular basis.

I have tried all the usual remedies to no avail.


The panic log is below, I'm out of ideas, the Mac only ever crashing when running Logic, but will still panic if left alone with Logic open.


At the moment all sleep/screen/energy savers are off

All current Au / VST are up to date


PCI cards have been re-seated (housing 8TB Raid)


Apple diagnostics find no faults


Log is below if anyone has any ideas


{"roots_installed":0,"caused_by":"macos","macos_version":"Mac OS X 13.4 (22F66)","os_version":"Bridge OS 7.5 (20P5058)","macos_system_state":"running","incident_id":"F7F8B366-265D-4257-877F-2651648B5AB0","bridgeos_roots_installed":0,"bug_type":"210","timestamp":"2023-06-17 12:20:40.00 +0000"}

{

"build" : "Bridge OS 7.5 (20P5058)",

"product" : "iBridge2,6",

"socId" : "8012",

"socRevision" : "10",

"incident" : "F7F8B366-265D-4257-877F-2651648B5AB0",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"kernel" : "Darwin Kernel Version 22.5.0: Mon Apr 24 20:06:41 PDT 2023; root:xnu-8796.121.2~1\/RELEASE_ARM64_T8010",

"date" : "2023-06-17 12:20:40.25 +0000",

"panicString" : "panic(cpu 0 caller 0xfffffff016e64a68): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0x6\nOS release type: User\nOS version: 20P5058\nmacOS version: 22F66\nKernel version: Darwin Kernel Version 22.5.0: Mon Apr 24 20:06:41 PDT 2023; root:xnu-8796.121.2~1\/RELEASE_ARM64_T8010\nKernelCache UUID: 16E7828CC2563A9099738DA23F031D0E\nKernel UUID: A04DA547-BD69-39FF-A0E2-D59ED179A076\nBoot session UUID: F7F8B366-265D-4257-877F-2651648B5AB0\niBoot version: iBoot-8422.121.2\nsecure boot?: YES\nroots installed: 0\nx86 EFI Boot State: 0x16\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x1\nx86 Previous Power Transitions: 0x70707060400\nPCIeUp link state: 0x89271611\nmacOS kernel slide: 0x3200000\nPaniclog version: 14\nKernel slide: 0x0000000010a4c000\nKernel text base: 0xfffffff017a50000\nmach_absolute_time: 0x3584e57b8f\nEpoch Time: sec usec\n Boot : 0x648d7fa0 0x0009c100\n Sleep : 0x648d7fae 0x000be89a\n Wake : 0x648d7faf 0x0008f950\n Calendar: 0x648da507 0x0008793c\n\nZone info:\n Zone map: 0xffffffdfa8288000 - 0xffffffe5a8288000\n . VM : 0xffffffdfa8288000 - 0xffffffe08e8ec000\n . RO : 0xffffffe08e8ec000 - 0xffffffe0db5b8000\n . GEN0 : 0xffffffe0db5b8000 - 0xffffffe1c1c1c000\n . GEN1 : 0xffffffe1c1c1c000 - 0xffffffe2a8280000\n . GEN2 : 0xffffffe2a8280000 - 0xffffffe38e8e8000\n . GEN3 : 0xffffffe38e8e8000 - 0xffffffe474f50000\n . DATA : 0xffffffe474f50000 - 0xffffffe5a8288000\n Metadata: 0xffffffdfa0954000 - 0xffffffdfa2154000\n Bitmaps : 0xffffffdfa2154000 - 0xffffffdfa2278000\n Extra : 0 - 0\n\nTPIDRx_ELy = {1: 0xffffffe1c1f82ba8 0: 0x0000000000000000 0ro: 0x0000000000000000 }\nCORE 0 is the one that panicked. Check the full backtrace for details.\nCORE 1: PC=0xfffffff017d6363c, LR=0xfffffff017c106b4, FP=0xffffffe5ae4dbf20\nCompressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space\nPanicked task 0xffffffe1c1b03a10: 0 pages, 168 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe1c1f82ba8, backtrace: 0xffffffe5ae457700, tid: 389\n\t\t lr: 0xfffffff017c41868 fp: 0xffffffe5ae457770\n\t\t lr: 0xfffffff017d61e70 fp: 0xffffffe5ae4577e0\n\t\t lr: 0xfffffff017d60e30 fp: 0xffffffe5ae4578c0\n\t\t lr: 0xfffffff017c055fc fp: 0xffffffe5ae4578d0\n\t\t lr: 0xfffffff017c412a4 fp: 0xffffffe5ae457c80\n\t\t lr: 0xfffffff018290ddc fp: 0xffffffe5ae457ca0\n\t\t lr: 0xfffffff016e64a68 fp: 0xffffffe5ae457cd0\n\t\t lr: 0xfffffff016e4c604 fp: 0xffffffe5ae457d30\n\t\t lr: 0xfffffff016e55aec fp: 0xffffffe5ae457d80\n\t\t lr: 0xfffffff016e4eb5c fp: 0xffffffe5ae457e20\n\t\t lr: 0xfffffff016e4bb94 fp: 0xffffffe5ae457e90\n\t\t lr: 0xfffffff016c61b40 fp: 0xffffffe5ae457ec0\n\t\t lr: 0xfffffff0181e1c4c fp: 0xffffffe5ae457ef0\n\t\t lr: 0xfffffff0181e153c fp: 0xffffffe5ae457f20\n\t\t lr: 0xfffffff017c106c0 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x902",

"bug_type" : "210",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 33640 (Uncompressed 97904) **\n",

"macOSPanicFlags" : "0x0",

"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",

"subKernelErrorWatcherContainer" :

Posted on Jun 17, 2023 5:51 AM

Reply
Question marked as Top-ranking reply

Posted on Jun 17, 2023 6:36 AM

"CATERR detected" is a serious internal Hardware problem such as a Processor cache error.


"macOSPanicString" : "BAD MAGIC! "


We have never been able to solve those here, they are generally connected to coproceesor or T2 chip issues.


You need to contact support, share the above information with them (they can read stuff you have posted here easily) and work with them using their more-rigorous fault-isolation procedures. (They never take our word for conclusions.)


Do not be shy about asking for a specialist to read those panic reports. They are the ‘smoking gun’ and key to resolution.


I do not recommend you take a Mac that passes user diagnostics to the Genius Bar unless/until Apple telephone support makes arrangement for Genius bar to perform specific action.


Too many stories of “Genius bar took it in, ran their diagnostics, it passed, they returned it, it crashed immediately."


--------

By far the easiest way to cause instability and crashing is to install ANY third-party speeder-uppers, Cleaners, Optimizers, or Virus scanners. or a VPN that you installed yourself.


The idea that a third party, with no special knowledge of the inner workings of MacOS, can somehow find a simple way to protect your computer — that is not already being done by MacOS itself — suggests that the MacOS developers are somehow "holding out on you". That is absurd.


You should remove any and all (other than Apple built-in) virus scanners, speeder uppers, optimizers, cleaners, App deleters or VPN packages you installed yourself, or anything of that ilk.

Similar questions

3 replies
Question marked as Top-ranking reply

Jun 17, 2023 6:36 AM in response to Dave Hage

"CATERR detected" is a serious internal Hardware problem such as a Processor cache error.


"macOSPanicString" : "BAD MAGIC! "


We have never been able to solve those here, they are generally connected to coproceesor or T2 chip issues.


You need to contact support, share the above information with them (they can read stuff you have posted here easily) and work with them using their more-rigorous fault-isolation procedures. (They never take our word for conclusions.)


Do not be shy about asking for a specialist to read those panic reports. They are the ‘smoking gun’ and key to resolution.


I do not recommend you take a Mac that passes user diagnostics to the Genius Bar unless/until Apple telephone support makes arrangement for Genius bar to perform specific action.


Too many stories of “Genius bar took it in, ran their diagnostics, it passed, they returned it, it crashed immediately."


--------

By far the easiest way to cause instability and crashing is to install ANY third-party speeder-uppers, Cleaners, Optimizers, or Virus scanners. or a VPN that you installed yourself.


The idea that a third party, with no special knowledge of the inner workings of MacOS, can somehow find a simple way to protect your computer — that is not already being done by MacOS itself — suggests that the MacOS developers are somehow "holding out on you". That is absurd.


You should remove any and all (other than Apple built-in) virus scanners, speeder uppers, optimizers, cleaners, App deleters or VPN packages you installed yourself, or anything of that ilk.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Mac Pro 2019 Kernel Panic only when Logic X is running

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.