George Garside Blog

A place of many ramblings about macOS and development. If you find something useful on here, it's probably an accident.

You can find the previous shutdown cause on your Mac by running the following command in Terminal. It used to be you could use Console.app, but as part of the move to unified logging, it’s no longer possible to query backwards with Console.app, so you need to use Terminal to find your previous shutdown cause.

log show --predicate 'eventMessage contains "Previous shutdown cause"' --last 24h

If Mac has shutdown in the time specified, you should see messages such as Previous Shutdown Cause: followed by a number. The number is a cryptic shutdown code representing the cause of the shutdown.

Below are a list of shutdown causes on macOS and OS X with a description of the code and explanations for what the codes mean, including some initial troubleshooting steps. The troubleshooting steps are by no means exhaustive, but should give you a good starting point for how to proceed with your investigation, especially if you suffer from the issue repeatedly.

CodeDescriptionSolution
7CPU thread error.If this occurs during boot, try Safe Mode by holding ⇧shift at boot to limit what opens during startup. If during application usage, see if there’s an update to the app by the developer, and leave a comment below with the name of the app and the model of your Mac.
6unknownHave you got this error too, or any information? Leave a comment below!
5Correct Shut Down.Shutdown was initiated normally, from the macOS Shut Down menu or other shutdown command such as /sbin/shutdown. This does not indicate an issue with your system.
3Hard shutdown.Check the power button if you did not perform a hard shutdown yourself. It could be the case that the power button stuck down and forced a shutdown.
0Power disconnected.Check power supply/battery on a laptop, or the power supply for a Mac without a battery. On a laptop, the Mac should hibernate before the battery becomes so discharged it is unable to shutdown correctly, therefore if you see this shutdown cause on a laptop it may indicate a hardware issue with the battery or with the battery controller for reading the charge. Try resetting the SMC by connecting the switched off computer to power, holding ⌃control+⌥option+⇧shift and pressing power.
-3Multiple temperature sensors exceeded the defined limit.Hold D on boot to run Apple Diagnostics and follow the instructions if any errors are found. If the issue persists, make an appointment at an Apple Store. For Authorized Service Providers, Run Apple Service Diagnostics to check which sensor went beyond expected thermal limits.
-14Electricity spike/surge.On Mac Pro, this can indicate an electricity issue to the built-in power supply, or an issue with the power supply itself.
-20BridgeOS T2-initiated shutdown.The T2 chip in your 2018+ MacBook Pro or other Mac (list in link) initiated a shutdown.
-60Bad master directory block (badMDBErr).Back up your data, erase the disk and reinstall macOS. If you continue to run the system, data loss may ensue. Use Time Machine to keep a backup until you are able to erase and restore. A common symptom is being unable to repair with Disk Utility — as such, erasing the disk is required as mentioned.
This is a very old error, from the days of Carbon. It’s unknown if this is actually relevant in macOS shutdown codes. Leave a comment below if you’ve got any more information.
-61Watchdog timer detected unresponsive application, shutting down the system.Troubleshoot for stuck application, startup item and any loading preferences. Boot to Safe Mode by holding ⇧shift on boot which disables most startup items and daemons. If the problem does not occur, try a new user account.
-62Watchdog timer detected unresponsive application, restarting the system.The system will automatically restart after this shutdown cause, unlike -61. Troubleshooting applies the same for cause -61. -61 is used where the system believes it cannot automatically recover, whereas -62 is used where the system determines it is likely to be resolved after restart. Hardware acceleration has been experimentally deemed a potential cause, based on kernel extensions being shown in logs. Memory management may be a potential cause, such as Google Chrome’s excessive use of RAM, which can be mitigated with various extensions that suspend tabs when not in use. While it is a bug with macOS that Google Chrome should be able to cause a -62, such mitigations might be necessary.
-63unknownSome comments have indicated that this only happens with more recent Macs, such as 2018 MacBook Pros. Have you got this error too, or any information? Leave a comment below!
-64unknownHave you got this error too, or any information? Leave a comment below!
-65unknownPotentially linked to operating system issue. Try reinstalling macOS as fresh or booting from clean install on an external drive.
-71SO-DIMM Memory temperature exceeds limits.If possible, swap memory module and check with known-good one to confirm issue is with memory. Check fans physically and with an app such as iStat Menus to determine whether the fans are rotating correctly and being reported correctly. Check air flow: open device and clean airways.
-74Battery temperature exceeds limits.Reset the SMC by connecting the switched off computer to power, holding ⌃control+⌥option+⇧shift and pressing power. Swap battery and check with known-good one to confirm issue is with customer battery.
-75Communication issue with AC adapter.Check power/MagSafe connector (plug), adapter and cable. Make sure the adapter in use is an official Apple power supply. On MacBook Pro with USB-C, connect power to opposite side of laptop to determine if issue is with specific ports.
-78Incorrect current value coming from AC adapter.Make sure the adapter is an official Apple power supply. Check AC adapter plug and cable. Confirm current at the wall where the adapter is connected to.
-79Incorrect current value coming from battery.Check battery statistics: check if cycles are excessive and may indicate the battery needs replacing. Check the battery connection to logic board.
-86Proximity temperature exceeds limits.Check thermal contact with heatsink, fan connection and physical/reported activity.
-95CPU temperature exceeds limits.Check thermal contact with heatsink, fans. Reset SMC by connecting the switched off computer to power, holding ⌃control+⌥option+⇧shift and pressing power.
-100Power supply temperature exceeds limits.Check fans and air flow. Confirm power supply is official Apple. If MagSafe, remove any MagSafe adapters in use (e.g. MagSafe 1 to 2).
-102OvervoltageSafety shutdown related to over voltage protection (MLB or Battery).
-103Battery cell under voltage detected.Check battery and replace with known-good. Perform one charge cycle, then try again.
-104unknownPossibly linked to battery issue. Perform one charge cycle and try D-boot to run diagnostics.
-108unverifiedLikely memory issue. Commonly occurs when RAM is full and there was an issue with paging. Can occur when the system is sleeping.
-112unverifiedMemory issue. Almost always occurs around -128, another memory issue. Almost certainly hardware fault. See -128 for troubleshooting.
-127PMU forced shutdown.Check power button on your hardware. Potentially fine if you forced shutdown, otherwise may be hardware/SMC issue.
-128unknownPossibly linked to memory issue. If the issue is persistent, try replacing the RAM with known-good if your hardware has removable RAM.

Have you got an error not listed, or any other information on an existing one? Leave a comment below and I’ll keep this list comprehensive and up-to-date!

Leave a Reply

21 James Reynolds’s avatar

Nobody seems to know what these codes mean but you. Where did you get this list?

Reply
4 tanya e. pfeffer’s avatar

Any thoughts on what -64 represents?

Reply
2 Stamina Bing’s avatar

6 anyone?

Reply
2 Boaz’s avatar

same here. a lot of it.

Reply
1 D3xbot’s avatar

I’m troubleshooting a 2020 MacBook Air (13-inch). It’s got the -63 shutdown cause

Symptom: when putting the Mac to sleep or a short while thereafter, the fans will sometime spin up to maximum speed and the system will shut down. The system feels a bit warm, but CPU package temps never exceeded 80C according to iStat Menus.

An AASP told me that it’s probably the StarTech dock providing too high voltage. iStat Menus shows that the voltage is within Apple’s requirements and within the USB PD spec.

Checking the Power Manager logs, powerd shut down the system with cause -63

Reply
0 D3xbot’s avatar

I should also mention – no crash report or spindump was generated on these shutdowns. Just the -63 cause

Reply
0 D3xbot’s avatar

In troubleshooting the Mac, there was another error:

Failure Darkwake Exit Failure during wake due to 0x18A2759D00000032

This forum says it may be related to USB:

https://www.tonymacx86.com/threads/mojave-10-14-5-intel-hd630-no-resume-from-sleep.277696/page-3

Reply
0 D3xbot’s avatar

Update: Apple recommended replacing the logic board

Reply
1 Diksha Jaswal’s avatar

-64 error

Reply
1 Chris’s avatar

I just received a -64 shutdown cause, but it did not generate any kind of diagnostic report log. What kind of information can I provide?

Reply
1 bys1’s avatar

I keep getting random shutdowns with code -102 when doing resource-intensive stuff (gaming) on my MacBook 7,1. Ran an AHT but it didn’t find any issues. Using a different charger or disconnecting the charger doesn’t help. Any ideas?

Reply
1 Chaitanya’s avatar

