GUIDE How to Fix You shut down your computer because of a problem error during Startup on macOS


Staff member
Jul 22, 2018
Supermicro X11SPA-T
Intel Xeon W-3275 28 Core
2xAMD RX 580 8GB
OS X/macOS
  1. OpenCore
  1. Mac mini
  2. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
How to Fix "You shut down your computer because of a problem" during the Startup on macOS

This guide covers fixes You shut down your computer because of a problem error message during startup on macOS. By following this guide, you'll be able to fix the error message "You shut down your computer because of a problem" at each boot.


If you are on macOS Monterey or newer, it's very likely possible that you might have come across this issue. When booting the system, at the startup/login, an error message appears "You shut down your computer because of a problem" and this message appears on each boot. As the message states, if you want to open the applications that were open when you shut down, click on Open and if you do nothing, the computer will continue the login with a countdown of 60 seconds. Restarting or Shutting down the system had no effect at all.

This message seems very similar to the “Your Computer was Restarted Because of a Problem” message, but note that, the message tells you that you shut your computer down because of a problem. In both cases, the shutdown was as usual. Some users who have had this problem have said that the message simply stopped appearing at some point. Others have tried many different things to get rid of the message; they have tried restarting, updating software, restarting in Safe Mode, resetting the PRAM/NVRAM, doing disk checks in Disk Utility, and even reinstalling macOS. This issue has been also seen on Apple computers. The issue is caused due to a panic file stored on the target disk. Note that it could be also stored in the native NVRAM. Luckily, the fix is quite simple and does not require much effort.
To fix the issue, follow the steps below.

STEP 1: Obtain Latest OpenCore and Kexts
To fix this issue, the first step is to obtain the latest OpenCore from the latest commit and also the related kexts. You can also use the stable release version which is available in the Downloads Section of this forum. To obtain the latest releases, follow the steps below.

1. Visit the builds section.

Screen Shot 2022-06-11 at 11.44.52 PM.png

2. Click on Select a product drop-down menu, and you'll find all the related products.
Screen Shot 2022-06-11 at 11.45.49 PM.png

3. Select OpenCorePkg from the list and click on the Release button to download the latest OpenCore.
Screen Shot 2022-06-11 at 11.47.01 PM.png

4. Like step 3, download the latest release for essential kexts like Lilu, VirtualSMC, WhateverGreen, AppleALC, CPUTscSync, and other kexts you need for booting your system.

STEP 2: Update OpenCore and Kexts
Once you're done with the STEP #1, the next step is to simply update the OpenCore and the related kexts. To update OpenCore and the latest kexts, follow the steps below.

1. Mount your ESP.
2. Replace all the latest kexts with the old one.
3. Use EFI folder from X64 directory in the OpenCore release folder.
4. Copy the sample.plist from Docs directory in the OpenCore release folder.
5. Make changes in the sample.plist with the reference of your original (old) config.plist
6. Rename sample.plist to config.plist
7. Once the above steps are done, replace the EFI with a newly made EFI folder to your ESP.

STEP 3: Delete Sleep Wake Failure diag
The next step is to delete the "Sleep Wake Failure" diag which is the main culprit. For Apple computer users, you just need to follow this step, followed by resetting PRAM/NVRAM. To delete this file, follow the steps below.

1. On your target disk, navigate to the following directory using Finder.

Macintosh HD/Library/Logs/DiagnosticReports

Assuming that Macintosh HD is the target disk.

2. Search for the diag file starting with Sleep Wake Failure....
3. Select all the files using your Mouse or Keyboard shortcut (CTRL+Click) with the name Sleep Wake Failure
4. Right-click on the selected files and select Move to Trash.
5. Empty Trash.

The next step is to clear NVRAM. To clear NVRAM, follow the steps below.

1. Open Terminal and execute the following command
sudo nvram -c

2. Press enter key.
3. Enter your password when prompted and then press enter key.
4. Quit Terminal.

STEP 5: Restart your System
Once you're done with the above steps, all you need to do is restart your computer and the error message should no longer appear during boot.

STEP 6: Reset NVRAM and CMOS
If the above steps do not fix the issue, probably, the panic report might be stored in the native NVRAM. Follow the guide linked below to reset NVRAM

If the issue is not fixed, consider doing a CMOS reset.

STEP 7: Flashing BIOS and ME
In some cases, by doing all the above steps, where the NVRAM implementation is buggy or has not been implemented correctly or isn't working for some reason, the last solution is to re-flash the BIOS and ME completely. Refer to Fixing NVRAM for more information.
Last edited:

Forum statistics

Latest member