Brand new Mac Studio restarts because of a problem all the time

That report is a serious hardware problem. If it is the same problem all the time, your Mac needs service (or an exchange).

if you send it for service, your files will not be returned to you, so good luck with Web-based backups -- restore can easily take THRRE DAYS. You may be better off in the long run connecting an external drive and making a time machine backup.

Having the same issue. A little bit different panic dump though . . .

{"bug_type":"210","timestamp":"2024-04-05 18:45:43.00 -1000","os_version":"macOS 14.4.1 (23E224)","roots_installed":0,"incident_id":"DB0B0F97-8087-4214-AA30-32244A0474E8"}

{

"build" : "macOS 14.4.1 (23E224)",

"product" : "Mac14,13",

"socId" : "6021",

"socRevision" : "11",

"incident" : "DB0B0F97-8087-4214-AA30-32244A0474E8",

"crashReporterKey" : "34E63189-386B-ED69-9C22-A164CDFC0057",

"kernel" : "Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:49 PDT 2024; root:xnu-10063.101.17~1\/RELEASE_ARM64_T6020",

"date" : "2024-04-05 18:45:43.15 -1000",

"panicString" : "panic(cpu 1 caller 0xfffffe001e26ad70): \"AppleT602XDPTXPort(lpdptx-phy0)::deactivateTimeoutOccurred(0x100000410): deactivate() incomplete 10 seconds after displayRelease()! (check DCPEXT)\\n\" @AppleT8112DPTXPort.cpp:574\nDebugger message: panic\nMemory ID: 0xff\nOS release type: User\nOS version: 23E224\nKernel version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:49 PDT 2024; root:xnu-10063.101.17~1\/RELEASE_ARM64_T6020\nFileset Kernelcache UUID: A5DBC30112639C0125B0F8101083FBF5\nKernel UUID: D3BBDD1F-7813-3F26-9F94-41BAABDA6E33\nBoot session UUID: DB0B0F97-8087-4214-AA30-32244A0474E8\niBoot version: iBoot-10151.101.3\nsecure boot?: YES\nroots installed:

Any educated thoughts?

Mahalo

the essence of that one is this line:

"panic(cpu 1 caller 0xfffffe001e26ad70): \"AppleT602XDPTXPort(lpdptx-phy0)::deactivateTimeoutOccurred(0x100000410): deactivate() incomplete 10 seconds after displayRelease()! (check DCPEXT)\\n\"

T6000 is the internal identifier of the M1 Max (or Ultra) system on a chip.

could be displayPort or ThunderBolt port Transmit out, which could be a display-generator.

MacOS tried to shut it off, and 10 seconds later it had still not said it had transitioned to OFF.

is this a recurring problem? a One-off problem?

what GROSS symptoms are you seeing outside of the panic report?

what EXACT model Mac by year, processor type and Pro/ Max/ Ultra

what displays are connected and how are they connected?

Thank you for your analysis.

My Mac Studio is a 2023 M2 Max, 64GB ram, 2TB disk.

I have a 27” Studio Display - directly connected and a 27” Dell monitor via direct HDMI.

The panics are ‘common’ with the occurrences seeming to be happening more frequently-sometimes multiple a day. Other times less often as in days apart.

I’m disconnecting peripherals [OWC 14 port bridge etc.] and will start disabling startup programs.  

i suspect, maybe, it might be my screen saver [world map w/ solar and weather] or the driver app for an ADA mouse [Contour roller mouse].

Overnight the problem wasn't present. I have the OWC Dock disconnected, not using the Contour App but still have the screen saver running. The OWC Dock has a DisplayPort but that isn't in use.

Mahalo for your assistance!

it seems like this specific issue should only be possible when you are telling a display to stop (and it does not affirm that it HAS stopped within ten seconds).

So at times when the display stays on all the time, or Off all the time, I would not expect to see that same issue at all.

UPDATE: My Mac Studio [M2 Max - 64GB / 2TB SSD] has been stable.

I unplugged the OWC 14 Port Dock [which only really removed a Canon f9000 Scanner and a Western Digital external USB drive] which has a mini DisplayPort [unused]. Tested the MS going to sleep by menu selection and by dormancy and both came back to life fine. Reattached the Dock after turning the Energy Saver off as suggested. Will report later - either way.

FrankBear--

Your post will be here for a long time, and readers may find your post by searching the internet for a similar issue.

Could you please summarize how you fixed this problem, and what more you learned that might help others in a similar position?

Thanks very much !

Aloha, I struggled with this issue early on. I agree it has to do with second monitor sleep timing.

The other smoking gun is having the second monitor fed from the HDMI jack on the Mac Studio.

After much experimentation and patience, my final solution was to purchase a USB-C to HDMI cable and use the USB-C connector on the back of the Mac Studio and have it feed the HDMI input to the second monitor. Miraculously the panic reboots stopped after that.

Third-party file Sync-ers such as DropBox, BackBlaze, OneDrive, or GoogleDrive can markedly SLOW performance, but are not inherently dangerous.

They were Quickly ported from that other Operating System, and were never re-written to take advantage of the MacOS ‘File System Event Store’.  The typical brute-force search they use takes all afternoon for one pass. That relentless searching is a completely un-necessary waste of resources.

Synch and Backup programs like iCloud Drive and Time Machine that DO use the MacOS File System Event Store can find changes really quickly and be done with their work and suspend themselves. Time machine can run backups Hourly, while all those others are still beating on the file system for the first pass, four hours later. By the time they have finished, they need to start again.

Hey Grant,

I just opened a new topic about a very similar issue.

Your input would be much appreciated!

Regards,

Ben

If you are not happy with this work-around, then send Feedback to Apple using the following links.

Feedback - Mac Studio - Apple

Feedback - macOS - Apple

I have been having the same issues with my Mac Studio.