Jump to content

No, my Macbook didn't shut down because of a problem.

Hey, all,

 

I recently upgraded my Macbook Pro that I bought in 2019 to macos 12.0.1 "Monterey."  Ever since upgrading, every time I power on my laptop, I get the error message "Your computer was shut down because of a problem" or something of the like (forgetting the exact phrasing).  This has happened to my every time I've powered on my device, but at no point did my laptop actually shut down due to a noticeable problem.  I shut the computer off regularly via the shutdown button in the toolbar. 

Has anyone else been having this issue?  Anyone find a good fix? 

Here's more specific info about my Macbook:
MacBook Pro (13-inch, 2016, Four Thunderbolt 3 Ports)
2.9 GHz Dual-Core Intel Core i5
16 GB 2133 MHz LPDDR3
Intel Iris Graphics 550 1536 MB

 

Thanks!

Link to comment
Share on other sites

Link to post
Share on other sites

Well, the message doesn't show up for no good reason, so there could actually be a problem. Does the MacBook Pro shut down completely normally when you tell it to shut down? When you do that the trackpad should stop responding - does that happen?

Phobos: AMD Ryzen 7 2700, 16GB 3000MHz DDR4, ASRock B450 Steel Legend, 8GB Nvidia GeForce RTX 2070, 2GB Nvidia GeForce GT 1030, 1TB Samsung SSD 980, 450W Corsair CXM, Corsair Carbide 175R, Windows 10 Pro

 

Polaris: Intel Xeon E5-2697 v2, 32GB 1600MHz DDR3, ASRock X79 Extreme6, 12GB Nvidia GeForce RTX 3080, 6GB Nvidia GeForce GTX 1660 Ti, 1TB Crucial MX500, 750W Corsair RM750, Antec SX635, Windows 10 Pro

 

Pluto: Intel Core i7-2600, 32GB 1600MHz DDR3, ASUS P8Z68-V, 4GB XFX AMD Radeon RX 570, 8GB ASUS AMD Radeon RX 570, 1TB Samsung 860 EVO, 3TB Seagate BarraCuda, 750W EVGA BQ, Fractal Design Focus G, Windows 10 Pro for Workstations

 

York (NAS): Intel Core i5-2400, 16GB 1600MHz DDR3, HP Compaq OEM, 240GB Kingston V300 (boot), 3x2TB Seagate BarraCuda, 320W HP PSU, HP Compaq 6200 Pro, TrueNAS CORE (12.0)

Link to comment
Share on other sites

Link to post
Share on other sites

1 hour ago, BondiBlue said:

Well, the message doesn't show up for no good reason, so there could actually be a problem. Does the MacBook Pro shut down completely normally when you tell it to shut down? When you do that the trackpad should stop responding - does that happen?

Yup!  Everything seems normal to me.  Yeah, I figure there must be some kind of problem I can't see, but everything looks normal except that message.  Maybe I'm just not being vigilant enough 😅

Link to comment
Share on other sites

Link to post
Share on other sites

24 minutes ago, server_mint said:

Yup!  Everything seems normal to me.  Yeah, I figure there must be some kind of problem I can't see, but everything looks normal except that message.  Maybe I'm just not being vigilant enough 😅

Strange. Have you tried forcibly powering it off by holding the power button? It won't hurt anything, so it's worth a try. 

Phobos: AMD Ryzen 7 2700, 16GB 3000MHz DDR4, ASRock B450 Steel Legend, 8GB Nvidia GeForce RTX 2070, 2GB Nvidia GeForce GT 1030, 1TB Samsung SSD 980, 450W Corsair CXM, Corsair Carbide 175R, Windows 10 Pro

 

Polaris: Intel Xeon E5-2697 v2, 32GB 1600MHz DDR3, ASRock X79 Extreme6, 12GB Nvidia GeForce RTX 3080, 6GB Nvidia GeForce GTX 1660 Ti, 1TB Crucial MX500, 750W Corsair RM750, Antec SX635, Windows 10 Pro

 

Pluto: Intel Core i7-2600, 32GB 1600MHz DDR3, ASUS P8Z68-V, 4GB XFX AMD Radeon RX 570, 8GB ASUS AMD Radeon RX 570, 1TB Samsung 860 EVO, 3TB Seagate BarraCuda, 750W EVGA BQ, Fractal Design Focus G, Windows 10 Pro for Workstations

 

York (NAS): Intel Core i5-2400, 16GB 1600MHz DDR3, HP Compaq OEM, 240GB Kingston V300 (boot), 3x2TB Seagate BarraCuda, 320W HP PSU, HP Compaq 6200 Pro, TrueNAS CORE (12.0)

Link to comment
Share on other sites

Link to post
Share on other sites

19 hours ago, server_mint said:

Hey, all,

 

I recently upgraded my Macbook Pro that I bought in 2019 to macos 12.0.1 "Monterey."  Ever since upgrading, every time I power on my laptop, I get the error message "Your computer was shut down because of a problem" or something of the like (forgetting the exact phrasing).  This has happened to my every time I've powered on my device, but at no point did my laptop actually shut down due to a noticeable problem.  I shut the computer off regularly via the shutdown button in the toolbar. 

Has anyone else been having this issue?  Anyone find a good fix? 

Here's more specific info about my Macbook:
MacBook Pro (13-inch, 2016, Four Thunderbolt 3 Ports)
2.9 GHz Dual-Core Intel Core i5
16 GB 2133 MHz LPDDR3
Intel Iris Graphics 550 1536 MB

 

Thanks!

There have been reports of memory leaks that cause macOS to crash, not sure if that's what happening but try and monitor the memory pressure.

