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.

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
Hopefully within the next week (Next Tuesday) or so Apple will release the next version so we can be done with this headache.
 

adingley

macrumors member
Nov 27, 2021
58
41
Philadelphia
Hopefully within the next week (Next Tuesday) or so Apple will release the next version so we can be done with this headache.
wowoowowow... this would be a huge relief.

I've been thinking about / planning to move to an M1Max (Mac mini) if/when those come out, which would mean selling off the trashcan eventually... and I didn't wanna "not disclose" the issue, but also didn't wanna have to explain that the issue was NOT a problem with this Mac, but is something that would likely eventually be fixed. phew!


(but also, I hope we're not breathing collective sighs of relief too soon). Fingers-crossed.
 

MisterAndrew

macrumors 68030
Sep 15, 2015
2,895
2,390
Portland, Ore.
wowoowowow... this would be a huge relief.

I've been thinking about / planning to move to an M1Max (Mac mini) if/when those come out, which would mean selling off the trashcan eventually... and I didn't wanna "not disclose" the issue, but also didn't wanna have to explain that the issue was NOT a problem with this Mac, but is something that would likely eventually be fixed. phew!


(but also, I hope we're not breathing collective sighs of relief too soon). Fingers-crossed.

I might be interested in an M1/M2 Max mini also, but I also want to see the new AS and Intel Mac Pro models. A top end Mac mini might not be too far in price from a low end AS Mac Pro. My 6,1 works well for me though.
 

adingley

macrumors member
Nov 27, 2021
58
41
Philadelphia
A top end Mac mini might not be too far in price from a low end AS Mac Pro.
Solid point, and I suppose we'll see what happens over the next few months. Very eager to see this 12.3 FW version proof out... and frankly, I can probably get a few more good years out of my MP6,1 if I'm not seduced into the  Silicon sooner. Frankly, I need to just abide by my spreadsheet of what is/isn't-yet AS compatible before I jump. For years, (as a recording engineer, who's industry has some vendors that can be very slow-to-update for new macOS versions) I've kept a spreadsheet of all my vital apps & if they're "ready for OS X.X.X" and now it's split across OS & CPU types.
 
  • Like
Reactions: MisterAndrew

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
Solid point, and I suppose we'll see what happens over the next few months. Very eager to see this 12.3 FW version proof out... and frankly, I can probably get a few more good years out of my MP6,1 if I'm not seduced into the  Silicon sooner. Frankly, I need to just abide by my spreadsheet of what is/isn't-yet AS compatible before I jump. For years, (as a recording engineer, who's industry has some vendors that can be very slow-to-update for new macOS versions) I've kept a spreadsheet of all my vital apps & if they're "ready for OS X.X.X" and now it's split across OS & CPU types.
Yes… very slow to update or never do forcing us to buy more gear. Have some bad tasting experiences with Tascam & Alesis etc. Good working expensive gear becomes a paper weight or door stopper if no updated drivers.
 

adamdport

macrumors member
Mar 19, 2011
64
295
My error is consistently around graphics, eg AMDFramebufferVIB::setPowerState(...) timed out after 43210 ms. There's been some talk of an external monitor causing issues, but I don't use one so I've always dismissed that. ...but I just realized that my crashes may have started when I set up a new LG TV that has AirPlay. I hadn't use it from my crashing iMac ever, but when I went to try I had to enter the 4-digit code to pair them. Maybe it's been crashing because it's an "available" display that isn't paired so it's "timing out"? Curious if anyone else here also has AirPlay, could be related?

edit: nope. just crashed.
 
Last edited:

GoztepeEge

macrumors 6502
Nov 21, 2015
267
185
Munich, Germany
I am experiencing the same issue for the last 4 nights. My 2021 MBP base-model 14" always crashed in long sleeps (e.g. 5-8 hours in sleep).

Here is what I created as a thread, before I know this thread.
MBP 2021 M1 Pro - Shutdown itself while sleeping (warning appears)

Long story short, for information that might be beneficial as details:
- I use AlDente and battery is limited to 50% charge
- I use an external monitor connected via HDMI output of the MBP (cable always connected, even in sleep, but the monitor is closed while the MBP in sleep)
- I leave these apps open: Safari, Mail, Spotify
- I use a Satechi keyboard (bluetooth) and a Magic Mouse, but both are turned-off when I close the MBP lid.

- MacOS Monterey 12.2.1 (currently the latest OS version)
 

Trunkz

macrumors regular
Jul 27, 2012
105
47
London, UK
I am experiencing the same issue for the last 4 nights. My 2021 MBP base-model 14" always crashed in long sleeps (e.g. 5-8 hours in sleep).

Here is what I created as a thread, before I know this thread.
MBP 2021 M1 Pro - Shutdown itself while sleeping (warning appears)

