Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Tomorrow marks 3wks with ZERO crashes-during-sleep. I've made no hardware changes / I'm not unplugging things when I walk away / I'm using my standard sysPrefs (allowing system to sleep as I would normally want to), and I can attribute the lack-of-crashing SOLELY to the change to the 430.100.23.0.0 firmware. (from the beta OS)

This machine was running macOS 11.6.2 before the Firmware change, and is still running the same 11.6.2 os after. No other OS changes / all normal peripherals plugged-in.

I used a separate SSD momentarily, and installed Monterey 12.3 Beta v5 / got the firmware update / then rebooted and set startup disk back to my Big Sur drive 3 Tuesdays ago. Not a single crash since.

Very much hoping that 430.x FW passes internal testing and gets released with a future Monterey update.
Which tells us they purposely removed 430.x FW from final release to boost Studio sells. I'm not buying any stories about improving FW for final release or similar. They left our Pro machines in the dust. What about famous sentence "it's just works", obviously not anymore.
I'm not gonna support that company by investing my money into their products anymore.
 
  • Like
Reactions: BubbaMc
I said I will write to Tim Cook, so I did:


Hi Tim,

It is not very often when I write to you, but this has come to a point that writing to you is unavoidable. 3 point release of macOS and this problem is not solved!

TLDR: MacPro 2013 Sleep Function is broken since the initial version of macOS Monterey. BASED ON YOUR SUPPORT POLICY, THIS IS A SUPPORTED COMPUTER, THEREFORE, I DEMAND YOUR ATTENTION ON THIS MATTER.

I am very much angry with you guys at Apple, my Mac Pro 2013 (a $10,000 machine) seems to be neglected since macOS Monterey, in particular the sleep function of the machine is not working, it is crashing in sleep, only to tell me that "Your computer has restarted because of a problem." This has never been a problem before Monterey.

1. Environmentally - why is this happening? Why can't my "supported" Mac Pro 2013 save energy and contribute to Earth's well being?
2. Why is Apple's latest operating system, in point 3 release, neglecting older hardware?
3. I am deeply and thoroughly concerned by todays Apple macOS - you seem to be neglecting older supported hardware.

THIS IS A MAJOR DISTURBANCE IN THE OPERATING OF MACOS, THIS PROFESSIONAL COMPUTER, The Mac Pro 2013, THAT I SPENT A SMALL FORTUNE ON SEEMS TO BE NEGLECTED IN YOUR LATEST RELEASES OF MACOS.

Best Regards,
Your long-time all-Apple-device-user-that-is-deeply-disturbed-by-your-negligence-of-older-hardware,
 
Last edited:
I said I will write to Tim Cook, so I did:


Hi Tim,

It is not very often when I write to you, but this has come to a point that writing to you is unavoidable. 3 point release of macOS and this problem is not solved!

TLDR: MacPro 2013 Sleep Function is broken since the initial version of macOS Monterey. BASED ON YOUR SUPPORT POLICY, THIS IS A SUPPORTED COMPUTER, THEREFORE, I DEMAND YOUR ATTENTION ON THIS MATTER.

I am very much angry with you guys at Apple, my Mac Pro 2013 (a $10,000 machine) seems to be neglected since macOS Monterey, in particular the sleep function of the machine is not working, it is crashing in sleep, only to tell me that "Your computer has restarted because of a problem." This has never been a problem before Monterey.

1. Environmentally - why is this happening? Why can't my "supported" Mac Pro 2013 save energy and contribute to Earth's well being?
2. Why is Apple's latest operating system, in point 3 release, neglecting older hardware?
3. I am deeply and thoroughly concerned by todays Apple macOS - you seem to be neglecting older supported hardware.

THIS IS A MAJOR DISTURBANCE IN THE OPERATING OF MACOS, THIS PROFESSIONAL COMPUTER, The Mac Pro 2013, THAT I SPENT A SMALL FORTUNE ON SEEMS TO BE NEGLECTED IN YOUR LATEST RELEASES OF MACOS.

