Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 6,1 Mac Pro 6.1 Monterey - Crashes in Sleep
- Thread starter vddobrev
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
yeah I know, sorry 
Edit: for me this issue started after upgrading to Monterey, no issues on Mojave or Big Sur. I couldn't find a thread within the monterey sub about this issue. If 12.1 doesn't fix it I'll start a new thread in the Monterey sub. Also considering to buy a simple usb-c to minidisplayport adapter to see if that resolves it.
I've also contacted Satechi support to see if they are aware of the issue.
Edit: for me this issue started after upgrading to Monterey, no issues on Mojave or Big Sur. I couldn't find a thread within the monterey sub about this issue. If 12.1 doesn't fix it I'll start a new thread in the Monterey sub. Also considering to buy a simple usb-c to minidisplayport adapter to see if that resolves it.
I've also contacted Satechi support to see if they are aware of the issue.
Last edited:
Even better workaround: you can set "triggers" in amphetamine. I've configured a rule that when an external display is connected, amphetamine turns on.
I posted here a few weeks ago that my Mac Mini 2018 started crashing after manually being put to Sleep (Sleep for multiple hours). It crashed a dozen or so times over the past few weeks and I've been hoping that 12.1 would have magically fixed it. Well, initial news is NOT good. Before I personally went to sleep last night, I started the upgrade to 12.1. I woke up this morning and it was dead, as before. I powered on and it booted to 12.1 and all is running okay but I'm not very confident that this has been fixed, obviously. I will see how things go this week and post back. If it happens again, I will have to do the Apple Support route to dive deeper.
Obviously keeping my expectations padded, but I did just update this Mac Pro 6,1 (FW: 429.60.3.0.0) to Monterey 12.1 last night. I'll be keeping an eye out for this crash over the next few nights. My gut says 12.1 isn't going to fix this issue, but there were two noted "power related" things that sounded focused on portable machine charging issues during sleep. If, by chance, they've overhauled something in the Sleep-related systems... then maaaaaaaaybe it'll help folks in our boat. (likely a very long shot)
Thankfully my day-job is a web-based world, so I can operate in Chrome via any recent-ish macOS. So I'll just keep testing each new .x iteration until we get there.
Thankfully my day-job is a web-based world, so I can operate in Chrome via any recent-ish macOS. So I'll just keep testing each new .x iteration until we get there.
12.1 update - so far so good! Did the update yesterday, returned Energy Saver settings to default, and it was fine all evening, and overnight (would often restart around 8/8.30am for some reason!) and today, after 5 sleep/wakes.
Will keep an eye on it, but looking good so far.
Will keep an eye on it, but looking good so far.
12.1 update - crash and burn. I posted yesterday that my Mac Mini didn't come back after the initial upgrade to 12.1. Well, I put it to Sleep about 6 hours ago, came back, and it was dead. Interestingly enough, I've noticed that a few times after it died (after being put to Sleep) that when I power it up and I'm not around to put in my login information, it actually dies and I have to power it back on again. It's really hard to imagine that this was not found in testing. At this point, it's time to deep dive with Apple Support. I will post back if anything good comes of it.
My Mac mini 2018 has been crashing since Monterey upgrade and 12.1 has not changed that, it still crashes over night. I have disabled sleep and it works fine. I spent several hours on the phone to Apple Support with no joy. They said they didn't have any record of it as a know issue and my only option was to take it to an Apple Repair centre. I haven't taken it as I upgraded the memory ages ago and I know from previous experience they will blame that upgrade. I ran a Ram checker for a week and it discovered no problems. So I think it's still an issue with Monterey as I had no problems with Big Sur. I am considering going back to Big Sur but would rather have a fixed version of Monterey.
Hard to believe that Apple doesn't know this is an issue with Monterey. Dozens of reports after crashes must have been sent to them over the past few weeks. After 12.1 didn't fix this issue for me I started an Apple Support case today. So far, boot into Safe mode, Shutdown, boot and run diagnostics ("D" when you power on), no issues were found. Apple Support said they didn't know about the issue and of course that they weren't sure if this would fix it so far. They said to reach back to the support case if it happens again and the next troubleshooting steps can be done. I have a feeling I'm in for a nasty ride through clueless support structures. I will revert back with findings either way.
Mine did this yesterday in 12.1 Monterey. It had 12.0 before that and no issues.
I wasn't sure what caused it.
I have a MacPro Late 2013 and have had the crash on sleep issues on and off since upgrading to Monterey. No issues before that. 12.1 has not helped at all. I have a MacBookPro 2016 model and a MacMini 2018 model on Monterey with no issues. When I spoke with Apple support a month ago they had me boot into safe mode, and no issues were reported. They said if it kept happening they would want me to re-install the OS. Since it never has issues while running, I have just lived with the issue in hopes they will get around to fixing it.
Mine restarted while sleeping this morning. It generated an MCA Error Report. Ran Apple Diagnostics. No issues found.
Last edited:
Since updating my macbook air to 12.1 three days ago I haven't had a single crash despite roughly 5 times wake/sleep a day and a long sleep overnight. The only thing that I changed since updating was leaving my external hard drive disconnected from the USB-C hub, so I will connect it after the weekend to see if that changes something.
I got a reply from Satechi support that they were not familiar with this issue and suggest to update to 12.1..
I got a reply from Satechi support that they were not familiar with this issue and suggest to update to 12.1..
@baas, I've had runs of a few days where it didn't crash and then it starts crashing again. I hope your experience is better. I left off with Apple Support where we ran diagnostics after Safe mode and there were no issues found (this past Wednesday), and see if it happens again. Well, it happened again. In fact, the crashes are happening in three different ways but all seem to be related. It crashes after being put to Sleep for a while, it crashes after I turn it back on and don't login, and it doesn't crash immediately after being asleep for a while and is still powered on but when I go to wake it up via bluetooth keyboard it crashes with a black screen of death saying it needs to restart. I told Apple Support that it crashed again and within seconds they said, "Have you reinstalled the OS?". This is a joke. Anyway, an advisor will be calling me shortly to discuss after I explained the frustration of having to spend more time on this when Apple is telling everyone that they don't know about this issue. Will update if anything good comes out of this but Apple Support seems to be incompetent, lying or BOTH.
Update: Was just on with the Apple Support advisor and he was completely clueless about this issue. He was saying that Apple Support isn't seeing any cases about this. He suggested going down the troubleshooting route but for me, living with the crash is so much less time consuming. It could crash 100 times and that would take up an hour or so of my time. Working with Apple Support would take days and would drive me insane. So, I'm going to live with this and just hope it eventually gets fixed. Go Apple!
Update: Was just on with the Apple Support advisor and he was completely clueless about this issue. He was saying that Apple Support isn't seeing any cases about this. He suggested going down the troubleshooting route but for me, living with the crash is so much less time consuming. It could crash 100 times and that would take up an hour or so of my time. Working with Apple Support would take days and would drive me insane. So, I'm going to live with this and just hope it eventually gets fixed. Go Apple!
Last edited:
Interestingly this is sort of in line with my experience as well. The issue with crashing Mac Pro 2013 started on macOS Big Sur (released on the same day as Security Update 2021-007 for Catalina 10.15.7) which I installed a couple of days before upgrading to Monterey. Has anyone seen the same crashes while still being on latest Big Sur?
Thanks. They are all unchecked and have been for a few weeks. It was one of the first things I tried and my machine didn't actually crash for almost a week, but then it did. I reset nvram and smc earlier today so fingers crossed but I don't think it's going to help.
Just updated to Monterey 12.2 Beta (21D5025f), crashed right away when going to sleep after the update. I'm regularly reporting the crashes via Feedback Assistent, but didn't get any feedback, yet.
I wouldn't expect any feedback. I've been sending in the error reports for weeks and haven't heard anything. According to Apple Support who I spoke with this morning they do not see any cases in Support about this issue and that Engineering has not sent them a notification that this is a known issue. Apple Support says they don't get the error reports from crashes, of course, but that Engineering does and will notify them of major issues. Something is amiss here.
As for 12.2, I am saddened to hear that the issue may still exist beyond 12.1. Ugh!
This is what happens when Apple pushes unbaked major releases every year. This has got to stop, either by we don't uptake the release, or Apple coming to their senses and do incremental feature updates without breaking core functions like sleep.
Just a quick note — You maybe have been one of the folks who already did submit reports to apple, but I'm also certain that a lot of people don't (they might just dismiss the prompt). Moreover, I know that a lot of folks don't spend their time calling into AppleCare, but I encourage anyone else who's dealing with this to call in about it too.
I spent 20+ min on the phone with a tier 2 support specialist at Apple (about 10days ago) and at the time, he shared that there were no similar/related issues reported to Apple Support... so my thoughts would be: If you're ONLY posting here on this thread, make sure to a) submit your error reports/crash-reports when you get the 'restarted because of a problem' pop-up and/or b) call this in to AppleCare and give them a thorough run-down of your MP6,1 setup & what you're experiencing.
My AppleCare case is still open, and I've been experimenting with 12.1 for 3+ days now — not a single crash so far. I have restarted the machine myself for other reasons, but it's never restarted itself since the update. If I get a week+ out of 12.1, I'm gonna go ahead and update my other partition to 11.6.2 (11.4 is rock solid, but 11.6 crashes in the same way on this machine) — as for 12.1: I'm still hesitant to imagine that it's truly solved (especially reading that others have not seen improvements) but seriously — make noise with Apple Support directly (if you haven't already).
Last edited: