With a slightly higher CPU load (during the game), there are repeated restarts, pink stripes appear on the black screen. I cannot interpret the reports (they are identical, see example below). The problem does not occur with the same load on Macbook Air 2015 (Football Manager 2020 game running via Epic Launcher and Chrome). Big Sur 11.1.
MacBook Air 13″, macOS 11.1
Hi all, lowering memory usage (from around 7GB closer to 6GB, of 8GB total) by closing safari tabs and some (e.g memory) resource hogging app's , e.g Spotify, resolves this issue for me. Apple needs a more elegant way of doing this, e.g low memory warning, unless this is actually a bug in macOS or M1 hardware.
BTW, I can now use an extra monitor memory again without KP's. Although not using an external monitor requires less Vram used (from main Ram) which may resolve the issue instead (but didn't for me, without closing app's).
How many of you who report it this happening very frequent when a screen is connected tired to use the screen without *any* adapter?
USB-C cable directly. And power directly.
No other externals? (internal keyboard or Bluetooth when on the two port air)
Maybe it is connected to a power issue that causes more frequent issues when more power is drawn from one port?
Yesterday’s security update from Apple, 11.5.1, had one detail that made me wonder if it might apply to this problem. There’s something mentioned about handling memory better. I’m curious if any of you are still experiencing problems after installing Yesterdays update.
Agreed. Update to 11.5.2 and this problem should go away. Finally!
Hi, it's been 2 months since they changed the motherboard, I think you just have to send it again.
Hi
FM seems to be the issue. I had the same generic reply from Sega. Surly tens of thousands of people with ARM Mac's with be playing FM, it seems that only a small percentage have this problem. I am wondering what some are doing that others are not.
Did you clean install your Mac M1 when new or transfer over with time machine. I initially had a lot of issues with the transfer causing access and permission issues.
I am having the same issues. I bought MacBook Air M1 a few months ago, connected to a LG monitor via a hub. Only used Safari, viewer, and Word. Mac crashed 3 times in 2 months since new with the pink screens. After the third time I serviced my Mac at the Apple store in the Netherlands. They told me it was a hardware fault, and installed a new Touch ID and Logic board.
Now, 6 weeks later, it crashed again. The crash log is similar to the ones posted here. I made photo's of everything and I am going back to the Apple store again. Looking at the messages in this thread here, I think the LG monitor (or monitors in general) could be the problem.
I had it now a few more times. Nothing connected to the Macbook. But i noticed the cursor starts to stutter while using the trackpad before its going to crash. The stuttering can be solved by closing the lid and wait a few seconds. Maybe that also prevents it from crashing.
Same here, same apple m1 dart-disp0 exception kernel panic, almost every day or second day while hooked up to external monitor Lenovo Thinkvision T25m-10 Fhd 25" - Black 25" 1920 x 1200 (directly hooked up over usb-C connection the monitor has)
Similar indeed. Are you using the HDMI cable though that came with your monitor? This would be helpful to know since this is day 4 of my using the Belkin Ultra HD High Speed HDMI cable and it hasn't rebooted on its own once....thank goodness....knock on silicon.....
Sorry to hear that Ced38.
FYI, after one month panic-free with the Belkin HDMI cable and Apple adapter the crashes started up again. So I uninstalled all software and peripherals, one by one. Eventually it came down to disconnecting the monitor, and voila - problem solved.
I'm thinking of getting a wireless adapter for the monitor, or buying a new one - I wonder if there is a particular brand of monitor recommended by Apple for the M1 machines? Just enjoying life without panics for now, though.
"Do you think it's time to give up on the M1 and wait until they release a setup that's properly tested and debugged?"
I would say "yes".
I went into my local Genius Bar last Saturday - you can see from my various comments on this thread that I've had very similar problems related to my external monitor on two M1 Macbook Airs. The head tech there said I could wait for a 'miraculous' firmware update from Apple or get my money back, as the product isn't working as advertised. Apparently he's seen a lot of folks with similar issues.
Can't wait around for the next gen Macbook, so I think I might get an M1 Imac instead, as I don't see any major problems with them reported on this forum. Yet.
Pink screen with restart just after connecting the MacBook to a dell external monitor and a generic dock directly with two usb-c cables. The problem was happening less frequently since I stopped using an anker hub.
Unfortunately the computer crashed again yesterday.
The log report have slightly changed, I am now know having :
panic(cpu 3 caller 0xfffffe0011997344): "busy timeout[0], (60s): 'AppleAPFSMedia'"
Debugger message: panic
Memory ID: 0x6
The apple senior advisor wants me to do a complete reinstall of the system without using the time machine as the previous backups might be corrupted.
"The apple senior advisor wants me to do a complete reinstall of the system without using the time machine"
There seem to be a lot of folks working at Apple who genuinely don't know about this problem - I was told the same thing regarding clean reinstall on a number of occasions.
Have you considered installing Monterey beta?
Guys, maybe the information will be useful for someone. So.. I was hoping that the problem with kernel panic arises purely from connecting the external monitor to hdmi, so I bought a Display Port to usb-C cable and connected my monitor directly to the computer port. And got panic again ...
Thus, the problem is not only in connection via hdmi, but when connecting an external monitor in any way ...
Your monitor is connected by Thunderbolt cable and not HDMI??
Macbook Air M1 - kernel panic
