Actually, that earlier instruction was likely made in error. The first option in the Energy Saver pane is a negative tense in the sense that when it is selected is turns off power management ("Prevent computer from sleeping automatically when the display is off"). This option should actually be turned on which prevents the computer from sleeping and thus, crashing. For a couple days now I have not experienced a crash on either Big Sur or Monterey with this option selected.
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
Thanks for the follow-up. That option was checked originally when I first experienced crashes. I turned it off as it was earlier suggested that this may help. It didn't.
I am not sure this will help but it doesn't hurt to try again. However, I am not trying to prevent the computer from sleeping when the display is off. I manually Sleep from the Apple Menu at the end of the day or when I just want to put the computer to sleep when I'm not using it, which is why I don't think this will help. I will update again after enabling this option again and seeing how it behaves.
If I'm enabling this option, I'm not experiencing crashes anymore because I don't put it to sleep manually.
So it sounds like you are not using sleep at all and just leaving it on. Is that right? My machine is not a server so I would rather not leave it running all the time and I would rather not shutdown every night. Sleep is the best option for me since it's less wear and tear and it's quick to start up where I left off.
Yeah, I'm using it as a server having "Wake for network access" enabled. It goes to sleep automatically at night when I'm not using it and should wake up when I'm trying to access it next time in the morning. So I don't want to have it running all the time, as well.
Got it. It sounds like the main difference is that I put it to sleep manually. I just woke it from a crash so it is still happening but I will try without the manual sleep and see how it goes.
Just updated to 12.2 Beta 2, no change in any of the versions in System Information.
EDIT: Crashed a few minutes after the update when it went to sleep automatically.
EDIT: Crashed a few minutes after the update when it went to sleep automatically.
Last edited:
Found this thread about a week ago. I was very glad to find I wasn't only person having this crashes during sleep issue since upgrading to Monterey. I have Mac Pro 6.1, 6 core, d500.
I had some short term success (reduced frequency of crashing) turning off all Energy Saver checkboxes, but crashing continued. For last 6 days or so, I've disconnected my WD MyBook drive used for Time Machine backups. Over that time, I've had "wake for network access" and "Enable Power Nap" checked. No crashes. When I took a shot at reconnecting the TM drive, I had a crash (woke computer up and saw a login screen).
I had no issues with the drive or time machine prior to upgrading to Monterey. If I plug in the TM drive and let it backup while I work and then disconnect it, I'm able to backup. Not as convenient, but so it goes. I also erased the TM drive, reformatted (APFS), and did a fresh backup; still crashed.
I'm not suggesting this is anything. And, it's possible the issue will return. But, I wanted to share.
I had some short term success (reduced frequency of crashing) turning off all Energy Saver checkboxes, but crashing continued. For last 6 days or so, I've disconnected my WD MyBook drive used for Time Machine backups. Over that time, I've had "wake for network access" and "Enable Power Nap" checked. No crashes. When I took a shot at reconnecting the TM drive, I had a crash (woke computer up and saw a login screen).
I had no issues with the drive or time machine prior to upgrading to Monterey. If I plug in the TM drive and let it backup while I work and then disconnect it, I'm able to backup. Not as convenient, but so it goes. I also erased the TM drive, reformatted (APFS), and did a fresh backup; still crashed.
I'm not suggesting this is anything. And, it's possible the issue will return. But, I wanted to share.
I believe if you select the option "Prevent computer from sleeping automatically when the display is off" it will prevent the computer from sleeping and your time machine backups will complete without crashing. I realize it is undesirable to leave the computer running but as you have observed we run risk of data corruption otherwise.
Interesting observation regarding the correlation to TM.
I have observed that simply putting the computer to sleep does not cause the crash but rather something that occurs after going to sleep appears to cause the crash. Your observation that TM backups correlate with the crash appears consistent with my observation to the extent that when waking from sleep when the TM schedule triggers a process may be causing the crash.
That is odd since the default for this option is off (not checked). So, unless you recall disabling sleep on your computer at some point, this option should have been unchecked. Turning it on should prevent the computer from sleeping and thus crashing. If you want to save power when not using the computer then I think you will have to shut down the computer until this problem is fixed.
I checked my TM settings and I have automatic TM backups turned off. Not quite the same situation as you described as you disconnected a direct attached storage target and I use network attached storage as my target.
My mistake. I looked back at my first post to this thread and I unchecked "Enable Power Nap" and "Wake for network access" as a troubleshooting step, which didn't work. I'm guessing that nothing will work at this point but it doesn't hurt to try certain suggestions so I am currently running with the following settings.
I am using a Mac Mini with an LG TV connected via HDMI so after 15 minutes the computer goes into low-power mode (wakes up with a keystroke or mouse movement). In this case, I don't believe the "Prevent.." option applies. Anyway, it hasn't crashed in almost 2 days but I don't expect that to last. If it does crash again I will just shut it down overnight or for long absences until this is fixed.
I see that also in my observations. You can put Mac Pro to sleep or allow it to sleep on its own, but sometime during the sleep process (whether it is a deep sleep or a specific time later) something causes it to crash and restart. I get a message that Mac Pro had to restart due to a crash. Maybe the logs would tell specifically what caused it to crash, but I am not familiar with how to generate the log or which log to get and look. If I put Mac Pro asleep and wait awhile, I can wake it up from sleep with no problems. but when unintended or it is some time (like I noticed the crash) was over-night.
Could be related to Time Machine or the snap shots it takes of your system regardless if you have time machine set up. This could be the issue. Hopefully, Apple will take note of this thread.
Your comment got me thinking. Even though I was disconnecting my external drive, I had never turned off the automatic TM backups. So, I plugged in my external WD MyBook and turned off (unchecked) the TM automatic backups. The computer went to sleep sometime yesterday evening. When I sat down this morning, I attempted to wake up the Mac Pro. It didn't immediately wake up (as is normal) and I heard the startup chime (computer restarted) and I was staring at the login screen.
This is one of two ways I've been experiencing crashes in the past month or so. The other is a crash when I'm not around (i.e. when I go to wake it up, it wakes right up but I'm staring at the login screen - it restarted sometime before I tried to wake it up).
So, just having the external drive connected last night seems to have resurrected this issue for me after a week of not having problems. I've not had much luck finding anything in the Console, but this morning I do see a "Sleep Wake Failure_2022-01-13-080051_Mac-Pro.diag" at the time I experienced the restart. The details say "Sleep Wake failure in EFI" with a "Failure code:: 0x03000010 0x0000001f".
I'll repeat that this may not be THE issue; maybe this is MY issue (hardware?). But, I thought I'd share just in case it provides any insight or ideas.
I put my two external monitors on a switch plug for the sake of this issue and to save energy. Since doing this, I put my iMac display sleep settings back on and so far I have not crashed while display is sleeping. I will keep everyone posted on if that changes.
For posts like this, it'd be increasingly helpful if posters include (for exactly how many days) in the "so far" parts. I realized that the desk I use in my studio DOES have a master power strip set up for all of the audio-gear. I suppose I could move the Mac Pro's connected display over to a switched outlet, and then when I am not using the computer, I could be easily powering off the display.
notably, The longest I ever got was 7-Days & 1hr.
I have reached day 5 with no crashes. Putting monitors on a switch is a massive pain because windows get all rearranged when the iMac detects no display. I use an application called Stay to keep all windows in place when the monitors turn back on.
To update things along; Apple Geniuses are replacing one of the graphics cards this morning for me. They have actually finished and are running tests to ensure the sleep problem is still not there 
Which graphics cards do you have and which one are they replacing? And how much do you have to pay?To update things along; Apple Geniuses are replacing one of the graphics cards this morning for me. They have actually finished and are running tests to ensure the sleep problem is still not there
D300 which should be the least problematic of the three options available to the MB 6,1 (the D500 and D700 had overheating issues I believe?)
Its a fixed cost of around £300-something.
Its a fixed cost of around £300-something.
I've got 3 pcs of 6,1 now. Mostly have been using the D300, and it's problematic unfortunately. It gives KPs far too frequently. With sleep enabled very often, without sleep, better but still too often KPs.
I've been reading it might be the D300 and it's f*cked up drivers. I've been reading it might be the RTC clock that is fading with it's voltage. I've been reading it might be the thermal design of the tube in general. I've been reading it might be xxx. So, mostly I've been reading, it seems.
Now I took the D500 to test more extensively, instead of the D300 one. We'll see..
I've been reading it might be the D300 and it's f*cked up drivers. I've been reading it might be the RTC clock that is fading with it's voltage. I've been reading it might be the thermal design of the tube in general. I've been reading it might be xxx. So, mostly I've been reading, it seems.
Now I took the D500 to test more extensively, instead of the D300 one. We'll see..
The GPU issue on the D300 is an old issue that goes back 7 years ago and is probably not related to the issue currently. Glad Apple is replacing the cards still (surprised they have any left). But if you (like most of us) do not have Apple Care or did not buy Mac Pro close to when they discontinued it, we are stuck with the issues. Apple wants Mac Pro 2013 to quietly go away..To update things along; Apple Geniuses are replacing one of the graphics cards this morning for me. They have actually finished and are running tests to ensure the sleep problem is still not there
Not worth paying for an issue that is really Apple's issue, especially if Apple Care is expired ("We kind of worked ourselves into a thermal corner"-summary quote from Craig F.). Apple makes us pay to fix their issue. They admitted that it is there issue...but there was no recall to fix it. They probably realized there is no "fix" and wrote it off as a "good attempt" at a new design and just "moved on". I like Mac Pro 2013, but had hope Apple "liked it too". They didn't and just moved on and all of us who bought into it paid $ for a faulty product. Apple just said, "Oh well...you are screwed, buy our next offering.."
I hope the Apple "Geniuses" continue to report your problem to their supervisors etc.. I would not be surprised if after they replace the card the issue is still there. It is probably a Firmware issue, but this process has to occur until they "might" get a fix for us. I would not be surprised if they don't fix it making everyone eventually have to upgrade to a newer system. Mac Pro is currently 7 years old (or really more), so they want everyone to move on. The concept is "don't listen, so it goes away eventually over time.." with older gear...and other things....
The thermal issues have nothing to do with the sleep issue that is occurring so I do not understand the need to reference the above. We also do not have any concrete proof that its down to firmware; and if so what aspect.
One way of figuring this out is checking who has a MP 6,1 with an old bootrom version that has not been updated. Pre 130.x might be a good start
One way of figuring this out is checking who has a MP 6,1 with an old bootrom version that has not been updated. Pre 130.x might be a good start
Until my Monterey update, I was running “129….” firmware and the problem started immediately after the Monterey update (which was the first time my Mac Pro 6,1 had an update to its firmware in years.)The thermal issues have nothing to do with the sleep issue that is occurring so I do not understand the need to reference the above. We also do not have any concrete proof that its down to firmware; and if so what aspect.
One way of figuring this out is checking who has a MP 6,1 with an old bootrom version that has not been updated. Pre 130.x might be a good start