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.

MG-Pro

macrumors newbie
Mar 15, 2022
6
9
Melbourne, Victoria
Its fixed :) updated to 430.100.23.0.0 firmware and its not crashed once. Thanks @MisterAndrew for the initial find.

For the inevitable questions:

1. Running 12.3 - public release
2. 1TB Intel SSD
3. MP 6,1 /w Xeon 12core proc, D300 graphics.
4. To grab the 430.x firmware; install 12.3 beta 5. I cant comment on earlier betas; but this is the latest one prior to the release candidate builds and this contained the 430.x firmware update for me.

I'm not sure if the forum permits linking to these builds; so either utilise the installmacos.py script or Google!
Okay, so I have just completed the same process you did. I am now on the 430.100.23.0.0. My Mac Pro 6,1 has the exact same config as yours. Fingers Crossed, I hope I wont have any more of the dreadful sleep crashing. I will post my updates on how it goes.
 
  • Like
Reactions: Trunkz and loby

MG-Pro

macrumors newbie
Mar 15, 2022
6
9
Melbourne, Victoria
Okay, so I have just completed the same process you did. I am now on the 430.100.23.0.0. My Mac Pro 6,1 has the exact same config as yours. Fingers Crossed, I hope I wont have any more of the dreadful sleep crashing. I will post my updates on how it goes.
Just wanted to provide an update. It's been about 24 hours since I the firmware update 430.100.23.0.0 from Beta 5 and so far, my Mac Pro has not crashed during sleep. I must also admit that my bluetooth mouse and keyboard are more stable. I previously would experience Magic Mouse stuttering and drop outs -- and now this has gone away. I will let you know how it goes with the sleep-crashing in the next 24 hours.
 

zetzetone

macrumors newbie
Sep 3, 2009
24
4
Just wanted to provide an update. It's been about 24 hours since I the firmware update 430.100.23.0.0 from Beta 5 and so far, my Mac Pro has not crashed during sleep. I must also admit that my bluetooth mouse and keyboard are more stable. I previously would experience Magic Mouse stuttering and drop outs -- and now this has gone away. I will let you know how it goes with the sleep-crashing in the next 24 hours.
I also tried to, but beta5 is gone from apple's downloads.. I wonder how you did this
 

Trunkz

macrumors regular
Jul 27, 2012
105
47
London, UK
For those struggling to find the beta; mrmacintosh.com currently has the information to these. Again I am unsure if we are permitted to link directly on the forums; so apologies for any infractions caused.
 

MisterAndrew

macrumors 68030
Sep 15, 2015
2,895
2,390
Portland, Ore.
  • Like
Reactions: BubbaMc

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
I am a bit puzzled…”If” this firmware does not fix the issue, why would Apple remove it from the public release unless it could cause some unknown issue that we users don’t know?

I am not cynical by nature..but I could see Apple purposely leaving the fix out just before the release of the Mac Studio so those who are having the issue will consider buying the Mac Studio? I really hope not…but can see Apple doing that unfortunately.

I hope I am wrong.
 

MG-Pro

macrumors newbie
Mar 15, 2022
6
9
Melbourne, Victoria
Just wanted to provide an update. It's been about 24 hours since I the firmware update 430.100.23.0.0 from Beta 5 and so far, my Mac Pro has not crashed during sleep. I must also admit that my bluetooth mouse and keyboard are more stable. I previously would experience Magic Mouse stuttering and drop outs -- and now this has gone away. I will let you know how it goes with the sleep-crashing in the next 24 hours.
Update #2: Not so good. My Mac Pro crashed overnight. I was optimistic and left it running with most of my apps open, i usually Quit all my apps to avoid crashing. -- so I'm unsure what has caused it to crash :(.

Also, I have noticed with the new firmware it takes longer for the Apple Logo to display on bootup -- no big issue, just an observation.

Tonight, i will quit all my apps and see if it will survive or crash.
 
  • Like
Reactions: loby

BubbaMc

macrumors regular
Nov 15, 2010
240
24
I am a bit puzzled…”If” this firmware does not fix the issue, why would Apple remove it from the public release unless it could cause some unknown issue that we users don’t know?

I am not cynical by nature..but I could see Apple purposely leaving the fix out just before the release of the Mac Studio so those who are having the issue will consider buying the Mac Studio? I really hope not…but can see Apple doing that unfortunately.

I hope I am wrong.
I was thining similar. Maybe they came up with some valuable fixes with that firmware but decided at the last minute not to release it, to give us more incentive to upgrade.
 
  • Like
