M1 MacPro kept crashing and restarting

TheLittles have provided good guidance for routine crashes and errors that can not be immediately identified.

But Yours looks like a fairly serious Hardware error. If it happens again for the same reason, it is likely that it will never get better.

The memory on the system on a chip is organized in planes, and Plane1 (or its Control Bus [TAG]) is generating a parity error.

The extensions at the scene of the crime are THE most fundamental Hardware drivers for Apple-silicon processors. T6000 is the Max processors internal designation. Seeing its Hardware error handler in your report is ominous.

You should run the User diagnostic, but the default message says "no faults detected", which is no where near "all is well".

if this Keeps up, you should, with or without a diagnostic failure, contact Apple Support and ask for a specialist to read your recurring reports, because discussion helpers says it looks like a serious hardware error. They can read these discussions if you guide them a little, but they do NOT take our conclusions at face value.

The problem with going to the Genius Bar directly is their standard procedure is to run their diagnostic overnight, and if "no faults detected", return your system in the morning and tell you its fine.

Please consider downloading and running this little "discovery" utility, Etrecheck, that creates a report of what your Mac is doing from the inside. It changes NOTHING.

If you follow the directions carefully, the generated report will be laundered of all personally-identifiable information, and safe to post back to the forums for readers to analyze.

How to use Etrecheck Pro for free

"M1 MacPro kept crashing and restarting"

-------

Troubleshooting a Crashing and Rebooting Mac:

A. Create New User:

For temporary use, create a new Administrator. See what happens when you log in to it. Do you still get this issue? If not, then is it an issue in the current user. If so, then its an issue with the entire Mac.

B. Boot in Safe Mode:

In Safe Mode, Login Items do not run at login, certain preferences are set aside, and damaged system files are then reset. So, once booted in to Safe Mode, wait 30 seconds, and then boot up normally, attempting another update install. For instructions, go here: How to Use Safe Mode on your Mac - Apple Support

C. Re-Mount the Drive:

Boot into Recovery Mode (Intel or Silicon) . You need to click the “Mount’ button to proceed. So, select the drives, and then click "Mount" Try rebooting once more. If of no success, then click unmount button, and then the mount button. Try rebooting once more. It looks dulled-out. So, if you cannot click it, then click the First Aid button to fix this volume.

D. Report this to Apple:

Do your Part: Report this to Apple. Apple may not get back to you directly, but the more feedback Apple receives on this, the more they will know what is going on, and what needs to be fixed in upcoming updates. Apple will know nothing of this, if you don't report it to them.

1. Go Here: Feedback - Mac Pro - Apple
2. Select: "Bug Report" for the "Feedback Type"
3. Comment: when this all started, and how you have troubleshot it thus far. Include the URL to this thread.
4. Proceed from there as necessary

Readers here are very interested in what the "fix" might be, so please keep us posted!

in the meantime, be sure you have a recent Trusted backup, because if they decide to fix it by replacing your mainboard, your Drive and its files will NOT be returned to you.

if you need any help with making such a backup, just post back.