M2 Air display sometimes stays black after waking

[bosskwei]

This issue was reported on May 2023, 1.5 years before. Apple has never really take a look of users feedback. Now it becomes a widespread fault on the most recent M4 iPad: https://forums.macrumors.com/threads/m4-13-inch-random-restarts-and-resets-anyone-else.2427119/

 

[cmiksovs]

Got tired of dealing with the random black screen so set up a genius appt. My machine is 2 years old so out of warranty. I reproduced the problem easily (Apple, Sleep, keys; or Apple, Lock, ESC). The guy seemed quite experienced and he was surprised by this issue. Said he hadn't seen it before. He ran a diagnostic on the machine and the results said the lid sensor was ok. His recommendation was to leave the machine and have them reinstall the firmware (3 day turnaround). I had actually made printouts from this thread showing responses where people only got it fixed after a replacement of lid sensor and display. He said the firmware would be the next thing to try (free). A new display and lid sensor will be $600. I may pony up and pay for it - I loaded this machine with RAM and other stuff so I'd like to keep it functional at least a few more years. BTW, the guy also said you can try calling 1 800 MY APPLE to speak to someone. He said sometimes they did exceptional things to help. I plan to do the firmware reinstall but need to find 3 days when I don't need my only machine.

 

[blackketter]

Got tired of dealing with the random black screen so set up a genius appt. My machine is 2 years old so out of warranty. I reproduced the problem easily (Apple, Sleep, keys; or Apple, Lock, ESC). The guy seemed quite experienced and he was surprised by this issue. Said he hadn't seen it before. He ran a diagnostic on the machine and the results said the lid sensor was ok. His recommendation was to leave the machine and have them reinstall the firmware (3 day turnaround). I had actually made printouts from this thread showing responses where people only got it fixed after a replacement of lid sensor and display. He said the firmware would be the next thing to try (free). A new display and lid sensor will be $600. I may pony up and pay for it - I loaded this machine with RAM and other stuff so I'd like to keep it functional at least a few more years. BTW, the guy also said you can try calling 1 800 MY APPLE to speak to someone. He said sometimes they did exceptional things to help. I plan to do the firmware reinstall but need to find 3 days when I don't need my only machine.

Thanks for posting this. Please tell us how it goes!

 

[OKoP]

Got tired of dealing with the random black screen so set up a genius appt. My machine is 2 years old so out of warranty. I reproduced the problem easily (Apple, Sleep, keys; or Apple, Lock, ESC). The guy seemed quite experienced and he was surprised by this issue. Said he hadn't seen it before. He ran a diagnostic on the machine and the results said the lid sensor was ok. His recommendation was to leave the machine and have them reinstall the firmware (3 day turnaround). I had actually made printouts from this thread showing responses where people only got it fixed after a replacement of lid sensor and display. He said the firmware would be the next thing to try (free). A new display and lid sensor will be $600. I may pony up and pay for it - I loaded this machine with RAM and other stuff so I'd like to keep it functional at least a few more years. BTW, the guy also said you can try calling 1 800 MY APPLE to speak to someone. He said sometimes they did exceptional things to help. I plan to do the firmware reinstall but need to find 3 days when I don't need my only machine.

Don’t waste your time on reinstalling the firmware. It’s a hardware issue. I’ve done a clean install of the firmware and it was just a waste of time. It isn’t worth 3 days off your machine. Replace the display and the lid angle sensor to get it permanently resolved. Good luck.

 

[Tautoz]

I have some bad news - I have a MacBook Air M3 that has just started exhibiting the exact same issue, so Apple didn't fix it for the jump to the M3.

It's reproducible randomly on wake, and with the same sleep/lock & esc/keypresses steps as all of you. I purchased my computer shortly after launch, so it’s been 9 months or so. I'm still under warranty, so I'll attempt to get Apple to replace the screen & angle sensor soon.

However! I also have good news.