Best Regards,
Your long-time all-Apple-device-user-that-is-deeply-disturbed-by-your-negligence-of-older-hardware,

Vladi Dobrev.
Sent from my iPad
Well done mate ?
 
  • Like
Reactions: loby
So what I did was delete the photos library in the Pictures folder and will let it sit and go to sleep and see what happens...

I did not use the photos app on macpro 6,1, so I would think that it would not do anything since there is no photos currently in it (and never has been), but will try your suggestion and report back is a few days (or if it crashes) to update those that are trying various possible solutions.

I don't think I have been counting the days for a next version of an OS so much as I have been doing as of recently. I hope I am wrong about Apple and their abandonment of Mac Pro 6,1 so people would look to the Mac Studio... I cannot afford to purchase one since I just bought close to a maxed out MacBook Pro. Of course I would love to get a Mac Studio, but I really want Mac Pro 6,1 to function without this sleep/crash problem and as my backup system. By the time I save up some cash, we may be on a M3 silicon or above.. :)
Reporting back..

Well...I have to say "so far"...I have not had a crash since I deleted the photos library in the pictures folder....

Maybe...the issues has to do with this. It might be a temporary fix, but Apple needs to fix the issue.

I personally do not use the photos app on Mac Pro 6,1, so I do not care if I have to delete the photos library, but many do, so if this is the problem, then Apple needs to do something to fix this.

This is my backup - second computer for production work, so I basically just had it on currently for testing and allow it to go to sleep and wait the next day and check to see if it has crashed (like it was previously doing). Since I deleted the photos library, Mac Pro 6,1 has not crashed. It has been 4 days. This is a record since the issue began, but I have woke up Mac Pro 6,1 a few times a day since to check. What I will do is leave it for a few days without touching it and see if it crashes. If it doesn't, then possibly the issue is linked to the photos app and library doing something while sleeping.

Thank you Jacobmerr for the possible temporary solution. I hope it is only the photo library that is causing the issue and if I have to live with deleting the photo library from Mac Pro 6,1 it does not affect my workflow.

Temporary solution UNTIL Apple address the issue... many thanks again! Will report back if there is a crash or not..
 
I said I will write to Tim Cook, so I did:


Hi Tim,

It is not very often when I write to you, but this has come to a point that writing to you is unavoidable. 3 point release of macOS and this problem is not solved!

TLDR: MacPro 2013 Sleep Function is broken since the initial version of macOS Monterey. BASED ON YOUR SUPPORT POLICY, THIS IS A SUPPORTED COMPUTER, THEREFORE, I DEMAND YOUR ATTENTION ON THIS MATTER.

I am very much angry with you guys at Apple, my Mac Pro 2013 (a $10,000 machine) seems to be neglected since macOS Monterey, in particular the sleep function of the machine is not working, it is crashing in sleep, only to tell me that "Your computer has restarted because of a problem." This has never been a problem before Monterey.

1. Environmentally - why is this happening? Why can't my "supported" Mac Pro 2013 save energy and contribute to Earth's well being?
2. Why is Apple's latest operating system, in point 3 release, neglecting older hardware?
3. I am deeply and thoroughly concerned by todays Apple macOS - you seem to be neglecting older supported hardware.

THIS IS A MAJOR DISTURBANCE IN THE OPERATING OF MACOS, THIS PROFESSIONAL COMPUTER, The Mac Pro 2013, THAT I SPENT A SMALL FORTUNE ON SEEMS TO BE NEGLECTED IN YOUR LATEST RELEASES OF MACOS.

Best Regards,
Your long-time all-Apple-device-user-that-is-deeply-disturbed-by-your-negligence-of-older-hardware,

Vladi Dobrev.
Sent from my iPad
It might have been good to say that many other users of Mac Pro 2013 had also voiced this issue on blogs etc. and is not an isolated or as Apple tends to say 'effects just a few users...' this issue is wide spread.

