Magenta / Pink Screen Kernel Panic - Mac Studio Ultra

[dspdoc]

Any chance anyone here can help me figure out what is causing these kernel panics on my new Mac Studio Ultra? I will paste a bit of the log here. The entire screen turns a magenta pink and then the machine reboots. The suspicious bit to me is the part stating "nCORE 11 is the one that panicked." I personally can't make much more out of it, but here it is:

{"bug_type":"210","timestamp":"2022-03-22 17:54:33.00 -0500","os_version":"macOS 12.3 (21E230)","incident_id":"EA244C3A-2F4E-4A45-B72D-52663C3E456C"}
{
"build" : "macOS 12.3 (21E230)",
"product" : "Mac13,2",
"socId" : "0x00006002",
"kernel" : "Darwin Kernel Version 21.4.0: Mon Feb 21 20:35:58 PST 2022; root:xnu-8020.101.4~2\/RELEASE_ARM64_T6000",
"incident" : "EA244C3A-2F4E-4A45-B72D-52663C3E456C",
"crashReporterKey" : "887C60ED-A6D1-280B-2AA4-7F1E14727BCD",
"date" : "2022-03-22 17:54:33.54 -0500",
"panicString" : "panic(cpu 11 caller 0xfffffe001fc434f0): [kalloc.type1.16]: element modified after free (off:8, val:0xfffffe1666e42440, sz:16, ptr:0xfffffe1666e41ec0)\n 8: 0xfffffe1666e42440\nDebugger message: panic\nMemory ID: 0x6\nOS release type: User\nOS version: 21E230\nKernel version: Darwin Kernel Version 21.4.0: Mon Feb 21 20:35:58 PST 2022; root:xnu-8020.101.4~2\/RELEASE_ARM64_T6000\nFileset Kernelcache UUID: 65F083231F3684E89C62E16ACD8BF64E\nKernel UUID: 178AA913-FCA9-33FD-A81C-DF08315F458D\niBoot version: iBoot-7459.101.2\nsecure boot?: YES\nPaniclog version: 13\nKernelCache slide: 0x0000000017b20000\nKernelCache base: 0xfffffe001eb24000\nKernel slide: 0x00000000182d0000\nKernel text base: 0xfffffe001f2d4000\nKernel text exec slide: 0x00000000183b8000\nKernel text exec base: 0xfffffe001f3bc000\nmach_absolute_time: 0x1888f21a61\nEpoch Time: sec usec\n Boot : 0x623a426d 0x0007b676\n Sleep : 0x00000000 0x00000000\n Wake : 0x00000000 0x00000000\n Calendar: 0x623a538e 0x0002eba6\n\nZone info:\n Foreign : 0xfffffe0026ba0000 - 0xfffffe0026bb0000\n Native : 0xfffffe100046c000 - 0xfffffe300046c000\n Readonly: 0xfffffe14cd138000 - 0xfffffe1666ad0000\n Metadata: 0xfffffe81ba624000 - 0xfffffe81c658c000\n Bitmaps : 0xfffffe81c658c000 - 0xfffffe81ddf9c000\n\nCORE 0 PVH locks held: None\nCORE 1 PVH locks held: None\nCORE 2 PVH locks held: None\nCORE 3 PVH locks held: None\nCORE 4 PVH locks held: None\nCORE 5 PVH locks held: None\nCORE 6 PVH locks held: None\nCORE 7 PVH locks held: None\nCORE 8 PVH locks held: None\nCORE 9 PVH locks held: None\nCORE 10 PVH locks held: None\nCORE 11 PVH locks held: None\nCORE 12 PVH locks held: None\nCORE 13 PVH locks held: None\nCORE 14 PVH locks held: None\nCORE 15 PVH locks held: None\nCORE 16 PVH locks held: None\nCORE 17 PVH locks held: None\nCORE 18 PVH locks held: None\nCORE 19 PVH locks held: None\nCORE 0: PC=0xfffffe001f44b418, LR=0xfffffe001f44b418, FP=0xfffffe6158ce3f00\nCORE 1: PC=0x00000001c18189d4, LR=0x00000001c18188c8, FP=0x000000016fbbde30\nCORE 2: PC=0xfffffe001f42bbd8, LR=0xfffffe001f42bb8c, FP=0xfffffe6160a53d30\nCORE 3: PC=0xfffffe001f47bf50, LR=0xfffffe001f9095f0, FP=0xfffffe8117cbbc80\nCORE 4: PC=0xfffffe001f44b308, LR=0xfffffe001f44b654, FP=0xfffffe814f72bf20\nCORE 5: PC=0xfffffe001f42bbd8, LR=0xfffffe001f42bb8c, FP=0xfffffe6160b53ed0\nCORE 6: PC=0xfffffe001f44b308, LR=0xfffffe001f44b654, FP=0xfffffe615a983f20\nCORE 7: PC=0x00000001bc312548, LR=0x00000001bc3124dc, FP=0x0000000174976870\nCORE 8: PC=0x00000001bc3124d4, LR=0x00000001bc152668, FP=0x000000028b58e870\nCORE 9: PC=0x00000001bc3f3268, LR=0x00000001bc3f30e4, FP=0x000000016fdfd9d0\nCORE 10: PC=0xfffffe001f44b418, LR=0xfffffe001f44b418, FP=0xfffffe8115b13f00\nCORE 11 is the one that panicked.

 

[4sallypat]

Did you migrate your old Mac data or did start with a clean slate ?

 

[dspdoc]

Did you migrate your old Mac data or did start with a clean slate ?

Totally clean slate.

 

[DeltaMac]

What is the result after running diagnostics?
If no codes are reported, try to use your Mac Studio normally. When you get a pink screen/restart, run the diagnostics as soon as possible (could be getting too hot, so running diagnostics quickly after the issue appears might report a problem.)

 

[dspdoc]

What is the result after running diagnostics?
If no codes are reported, try to use your Mac Studio normally. When you get a pink screen/restart, run the diagnostics as soon as possible (could be getting too hot, so running diagnostics quickly after the issue appears might report a problem.)

Diagnostics indicated nothing. The machine is definitely not hot because it is more or less idling when it has occurred. It is not task specific and a few times I wasn't even running an application. The last time I was simply installing a .pkg. I have reported this to Apple and uploaded data. Anxious to see what engineering comes back with. I just really want to know if I have bad hardware or whether they say it is a 3rd party peripheral or if there needs to be a macOS update for these new machines.

 

[Fravin]

How’s your display setup? Which port, which cable are you using to hook up your display?

 

[dspdoc]

How’s your display setup? Which port, which cable are you using to hook up your display?

LG display via HDMI.

 

[Fravin]

LG display via HDMI.

In M1 early days, the Mac Mini’s HDMI port has raised a lot of complains of crashes exactly like that. You can search in the forum for backup information if you want to.
We learned to forget the HDMI port in Mini and use the Thunderbolt ports to output video. Get yourself an USBC to HDMI cable and see if this happens again. I bet it won’t.

 

[dspdoc]

In M1 early days, the Mac Mini’s HDMI port has raised a lot of complains of crashes exactly like that. You can search in the forum for backup information if you want to.
We learned to forget the HDMI port in Mini and use the Thunderbolt ports to output video. Get yourself an USBC to HDMI cable and see if this happens again. I bet it won’t.

I just switched out the cable to USB-C because the LG has USB-C input. We will see what happens. No more HDMI... Fingers crossed!

 

[cpnotebook80]

Just wanted to add that I initially connected my monitor via hdmi and was getting flicker (no pink or kernal panic) and also 5 sec screen blanks like on and off every 5 seconds, so i bought a usb-c cable and so far so good. Looks like hdmi issue and i tried 2 different hdmi cables.

 

[dspdoc]

I wasn’t even aware that kernel panics could occur because of an HDMI connection.