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

this problem:

"panic(cpu 14 caller [...]: cpu14: LLC Bus error from cpu2:

LLC bus is likely a cache bus. Data items on their way from memory are cached multiple levels, and at one point your data incurred a Bus Error.

This could be a one-off error. If it does not look that way, you may have a serious Hardware issue. Luckily if your Mac is new, it has a serious warranty as well.

¿what is the date of your most recent backup, and by what method?

NB>> Genius Bar technicians are NOT trained to interpret kernel panic reports.

if you just make an appointment at the Genius Bar, Genius Bar will only fix your Mac if it fails diagnostics. You may need to work with Apple support to affirm that there is a problem, and if they agree, they will DIRECT an Apple store or an Apple-Authorized service Provider to swap the mainboard to effect the repair.

Also, if your Mac was bought DIRECT from Apple, (not from Reseller of any description) you have 14 days [firm] to return or exchange for full value, for any reason.

Hi Frank

The latest macOS versions are having various issues with automatic computer sleep mode.

Some systems crash and force a restart, others freeze up and are unresponsive.

As a test:

Turn on "Prevent automatic sleeping when display is off" and only allow the display to turn off.

Leave the Mac ON and allow the display to turn OFF during the day, then shut down for longer periods of non-use.

If that helps...?

Then sending Feedback to Apple could also help.

Feedback - Mac Studio - Apple

Feedback - macOS - Apple

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.

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?

Kernel panic and the automatic Restart that follows it is not ONE problem, it is one of Thousands of Problems. It is extremely unlikely to have the same underlying cause as any other similar-sounding complaint posted here.

Best Practice is to start a NEW discussion, with your model and year and MacOS version included:

Start a NEW Discussion

The Official Apple path to resolution is to contact Apple Support, and they can have a specialist who can read panic reports contact you to interpret yours.

The technicians at the Genius Bar are not certified on reading panic reports, so you will only find someone who can interpret them rather by accident. Their main discovery tool is inspection and the Service Diagnostic. There is also a User Diagnostic that you can run yourself. Both of these check for GROSS hardware issues, but the "no faults detected while testing" code is NOT the same as "All is Well".

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.

Hi thank you. The issue was the computer going to sleep and it conflicting with the monitor which didn’t sleep at the same time. I changed the sleep settings and it fixed it. No more issues. Thank you

If you post your kernel panic here in its entirety, using the additional text icon in the reply footer, we do have some Readers (typically with developer background) who can attempt to interpret those panic reports. Even if no clear symptom emerges, this can still save a step if you DO need to contact Apple support later, because Apple Support specialists can read the panic reports you posted here, if you tell them what discussion or what Avatar.

Kernel Panic Reports are stored in the Folder at:

/Library/Logs/DiagnosticReports

If you copy and paste that string into:

Finder > Go menu > Go to Folder

it will take you to the Folder where those reports are stored.

Kernel panic reports are named with Date&Time and start or end in ‘panic’

If you find one, please post the entire report here, by using the “additional text” Icon in the reply footer (looks like a paper with writing).

Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.

mannytat--

When you post a PICTURE of text, as you have done, instead of actual TEXT, it is not searchable and not auto-translatable. For readers with limited vision, it is very difficult to enlarge to actually be read. the entire panic report should be posted using the additional text icon in the reply footer.

it might say:

panic(CPU0 ... Apple602XDPTXPort(lpdptx-phy0::

DeactivateTimeoutOccurred( ... )deactivate() incomplete 10 seconds

after displayRelease()| check DCPEXT

@AppleT8112DPTXPort.cpp.574

This suggest some hardware associated with the T602 refused to shut up when told to stop, kept talking for 10 seconds. it might be Apple T8112DPTXPort ?possibly a a display controller? that was still talking

That is a hardware malfunction.

By far the easiest way to cause poor performance, instability, overheating and crashing is to install ANY third-party speeder-uppers, Cleaners, Optimizers, or Virus scanners, Bit Torrent, or a VPN that you installed yourself. The main reason is that they are relentless in scanning your files, non-stop, looking for virus-like patterns in Everything, or looking for files that have changed. When completed, they do it all again.

¿are you running anything from any of those categories?

Without its panic reports, I do not know what was wrong with the one you turned in. But this one appears to have a Hardware Issue.

I/O DART is a Direct Memory Access controller that whips data in or out of memory at very high speeds semi-autonomously, used to support displays and mass storage device high-speed block transfers.

Unfortunatley to get satisfaction from the Genius Bar directly, it needs to FAIL a diagnostic. Their diagnostic is slightly more rigorous, but it still could pass, and then they will hand your machine back to you. They are not trained to read panic reports.

You should run the diagnostic, which typically finds only GROSS errors, but can provide more information.

if no joy AND no known Bad Actors loaded, you have to contact Apple Support and have them expedite you issue to a Specialist who can read panic reports and draw conclusions. First responders are not trained to read panic reports.

Official Apple Support

.

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.

Turn on "Prevent automatic sleeping when display is off" and only allow the display to turn off.

Leave the Mac ON and allow the display to turn OFF during the day, then shut down for longer periods of non-use.