M2 Air display sometimes stays black after waking

[dde3]

Same issue for me on MacOS 14.5.
Pressing Esc on the login screen after waking up really is an effective way to reproduce this.

panic(cpu n caller 0xfffffe001c7092a8): 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

Since I still have warranty, I wonder if this is a hardware issue as mentioned somewhere earlier in this thread and if it can be resolved by sending in my MacBook for repair. And if I decide to do so, should I try to give hints that it might be the display and the angle sensor?

 

[salanderhsu]

I have encountered the exact same issue, but I will provide some new information to help everyone locate the root of the problem. During one occasion when I was using an external monitor, I changed the system settings for the built-in display from “Default” to “More Space” under System Settings - Display. Then, to my surprise, the black screen became smaller and turned into an immovable, unmanageable black overlay. I can interact with other files and software on my desktop, but this black area cannot be deleted or moved. I suspect this is a process that cannot be closed or handled after waking up. However, I couldn’t locate it in the Activity Monitor. I hope someone can find a way to address this issue based on this phenomenon.

 

[yz700]

I can reproduce this problem and mine is even worse. When I clicked the ESC the second time, my computer will be dead. But I tried it on Mac pro, it won't happen.

 

[yz700]

I was able to consistently reproduce the issue with above approach with my 13-inch M2 air and the same issue could occur randomly when waking the machine from sleep. I went to genius bar this weekend and I was even able to replicate the issue on their demo machines in the store. They've tried reinstalling ventura and reverting back to monterey but neither worked. A case has been filed to escalate this issue. I am still waiting for the result. If you have found a solution please do share with us. For folks who haven't submitted this issue to Apple, please do so as it may be a widespread defect.

Hi did you get any response from Apple?

 

[naterator]

Just to share my experience with this issue and how I got my MBA 13.6" M2 repaired...

A few months ago my 1.5 y/o MBA 13.6" M2 started experiencing kernel panics that were consistently styled as:

panic(cpu 3 caller 0xfffffe0026364a1c): DCP PANIC - ASSERT!AppleDCPDPTXPowerController.cpp:538 No device added after powering on the rails. HPD=0 - dcpav(27)

Based on my searching, this was a hardware issue. I did an AppleCare+ depot repair, and they replaced the USB-C ports. But the kernel panics kept occurring. I provided multiple full panic logs to Apple Support. I mailed in my MBA in to Apple for AppleCare+ depot repair two (2) more times, but they "didn't find a problem".

Getting nowhere with Apple Support, I e-mailed an executive at Apple and summarized the problem. They assigned somebody from their Executive Customer Relations team, who got somebody from support involved, who was able to pass the kernel panic logs along to an engineer. The engineer said the problem was caused by the display angle sensor.

So I mailed my MBA in for a fourth depot repair. They replaced the display hardware assembly & the angle sensor, and the issue is now resolved.

It's just surprising that this issue could be a known issue happening with several (many?) folks, and Apple doesn't have it (and the necessary repairs) documented for folks in Apple from all angles. I get that Apple is big, but this is a sort of problem they can literally throw billions of dollars at if they cared. I spent about 25 hours on this problem because Apple can't "get it together".

 

[halledise]

Just to share my experience with this issue and how I got my MBA 13.6" M2 repaired...

A few months ago my 1.5 y/o MBA 13.6" M2 started experiencing kernel panics that were consistently styled as:

panic(cpu 3 caller 0xfffffe0026364a1c): DCP PANIC - ASSERT!AppleDCPDPTXPowerController.cpp:538 No device added after powering on the rails. HPD=0 - dcpav(27)

Based on my searching, this was a hardware issue. I did an AppleCare+ depot repair, and they replaced the USB-C ports. But the kernel panics kept occurring. I provided multiple full panic logs to Apple Support. I mailed in my MBA in to Apple for AppleCare+ depot repair two (2) more times, but they "didn't find a problem".

Getting nowhere with Apple Support, I e-mailed an executive at Apple and summarized the problem. They assigned somebody from their Executive Customer Relations team, who got somebody from support involved, who was able to pass the kernel panic logs along to an engineer. The engineer said the problem was caused by the display angle sensor.

So I mailed my MBA in for a fourth depot repair. They replaced the display hardware assembly & the angle sensor, and the issue is now resolved.

thank you for your post - and your perseverance!
indeed, it was discussed earlier in this thread that it was most likely a hardware issue related only to M2 MBAs.
and as you’ve established - it is the lid angle sensor.
definitely annoying but not fatal, which would explain why Apple look the other way.
by rights, they shoulda initiated a repair program for all affected models.
however, the fact that the whole top case could need replacing they may have deemed it too potentially expensive for their bottom line. hence the ‘nothing to see here’ attitude and just deal with it on a case by case complaint.
overall Apple are a great company, but, like all of us, they can be dicks at times 😏

 