Apple might say, "Not many people have contact us about it.." Well many find it goes to deaf ears or if we contact support we have to pay because it is out of Apple care etc. just to contact support. Some of us cannot bring it into an Apple store because there is not one close bye.

If people send in the crash report when prompted, Apple should know that there is an issue across the board, not just a few users.

Thanks for sending the letter in. Tim Cook probably does not read them (busy guy), but his readers may pass it up to support (we hope).
 
Reporting back..

Well...I have to say "so far"...I have not had a crash since I deleted the photos library in the pictures folder....

Maybe...the issues has to do with this. It might be a temporary fix, but Apple needs to fix the issue.

I personally do not use the photos app on Mac Pro 6,1, so I do not care if I have to delete the photos library, but many do, so if this is the problem, then Apple needs to do something to fix this.

This is my backup - second computer for production work, so I basically just had it on currently for testing and allow it to go to sleep and wait the next day and check to see if it has crashed (like it was previously doing). Since I deleted the photos library, Mac Pro 6,1 has not crashed. It has been 4 days. This is a record since the issue began, but I have woke up Mac Pro 6,1 a few times a day since to check. What I will do is leave it for a few days without touching it and see if it crashes. If it doesn't, then possibly the issue is linked to the photos app and library doing something while sleeping.

Thank you Jacobmerr for the possible temporary solution. I hope it is only the photo library that is causing the issue and if I have to live with deleting the photo library from Mac Pro 6,1 it does not affect my workflow.

Temporary solution UNTIL Apple address the issue... many thanks again! Will report back if there is a crash or not..
I have determined that trying to "hide" the Photos files (all *.photoslibrary files) does not prevent the crashes and now have them offline on a portable drive.
 
I have determined that trying to "hide" the Photos files (all *.photoslibrary files) does not prevent the crashes and now have them offline on a portable drive.
IT IS IMPORTANT TO NOTE THAT THIS CRASH MOVED FROM MY iMAC TO A NEW MAC STUDIO USING MIGRATION ASSISTANT.
 
  • Like
Reactions: loby
Any word on today’s release of v12.4 beta? Firmware update for Mac Pro 6,1?

Of course we have to wait a few days to know if any fixes to the crashing, but just wondering if any firmware updates to today’s beta release.
 
Tomorrow marks 3wks with ZERO crashes-during-sleep. I've made no hardware changes / I'm not unplugging things when I walk away / I'm using my standard sysPrefs (allowing system to sleep as I would normally want to), and I can attribute the lack-of-crashing SOLELY to the change to the 430.100.23.0.0 firmware. (from the beta OS)

This machine was running macOS 11.6.2 before the Firmware change, and is still running the same 11.6.2 os after. No other OS changes / all normal peripherals plugged-in.

I used a separate SSD momentarily, and installed Monterey 12.3 Beta v5 / got the firmware update / then rebooted and set startup disk back to my Big Sur drive 3 Tuesdays ago. Not a single crash since.

Very much hoping that 430.x FW passes internal testing and gets released with a future Monterey update.
Same here no freeze in weeks with 430. We could send Apple feedback asking to release new firmware.
 
Reporting back..

Well...I have to say "so far"...I have not had a crash since I deleted the photos library in the pictures folder....

Maybe...the issues has to do with this. It might be a temporary fix, but Apple needs to fix the issue.

I personally do not use the photos app on Mac Pro 6,1, so I do not care if I have to delete the photos library, but many do, so if this is the problem, then Apple needs to do something to fix this.

This is my backup - second computer for production work, so I basically just had it on currently for testing and allow it to go to sleep and wait the next day and check to see if it has crashed (like it was previously doing). Since I deleted the photos library, Mac Pro 6,1 has not crashed. It has been 4 days. This is a record since the issue began, but I have woke up Mac Pro 6,1 a few times a day since to check. What I will do is leave it for a few days without touching it and see if it crashes. If it doesn't, then possibly the issue is linked to the photos app and library doing something while sleeping.

