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.

beardalex

macrumors newbie
Jan 15, 2022
1
0
I have MBP 18,1 (M1) and see the same issue. Computer restarts whenever it goes to sleep and I have attached an external HDD or monitors. If I switch off my docking station, disconnecting all peripherals, it doesn't restart. Have tried all the proposed solutions here, nothing worked so far.
 

sarkekim

macrumors newbie
Jan 12, 2022
3
2
My theory of the crash being related to the external drive seems to be false. I had a Sleep Wake Failure at 2:21am this morning with no external drive connected. Sat down to the login screen this morning. Doh.
 
  • Like
Reactions: loby

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
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.)
Didn’t start until updated to Monterey. My Mac Pro 2013 firmware is updated to the latest (can’t check due to currently in different location), but know whatever firmware is current as of macOS Monterey 12.1 (21C52) is when I noticed the issue. I usually shut down my system after usage, but with macOS Monterey 12.1 I started to put it to sleep only and then noticed.
 

MisterAndrew

macrumors 68030
Sep 15, 2015
2,895
2,390
Portland, Ore.
My 6,1 crashed again today. I attempted to wake it from sleep and instead it restarted. This is what the beginning of the crash report looks like. I have no idea what it means.

*** MCA Error Report ***
CPU W<ine 7]<k Ar7Mectu'^TrrorDX^p (CZ*InteG
% Xeog
% CPUTXV1680d.@ 3.vz, CZI: 0x7fV4)
 

Mr.Chefkoch

macrumors newbie
Dec 5, 2021
12
2
My 6,1 crashed again today. I attempted to wake it from sleep and instead it restarted. This is what the beginning of the crash report looks like. I have no idea what it means.

*** MCA Error Report ***
CPU W<ine 7]<k Ar7Mectu'^TrrorDX^p (CZ*InteG
% Xeog
% CPUTXV1680d.@ 3.vz, CZI: 0x7fV4)
This is similar to the error I'm seeing, just different random letters. Basically MCA means some sort of CPU failure (or hardware in general?) and this is supposed to be the message the CPU explains its problems in, but it's not understandable. I already switched my CPU, so it must be something else.
 

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
This is similar to the error I'm seeing, just different random letters. Basically MCA means some sort of CPU failure (or hardware in general?) and this is supposed to be the message the CPU explains its problems in, but it's not understandable. I already switched my CPU, so it must be something else.
Anybody NOT upgrade and still on Mojave or lower and therefore not upgrade? These are those who have not upgraded and gone back. When you upgrade it will automatically update your firmware.

This could really isolate the issue “if” anyone on the forum has not at all updated yet and comment. Please do.. :)
 

Trunkz

macrumors regular
Jul 27, 2012
105
47
London, UK
Alright to update things along;

Got my mac pro back last night from the apple store. They had replaced the D300 board A; it cost less than what I thought (part was £130 plus the £90 out of warranty repair fee). I left the MP on sleep overnight and came this morning and it had not crashed. Just realised when I put it to sleep there was no running apps; so im leaving a few open now and will be putting it to sleep.

Lets see :)
 

Trunkz

macrumors regular
Jul 27, 2012
105
47
London, UK
That didnt last. 30minutes after leaving Outlook, Mail, Whatsapp and Chrome open then placing it into sleep. Same error as above :-D
 

haroldkman2000

macrumors newbie
Nov 20, 2021
24
12
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.

View attachment 1942981

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.
An update on my situation since my last update had some errors on my part and I wanted to clear that up. With the settings above, my display would turn off after 15 minutes and would go into "display sleep" meaning the Mini is still running but the TV would no longer show the output from the Mini. The "Prevent your..." checkbox ensured that it didn't fully go to sleep and it was just "display sleep". Naturally, it didn't crash (~5 days) when I woke it up because it wasn't coming out of a full sleep and was actually running the whole time.

This seems pretty obvious to me now but I managed to confuse things along the way. Anyway, it of course crashed again once I unchecked the "Prevent your..." option. As it stands now, I will no longer have it manually or automatically sleep and will just shutdown when I know I won't be using it for more than a few hours since it's better than "display sleep" or having it crash.

Apple Support is useless so some other ways to report this is via https://www.apple.com/feedback/ or use social media to try and raise awareness with @apple.
 
Last edited:

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
That didnt last. 30minutes after leaving Outlook, Mail, Whatsapp and Chrome open then placing it into sleep. Same error as above :-D
Anyone using Ethernet instead of wifi? Switch to Ethernet and after day one has not crashed. We will see..
 

th0masp

macrumors 6502a
Mar 16, 2015
851
517
Anybody NOT upgrade and still on Mojave or lower and therefore not upgrade? These are those who have not upgraded and gone back. When you upgrade it will automatically update your firmware.

This could really isolate the issue “if” anyone on the forum has not at all updated yet and comment. Please do.. :)
What's your question? I have not upgraded beyond Mojave (and won't), firmware is whatever was installed with 10.14.6 (no further security updates installed). No crashes. System is in use daily and put to sleep when not in use.

System uptime:
12:08 up 191 days, 13:59, 5 users, load averages: 6.60 5.44 5.21

?
 

loby

