Macbook Air M1 - kernel panic

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

Posted on Dec 22, 2020 1:17 PM

Reply
Question marked as Top-ranking reply

Posted on Apr 6, 2021 8:50 AM

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).

Similar questions

214 replies

Jul 8, 2021 7:54 PM in response to MacJam2010

I thought it was my usb C hub too and was about to spend another 100 bucks for another one but I guess that's not the issue. first the mouse stops to move, then the display goes pink, and the MacBook restarts, exact same problem. And when I just use the laptop, it works fine. It happens like 5 times daily and I am sick and tired of it now.

Jul 8, 2021 7:57 PM in response to blatny

It's happening up to 5 times daily now.


panic(cpu 0 caller 0xfffffe002e459798): "dart-disp0 (0xfffffe2332d8c000): SMMU(SMMU) error: SID 0 PTE invalid exception on read with DVA 0x24000 (TTBR 0 SEG 0 PTE 0x9) ERROR_STATUS 0x80000004 TIME 0x6df96286a803 TTE 0 AXI_ID 0)"

Debugger message: panic

Memory ID: 0xff

OS release type: User

OS version: 20F71

Kernel version: Darwin Kernel Version 20.5.0: Sat May 8 05:10:31 PDT 2021; root:xnu-7195.121.3~9/RELEASE_ARM64_T8101

Fileset Kernelcache UUID: FB10CC0AB8BAC020BC47A50D64476F11

Kernel UUID: 07259C53-9EF7-32FF-821D-8F28A5985DFA

iBoot version: iBoot-6723.120.36

secure boot?: YES

Paniclog version: 13

KernelCache slide: 0x0000000025280000

KernelCache base: 0xfffffe002c284000

Kernel slide:   0x0000000025dc8000

Kernel text base: 0xfffffe002cdcc000

Kernel text exec base: 0xfffffe002ce98000

mach_absolute_time: 0x2a3ae6d1677

Epoch Time:    sec    usec

 Boot  : 0x60c4bb2d 0x0007186e

 Sleep  : 0x60c96385 0x0008e8c2

 Wake  : 0x60c96479 0x00024e93

 Calendar: 0x60c98a91 0x0003ea66


CORE 0 recently retired instr at 0xfffffe002d009240

CORE 1 recently retired instr at 0xfffffe002d00a6f4

CORE 2 recently retired instr at 0xfffffe002d00a6f4

CORE 3 recently retired instr at 0xfffffe002d00a6f4

CORE 4 recently retired instr at 0xfffffe002d00a6f8

CORE 5 recently retired instr at 0xfffffe002d00a6f8

CORE 6 recently retired instr at 0xfffffe002d00a6f8

CORE 7 recently retired instr at 0xfffffe002d00a6f8

Panicked task 0xfffffe1667b30e60: 3707 pages, 19 threads: pid 342: WindowServer

Panicked thread: 0xfffffe1667b7b960, backtrace: 0xfffffe30193e74f0, tid: 3053

 lr: 0xfffffe002cee6be4 fp: 0xfffffe30193e7560

 lr: 0xfffffe002cee69c8 fp: 0xfffffe30193e75d0

 lr: 0xfffffe002d00fa70 fp: 0xfffffe30193e75f0

 lr: 0xfffffe002d0012b8 fp: 0xfffffe30193e76a0

 lr: 0xfffffe002ce9f7e8 fp: 0xfffffe30193e76b0

 lr: 0xfffffe002cee6658 fp: 0xfffffe30193e7a40

 lr: 0xfffffe002cee6658 fp: 0xfffffe30193e7ab0

 lr: 0xfffffe002d6983e8 fp: 0xfffffe30193e7ad0

 lr: 0xfffffe002e459798 fp: 0xfffffe30193e7d40

 lr: 0xfffffe002e459270 fp: 0xfffffe30193e7dd0

 lr: 0xfffffe002e458a5c fp: 0xfffffe30193e7e80

 lr: 0xfffffe002d5c5ec0 fp: 0xfffffe30193e7ec0

 lr: 0xfffffe002d5fbdc0 fp: 0xfffffe30193e7f20

 lr: 0xfffffe002e0068c8 fp: 0xfffffe30193e7fb0

 lr: 0xfffffe002d5ec9e0 fp: 0xfffffe30193e7fc0

 lr: 0xfffffe002d003ce0 fp: 0xfffffe30193e7fe0

 lr: 0xfffffe002ce9f85c fp: 0xfffffe30193e7ff0

   Kernel Extensions in backtrace:

     com.apple.driver.AppleT8020DART(1.0)[F6E1E036-504F-3FDF-B83B-6732226FF906]@0xfffffe002e454000->0xfffffe002e45bfff

      dependency: com.apple.driver.AppleARMPlatform(1.0.2)[F784412E-33CC-3859-B0CB-D0A62C9E26CB]@0xfffffe002d7f4000->0xfffffe002d843fff

      dependency: com.apple.driver.IODARTFamily(1)[55309CB3-D624-3B9B-962A-E82571B663FC]@0xfffffe002ef2c000->0xfffffe002ef3ffff

     com.apple.driver.AppleInterruptController(1.0d1)[E7931F7A-8581-32B7-8A33-394B279B926C]@0xfffffe002e004000->0xfffffe002e007fff

      dependency: com.apple.driver.AppleARMPlatform(1.0.2)[F784412E-33CC-3859-B0CB-D0A62C9E26CB]@0xfffffe002d7f4000->0xfffffe002d843fff


last started kext at 1042743109: com.apple.driver.usb.IOUSBHostHIDDevice 1.2 (addr 0xfffffe002cc54000, size 16384)

loaded kexts:


My first apple product and it is freaking disappointing!!!

Jul 18, 2021 5:58 PM in response to Libavius

I’m old enough that my memory does play tricks on me, but I’m quite sure the poster said she had the problem with an iMac. I don’t recall however if an additional monitor was mentioned or not. My MBP has only done it with an additional monitor attached, and had the worst frequency of kernel panics with a Dell monitor. I have had one panic event with an LG monitor. It has not occurred when I am just using the laptop without any peripherals. There are a few posters in the thread who have, however. I’m sorry if I’ve remembered incorrectly about the iMac issue, but sometimes I can’t remember what I had for breakfast.

Jul 21, 2021 1:13 AM in response to Rodolphe33

Well, my replacement M1 had the pink flash, Kernel panic and spontaneous reboot this morning, while checking emails plugged into a monitor. First defective M1 they sent did the same - and I also have logs to show that one crashing with no peripherals, nothing more than Safari running. I wasn't using Safari today. I've had crashes whether I've used a Mac Thunderbolt adapter; an Anker one or had no peripherals attached at all. It may be that the pink flash only happens when my (2 year-old) external monitor is attached. It may be that I've only noticed the pink flash with that particular setup.


Does anyone know which department of Apple to write to about this? I don't want to go through tech support and be palmed off again with the 'it's a one off' / 'it's your setup' story again. All the evidence here suggests otherwise. They shouldn't be surprised to get another call about this - I'd be astonished if they're not aware this is a systemic problem.


This machine is unusable as it's so prone to crashing. At least that means we have consumer rights law.

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.

Macbook Air M1 - kernel panic

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