Thank you Jacobmerr for the possible temporary solution. I hope it is only the photo library that is causing the issue and if I have to live with deleting the photo library from Mac Pro 6,1 it does not affect my workflow.

Temporary solution UNTIL Apple address the issue... many thanks again! Will report back if there is a crash or not..
Well...that did not work. After two days of not touching my Mac Pro 6,1 and letting it sleep, it crashed again.

We have to wait until Apple gives us an official fix, or install the firmware beta...
 
Same here no freeze in weeks with 430. We could send Apple feedback asking to release new firmware.
Yep; already did so through the tier-2 support conversation I had after week-1. I would encourage ANYONE else who’s also used the beta v5 firmware trick to setup a support ticket and ask to speak to a senior advisor and just clearly articulate the issue and the fact that this seems to have fixed it while NOTHING else did.
 
Well...that did not work. After two days of not touching my Mac Pro 6,1 and letting it sleep, it crashed again.

We have to wait until Apple gives us an official fix, or install the firmware beta...
beta firmware works fine
 
  • Like
Reactions: loby
I said I will write to Tim Cook, so I did:


Hi Tim,

It is not very often when I write to you, but this has come to a point that writing to you is unavoidable. 3 point release of macOS and this problem is not solved!

TLDR: MacPro 2013 Sleep Function is broken since the initial version of macOS Monterey. BASED ON YOUR SUPPORT POLICY, THIS IS A SUPPORTED COMPUTER, THEREFORE, I DEMAND YOUR ATTENTION ON THIS MATTER.

I am very much angry with you guys at Apple, my Mac Pro 2013 (a $10,000 machine) seems to be neglected since macOS Monterey, in particular the sleep function of the machine is not working, it is crashing in sleep, only to tell me that "Your computer has restarted because of a problem." This has never been a problem before Monterey.

1. Environmentally - why is this happening? Why can't my "supported" Mac Pro 2013 save energy and contribute to Earth's well being?
2. Why is Apple's latest operating system, in point 3 release, neglecting older hardware?
3. I am deeply and thoroughly concerned by todays Apple macOS - you seem to be neglecting older supported hardware.

THIS IS A MAJOR DISTURBANCE IN THE OPERATING OF MACOS, THIS PROFESSIONAL COMPUTER, The Mac Pro 2013, THAT I SPENT A SMALL FORTUNE ON SEEMS TO BE NEGLECTED IN YOUR LATEST RELEASES OF MACOS.

Best Regards,
Your long-time all-Apple-device-user-that-is-deeply-disturbed-by-your-negligence-of-older-hardware,

Vladi Dobrev.
Sent from my iPad

That's a funny email. I hope it gets a response though. The 6,1 maxed out at $9599 with the 12 core CPU, 64GB RAM, 1 TB SSD, and D700 GPUs before the 2017 spec bump. After that it maxed out at $6599. That's if you maxed out the base $2999 model (MD878LL/A). Oddly enough, if you maxed out the $3999 upper tier model (MQGG2LL/A) it was $6999 with the same specs. I have the Apple Store pages archived.
 
That's a funny email. I hope it gets a response though. The 6,1 maxed out at $9599 with the 12 core CPU, 64GB RAM, 1 TB SSD, and D700 GPUs before the 2017 spec bump. After that it maxed out at $6599. That's if you maxed out the base $2999 model (MD878LL/A). Oddly enough, if you maxed out the $3999 upper tier model (MQGG2LL/A) it was $6999 with the same specs. I have the Apple Store pages archived.
Ooops... I guess I used the $ sign instead of local currency, I purchased mine in 2018. But regardless, that was just a figurative number, to express that it was expensive, I was not even thinking of quoting an exact amount.
 
Ooops... I guess I used the $ sign instead of local currency, I purchased mine in 2018. But regardless, that was just a figurative number, to express that it was expensive, I was not even thinking of quoting an exact amount.
Sorry. I'm not trying to correct you. I'm just kind of a nerd for details like that.