[bosskwei]

Just to share my experience with this issue and how I got my MBA 13.6" M2 repaired...

A few months ago my 1.5 y/o MBA 13.6" M2 started experiencing kernel panics that were consistently styled as:

panic(cpu 3 caller 0xfffffe0026364a1c): DCP PANIC - ASSERT!AppleDCPDPTXPowerController.cpp:538 No device added after powering on the rails. HPD=0 - dcpav(27)

Based on my searching, this was a hardware issue. I did an AppleCare+ depot repair, and they replaced the USB-C ports. But the kernel panics kept occurring. I provided multiple full panic logs to Apple Support. I mailed in my MBA in to Apple for AppleCare+ depot repair two (2) more times, but they "didn't find a problem".

Getting nowhere with Apple Support, I e-mailed an executive at Apple and summarized the problem. They assigned somebody from their Executive Customer Relations team, who got somebody from support involved, who was able to pass the kernel panic logs along to an engineer. The engineer said the problem was caused by the display angle sensor.

So I mailed my MBA in for a fourth depot repair. They replaced the display hardware assembly & the angle sensor, and the issue is now resolved.

It's just surprising that this issue could be a known issue happening with several (many?) folks, and Apple doesn't have it (and the necessary repairs) documented for folks in Apple from all angles. I get that Apple is big, but this is a sort of problem they can literally throw billions of dollars at if they cared. I spent about 25 hours on this problem because Apple can't "get it together".

I still think the undering issue is Apple's buggy system. This can be reproduced by (1) lock screen, (2) press ESC multiple times.

The anger sensor may be a problem, but can be fixed / mitigated by the undering firmware, e.g., instead of panic, the kernel wait for seconds until the display is detected.

 

[halledise]

I still think the undering issue is Apple's buggy system. This can be reproduced by (1) lock screen, (2) press ESC multiple times.

The anger sensor may be a problem, but can be fixed / mitigated by the undering firmware, e.g., instead of panic, the kernel wait for seconds until the display is detected.

if it could be fixed with a firmware update, Apple would've issued one by now.
it is a hardware issue peculiar to M2 Airs.
(unsure if M3 Airs have the same issue?)
why people want to persist with ways to make it happen, escapes me.
also, i presume you mean 'angle' not anger and 'underlying' not undering?

 

[bosskwei]

if it could be fixed with a firmware update, Apple would've issued one by now.
it is a hardware issue peculiar to M2 Airs.
(unsure if M3 Airs have the same issue?)
why people want to persist with ways to make it happen, escapes me.
also, i presume you mean 'angle' not anger and 'underlying' not undering?

Sorry for the typo. This kernel panic is not specific to a certain model or environment (reproduced on M2-M4, mostly on MBA), here are some user complains:

1. https://forums.macrumors.com/threads/m2-air-display-sometimes-stays-black-after-waking.2389035
2. https://forums.macrumors.com/threads/m4-13-inch-random-restarts-and-resets-anyone-else.2427119
3. https://forums.macrumors.com/thread...ack-after-waking.2389035/page-3?post=33014754
4. https://github.com/waydabber/BetterDisplay/discussions/2622

From my experience, it was initially brought by a system upgrade from 13.4-13.5, and deteriorated since 14.4

Anyhow, I'm not using MBA anymore. I have reported this issue frequently before with no fixes, now enjoying the smoothness of Fedora Linux on AMD Ryzen 7840.

Just give up MBA MBP, to all who see this reply

 

[Agnapot]