Reactions: loby

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
I was thining similar. Maybe they came up with some valuable fixes with that firmware but decided at the last minute not to release it, to give us more incentive to upgrade.
The only issue with the thought is Apple stopped selling Mac Pro 2013 in 2019 and any apple care (if they had any sales) would be running out probably this year or early next...so they would have to address the issue with those who bought late...maybe just address the issue individually (if a complaint came eventually to upper management). Sales were probably very low for end of life product in 2019 and Apple had already forgot about or wrote off Mac Pro 2013 just within a few years after it came out.

But..probably the number of buyers in 2019 were VERY low...so they could get away with this.

Who could call them on this if they purposely held off on an update to a very expensive (and outdated) product in order to drive more sales?

Marketing would have no issues telling engineering to hold off on putting out a fix until at least version 12.4 (or don't) to give people reason to upgrade to Mac Studio...not out of thinking for marketers since Apple is now completely driven by data and forecasting (good, bad & ugly). The marketing department would tell engineering (and Tim) "If anyone asks..(wink, wink) just tell them you still needed to test the fix...just to make sure it works for the benefit of our loyal (and stupid) customers..."

It sickens me to think this..but not out of reach for Apple...
 
  • Like
Reactions: BubbaMc

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
The only issue with the thought is Apple stopped selling Mac Pro 2013 in 2019 and any apple care (if they had any sales) would be running out probably this year or early next...so they would have to address the issue with those who bought late...maybe just address the issue individually (if a complaint came eventually to upper management). Sales were probably very low for end of life product in 2019 and Apple had already forgot about or wrote off Mac Pro 2013 just within a few years after it came out.

But..probably the number of buyers in 2019 were VERY low...so they could get away with this.

Who could call them on this if they purposely held off on an update to a very expensive (and outdated) product in order to drive more sales?

Marketing would have no issues telling engineering to hold off on putting out a fix until at least version 12.4 (or don't) to give people reason to upgrade to Mac Studio...not out of thinking for marketers since Apple is now completely driven by data and forecasting (good, bad & ugly). The marketing department would tell engineering (and Tim) "If anyone asks..(wink, wink) just tell them you still needed to test the fix...just to make sure it works for the benefit of our loyal (and stupid) customers..."

It sickens me to think this..but not out of reach for Apple...
I really want to believe that I am wrong.
 

MisterAndrew

macrumors 68030
Sep 15, 2015
2,895
2,390
Portland, Ore.
The only issue with the thought is Apple stopped selling Mac Pro 2013 in 2019 and any apple care (if they had any sales) would be running out probably this year or early next...so they would have to address the issue with those who bought late...maybe just address the issue individually (if a complaint came eventually to upper management). Sales were probably very low for end of life product in 2019 and Apple had already forgot about or wrote off Mac Pro 2013 just within a few years after it came out.

But..probably the number of buyers in 2019 were VERY low...so they could get away with this.

Who could call them on this if they purposely held off on an update to a very expensive (and outdated) product in order to drive more sales?

Marketing would have no issues telling engineering to hold off on putting out a fix until at least version 12.4 (or don't) to give people reason to upgrade to Mac Studio...not out of thinking for marketers since Apple is now completely driven by data and forecasting (good, bad & ugly). The marketing department would tell engineering (and Tim) "If anyone asks..(wink, wink) just tell them you still needed to test the fix...just to make sure it works for the benefit of our loyal (and stupid) customers..."

It sickens me to think this..but not out of reach for Apple...

I have two 6,1s with AppleCare+ that expires in June 2023. I'll renew them to monthly at that time if they offer it.
 
  • Like
Reactions: loby

adingley

macrumors member
Nov 27, 2021
58
41
Philadelphia
It wasn't very easy to find the page it's listed on, but I found it here: https://mrmacintosh.com/macos-12-monterey-full-installer-database-download-directly-from-apple/
I just downloaded the 12.3Beta V5 from that link on Mr. Macintosh, and using a spare USB SSD I was able to install the beta / my machine is now showing 430.100.23.0.0 — I'll start my clock now and report back over the coming week+. Worth noting, I'm the one who's running Big Sur on this machine and still continued to get the crash-during-sleep even after taking ALL versions of Monterey off of the machine. So, it was very clearly NOT just the OS causing the crashes — if this FW keeps my machine from crashing during sleep, I'm gonna hold fast on ANY updates until they have a release that officially includes this FW.

If nothing else, this (if it solves the problem) will allow me to eventually sell-off the machine with a clean conscience, once I do finally move up to a Mac Studio.
FW 430.100.23.0.0.png
 

mikas

macrumors 6502a
Sep 14, 2017
898
648
Finland
Thanks for your efforts too, eager to hear your results later.

I'm running Mojave on external NVMe now on a D300 429.60.3.0.0., up six days now. Tried some sleep, no crash, but no long sleep yet. Will try that next. I couldn't find all the variations tested, so I'm trying myself.

Note to myself and others too: This is not something we, the users, should troubleshoot, but Apple should.
 

vddobrev

macrumors 6502a
Original poster
Oct 28, 2016
962
833
Haskovo, Bulgaria
One thing to note is that if Apple pulled firmware 430.100.23.0.0 from the final release, then there must be a valid reason for doing so, it is not uncommon. They may have discovered an additional bug or felt that it is not ready for public release. However, this is odd, because anyone who took the beta, cannot revert the firmware back to lower revision. Granted, we can only wait and see, or install the beta to get the 430.100.23.0.0. Since my MP6,1 is used for production and I depend on it, I can't afford the risk updating to a beta release.
 
  • Like
Reactions: loby

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
One thing to note is that if Apple pulled firmware 430.100.23.0.0 from the final release, then there must be a valid reason for doing so, it is not uncommon. They may have discovered an additional bug or felt that it is not ready for public release. However, this is odd, because anyone who took the beta, cannot revert the firmware back to lower revision. Granted, we can only wait and see, or install the beta to get the 430.100.23.0.0. Since my MP6,1 is used for production and I depend on it, I can't afford the risk updating to a beta release.
This is my hesitation to install the beta. Since I usually turn off my system after use (don't leave on overnight), I will wait until Apple gives us a solution (and trusting that they will provide a solution).

Extra note: Having Mac Pro 2013 (liking it), I have had to do maintenance every once-in-a-while with dusting out the system over the years. With Mac Studio...it is designed NOT to be able to open it up and dust it out.

If you have owned Mac Pro 2013 you would know that Mac Studio has the same design concept with the fan cooling from the bottom of the machine as the air flows up and out. Mac Studio's air flows goes out of the back instead of out top of the unit like Mac Pro 2013...

I say all of this because I feel that Mac Studio is design to only last 4-5 years (average) unless you break open the unit and dust it out.

Even opening it, you would have to still do surgery just to get to where you need to blow out the dust. Plus, given it seems to need a large fan(s) due to heat, I don't see the thermal paste lasting for more than 3-4 years if you do heavy lifting on it (as those who would REALLY need it would use it for).

Unless you are a "Pro" that changes out your system every 3 years (and can), Mac Studio looks to be a disposable Recyclable unit, not meant to last a long time.

Though I would like to have one (Video editor), I will pass on the Mac Studio for now...the monitor...I needed it last year...but can't justify spending $2,000+ on a "really" sub-par monitor (though it looks great) just to have "All Apple" anymore. I am over that as I look at my wallet. :)
 

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
@loby The Mac Studio should have had a similar enclosure like the Mac Pro 6,1 - a sliding top with a lock mechanism, where you can slide up the top, and dust the fans. Easy access to the fans should have been a priority.
The engineers who designed it will probably not use it everyday (or at all) and would not think it is needed, especially the marketers who inform them what to create from their analysis and forecasting.

Their mentality is “since” there is NO UPGRADABLE parts…NO NEED FOR THE USER to open it, so design it so if it is needed to be opened, you bring it in to Apple to do it. Why the need to open it? Their thinking is that it would only be opened after purchase for repairs only…

But since no one at Apple really has a need to use it (Tim uses probably an iPad and the rest probably uses a colorful iMac, MacBook Air or MacBook Pro for a larger screen etc.) No one at Apple now would “think” that you need an opening to clean the fans. That is why possibly from a designers view point, they may have “purposely” not want people to keep it for longer than a few years in order for consumers to rebuy or buy the next thing once it comes out. This is why my thinking of not fixing Mac Pro 2013 BEFORE Mac Studio comes out did not happen…MAKES people SPEND more money.

From their Mac Pro 2013 experience (or no one is left at Apple designing from that era), you WOULD KNOW that Mac Studio WILL NEED a way to frequently open it and to dust out the big old fans especially. Love the power of the Mac Studio, but I don’t see how it is a long term purchase. Yes, the fans may not come on that much, but it will still require cleaning out occasionally and eventual thermal paste change.
 

arw

macrumors 65816
Aug 31, 2010
1,238
980
I'd like to update my 11.5.1 Big Sur to 11.6.5 but keep my 428.140.7.0.0 firmware.
Any ideas how to achieve this? Thanks
- Remove firmware from installer and patch checksum?
- OpenCore and spoof a higher firmware before installing?
- Installing on Mac Pro in Target disk mode?

edit: I'm more likely to believe Apple pulled the 430.100.23.0.0 because of other/new problems than out of pure greed to push Studio sales.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.