It's possible Tim Cook doesn't know what the 6,1 cost new or even cares. If you asked a current Apple employee they'd probably think it cost the same as the 2019 model because it's the same product line. (e.g. AppleCare+ costs the same for both 2013 and 2019 Mac Pro.)
 
Last edited:
Pulling out a firmware out of a beta release does not mean it is defective, or that Apple is greedy and they want to upgrade. From software perspective, it can mean that it was not ready for production for a number of reasons - a bug was discovered late in the testing, or there were some oversights in terms of compatibility with old or new OS releases, or even planned features, that are yet to be included in the firmware.
Well, I'm a believer. Installed the 12.3 beta v5 over 12.3.1 (was surprised the installer allowed me to downgrade) and noted that firmware version 430.100.23.0.0 was installed. I put the machine to sleep, waited about 10 minutes and then woke it up. Woke perfectly. Tried this a few more times with no problems (it -had- been crashing EVERY time it woke from sleep). I then installed 12.3.1 (non beta) and still no problems. I'll post back if any thing changes.

Thanks to everyone who has suffered through this situation and worked to find a workaround. I'm less frustrated today than yesterday but more annoyed at Apple for not addressing this problem.

Also note: someone posted a while back that the firmware would not be installed if you had a non-Apple SSD. Mine is an OWC 1.9 TB aftermarket drive and the firmware installed fine.
 
Also note: someone posted a while back that the firmware would not be installed if you had a non-Apple SSD. Mine is an OWC 1.9 TB aftermarket drive and the firmware installed fine.
You might be referring to my posts, and the “Apple SSD Requirement” used to be a thing, but that ended in (I believe) Mojave. Whoever owned my 6,1 before me had upgraded to a 3rd party SSD back in the early days of owning the tower, so my machine NEVER got any of the FW updates between high-Sierra and Big Sur. That said, it was able to run Big Sur even with its older firmware.

I uncovered that oddity when I was (originally) unable to install Monterey. I needed to be on a somewhat newer FW before it would take. Buying a used Apple Orig SSD is what allowed me to even get Monterey installed (and what brought me all this frustration)
 
  • Like
Reactions: wagonfixin
IT IS IMPORTANT TO NOTE THAT THIS CRASH MOVED FROM MY iMAC TO A NEW MAC STUDIO USING MIGRATION ASSISTANT.
As Loby said above, his Mac still crashed after removing the Photos app's data file. Mine has done the same thing on my Mac Studio and iMac. I just looked at the crash reports and I have a string of 15 going back to April 14 that identify DYMO.WebApi.Server as the culprit. I tried to delete the app, "DYMO.WebApi.Mac.Host", which I had never seen before in my Applications folder, but it was open and could not be deleted via the Trash. I used "Activity Monitor" to delete it. My DYMO label printer still works, though I see there is a new application for printing DYMO labels called DYMO Connect.app. I will now continue testing to see if either the Mac Studio or the iMac crashes while sleeping.
 
  • Like
Reactions: loby
Well, I'm a believer. Installed the 12.3 beta v5 over 12.3.1 (was surprised the installer allowed me to downgrade) and noted that firmware version 430.100.23.0.0 was installed. I put the machine to sleep, waited about 10 minutes and then woke it up. Woke perfectly. Tried this a few more times with no problems (it -had- been crashing EVERY time it woke from sleep). I then installed 12.3.1 (non beta) and still no problems. I'll post back if any thing changes.

Thanks to everyone who has suffered through this situation and worked to find a workaround. I'm less frustrated today than yesterday but more annoyed at Apple for not addressing this problem.

Also note: someone posted a while back that the firmware would not be installed if you had a non-Apple SSD. Mine is an OWC 1.9 TB aftermarket drive and the firmware installed fine.
About a month here without issue
 
  • Like
Reactions: loby
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.