For -128 (MBP Mid 2014) Try Ctrl+Cmd+Shit+Esc. Hopefully it will work keeping system stable rather than frequent shutdowns with -128 cause. I experienced the same and from Oct (post installing Catalina) Even downgrading to Mojave didn’t help. Took MBP Apple to Genius Bar. They diagnosed the system throughly and didn’t report or see any issue; hence, ruling out the logic-board/RAM or any other hardware issue for now).

I am assuming previous opened processes (just before are the crash( are not getting purged and causing system failure. I might be totally wrong. Even shutdowns and restarts didn’t help but trying the (Ctrl+Cmd+Shit+Esc) killing all processes followed with normal shutdown, starting system worked for me.

Reply
0 chaitanya’s avatar

Correction: Alt+Cmd+Shift+Esc to kill the processes.

And apologies for typos in my initial note.

Reply
1 Sharath Raju’s avatar

I am consistently getting the -128 error on a mid-2014 MBP (non-removable RAM). Any thoughts/suggestions on how to diagnose?

Thanks!

Reply
0 Justin’s avatar

-128 is most common with failing memory. So in your case you would need a logic board replacement since the memory is on board.

Reply
0 Happen’s avatar

Same here, same machine. MacBook Pro (Retina, 15-inch, Mid 2014), Catalina 10.15, -128 error. Nothing works so far, including:

– Reset SMC

– Reset NVRAM/PRAM

– upgrade Catalina to latest version

– Alt+Cmd+Shift+Esc to kill the processes

Reply
0 Denis’s avatar

Hey guys, this recently started to happen to me. Same mac as you both and started immediately after downloading Catalina. I have also tried your suggestions without any luck. Have you managed to solve this since you posted this? Appreciate your answers

Reply
0 Lulu’s avatar

guys same here but I have late 2015, I’m really not sure what’s happening

I tries killing all processes and shutting down its just way more frequent now I seriously don’t know what to do, if anyone found a way please reply

Reply
1 Chaitanya’s avatar

Interesting, looks like I am observing there is some pattern here.I also mid 2014 MBP. And I also started getting this since last week of Oct 2019 (post installing Catalina this has become more). Down grading to Mojave didn’t help. Took two months for me to observe there is an issue as the system shutdown intermittently.

Recently went to Genius Bar, they diagnosed it and mentioned all good with my MBP and couldn’t trace the exact issue/cause. Assume some occupation. (I also have Mac Air which have same Catalina installed using Time machine and it is working normal and good.)

Give a try for the below. Hopefully, it will not crash so frequently. Press Ctrl+Command+Shift+Esc : to kill all the processes. Me doing this stopped issue at least for certain time. Otherwise, it is horrible to use the system. Assuming there are some processes that are obsolete and system is not able to recover from it and shutting down. Even restarts and shutdown didn’t help and keeps occurring, until you kill them in this manner and start again. Good luck. Let me know if helps.

Reply
0 chaitanya’s avatar

Correction: Alt+Cmd+Shift+Esc to kill the processes.

And apologies for typos in my initial note.

Reply
0 Andy Rawlins’s avatar

Do you mean you use this to close every process in Activity Monitor individually? I see several hundred processes and some of them are presumably going to kill the OS if they are stopped.

Reply
0 Springer55’s avatar

I started to get the -128 issue on a fresh install of Catalina, too.

Reply
0 Lorenzo’s avatar

Same here, same machine. I think this could be fixed via software.

Reply
0 Sarm’s avatar

Same here, same machine. I tried everything under the sun to fix it but, following as complete OS reinstall combined with HDD wipe and transfer from time machine, stumbled across this page. It’s started happening in the past week.

Reply
1 kikyou’s avatar

Same here, same machine.

Reply
0 Denis’s avatar

Hey, did u solve the issue? this recently happened to me and ive tried everything with no luck. Appreciate your answer

Reply
0 Gideon’s avatar

I’m getting exactly the same problem: mid-2014 MBP, Catalina, started randomly shutting down 2w ago, sometimes when I’m in the middle of something. Shutdown cause is always -128. Setting hibernatemode to 0 didn’t help. Will see if an SMC reset helps.

Reply
0 James’s avatar

I also have this issue on a mid-2014 mbp. Currently trying to fix it. I’ve probably reset the SMC like 20 times, replaced my charger, replaced my battery, and did some weird solution to disable a thunderbolt port. Will continue to try to fix it.

Reply
0 xakerbox’s avatar

Hi, man… Did you get success in fixing that problem?

Funny thing: I’ve the identical MacBook Pro 2014 15”…. And it could be a real fuckup from Apple side….

Give me a note, did you solve the cause -128 and random shutdowns? Thanks a lot!

Reply
1 raul’s avatar

ia have a -102

any ideas?

Reply
1 Rino Armadiaz’s avatar

Hi George,

I’m having a random restart with my MacBook Pro 13″ 2018 and the logs says im having “shutdown cause : -20”

i searched on google seems very few people are getting the same problem.

Do you have any idea what the problem is? thanks!

Reply
0 mk’s avatar

I also have the code of -20. But it says here in my mbp 15 2019. Bad ‘cos I just got it.

0xcf Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -20

Could it be SMC?

Reply
0 LuxoNum’s avatar

I think this may be a T2 chip issue because my MacBook Air 2018 is having the same code display and I’ve only seen 2018 or 2019 MacBooks with this issue in this comment section

Reply
1 rrraaarrr’s avatar

I’ve been getting the same one (-20) on a 2019 16″ MBP.

Reply
0 vp’s avatar

The cursed T2 chip produces BridgeOS induced kernel panics with code -20. Every few days without fail, sometimes more often.

Reply
0 Caroline’s avatar

Yes me too with MacBookk Air 2019 and a -20 code. Just happened twice in 15 mins. Anyone know a fix?

Reply
0 Anuar’s avatar

I just bought my MacBook Pro 2020 a month ago and I am having the -20 code every time I’m trying to launch an Apple Arcade game. I tried to update for the latest software available and it didn’t help. So I just don’t play Apple Arcade games.

Reply
1 stephen boyle’s avatar

not sure if anyone is watching here – but ive been trying to build a script that keeps track of previous shutdown causes for our records. this is working great and i love the description above — but does anyone have weird behavior on their machine not always logging 5?? for example if i restart my laptop which is working fine it seems to always log a 3. although i was testing this out and previously had done a bad restart. the only way i can get back to 5 is to shutdown and start up again. another machine i have tested on has logged a 0 when it was a normal reboot too… i just wonder how accurate apple treats these.

Reply
0 Kev’s avatar

Okay so I get repeated -63 on 2018 Mbp.

Reply
0 Anders’s avatar

Getting the -63 too. Any help on what this issue can be would be awesome.

Reply
0 anders’s avatar

Also getting repeated -63 on 2018 – any tips would be helpful

Reply
0 Karntchana Sangjan’s avatar

Could be T2-related kernel panics. Check kernel logs to confirm.

Reply
0 Ben’s avatar

I have multiple -63 resets. New iMac 2020 (with a T2).

Seems to be related to MCA errors when running virtual machines. Reproducted it with both Parallels and VirtualBox on this (brand new!) hardware.

Gonna try apple support, but I feel that this is going to be a black hole.

Reply
0 Thomas Röttig’s avatar

FYI. Had a -63. I did install a new 4k display. Not sure if this caused it. Also a 5 from yesterdays shutdown.

Timestamp Thread Type Activity PID TTL

2020-11-24 20:38:18.242750+0100 0xd8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -63

2020-11-25 07:20:00.359403+0100 0xd8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

Reply
0 Aakansha Gharde’s avatar

me too, someone help, please

Reply
0 brandon11’s avatar

estoy con lo mismo MBP mid 2014.

Empezo desde la actualizacion a la ultima version de catalina.

Supongo q esperare hast aotra actualizacion y lo llevare a revisar.

Reply
0 sheikh rakib’s avatar

I got -128 and -5 reading what should I do now

Reply
0 nitron’s avatar

what does -11 indicate and I am using macbook pro 2020

Reply
0 Oudee’s avatar

I got a -2 on my Macbook Air mid-2012. It is not listed in here. What could it be? Please answer

Reply
0 Krrishna’s avatar

Last login: Wed Sep 30 13:33:03 on console

The default interactive shell is now zsh.

To update your account to use zsh, please run chsh -s /bin/zsh.

For more details, please visit https://support.apple.com/kb/HT208050.

Sais-Air:~ stranger$ log show –predicate ‘eventMessage contains “Previous shutdown cause”‘ –last 24h

Filtering the log data using “composedMessage CONTAINS “Previous shutdown cause””

Skipping info and debug messages, pass –info and/or –debug to include.

Timestamp Thread Type Activity PID TTL

2020-09-29 13:49:28.076565+0530 0xa9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-29 15:31:48.002112+0530 0xa9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-29 15:37:33.050287+0530 0xa9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-29 16:28:12.081091+0530 0xa9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-29 18:28:12.001344+0530 0xa9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-29 18:33:55.974510+0530 0xa9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-29 21:41:41.195545+0530 0xa9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-01-01 05:30:24.522326+0530 0xa8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 0

2020-09-30 12:56:14.046241+0530 0xa9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-30 13:32:45.064564+0530 0xa9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

Log – Default: 10, Info: 0, Debug: 0, Error: 0, Fault: 0

Activity – Create: 0, Transition: 0, Actions: 0

Sais-Air:~ stranger$

Reply
0 Gaurav’s avatar

Anyone with “-6”.

I have the latest OS Catalina 10.15.7 on MacBook Air 2015

My system keep shutting down more frequently then you can imagine.

Is there any way to figure what causing this issue?

Reply
0 R’s avatar

same issue here and every time I take it to the shop for check up it turns on just fine and starts working perfectly. Guy said all looks pristine so I don’t know what’s going on!

Reply
0 Sourish’s avatar

2020-09-21 00:11:54.717741+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-21 00:46:33.727869+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-21 10:31:48.783130+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-09-21 12:32:34.773357+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-21 16:15:14.790684+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-09-21 16:40:37.766862+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-21 16:44:22.728580+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-21 16:46:40.752260+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-21 17:08:51.762764+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-21 17:44:34.739054+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-09-21 22:24:12.721194+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

2020-09-21 23:53:00.721707+0530 0xb5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -128

I am facing -128 issue plz help someone???

Reply
0 Sourish’s avatar

please give more information on -128 code I am facing serious problems in my MacBook Pro 15 inch retina

Reply
0 David Cogen’s avatar

I got cause “1”. What is that?

Reply
0 EliDeuce’s avatar

I have encountered a -11 shutdown code on my 2018 Mac mini (6-core i5; MacOS 10.15.6) connected via TB3 to four (4) AMD Vega 56 eGPUs.

Reply
0 Chris’s avatar

My MBP 2019 showed many Previous shutdown cause: -20, when running Grapher. Why?

Reply
0 ACloseShave’s avatar

On my 2019 MacBook Pro, I have received multiple instances of error code 1 (not listed):

2020-08-17 18:02:56.646374-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1

2020-08-20 13:26:38.016674-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1

2020-08-21 09:54:20.816082-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1

2020-08-25 22:48:18.389554-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1

2020-09-02 14:24:33.388291-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1

This uses the same thread (0xc8) as codes 3, 5 and 7 but that’s the only similarity I can see:

2020-08-20 11:42:31.465576-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -20

2020-08-20 13:26:38.016674-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1

2020-08-21 09:54:20.816082-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1

2020-08-25 11:42:09.007567-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 3

2020-08-25 22:48:18.389554-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1

2020-08-27 23:00:37.924673-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 7

2020-09-02 07:02:33.910209-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-09-02 14:24:33.388291-0500 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1

Reply
0 Keith’s avatar

Hello,

So here is the message I get about the shutdown but I can’t find -40 from the reasons.

2020-09-03 07:55:48.054294+0200 0xab Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-01-01 02:00:07.862841+0200 0xab Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 0

2020-01-01 02:16:28.021713+0200 0xab Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -40

Please help.

Reply
0 Miikkali’s avatar

We are seeing -62 and -63 on a couple of 2013 Mac Pro’s that we recently upgraded to macOS 10.15.5. I witnessed a couple of crashes myself. When they happened, I hadn’t launched any other applications than System Preferences. I had also just rebooted a few minutes before.

Reply
0 russianxanadu’s avatar

log show –predicate ‘eventMessage contains “Previous shutdown cause”‘ –last 24h

log: warning: The log archive contains partial or missing metadata

log: cannot use –last when archive metadata is missing

Reply
0 Brad Diggs’s avatar

cause: 1 appears to be the result of “sudo shutdown -r now”

Reply
0 Ethan Sharp’s avatar

Does anyone know what -59 means?

Reply
0 MG’s avatar

I get a -113 while my MacBook Pro retina mid-2012 sleeps. Works fine however when it wakes up. Any clue?

Reply
0 AndyW’s avatar

Hi,

Late 2014 iMac 27″ Retina, macOS 10.15.5

Timestamp Thread Type Activity PID TTL

2020-07-16 20:57:17.631524+0100 0xa7 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -64

2020-07-17 11:47:48.598533+0100 0xa7 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 6

-64 shut down last night while not being used (but 3 people logged in), restarted without anyone noticing until logging in has to reload everything.

6 today while I was using it with loads of things open at once, but just writing an outlook email. Hung on black screen for about a minute, but still with power to USB. Then came with the unexpected shutdown message and restarted fine.

Had a few other random shutdowns, but not seen these numbers before – I put it down to a power cut or an overnight software update. I shall start keeping a better log.

Reply
0 DP’s avatar

I got this- Mac Os 10.14.6

2020-07-10 06:14:55.063013+0530 0xa5 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -40

Reply
0 caroline’s avatar

Hi George – I keep getting a -20 shutdown cause. What does that mean? My MacBook Air keeps crashing with no warning… Thanks 🙂

Reply
0 Pranshu’s avatar

Hey, I got a -1 as a result. Can you please tell what is it?

Reply
0 vp’s avatar

-14 on Catalina/Mac Pro : electricity surge or spike shutdown

Reply
0 prof. Dr. Spraul’s avatar

Ich denke dass der normale Shutdown 1. ist. Aber was ist 6 und was 63 ?

Reply
0 rojocomp’s avatar

Three codes not on your list, 1, 7, -20

iMini 2018 running on Mojave 14.6 on ssd drive with one usb hard drive connected

Timestamp Thread Type Activity PID TTL

2020-06-20 16:33:02.997851+0100 0xb1 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 7

2020-06-21 04:16:39.250435+0100 0xb1 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -20

2020-06-21 11:52:24.205419+0100 0xb1 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1

Reply
0 Scorpion2782’s avatar

Any solution for -128? I have been trying to understand the cause on my Mac mini 5.1 for days

Reply
0 Srini’s avatar

Timestamp Thread Type Activity PID TTL

2020-05-13 17:59:31.850258-0700 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 7

2020-05-29 05:28:16.373836-0700 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-05-30 04:06:35.849757+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 3

2020-05-30 10:11:39.474985+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 3

2020-05-30 13:28:33.419363+0530 0xc8 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-05-30 13:58:11.637817+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 3

2020-05-30 14:38:48.645261+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 7

2020-05-30 15:22:09.661184+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 3

2020-05-30 15:31:41.473628+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1

2020-05-30 19:22:26.400742+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-05-30 19:35:00.944266+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -20

2020-05-30 20:23:56.851733+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-05-30 20:55:06.132177+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-05-31 08:53:46.348060+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-06-01 10:42:04.527133+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-06-01 18:25:48.512685+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -20

2020-06-01 18:42:33.946283+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -20

2020-06-01 19:30:07.896876+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -20

2020-06-01 20:52:00.062405+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -20

2020-06-01 23:35:50.249802+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-06-02 00:31:17.226666+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -20

2020-06-02 06:31:09.558955+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5

2020-06-03 05:35:30.818116+0530 0xc9 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -20

Reply
0 G Pongo’s avatar

The “log show” command above proved causes of “5” for my MacBook Pro (15″, 2016) black screen crash. Console showed iBridge Panic and no other cause for the shutdown, however– so sometimes this command isn’t informative enough.

Reply
0 Ocie Mitchell’s avatar

The formatting on this page seems messed up to me in Chrome. The table cuts off the “Code” column and part of the “Description” column.

Reply
0 Wil E. Coyote’s avatar

How about “-30” in OS X 10.11.6? I suspect that it’s overheating (it’s a Mac Mini, and the fan has been noisy lately), but I can’t be certain.

Reply
0 Devansi’s avatar

Hi! I got -20. Any idea on this one?

Reply
0 TantrumV’s avatar

Error code 6 – Do not know what it was :/ But it was after waking up from sleep. As I opened lid, it restarted.

Reply
0 Rombout Versluijs’s avatar

that list is kinda hard to read, seems broken

Reply
0 Ben Edwards’s avatar

Mojave – late 2013 user chucking his name into this error ring.

Random shutdowns from a week ago with error -128. No hardware or software updates.

Reply
0 Sarm’s avatar

Late 2014, Catalina (although it was happening with Mojave, software upgrade was something Apple recommended).

It’s been happening to me for about a week; found this page today and yes, also error -128.

Reply
0 Danilushka’s avatar

2019 Macbook Pro 32GB DRAM MacOS Catalina 10.15.3 tried to shutdown over night (I was running a process in iTerm2 and iTerm2 prevented shutdown without user affirmation, thankfully). Command log show results showed no cause!

log show –predicate ‘eventMessage contains “Previous shutdown cause”‘ –last 24h

Filtering the log data using “composedMessage CONTAINS “Previous shutdown cause””

Skipping info and debug messages, pass –info and/or –debug to include.

Timestamp Thread Type Activity PID TTL

Log – Default: 0, Info: 0, Debug: 0, Error: 0, Fault: 0

Activity – Create: 0, Transition: 0, Actions: 0

Any known HW problems that could cause this and that would be be recorded in the logs?

Reply
0 com’s avatar

2020-03-03 01:44:07.148555+0200 0xb1 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -64

2020-03-03 17:31:08.734515+0200 0xb1 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 6

Reply
0 AndyW’s avatar

I had the same two (I’ve posted at bottom of this list too). Has yours done it again com?

Late 2014 iMac 27″ Retina, macOS 10.15.5

Timestamp Thread Type Activity PID TTL

2020-07-16 20:57:17.631524+0100 0xa7 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -64

2020-07-17 11:47:48.598533+0100 0xa7 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 6

Reply
0 Ryan’s avatar

What does -64 represent?

Reply
0 TK’s avatar

I seem to get a 7 when I check the last shutdown code after a restart command. You might want to put that in the list.

But more strangely, my 2018 Mac mini was in the middle of processing a task this morning and it shut down for no apparent reason and logged a -14. What is a -14?

Thanks for the article.

Reply
0 stephen boyle’s avatar

I have seen 7 when newer machines (T2?) are doing an update? maybe this is bridge os? i think then bridge OS gets updated the machine is shutdown and auto-powered back on after x amount of seconds.

Reply
0 Christian’s avatar

I got the shutdown cause -11. Any idea, what this means?

Reply
0 Máximo’s avatar

Me too! Did you solve it? I’m getting it a lot lately and it’s driving me crazy!

Reply
0 Someone’s avatar

Got the same problem!

Reply
0 Nath’s avatar

Has anyone seen “Previous shutdown cause: -1”?

Reply
0 Dan’s avatar

Anyone knows about -20 cause?

Reply
0 LuxoNum’s avatar

I’m having that exact issue, but I’m not sure but I think It may be a kernel panic though

Reply
0 Al’s avatar

Hi, in Catalina I have ” Previous shutdown cause: 1 “.

Never seen 1. Anyone know what it means?

Thanks

Reply
0 Karan Bansal’s avatar

Anyone knows about -59?

Reply
0 Griffin’s avatar

Getting -59 as well on 2018 MacBook Air 10.14.6. No clue. Very annoying. It happens every time i put it to sleep by closing lid. I have to power it back on manually and previous shutdown cause is -59.

Reply
0 Bilal’s avatar

I am having the same issue did you ever find out what’s going on? I have the same machine MacBook Air 2018.

Reply
0 GGSS’s avatar

I’m getting cause -40, after a bunch of -128. Don’t know what it is.

Reply
0 nev’s avatar

I’, gettimg -40, too. No-one seems to have the faintest clue what it means.

Reply
0 Alex99’s avatar

What is the shutdown code «-5» means? I’ve got code -5 instead of 5. My mac just shutting down randomly without a reason! Please help

Reply
0 Ethan Cho’s avatar

What is Cause -11 ? I have a macbook pro 2019, shutdown cause -11 happened 5 times today!

Reply
0 Maximo’s avatar

Did you ever solve this? It is happening a lot to me on my macbook air 2019, and it’s driving me crazy!

Reply
0 Vic’s avatar

I’m getting a lot of cause -20 and -11. This is on a 2018 Macbook Air. Any suggestions to these new causes? I can’t find them anywhere.

Reply
0 Maximo’s avatar

Did you ever solve this? I’m also getting a lot of -11 shutdowns!

Reply
1 Vic’s avatar

Today I got a cause: 1 also….

Reply
0 Dan’s avatar

1 comes up for me if I did a restart instead of a shutdown. But only on Mojave

Reply