To add to the list of resolutions to this issue let me tell you my story with my 15' Air:
I'm not sure when it started but it would happen quite often where I would lift the lid from sleep or do any of the other wake-from-sleep things mentioned here and the screen would stay black. Oddly, in 14.4 the screen would stay black but not restart, after updating to 14.5 I could interact for about 5 seconds before the machine hard rebooted itself (Either way I'd get the "DCP PANIC - No device added after powering on the rails" crash message).
Reading this form convinced me it was a hardware issue (tho salanderhsu's issue of the black square while being able to interact with the machine is very interesting and weird!) so I took it in. It took FOUR repairs for them to finally do the thing it needed.
First they did a factory reset, which did nothing
Then they replaced the Logic board, trackpad (??) and touch ID sensor, and the issue happened again while waiting in the store after picking it up.
Then they replaced the Lid Angle sensor and "Adjusted" something, and it happened again the next morning
Then they finally replaced the display and lid angle sensor again and that seems to have resolved the issue.
So, my guess is it's the display, or maybe a bent pin, or some connector or something, but I hope this issue gets resolved for everyone!

 

[halledise]

To add to the list of resolutions to this issue let me tell you my story with my 15' Air:
I'm not sure when it started but it would happen quite often where I would lift the lid from sleep or do any of the other wake-from-sleep things mentioned here and the screen would stay black. Oddly, in 14.4 the screen would stay black but not restart, after updating to 14.5 I could interact for about 5 seconds before the machine hard rebooted itself (Either way I'd get the "DCP PANIC - No device added after powering on the rails" crash message).
Reading this form convinced me it was a hardware issue (tho salanderhsu's issue of the black square while being able to interact with the machine is very interesting and weird!) so I took it in. It took FOUR repairs for them to finally do the thing it needed.
First they did a factory reset, which did nothing
Then they replaced the Logic board, trackpad (??) and touch ID sensor, and the issue happened again while waiting in the store after picking it up.
Then they replaced the Lid Angle sensor and "Adjusted" something, and it happened again the next morning
Then they finally replaced the display and lid angle sensor again and that seems to have resolved the issue.
So, my guess is it's the display, or maybe a bent pin, or some connector or something, but I hope this issue gets resolved for everyone!

seems like you've ended up with pretty much a new, rebuilt mac.
the repairers coulda saved a lot of time and effort by just swapping it out for a brand new mac, though you would've still be in the dark as to the cause in the first place.

 

[halledise]

this problem didn’t occur with the wedge-shaped Air with M1 processor, irrespective of which version of macOS is running.
(i’m happy to stand corrected on that).
it seems to me the issue only manifested with the flat-bottomed Airs starting with the M2 and doesn’t seem to affect Pro models.
i’m currently running Sequoia beta on an M2 Air and the issue still manifests.
thus, back to my original comments - it has to be hardware and, as Agnapot has pointed out, most likely a faulty/bent connector pin.
probably occurs in the manufacturing process …

 

[boondocks]

As noted by others I have not only been able to consistently reproduce this issue on my own M2 MacBook Air, but also on any display model I found in stores around me.
At this point I find it annoying enough that I'm considering just replacing it with a new M3 model instead (e.g. using the "trade-in" program for my M2 and let Apple deal with it). Anyone know if there have been instances of M3 MacBook Airs experiencing the issue? (no local shops have them on display yet, and there is not an Apple store nearby, unfortunately).

 

[halledise]

As noted by others I have not only been able to consistently reproduce this issue on my own M2 MacBook Air, but also on any display model I found in stores around me.
At this point I find it annoying enough that I'm considering just replacing it with a new M3 model instead (e.g. using the "trade-in" program for my M2 and let Apple deal with it). Anyone know if there have been instances of M3 MacBook Airs experiencing the issue? (no local shops have them on display yet, and there is not an Apple store nearby, unfortunately).

appleinsider’s editor just posted an excellent review 3 months with an M3 Air.
he doesn’t mention at all the screen issue we all seem to have.
guess you could always contact him directly and ask?
let us know what he says, if you do …
3 months with M3 Air

 

[johnc22]

As noted by others I have not only been able to consistently reproduce this issue on my own M2 MacBook Air, but also on any display model I found in stores around me.
At this point I find it annoying enough that I'm considering just replacing it with a new M3 model instead (e.g. using the "trade-in" program for my M2 and let Apple deal with it). Anyone know if there have been instances of M3 MacBook Airs experiencing the issue? (no local shops have them on display yet, and there is not an Apple store nearby, unfortunately).

Just opened my 15" M3 Air. I keep telling my wife she should trade in her M2 with multiple issues (black screen for sure) for a newer model.

 

[Phonzoxd]

So I haven’t read ever post. But are the m3s safe?

 

[halledise]

So I haven’t read ever post. But are the m3s safe?

well, that's just plain lazy.
just read the posts on this page, if you can manage it, and there should be an answer to your query …

 

[boondocks]

Well, the place where I do have access to test MacBooks (in a limited fashion) seems to now have M3s too. Also they still have M2s, but interestingly the one I could reproduce the issue on was gone (replaced by a different color one). So what I found that I could _not_ reproduce the issue on any of the new display models that I tried on, i.e. on:

• MacBook Air M2 13" (2022) with Sonoma 14.5
• MacBook Air M2 13" (2024) with Sonoma 14.5

Note that on these display models (probably also on the earlier ones, where I could reproduce the issue?) the "Turn Display Off" is set to "Never" (for both power adapter and batter) in a way that it can not be changed (demo user). However when the lid is closed/opened the display (obviously) still turns off/on (but not clear about whether it goes to sleep and whether that matters). Also one can still set some other option (e.g. using "Hot corners") to tun the display off. So I played around with all that and could not trigger the issue on these display models (although on the M3 it happened more than once that after opening the screen came on, then went to black for a few seconds again before coming on again).
Edit: An important distinction (that I saw being mentioned somewhere else too): These "fixed" MacBook Airs all had the display come back on much quicker after opening the lid then the one (like mine) that exhibit the issue.

For a while now I have been using my M2 (that exhibits the issue and is still on Ventura) with the lid always open (and the "Turn Display Off" set to "Never" - but using a dark screen saver). This way I have been able to avoid the issue (Duh!), but obviously it is not very sustainable.
Also, I know that this is said to be a HW issue, but (given that a reboot - _WITHOUT_ adjusting the display angle - "fixes it") one would think that there would be a software based workaround (or - eventually - a firmware based fix) available that would not require a reboot (or a HW "repair").
Edit: My hunch is that some HW element (e.g. "TCON board"?) has a version that is somehow slow(er) or has some sort of timing issue that the software does not expect (but maybe could work around it - e.g. retry/re-initialize - if apple implemented that). In Sonoma this unexpected state results in a kernel panic (but in Ventura it "only" results in a a block screen (but the system still working)). This hypothesis actually seems to be supported by the fact that if the display has gone to sleep (e.g. activated using "hot corners") the issue is more likely to happen if one tries to reactivate it right away (as opposed to waiting a few (5+?) seconds)...

Also I found this reddit thread entry that seems to go into more detail on the possible underlying cause

 

[diego.caraballo]

My hunch is that some HW element (e.g. "TCON board"?) has a version that is somehow slow(er) or has some sort of timing issue that the software does not expect

I agree with this.
I believe that some of the displays have a slightly-out of specifications timing.
When the macOS powers the display back ON, it doesn't wait the necessary time (for the affected displays) to start sending video data and then the Mac just crash.
I'm hopeful for a software/firmware fix.

 

[kae3112]

I agree with this.
I believe that some of the displays have a slightly-out of specifications timing.
When the macOS powers the display back ON, it doesn't wait the necessary time (for the affected displays) to start sending video data and then the Mac just crash.
I'm hopeful for a software/firmware fix.

My MBA M2 is on macOS Sequoia Public Beta now. The issue is not addressed yet. I am reporting the issue whenever it occurs. At this point, I am not sure if they are going to address it.

 

[diego.caraballo]

My MBA M2 is on macOS Sequoia Public Beta now. The issue is not addressed yet. I am reporting the issue whenever it occurs. At this point, I am not sure if they are going to address it.

I'm reporting it every time with a description of the issue.
I keep my fingers crossed that they will fix it at software level 😅
I recently noticed that when on low power mode or with low bat the issue happens much more frequently.

 

[bosskwei]

For all your infomation, the issue is not resolved in 14.6 RC

 

[halledise]

For all your infomation, the issue is not resolved in 14.6 RC

that’s because it’s not a software issue.

 

[boondocks]

that’s because it’s not a software issue.

That might be (and is probably) true. However - as pointed out before - one would hope that it could still be mitigated in software/firmware (after all a reset “fixes” it). OTOH, since it has not been addressed so far (and the issue has been around for a year or two), maybe it can’t be.

 

[boondocks]

Since I did not want to be without my MacBook (not to mention that it is out of warranty, and I have no Apple store nearby) I just opted to do a “trade-in upgrade” with Apple to an M3 which does not exhibit the issue (although I still have a bit of PTSD every time I wait for the screen to turn back on (e.g. when opening the lid) ).

---

Some additional thoughts/notes regarding my M3 “trade-in” upgrade:

• Trade-in
  • Letting Apple know of the issue
    I did place a large printout (including links to this and other forums) in my “trade-in” return package (that was sent back to Apple) describing the problem with the M2. They still honored the trade-in value they determined at the time of my M3 order (although given that one needs to give a trade in device’s serial number, one wonders if they could have determined whether it has the issue in advance and already adjusted the trade-in value accordingly):
  • Trade-in value/selling refurbished
    Interestingly while I was contemplating this trade-in move - for about a week - the Apple offered trade in value dropped by about $100 (to $730). Yes, I might have gotten more by selling the M2 private (ebay, etc.), however - even if disclosed - I would not wish the frustration that comes with this issue upon anyone… I hope Apple addresses it (e.g. doing a screen/sensor replacement?) before selling it as “refurbished”. (If anyone is ordering refurbished from Apple it might be worth checking for this issue _first_ (i.e. before doing anything else))
• OS upgrade on the M2
  Before I sent the M2 back I fully wiped/reset it and then updated from Ventura (13.x) to Sonoma (14.x): The only difference that made was that instead of having to “hand-reboot” it when the issue happened it “conveniently” kernel-paniced and then rebooted on its own (with the usual "No device added after powering on the rails" message), as opposed to Ventura (where I had to manually restart it). While that at least meant that in Sonoma I could submit the crash report to Apple, one could say that is still a step back since in Ventura one could at least continue to use the machine “blindly” (e.g. over the network) or - presumably - with an external display.