macrumors 68000
Jul 1, 2010
1,882
1,514
What's your question? I have not upgraded beyond Mojave (and won't), firmware is whatever was installed with 10.14.6 (no further security updates installed). No crashes. System is in use daily and put to sleep when not in use.

System uptime:
12:08 up 191 days, 13:59, 5 users, load averages: 6.60 5.44 5.21

?
That’s the question. ;). It might point to a firmware issue and/or macOS Monterey itself if those who have not upgraded to Monterey are not having the issue. That would help Apple “if” they will get a fix out for us.

Hopefully they will slip in a fix when macOS Monterey 12.2 comes out. From what I heard, currently the beta doesn’t fix the issue…
 

Trunkz

macrumors regular
Jul 27, 2012
105
47
London, UK
What's your question? I have not upgraded beyond Mojave (and won't), firmware is whatever was installed with 10.14.6 (no further security updates installed). No crashes. System is in use daily and put to sleep when not in use.

System uptime:
12:08 up 191 days, 13:59, 5 users, load averages: 6.60 5.44 5.21

?
Can you confirm your bootrom version please?
 

steve123

macrumors 65816
Aug 26, 2007
1,155
719
This is definitely related to the firmware update and it is a REGRESSION. This same issue has occurred with every macOS / OS X release for the past several years. You need to turn off sleep to avoid the crash and potential data loss until Apple fixes this.

Here's a thought. Maybe we should report this to their environmental team? It seems Apple takes their environmental performance seriously and we are all wasting energy for which the root cause is a defect that Apple can fix. If someone has a lot of followers, maybe someone can tweet something to the effect thAT Apple is unnecessarily polluting the world .. this problem is definitely generating increased CO2 emissions.
 

MisterAndrew

macrumors 68030
Sep 15, 2015
2,895
2,390
Portland, Ore.
That's interesting to think it might be a firmware issue. Has anyone who didn't have the issue before installing Monterey 12.1 gone back to 12.0 or earlier and still have the issue?

Also, has anyone checked the firmware version in the latest 12.2 beta? Edit: Just installed it. Same firmware. :/
 
Last edited:

haroldkman2000

macrumors newbie
Nov 20, 2021
24
12
This is definitely related to the firmware update and it is a REGRESSION. This same issue has occurred with every macOS / OS X release for the past several years. You need to turn off sleep to avoid the crash and potential data loss until Apple fixes this.

Here's a thought. Maybe we should report this to their environmental team? It seems Apple takes their environmental performance seriously and we are all wasting energy for which the root cause is a defect that Apple can fix. If someone has a lot of followers, maybe someone can tweet something to the effect thAT Apple is unnecessarily polluting the world .. this problem is definitely generating increased CO2 emissions.
Apple will counter this with, "We are actually helping the environment because a dead computer, either by crashing it or people using shutdown instead sleep, is using less energy. So there!". ?
 
  • Haha
Reactions: loby and steve123

th0masp

macrumors 6502a
Mar 16, 2015
851
517
Can you confirm your bootrom version please?
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: 6-Core Intel Xeon E5
Processor Speed: 3,5 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Hyper-Threading Technology: Enabled
Memory: 64 GB
Boot ROM Version: 132.0.0.0.0
SMC Version (system): 2.20f18
Illumination Version: 1.4a6
 
  • Like
Reactions: adingley

steve123

macrumors 65816
Aug 26, 2007
1,155
719
No crashes. System is in use daily and put to sleep when not in use.

System uptime:
12:08 up 191 days, 13:59, 5 users, load averages: 6.60 5.44 5.21

?
I recall Big Sur was ok after 11.4 until this Monterey fiasco.
 

Trunkz

macrumors regular
Jul 27, 2012
105
47
London, UK
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: 6-Core Intel Xeon E5
Processor Speed: 3,5 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Hyper-Threading Technology: Enabled
Memory: 64 GB
Boot ROM Version: 132.0.0.0.0
SMC Version (system): 2.20f18
Illumination Version: 1.4a6
Looks like a bootrom issue then. I initially thought it may have been because I upgraded to a 12-Core Xeon processor and the issues started happening around that time; but it was also when i upgraded the bootrom and Catalina (then eventually Mojave)
 

Trunkz

macrumors regular
Jul 27, 2012
105
47
London, UK
This issue hasn't happened yet with 12.2 beta, so maybe it's not a firmware issue. The Mac wakes up from sleep quickly now.
The issue doesnt lie with the OS. If you check your bootrom version; I'll bet its 132.x or lower :)

If you are running a non-Apple SSD in your mac pro; the bootrom is most likely version 127.x or lower as Apple removed the restrictions on 3rd party SSDs to update the bootrom with version 130.x
 

TheBeverage

macrumors member
Feb 2, 2014
70
194
Where would I find the bootrom version in 12.1? In system information, I only see what's attached. I wanted to check as I've been running a third party Auro Pro X2 SSD in my Mac Pro for a couple of years, but have also had this intermittent crashing bug since Monterey launched.
 

Attachments

  • Screen Shot 2022-01-18 at 6.50.58 AM.png
    Screen Shot 2022-01-18 at 6.50.58 AM.png
    28.5 KB · Views: 72
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.