Pink screens, kernel. panic, and guarateed re-boots

Platforms Mac
1

Hi all!

Only my second post here, granted, however, this issue is far more specialized and particular than the general post about Plex that I shared in the ‘General’ section.

I’m looking for anyone who can please help me try to explain why I am getting a pink screen and a re-boot on my M1 Mac Mini EVERY SINGLE TIME that I try to add a local SMB share??

Unfortunately, as it happens every time, I can replicate this on-command.

I’m a technically-inclined person, though, not accustomed to reading Apple logs. Each time my computer re-boots and the log appears on-screen, I can see something referencing a “kernel panic.”

I do apologize for using all caps above, but, I’m feeling a little bit desperate here. I’ve been at this for the past few days, and trying to set this up this has been nothing short of an absolute nightmare, unfortunately. I’d love to be able to state otherwise.

Thank you for the help!

2

Which version of macOS are you using?

If you see this again can you send in a report from your device (and post the code here) so we can look further into this?

3

Thanks for the prompt response, once again, James. I do appreciate it.

Currently using Infuse Pro with an M1 Mac mini, 16GB of RAM, on Tahoe 26.3.1.

I will work on getting you those logs and will edit this post, as necessary, as I can’t trigger a kernel panic and reset my machine during work. Haha. I’m sure you understand. Thanks!

4

OK, I sent in 2 and all I got in the emails were the following

Diagnostics: HX24D

Diagnostics: XB31A

5

Just looking for confirmation that I did this correctly, please?

6

I’m not trying to be difficult. I’m just a guy who spent $108 on a piece of software that I’m desperate to get working properly.

Can anyone please help a brother out? Thanks!

7

Not saying I have an answer, or at least one that is positive but I had the pink screen and kernel panics on a Pismo and that turned out to be it’s death rattles. It’d go pink tint on the screen and even on the desktop then crash after a minute (or seconds).

You say it happens when you add a SMB share, have you tried any other apps that use SMB with log ins? I think VLC has that ability to add a SMB share so I’d try another app with SMB share adding and see if it’s by chance an OS related problem related to networking. Maybe an internal ram sharing issue.

Really just a wild guess but I know how it feels when you have a unique issue that no one else seems to experience.

8

HI NC, thanks so much for the prompt reply. I really appreciate it.

So, I take your points on board. I’ve unfortunately already got an SMB share set up on the same Mac mini with the Mrs. and her Windows computer, as well as another Windows PC I have.

This is almost assuredly an isolated issue with Infuse, as I can replicate it every single time without fail.

It happens, each time, within 30 seconds of adding the share. The entire machine locks up for 5-10 seconds, I see a pink screen, and, bang, I’m reset.

I’ve got a Roon server on this thing, a Plex server, an Emby server applet that I, admittedly, never use, and said SMB shares, with almost zero down-time to speak of within the past five years.

Both living in power wheelchairs & with a disability, me & my Wife each work from home, and we’re routinely in front of our computers 16-20 hours a day. In other words, our tech has to be rock solid with almost no wiggle room.

I’m a simple man. I merely want to put this behind me and use the software that we’ve paid for in the manner advertised.

Thanks to all for your replies and assistance.

9

If you have other SMB shares already set up on the same mac mini were they set up before you started with Infuse if so, maybe try a new SMB add in case it’s something on the initial setting up causing the issue otherwise maybe another thing to try is to delete (not off load) the Infuse app and re-download it and start fresh again in case the app was corrupted during the initial install.

In my past Mac experience, a pink screen has usually been a Mac hardware or OS software issue, not from apps like Infuse.

Google AI says this:

AI Overview

A pink screen on an M1 Mac mini usually indicates a

kernel panic—a critical software error—often caused by GPU initialization issues, incompatible software (like outdated kernel extensions), or display connection problems (HDMI/cable issues). It often occurs alongside reboots and can usually be fixed by updating macOS or resolving software conflicts.

Common Causes for M1 Mac Mini Pink Screen:

  • Kernel Panic (Software Conflict): The most common cause, often triggered by DisplayLink drivers, Karabiner-Elements, or outdated third-party kernel extensions (kexts).
  • Display/Cable Issues: Faulty HDMI cables, adapters, or issues with high-resolution monitors can cause pink tints or squares.
  • GPU Initialization Error: When waking from sleep or booting, the M1 chip’s GPU may fail to initialize properly, leading to “pink snow” or colored blocks on the monitor.
  • Insufficient Power/Bandwidth: Some users report that USB-C hubs or heavy power draw on ports can trigger this display error.

Maybe this can give you some other avenues to check also.

10

Hi NC,

Thanks again for the prompt reply. It appears to be a ‘kernel panic’, as there’s specific mention of this in the Apple logs which pop-up upon re-start, though, I’m admittedly not very well-versed in reading and troubleshooting these.

In any case, I completely un-installed and re-installed. Will play around tonight and report back.

Thanks again!

11

Just to cover all the bases, you may try installing macOS 26.4 and Infuse 8.4 which were both released today.

12

Thank you to James, NC, and anyone else who reached out.