Long story short, for information that might be beneficial as details:
- I use AlDente and battery is limited to 50% charge
- I use an external monitor connected via HDMI output of the MBP (cable always connected, even in sleep, but the monitor is closed while the MBP in sleep)
- I leave these apps open: Safari, Mail, Spotify
- I use a Satechi keyboard (bluetooth) and a Magic Mouse, but both are turned-off when I close the MBP lid.

- MacOS Monterey 12.2.1 (currently the latest OS version)
You should raise a support ticket with Apple; as this thread does not cover the issue you have mentioned. The sleep issues the MP6,1 is experiencing is down to something in the bootrom.
 

thos101

macrumors newbie
Mar 6, 2022
9
9
Yes… very slow to update or never do forcing us to buy more gear. Have some bad tasting experiences with Tascam & Alesis etc. Good working expensive gear becomes a paper weight or door stopper if no updated drivers.
So true. A few years back I bought a Tascam US-1200 USB interface. Tascam quit updating their driver at Catalina. Big waste of money.

BTW I am new to the forums but have been using macs since the mid 90's (Performa) as a graphic designer.

Having the same sleep crash in Monterey 12.2.1 as described here. I have tried most of the suggestions to no avail so I am no longer allowing the computer to sleep (just the monitors). I'm hoping the 12.3 firmware will work. Here's what I am running:

MP6,1 purchased 2018
12-core (upgraded from 6-core), 32 GB memory, 2TB HD (OWC upgrade from 500 GB), D700 graphics, firmware 429.60.3.0.0

Also, the "sudo pmset -a standby 0" suggestion did absolutely nothing to help in my situation. Turning off (unplugging) my two monitors is out of the question since I am in and out of my office all day and rely on "sleep" after 15 minutes to keep the energy usage in check.

The strange thing is that the crashing didn't start as soon as I upgraded to 12.2. It was probably a week after I went to 12.2.1 that it started. I had removed some software (Microsoft autoupdate and OneDrive) using CleanMyMac and wondered if I (or CleanMyMac) removed something that should not have been touched. So I reverted to an APFS snapshot that I had before the software removal (and before the crashing began) but the sleep-crash was still there.

Go figure..... Hope 12.3 fixes this.
 
  • Like
Reactions: loby and vddobrev

Trunkz

macrumors regular
Jul 27, 2012
105
47
London, UK
Not that I can think off. I was on 12.2.1 prior to getting the beta profile for the 12.3 RC and my firmware was the latest file.

Time will tell when 12.3 becomes public.
 

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
I thought Apple would come out with 12.3 today so I can fix Mac Pro..now we have to wait for a week more if we are not on the beta. Screwed up my administration schedule.
 

applefvcker

macrumors newbie
Mar 9, 2022
6
5
That's odd. Have you had issues with firmware updates in the past?

Is the firmware updating for others?
I have the same issue but I have a Samsung 2TB NVME with adapter instead of the stock Apple OEM NVME. I updated to 12.3 Beta and my firmware did not update and still showing 429.60.3.0.0. Could it be that the firmware will not updated because I need to put the Apple NVME back.
 

MisterAndrew

macrumors 68030
Sep 15, 2015
2,895
2,390
Portland, Ore.
I thought Apple would come out with 12.3 today so I can fix Mac Pro..now we have to wait for a week more if we are not on the beta. Screwed up my administration schedule.
It's likely the RC is the same build or just slightly different than the public build coming next week. I have noticed a couple bugs with the RC though that weren't present in the previous beta. After the initial update Finder was unresponsive and I had to relaunch it. Safari also has some glitches, like frozen text boxes on websites (e.g. Reddit comments) and inability to click buttons on some websites (like add to cart). Overall performance seems faster though, especially Safari.
 
  • Like
Reactions: loby

MisterAndrew

macrumors 68030
Sep 15, 2015
2,895
2,390
Portland, Ore.
I have the same issue but I have a Samsung 2TB NVME with adapter instead of the stock Apple OEM NVME. I updated to 12.3 Beta and my firmware did not update and still showing 429.60.3.0.0. Could it be that the firmware will not updated because I need to put the Apple NVME back.
I have a 3rd party NVMe installed with an adapter too (sk Hynix) and the firmware updated just fine.
 

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
It appears firmware 430.100.23.0.0 isn't included with the 12.3 RC. My 6,1 just made an eficheck.dump. (MP61.88Z.F000.B00.2201101802)
Humm...so...is the sleep/crash issue with mp6,1 fixed with 12.3 RC? If so, then it was an OS issue and not a firmware issue as thought by many?
 

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
Also...it may not be a firmware issue. I also had the same thing happen on my MacBook Pro 2018 i9 as some others had stated on other Macs. It crashed and restarted over the night with the same message. Maybe an OS issue instead.
 
  • Like
Reactions: MisterAndrew
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.