Edit: Full read the post, Proabbly isn't a memory leak but do what maplepants just said

"A high ideal missed by a little, is far better than low ideal that is achievable, yet far less effective"

 

If you think I'm wrong, correct me. If I've offended you in some way tell me what it is and how I can correct it. I want to learn, and along the way one can make mistakes; Being wrong helps you learn what's right.

Link to comment
Share on other sites

Link to post
Share on other sites

17 hours ago, BondiBlue said:

Strange. Have you tried forcibly powering it off by holding the power button? It won't hurt anything, so it's worth a try. 

Good suggestion!  Unfortunately, I tried that and received that same prompt. 

no_problem.JPG

Link to comment
Share on other sites

Link to post
Share on other sites

Nothing comes up in the crash reports except for when Company of Heroes 2 crashed late last month (yep, I can't afford a PC right now, so I play games on my Mac 😅).  Nothing that would necessarily indicate a startup problem. 
However!... When I checked the general "Log Reports," they seemed to correspond with my startups.  I'm pasting just one of the reports here if it makes any sense:

SessionID=876fdd92-01e5-49a3-8605-53f4aa46ae30.1638890566009 Timestamp=2021-12-07T10:22:46:167-0500 ThreadID=7156 Component=ngl-lib_NglAppLib ErrorID=403 Description="GetCachedNglProfile Status: NGL Profile Unavailable"
SessionID=876fdd92-01e5-49a3-8605-53f4aa46ae30.1638890566009 Timestamp=2021-12-07T10:22:46:222-0500 ThreadID=7156 Component=ngl-lib_NUSecureProfileDao Description="GetPrefetchedSecureProfile : Prefetched ASNP not found"
SessionID=876fdd92-01e5-49a3-8605-53f4aa46ae30.1638890566009 Timestamp=2021-12-07T10:22:46:222-0500 ThreadID=7156 Component=ngl-lib_NUSecureProfileFetcher ErrorID=SPDaoLevelStatus:11 Description="ValidateAndGetPrefetchedSP : Failed to fetch prefetched ASNP"
SessionID=876fdd92-01e5-49a3-8605-53f4aa46ae30.1638890566009 Timestamp=2021-12-07T10:22:46:222-0500 ThreadID=7156 Component=ngl-lib_NglAppLib ErrorID=228 Description="GetPrefetchedNglProfile Status: Data Not Found : Cached NGL Profile"
SessionID=876fdd92-01e5-49a3-8605-53f4aa46ae30.1638890566009 Timestamp=2021-12-07T10:22:46:425-0500 ThreadID=7159 Component=ngl-lib_HttpRequestDelegate Description="Received Response with status 200"
SessionID=876fdd92-01e5-49a3-8605-53f4aa46ae30.1638890566009 Timestamp=2021-12-07T10:22:46:805-0500 ThreadID=7161 Component=ngl-lib_HttpRequestDelegate Description="Received Response with status 204"
SessionID=876fdd92-01e5-49a3-8605-53f4aa46ae30.1638890566009 Timestamp=2021-12-07T10:22:46:805-0500 ThreadID=7161 Component=ngl-lib_HttpRequestDelegate Description="Got empty response"
SessionID=876fdd92-01e5-49a3-8605-53f4aa46ae30.1638890566009 Timestamp=2021-12-07T10:22:46:837-0500 ThreadID=7166 Component=ngl-lib_NUSecureProfileFetcher ErrorID=COPRetrieverStatus:13 Description="GetDeviceTokenAndProfile : We have a valid access token but could not reach COPS, fill in userprofile from IMS"
SessionID=876fdd92-01e5-49a3-8605-53f4aa46ae30.1638890566009 Timestamp=2021-12-07T10:22:46:837-0500 ThreadID=7166 Component=ngl-lib_NglAppLib ErrorID=110 Description="GetLatestNglProfile Status: Unhandled Error"

 

Screen Shot 2021-12-07 at 12.45.52 PM.png

Screen Shot 2021-12-07 at 12.49.22 PM.png

Link to comment
Share on other sites

Link to post
Share on other sites

What's it say under crash reports and diagnostic reports? Log reports usually contains much more innocuous stuff. 

 

Here's where I'm going with this, that message should come with a little button on it that offers you a chance to view the report. This pop-up comes because of a parameter in your Mac's NVRAM. It's not exactly this simple, but imagine on startup the system sets a flag that says "I have shut down on purpose" to "false". Then when it shuts down normally, it sets "I have shut down on purpose" to "true". So on boot, if "I have shut down on purpose" is "false" then the system knows there was a problem, throws up this dialog and wants to link you to what it thinks the relevant crash report is. But in your case, it doesn't link you to that report... odd.

 

Earlier in the year some Intel Mac users on MacRumors were reporting that their Mac was showing this pop-up after every boot just like you've got. However, they reported it fixed with 11.2.3 and here we are on 12.0.1.

 

So I suspect one of three things.

 

1. Some piece of external hardware isn't responding to the OS shutdown command before the process times out and the computer does a hard shutdown

2. Some piece of software is freezing in response to the OS shutdown command causing the same wait, timeout, and hard shutdown as option 1 would cause

3. The OS shutdown procedure is not properly updating the values in the NVRAM to confirm that the machine was shut down on purpose. 

 

My hope is that by taking a look at your crash reports and your diagnostic reports immediately after a fresh boot, something will jump out at us. If it does, then we move forward and see what we can do about it.

 

But if there's nothing there, then it's that old Big Sur bug come back to haunt you specifically (sorry about your luck) and if you want I can guide you through the steps of filing a "Feedback" ticket with Apple.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×