I found a workaround that will get the screen back up and working, at least in my case (remembering that I have an M3, so I have no idea if it will also work for the M2 - but I figure it's worth a try, since my Air exhibits exactly the same issue).

I found that connecting and disconnecting an external monitor would (sometimes) cause the internal display to reset and start displaying video again. Since it's a laptop, and I don't usually have an external monitor handy, I've bought a ~US$10 tiny portable "dummy plug" or "virtual display adapter" that you can plug into the USB-C port that emulates an external monitor. Sometimes it takes a couple of times plugging & unplugging, but so far I've always been able to get the screen to come back without resorting to powering down.

This is the adapter I bought: https://www.aliexpress.com/item/3256807330821015.html If you bring a USB-C to HDMI adapter with you anyway, you can get an HDMI dummy plug for even less, more like $2.

I hope that this works for the M2 Airs with this issue just as well as it works for my M3.

 

[1TinWoman]

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

G’day thanks sooo much for your share. I’m having the exact same issue with a MBA 2 I bought for my 14 year old daughter on the 14 Jan 2025.

Is there any chance you might share the Apple Executive and/or email address as Apple Support isn’t being g helpful at all. Cheers

 

[1TinWoman]

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

PS: I have reinstalled macOS twice and installed new updates, still having the same problem 🤦🏻‍♀️

 

[Bigwaff]

I recently had my M2 MBA repaired under AppleCare for this issue. The display and the display angle sensor were replaced. Just got it back so I haven't had an opportunity to test whether the issue is fixed, but I can say I can no longer use the ESC key to recreate the issue.

 

[bryanrojas99]

Good afternoon guys, it plays this error many times on my Macbook Air M2 with 16gb for months , I'm sure since Sequoia 15.0 beta public 3, sometimes when I had long hours of sleep and sleeping manually shutdown and reboot , also when I locked the screen and pressed the ESC key had even kernel panic.

Today I updated to version 15.3.1 Sequoia🌳 with the hope that apple has solved the error and so far it has not happened, I have done:
put the MacBook to sleep on power and wake up, then tap the escape key: No error. no kernel panic.✅
put the MacBook to sleep on battery power and wake up, then touch the escape key: No error, no kernel panic.✅
I have done the above 5 times
I also did the test with an Apple Thunderbolt Display 2011 connected.
I hope it helped , anyway I will continue to test with continuous use.
Regards

 

[jylcheung]

Good afternoon guys, it plays this error many times on my Macbook Air M2 with 16gb for months , I'm sure since Sequoia 15.0 beta public 3, sometimes when I had long hours of sleep and sleeping manually shutdown and reboot , also when I locked the screen and pressed the ESC key had even kernel panic.

Today I updated to version 15.3.1 Sequoia🌳 with the hope that apple has solved the error and so far it has not happened, I have done:
put the MacBook to sleep on power and wake up, then tap the escape key: No error. no kernel panic.✅
put the MacBook to sleep on battery power and wake up, then touch the escape key: No error, no kernel panic.✅
I have done the above 5 times
I also did the test with an Apple Thunderbolt Display 2011 connected.
I hope it helped , anyway I will continue to test with continuous use.
Regards

Hi Bryan,
Thanks for sharing.
I've a MBA M2 8GB that has been suffering from this annoying DCP PANIC issue for a few months and am able to reproduce this when I select "Lock Screen" and press ESC twice which may take me a couple of attempts.
But having just installed the latest 15.3.1 update - I'm still able to reproduce this issue

 

[bryanrojas99]

Hi Bryan,
Thanks for sharing.
I've a MBA M2 8GB that has been suffering from this annoying DCP PANIC issue for a few months and am able to reproduce this when I select "Lock Screen" and press ESC twice which may take me a couple of attempts.
But having just installed the latest 15.3.1 update - I'm still able to reproduce this issue

I'm sorry to hear that it didn't work for you

My configuration:

FileVault🔐 = Disabled
Share->Screen Sharing🖥️ : Disabled

mi configuración de sueño🤖 $ pmset -g
System-wide power settings:
SleepDisabled 0
Currently in use:
standby 1
Sleep On Power Button 1
hibernatefile /var/vm/sleepimage
powernap 1
networkoversleep 0
disksleep 10
sleep 1 (sleep prevented by powerd, sharingd)
hibernatemode 3
ttyskeepawake 1
displaysleep 5
tcpkeepalive 1
lowpowermode 0
womp 0

Anyway, I will do tests with the battery between 50% and 20%
Saludos

 

[StoneJack]

when such things happen to my Macbook Pro 3 is when it was closed and when I open the lid, it is still black.
So I just close the lid and reopen it and it is fine.

 

[YEYE33]

Good afternoon guys, it plays this error many times on my Macbook Air M2 with 16gb for months , I'm sure since Sequoia 15.0 beta public 3, sometimes when I had long hours of sleep and sleeping manually shutdown and reboot , also when I locked the screen and pressed the ESC key had even kernel panic.

Today I updated to version 15.3.1 Sequoia🌳 with the hope that apple has solved the error and so far it has not happened, I have done:
put the MacBook to sleep on power and wake up, then tap the escape key: No error. no kernel panic.✅
put the MacBook to sleep on battery power and wake up, then touch the escape key: No error, no kernel panic.✅
I have done the above 5 times
I also did the test with an Apple Thunderbolt Display 2011 connected.
I hope it helped , anyway I will continue to test with continuous use.
Regards

Hey, did you put the MacBook to sleep and immediately press the ESC or Space key within 1 second? does this error occurred in recent days?

 

[bryanrojas99]

Hey, did you put the MacBook to sleep and immediately press the ESC or Space key within 1 second? does this error occurred in recent days?

Yes, I put the Mac to sleep and immediately pressed ESC (with the screen off) and it just woke up, I pressed ESC again on the login screen, it turned off but with another key it woke up again, it seems that the normal behavior is that if you have the screen locked ESC turns off the screen (as if you were closing the lid of the MacBook)

I haven't had any kernel panic since the upgrade. I work as a programmer so I get very heavy use.

 

[thohnb]

Yes, I put the Mac to sleep and immediately pressed ESC (with the screen off) and it just woke up, I pressed ESC again on the login screen, it turned off but with another key it woke up again, it seems that the normal behavior is that if you have the screen locked ESC turns off the screen (as if you were closing the lid of the MacBook)

I haven't had any kernel panic since the upgrade. I work as a programmer so I get very heavy use.

How is your Macbook right now? You encounter anything from since?
I just get my Mac Air M2 yesterday from my local store. I worried that will happend to me in future too

 

[bryanrojas99]

How is your Macbook right now? You encounter anything from since?
I just get my Mac Air M2 yesterday from my local store. I worried that will happend to me in future too

Dear Thohnb, since the last update (15.3.1) until today I have not had any problems with the MacBook Air, I can say that the update has solved the problem. My common use is 10 hours a day, with or without an external monitor.

Greetings

 

[Shinra-Tensei]

Hello,
I have the same issue with my MacBook Pro 14” M3.
When I’m watching a movie and pause it, the screen goes black after two minutes (which is expected). However, I can’t get it back by pressing any key on the keyboard—only F1 or F2 (brightness controls) seem to bring the screen back.

I went to the Apple Store, and the diagnostic showed no issues. They first formatted the Mac, but that didn’t solve the problem. Then, they replaced the screen and the lid angle sensor, but it didn’t work either. Finally, they even changed the logic board, yet the issue persists.

I first noticed this problem in October 2023, and I have no idea how to fix it. Does anyone have a solution?

However, if I disable automatic brightness adjustment, the issue seems to go away.

 

[Bigwaff]

However, if I disable automatic brightness adjustment, the issue seems to go away.

Interesting. Perhaps there is an issue with the ambient light sensor near the camera... but you say they replaced the display, which would have included a new ambient light sensor. Seems software related... Are you covering the camera with a privacy shield?

 

[Shinra-Tensei]

Interesting. Perhaps there is an issue with the ambient light sensor near the camera... but you say they replaced the display, which would have included a new ambient light sensor. Seems software related... Are you covering the camera with a privacy shield?

Hello
That’s what they told me at the Apple Store, and they replaced the screen for that reason. I initially thought it might be a software issue since I’ve had this problem for a long time, and I see others have experienced it for a long time too. I assumed it was software-related, which is why I waited until now to visit Apple. I’m not covering the camera or anything.

 

[thohnb]

Hello . Does this usually happened in Macbook air M2 after long time usage?

 

[ParsaS]

I have it too
Bought it 5 months ago
And today just experienced it.
Is there anyone with a new MacBook Air m2 not experiencing it?
Or is it just kinda all of them

 

[OKoP]

I have it too
Bought it 5 months ago
And today just experienced it.
Is there anyone with a new MacBook Air m2 not experiencing it?
Or is it just kinda all of them

You're within the warranty. Open a case to replace the lid angle sensor and the display, don't wait for the warranty to expire.

 

[ParsaS]

You're within the warranty. Open a case to replace the lid angle sensor and the display, don't wait for the warranty to expire.

Nope I don’t have the option there’s no Apple Store here

 

[OKoP]

Nope I don’t have the option there’s no Apple Store here

Contact them online. I shipped my MBA through a delivery service for this repair. They arranged everything. Got it fixed and back within a couple of days.

 

[ParsaS]

Contact them online. I shipped my MBA through a delivery service for this repair. They arranged everything. Got it fixed and back within a couple of days.

Why would I do that it’s too risky, I never experienced it in 5 months cause I never turn it on with esc, pressing one button multiple times for turning it on, let it alone

So I guess I’d consider it a thing with my computer for 4 years, it’s gonna change and your gonna get another computer in years just use it, and don’t be a creepy person who presses esc multiple times to turn the Mac on. If it was something normal they’d find out about it during their testing before manufacturing for the world