8

My MacBook Air M2 2022 (16G, 512 GB SSD) crashes sporadically under certain circumstances. This happens for example when I accidentally move my external mouse after closing the lid. If an external monitor is connected, it turns back on and then the MacBook restarts after freezing. Afterwards, the error message reads:

panic(cpu 0 caller 0xfffffe00305392a8): DCP PANIC - ASSERT!AppleDCPDPTXPowerController.cpp:538 No device added after powering on the rails. HPD=0 - dcpav(27)
ASSERT!AppleDCPDPTXPowerController.cpp:538 No device added after powering on the rails. HPD=0
RTKit: RTKit-2419.120.45.release - Client: local-ipad14dcp.RELEASE

The cpu number varies.

This can be reliably reproduced by repeatedly hitting Esc on the login screen. The MacBook switches between hibernation and being awake and crashes after a few hits.

I have already

  • factory reset the MacBook,
  • reproduced the issue in safe mode and
  • reinstalled MacOS.

Even after these, the issue still occurs. Directly after the factory reset, without having anything external ever connected, the issue appears. This is therefore not related to the external monitor or external peripherals.

The current MacOS version is MacOS Sonoma 14.5. It also happened on 14.4. It is generally unclear when this started because, as mentioned above, it only happens sometimes.

Then, I have sent the MacBook in for repair to Apple since I was told this could be a hardware issue. In the report, it says that the "Logic Board" and "Touch ID" were replaced. But the issue is not fixed and I can still reproduce this.

For reference, on MacOS Sonoma 14.4, the message was:

panic(cpu 1 caller 0xfffffe0014798a1c): DCP PANIC - ASSERT!AppleDCPDPTXPowerController.cpp:538 No device added after powering on the rails. HPD=0 - dcpav(27)
ASSERT!AppleDCPDPTXPowerController.cpp:538 No device added after powering on the rails. HPD=0
RTKit: RTKit-2419.101.1.release - Client: local-ipad14dcp.RELEASE
Improve this question
13
  • 1
    Does this happen when the external monitor and mouse are disconnected? Have you tried connecting another external monitor (with a different cable) and another mouse?
    – IconDaemon
    Commented Jun 3 at 9:51
  • 1
    In that case, is sending it back to Apple an option? They obviously didn't fix the issue yet.
    – nohillside ♦
    Commented Jun 3 at 10:01
  • 1
    @nohillside Yes, I will do that. But first, I want to figure out if I can maybe further diagnose the issue so I can maybe provide a hint as to what they were missing. Clearly, it was not the Logic Board that was the issue.
    – schade96
    Commented Jun 3 at 10:04
  • 1
    It seems as if Apple didn’t really fix it then. Hard to diagnose from where I sit.
    – IconDaemon
    Commented Jun 3 at 10:06
  • 1
    I've also had this issue (on an M2 MacBook Air) in a similar way - I have the screen set to turn off after 2 minutes of inactivity, and when the screen turns off, if I immediately press a key to bring it back on, the laptop crashes on the spot - with the same error message.
    – numbermaniac
    Commented Jun 21 at 15:55

1 Answer 1

Reset to default
3

I have received the MacBook back from Apple the second time. This time, they also replaced the display and the lid angle sensor. This seems to have fixed the issue. I can no longer trigger it by hitting Esc on the login screen. Additionally, the screen now also feels much more responsive when it comes to sleep mode and waking up. Before, there seems to have been a longer delay and now it is almost instantaneously.

So to summarize, this was indeed a hardware issue, most likely related to the display or the lid angle sensor or both.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .