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

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

This is a software BUG, ​​for some reason some software causes this error. I was on Sequoia and it started happening for no apparent reason. After I downgraded to Sonoma 14.7, the problem went away.

MacBook M3 PRO

Error:

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

ASSERT!AppleDCPDPTXPowerController.cpp:564 No device added after powering on the rails. HPD=0

RTKit: RTKit-2758.60.99.release - Client: AppleDCP-811.60.48~457-t6030dcp.RELEASE

!UUID: a1000010-2140-1ed5-a178-80d201401ed5

ASLR slide: 0x0000000000194000

Time: 0x000000006194a393

Faulting task 27 Call Stack: 0x00000000001b3f64 0x00000000001b3924 0x00000000001b3738 0x00000000001ac368 0x000000000020cd38 0x0000000000215da0 0x00000000002f55c4 0x00000000002e5db4 0x00000000001b43b8 0x00000000001aeebc 000000000000000000

RTKit Task List:

name | pri | stack use | status | resource | warning

0 rtk_background | 007 | 848/2048 | SEMWAIT | 0xa70060 |

0x00000000001ae390 0x00000000001af2fc 0x00000000001b434c 0x00000000001aeebc

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

Perhaps. Perhaps not. Why leave it to chance? If Apple support agents are trying to deal with this problem because users submit support tickets, then that will be more likely to get Apple's attention as those support agents are likely to report an uptick in those cases without any answer. Plus you can escalate your case to get someone to work on the issue for you. What if your specific case is nothing like the others being reported? You may be waiting for something that may not even help if Apple releases a fix.

Another similar option would be if you experience the issue related to a specific third party device or software, then contact that third party device provider where the issue occurs to ask for assistance. If the problem is not with their third party device or software, then they will need to contact Apple for assistance for resolving the problem. It would add pressure from other sources for Apple to resolve the problem.

Keep in mind it can take a lot of time & work to be able to reproduce a problem others are having or to interpret where the problem may be from submitted log reports. I have a very hard time trying to figure out an issue with a Mac directly in front of me these days where I'm trying to reproduce an issue on of my clients/co-workers are having with their device, then if I can reproduce the issue....the problem becomes trying to figure out what is causing the issue & how to fix it. This is under controlled conditions. Apple doesn't have any controlled conditions unless they are able to reproduce it on demand in their own testing.

It is not unusual for some fixes to take months once Apple (or any developer) is made aware of an issue.

This is a known, widespread issue to many mac user communities, however sadly Apple has not acknowledged the problem. The display hardware is commonly faulty, which causes it, and Apple should do a recall.

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.

It can be reproduced using the following method (found on Reddit) here:

https://www.reddit.com/r/mac/comments/1c3cnsr/unexpected_restart_on_macbook_air_m2/

https://www.reddit.com/r/mac/comments/1cwc1hz/no_device_added_after_powering_on_the_rails_a/

• If I put my MacBook to sleep, wait a moment, then spam the Esc key (interrupting the sleep wake-up process), I get this error 100% of the time. 
• If I put my MacBook to sleep while simultaneously spamming inputs (interrupting the go-to-sleep process), I get this error 100% of the time. Inputs that I’ve found reliably interrupt the go-to-sleep process: 

1. 1. Spamming any keyboard key on integrated keyboard OR external Bluetooth keyboard 

• 2. Jiggling of mouse on trackpad OR external Bluetooth mouse

zxmys wrote:

What perhaps are you talking about? I already told you we have notified Apple about the issue. There is no perhaps here.

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. HWTech specifically described contacting Apple Support where you will get a Support Ticket. That will be followed up by an engineer who will make contact and specifically request the logs from your computer. You usually get a contact number or date to expect a response. That is what it means to notify Apple! This will take time on your part too and if you are unwilling to do that, then that is fine too, but your complaints will not be heard. Perhaps now you understand the difference the HWTech was trying to explain to you. This is far more direct than knowing people who took their computer to the Genius Bar.

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 totally agree.. this are brand new Macs. Same happens to me, and I am an HONEST person I could not sell my mac knowing this is happening.

I feel ripped off, no response at all I report absolutely every kernel panic. I don't even feel like buying another mac, the truth is that having this is a mess, in other occasions, mac was in charge of their mess, but this so long without saying anything... it is because the situation is serious and they scammed many people, that update broke everything, broke hardware there is no solution but being repaired BY APPLE.

[Edited by Moderator]

Upgrading to Sequoia (MacOS 15) resolved about 90% of my issues but I still occasionally experience a kernel panic after the display goes to sleep. After reading your issues with Adobe, I'm thinking Adobe Creative Cloud might be part of my issue. Since I rarely use the Adobe apps, I figure I don't need Adobe Creative Cloud always running in the background. I will turn it on, as needed.

Hopefully that will resolve what the upgrade failed to resolve.

I'm from Brazil and I have the same problem. I contacted them and they sent me to technical assistance for analysis.

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

Apple will not acknowledge the issue unless it gets publicly embarrassed. It is an issue that is so widespread that they have to recall almost all M2 machines. Apple is driven by profit, so it is not in their interest to give even a hint that they recognize the problem.

zxmys wrote:

What perhaps are you talking about? I already told you we have notified Apple about the issue. There is no perhaps here.

So you know for a fact that an Apple engineer has reviewed the Kernel Panic log you submitted?