As I said yesterday, I happen to have a disability and use a power chair. Makes no mistake, I say this not for sympathy or extra attention. I state it as a practicality. For me to get off of my butt and stand up and sit down over and over again to unplug things, change cables, snake cables, etc. is really freaking tiring.

That said, I spent the morning doing just that. Re-installing the newest Infuse update, updating Tahoe to .4, re-wiring things, using newer HDMI cables, changing USB ports.

Unfortunately, nothing has worked out any better. As a matter of fact, because my mini kept re-booting on me, it would re-start with Infuse already open, and I got FOUR pink screens and re-boots WHILE writing this very post. I finally just closed the program prior to writing that last sentence.

In any case, while I genuinely appreciate what NC posted as far as potential Gemini resolutions, here’s my bottom line: pre-Infuse install, my Mac mini rarely, if ever, gets turned off, except when we go on our annual vacation once a year for two weeks, runs a Roon server, a Plex server, two SMB shares, has to be rock-solid for 16-20 hour work days, and comes with a partridge and a freaking pear tree, OK? LOL.

It’s not the HDMI port, it’s not the cable, GPU initialization issues from sleep aren’t causing it, because it’s not only happening when it awakens from sleep, it happens on-demand, every time I attempt to load a share with Infuse. Insufficient bandwidth or power is unlikely, given the external is connected directly to the mini and there are no other dongles or docks involved.

I’m not sure what the cause might be, maybe it is one of those, none of those, all of them, or some of them, but, at this point, I’m choosing to post the initial piece of the Apple logs that pop-up upon each re-boot for anyone at Infuse who wants to take a gander. Why? I don’t know, really. Maybe it helps the next person down the line who desperately searches the web to rectify a similar issue.

As far as I’m concerned, I believe my little tryst with Infuse is just about over. I will have to find another way to engage with Steven Wilson’s Headphone Dust music store, as his site’s recommendation of using Infuse, along with my own long-standing need of real .ISO support, was central to my decision to finally purchase the software.

Thanks again to all who tried to assist. Here are those Apple logs. If there is anything personally revealing in there, please do be a noble individual and let me know so I can remove it. Please don’t let me unwittingly keep something stupid up here LOL. All the best and thanks again.

panic(cpu 3 caller 0xfffffe0030ebd670): Kernel data abort. at pc 0xfffffe0030560c2c, lr 0xc0edfe002be80c1c (saved state: 0xfffffe866f0272d0)
x0: 0xfffffe2d5227d010 x1: 0xfffffe1cf31a5820 x2: 0x000000000072d045 x3: 0xfffffe2d52280000
x4: 0xfffffe1cf31ae810 x5: 0x0000000000000010 x6: 0x0000000000000000 x7: 0x0000000000000000
x8: 0x0000000000030001 x9: 0x0000000000000000 x10: 0xa5a6fe21bb326780 x11: 0x0000000003080000
x12: 0x0000012800000080 x13: 0x000a000000181b00 x14: 0x00000050000000d3 x15: 0x0072006500730075
x16: 0xfffffe0030560bd0 x17: 0x000000000000bcad x18: 0x0000000000000000 x19: 0xfffffe866f027728
x20: 0xfffffe1cf5a09f70 x21: 0xfffffe1cf5ab3050 x22: 0xfffffe2d5227d010 x23: 0xfffffe2d5209d640
x24: 0x0000000000000048 x25: 0xfffffe22d63fb120 x26: 0x0000000000000000 x27: 0xfffffe2d5209d610
x28: 0xfffffe2d5227caa8 fp: 0xfffffe866f027620 lr: 0xc0edfe002be80c1c sp: 0xfffffe866f027620
pc: 0xfffffe0030560c2c cpsr: 0x20401208 esr: 0x0000000096000047 far: 0xfffffe2d52280000

Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 25E246
Kernel version: Darwin Kernel Version 25.4.0: Thu Mar 19 19:32:36 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T8103
Fileset Kernelcache UUID: F0E2DD2762128E1332725AB6051CB6B3
Kernel UUID: 70D53731-2352-3FFF-9B2C-0E87E2A8BFF0
Boot session UUID: 5F5EE484-7AEF-4442-BE92-1DEC7F71477F
iBoot version: mBoot-18000.101.7
iBoot Stage 2 version: mBoot-18000.101.7
secure boot?: YES
roots installed: 0
Paniclog version: 15
KernelCache slide: 0x0000000024f44000
KernelCache base: 0xfffffe002bf48000
Kernel slide: 0x0000000024f4c000
Kernel text base: 0xfffffe002bf50000
Kernel text exec slide: 0x000000002955c000
Kernel text exec base: 0xfffffe0030560000
mach_absolute_time: 0x10f2a6a43
Epoch Time: sec usec
Boot : 0x69c3e3b4 0x00016f67
Sleep : 0x00000000 0x00000000
Wake : 0x00000000 0x00000000
Calendar: 0x69c3e46c 0x00084716

13

We’re looking into your logs to see if there are any clues as to what may be causing this. It’s not something we’ve seen or had reports of before.

Thanks for your patience.