Kernel panic after waking up: DCP PANIC - ASSERT!AppleDCPDPTXPowerController.cpp:538

Same issue here with M2 Pro mac 2023, my mac's main display would go blank but rest of the mac works fine (I can hear the OS sounds and see the mac on external monitor) and after several restarts the display comes back live with this same kind of panic error.

Sometimes even after several restarts the mac display doesn't come back and then after hours of leaving the mac to rest, it reboots itself back with a working display. There seems to be no specific trigger point to this problem that I could identify, sometimes it happens when display goes to sleep with open lid, the other times it happens in between I'm working and also sometimes when mac's lid is closed.

Went to apple authorized service centre for this...they first said that this is a software issue and re-installed the macOS and also reinstated the firmware (as they claimed) but even after that, the issue persisted and then this time they said it's an hardware issue with the logic board which needs to be replaced.

But then I contacted apple support over a call and the support person looked at the error logs from console of my mac through screen sharing and concluded that this is caused by some applications demanding for root access/superuser access of my mac repeatedly (in my case adobe softwares as he claimed) and the mac denies it every time thus sending the mac into a forever loop causing the display issue and the kernel panic error.

Will be trying to use the mac after uninstalling the adobe apps.

b3nparker wrote:

@Utania Is that something only the Apple Store staff can do? Or do you mean that the genius reset the PRAM?

The only reprogramming available is a DFU firmware Revive or Restore:

How to revive or restore Mac firmware - Apple Support

I solved this error message by upgrading to 15.0.1 Sequoia from Sonoma 14.7.

My specifics:

• MacBook Air M2 (2022)
• No peripherals
• Nothing running upon shutdown other than login items & copied.app
• 60% of the time I'd get this error message after shutdown: panic(cpu 0 caller 0xfffffe0029aaeea8): DCP PANIC - ASSERT!AppleDCPDPTXPowerController.cpp:538 No device added after powering on the rails. HPD=0 - dcpav(27)

You have to call Apple Support to get them to refer you, at least that's what I just did, I have my appointment tomorrow at the Genius Bar

I had this same problem on my M2 MB Air. I took it to the Genius Bar, but they did not know of a solution. The genius reprogrammed the ROM for the heck of it, and that has fixed the problem. No more kernel panic!

I have the same problem and it does seem to be when the MB2 Air sleeps- it only i started to happen today and ti has crashed twice in the last 2 hrs when I left it on- is there any reply from Apple on this? Thanks

I have the same issue for weeks now: “No device added after powering on the rails” error on a 2022 MacBook Air M2. I am out of warranty, and I am unwilling to replace the screen for the obscene amounts of money that Apple is asking. Replacing the screen is the only way to solve the problem, if I read the many comments in the Reddit thread: https://www.reddit.com/r/mac/comments/1cwc1hz/no_device_added_after_powering_on_the_rails_a/

Many of us did. You know mac os asks you if you want to send kernel crash logs to Apple after the system reboot from a crash right? Apple must have received tons of report pointing to the same issue.

Also, many got their laptops repaired by Apple to fix the issue. Apple must have seen an uptick in this kind of repair.

“If you think clicking the button to send the Kernel Panic to Apple is the same thing as what HWTech detailed in the post, you are sadly mistaken”

I never said or thought so. Where did you get the idea of that?

ConcernedCitezen wrote:

I am experiencing the same issues. It just started happening. Can I bring it in for a replacement?

Follow the advice by HWTech and contact Apple directly for support with the problem. The more information they get from the computers that are experiencing the problem, there is a better chance that a solution will be provided.

While the OP was able to reproduce the problem by locking the screen and pressing ESC several times, that is not the root of the problem that will have to be addressed. If that was it, all they would need to do is restrict the ESC key press in the Lock Screen.

I'm seeing the Genius Bar tomorrow in Beijing, MacBook Air, M2

panic(cpu 1 caller 0xfffffe002f786ea8): 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

Is there any advice in case my Genius has no idea about this? Something I can tell the "Genius"?

Perfect, I have suspended the appointment and followed what you said he'd do and was able to solve it from restarting with panic when trying to shut down by updating to OS15 in safe mode.

But now I see its to do with display and since it started after I upgraded to 14.5 and stayed when I upgraded to 14.7 I didn't think 15 would do anything so I didn't bother further upgrading to 15 until I realized that's what they'd do so I saved myself a trip, thank you.

I haven't tried the display port to my external monitor yet which I now after your reading your decode see that there was something to do with my adding an external monitor, I'll know more later when I get to the office and plug in my external displays.

But for now it's working as usual again, I'll be back if the external displays trigger the problem, I'll also switch adaptors which were from USBc to HDMI to my LG TV. I'll also plug them together with the monitor on instead of powering up after cables are connected, maybe that caused it? I also added after updating to 14.5 an Epson scanner which could have screwed something up with the old drivers, old scanner Epson Perfection V30, we'll see if the issue returns and then I can go back to the Genius Bar with more details.

Thanks.

Macbook Air M2, 2022

Same issue start happening just after updating Sonoma.

Never happened before. And Still happening now.

I did all apple support guidance, even wiped all HD (factory reset - the last "solution") and still happens, updated to last macOS, STILL happens.

The worst of all is that when a kernel panic like this happens, its a HARDWARE issue, so Apple broke our Apple's macbooks.

I don't know why, but your Sonoma broke down your, our, my computer/s you have to recall or fix this.

Kernel panic happens just when macbook goes into sleep mode and when it tries to wake, BOOM shuts down.

These are NEW computers. I dont know but we have to do something. We are apple clients and they are the responsible of this. You broke our computers with your macOS update. You have to fix it.