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 24hCode language: JavaScript (javascript)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.
| Code | Description | Solution |
|---|---|---|
| 7 | CPU 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. |
| 6 | unknown | Have you got this error too, or any information? Leave a comment below! |
| 5 | Correct 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. |
| 3 | Hard 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. |
| 0 | Power 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. |
| -3 | Multiple 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. |
| -14 | Electricity 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. |
| -20 | BridgeOS T2-initiated shutdown. | The T2 chip in your 2018+ MacBook Pro or other Mac (list in link) initiated a shutdown. |
| -60 | Bad 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. |
| -61 | Watchdog 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. |
| -62 | Watchdog 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. |
| -63 | unknown | Some 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! |
| -64 | unknown | Have you got this error too, or any information? Leave a comment below! |
| -65 | unknown | Potentially linked to operating system issue. Try reinstalling macOS as fresh or booting from clean install on an external drive. |
| -71 | SO-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. |
| -74 | Battery 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. |
| -75 | Communication 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. |
| -78 | Incorrect 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. |
| -79 | Incorrect 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. |
| -86 | Proximity temperature exceeds limits. | Check thermal contact with heatsink, fan connection and physical/reported activity. |
| -95 | CPU 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. |
| -100 | Power 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). |
| -102 | Overvoltage | Safety shutdown related to over voltage protection (MLB or Battery). |
| -103 | Battery cell under voltage detected. | Check battery and replace with known-good. Perform one charge cycle, then try again. |
| -104 | unknown | Possibly linked to battery issue. Perform one charge cycle and try D-boot to run diagnostics. |
| -108 | unverified | Likely memory issue. Commonly occurs when RAM is full and there was an issue with paging. Can occur when the system is sleeping. |
| -112 | unverified | Memory issue. Almost always occurs around -128, another memory issue. Almost certainly hardware fault. See -128 for troubleshooting. |
| -127 | PMU forced shutdown. | Check power button on your hardware. Potentially fine if you forced shutdown, otherwise may be hardware/SMC issue. |
| -128 | unknown | Possibly 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!
Nobody seems to know what these codes mean but you. Where did you get this list?
Hello,
Nice and helping page but like other people I didn’t find the answer to my problem, any thoughts on what -11 represents? 🙂
My specs for my MacBook Pro (15-inch, 2019)
2,3 GHz 8-Core Intel Core i9 / 16 GB 2400 MHz DDR4
Catalina 10.15.7
I had similar issues. I got -11.
Any thoughts on what -64 represents?
-64 error
6 anyone?
What model of Mac and version of macOS are you having this issue on? When did the issue start?
Hello,
I have 6 too on my Macpro 2009 (Macpro4.1 patched on Macpro5,1)
I suppose it is electric leakage.
I added a cable between the Mac case and “the earth”
Let see if it is better …
Emmanuel.
I too have shutdown cause 6 (and -62) in the logs. This has been ongoing and persisted throughout different versions of Mac OS X and macOS on the same Mac Pro; different and new users accounts as well.
Current version of macOS: 10.15.7 (19H1030)
Hardware Overview:
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: 428.0.0.0.0
SMC Version (system): 2.20f18
Recent log view:
2021-05-03 06:27:25.058316-0400 0xd6 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 6
2021-05-03 17:23:18.993050-0400 0xd6 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -62
same here. a lot of it.
I’m getting a lot of -11s. Apple support said “probably hardware issue”. Thanks!
Hi all. Just wanted to mention. I was recently servicing a MacBook Pro 13″ Intel 2020 model (the one with two Thunderbolt ports) with shutdown issues after liquid damage. It was throwing specifically -11 errors. All the liquid damage in the unit, aside from inside the display, was in the Touch ID connector. And the unit would shutdown amid login. Power would stay on just fine if I unplugged the whole audio board, where the Touch ID connector is on that model. I suspect the issue is probably due to some issue with Touch ID/T2 or Power Management since that connector also carries power on off signals, though I feel like that would be more likely to be shown as a hard power off
I’m not sure -128 is RAM related… I have a Macbook Pro 13″ non-touchbar model that started suffering from this only after upgrading to Big Sur. It was on Mojave previously without problems. I have totally wiped it out and put a new install on, and even the beta of Monterey, but still it will sit for long periods fine, but if you use it the input will stop responding, very rarely it will resume working, but typically it reboots. The haptics and trackpad are not responsive when it is frozen waiting to reboot (or rarely revive itself). I have run memtest86 for extended periods of time and no RAM issues have been reported, and Apple’s Diagnostic shows everything is fine. But it clearly is not. But Mojave never had a problem on this computer. Strange.
Hello everyone I have an imac at the late 2015 32 go and I have the error -128 I noticed that the ram is 1600 MHz DDR3, do you think the problem comes from there?
I just got -11 code? Anybody knows what this means? I have a Macbook Pro 2019 that keeps shutting down with no battery when it has battery. I tried reset SMC, reset NVRAM/PRAM, update the software and nothing works, the problem still continue.
I have a -6 shutdown cause and its not on the list. I have a MacBook Air 2015 (which is about 2 years old only) and it started shutting down constantly. I then updated the system to MacOS Big Sur and then it stopped the issue for about a week. Now it has shutdown again randomly with -6. Please let me know if anyone has the solution or the possible reason that this may be happening
Hi. I am also getting -6, did you find any solution for the same?
Hey @Parag is the issue fixed ??
Got the same issue -6, did you guys got any fix for this??
If yes, Please share what you did?
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
I should also mention – no crash report or spindump was generated on these shutdowns. Just the -63 cause
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:
www.tonymacx86.com/threads/mojave-10-14-5-intel-hd630-no-resume-from-sleep.277696/page-3
Update: Apple recommended replacing the logic board
Thank you for coming back to update this thread. I guess that (sort of) links to the USB issue as it could be the USB controller or other USB hardware issue. If you hear any more about what the problem is I’d be very interested — thank you for your contributions.
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?
I got a -11 error on my MacBook Pro (15-inch, 2019).
Any thoughts on what represents?
I also received a -11.
-11 shutdown cause anyone know what has caused it??
Got a -60 on a MacBook Pro (Retina, 13-inch, Early 2015) running Mojave 10.14.6. I recently replaced my battery, maybe it’s related?
Hi, is this still happening to you? I’ve got a similar situation. Retina, 15-inch, mid-2012 running Mojave 10.14.6. Recently my computer started shutting down even when plugged into wall power and reporting -60 (BadMDBErr). I replaced both the SSD and battery about a year and half ago, and haven’t had any issues until now. Tried booting with the old drive and after a day got another -60 shutdown, so now I guess I’ll try to replace the battery. Would love to hear what you’ve tried and how it went. Haven’t found much info on this specific issue.
Hi, is this still happening to you? I’ve got a similar situation. Retina, 15-inch, mid-2012 running Mojave 10.14.6. Recently my computer started shutting down even when plugged into wall power and reporting -60 (BadMDBErr). I replaced both the SSD and battery about a year and half ago, and haven’t had any issues until now. Tried booting with the old drive and after a day got another -60 shutdown, so now I guess I’ll try to replace the battery. Would love to hear what you’ve tried and how it went. Haven’t been able to find many other posts about this specific issue.
Who knows what cause -2 means? I’ve been getting that on a late 2013 Mac Pro.
I could swear I’ve asked this on here already, but since I don’t see my question, I think I’ll just ask.
Hi Bert, yes your previous comment is here: #comment-5146
Hi Bert
Did you ever find out the issue? I have the same machine and the same -2 shutdown error and cant seem to figure out the issue?
thanks
jon
I got a -40 error from my 2011 iMac on 1 of the shutdowns
Me too I got 2 -40 errors and a couple -128
I do not see anything about -40 on here.
Great article!
Have you found the equivalent Unified Logging predicate for Apple Silicon Macs? I have found that the above predicate responds back blank on two different M1 systems.
Thank you for the article and for fielding questions.
Hello,
First time posting here but I’m having some issues with a Macbook Air 2020 (Not the M1) having some shutdowns, I have run the terminal command and it’s coming up with shutdown cause -67 and I can’t seem to find this one anywhere. Hoping someone has some guidance, Running most up to date Big Sur, (11.1). Clean installed the OS and didn’t transfer a backup over and it seems to be still happening. Also tried an SMC / NVRAM reset, Safe mode, first aid disk. Any advise would be appreciated!
Just got a code 8. Unsure of what this means.
Hi Rick, I got a code 8 too!
My macbook air started shutting down randomly after I spilled some water on it (the screen is a bit water damaged but the rest seems fine (besides the random shutdowns… so not fine I guess)).
Did anything similar happen to your mac? Have you managed to solve it?
I just updated to big sur and haven’t had any issues so far (but we’ll see).
I got a -2 on my Macbook Air mid-2012. It is not listed in here. What could it be? Please answer
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?
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!
me too! I also have a MacBook Air 2015 and have -6 shutdown cause. please let me know if you figured out the issue.
Hi Gaurav, how did you fix the issue??
cause: 1 appears to be the result of “sudo shutdown -r now”
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?
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.
Correction: Alt+Cmd+Shift+Esc to kill the processes.
And apologies for typos in my initial note.
I am consistently getting the -128 error on a mid-2014 MBP (non-removable RAM). Any thoughts/suggestions on how to diagnose?
Thanks!
-128 is most common with failing memory. So in your case you would need a logic board replacement since the memory is on board.
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
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
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
Same problem here. Good note on how it started happening after updating to catalina. Looks like we have an issue with the update. I’m going to try big sur.
Did updating to big sur solve the issue for you?
Do you shut down your computer every night? Try doing that and see if the issue persists
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.
Correction: Alt+Cmd+Shift+Esc to kill the processes.
And apologies for typos in my initial note.
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.
I started to get the -128 issue on a fresh install of Catalina, too.
Same here, same machine. I think this could be fixed via software.
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.
Same here, same machine.
Hey, did u solve the issue? this recently happened to me and ive tried everything with no luck. Appreciate your answer
Hi all, recently I’ve got issue with random shutdown, code -128 (MacBook pro Retina 15” mid 2014 model 1398). SD has happened from time to time, depending on different actions, for instance during chrome open or video creator opening etc. So during some period of troubleshooting I’ve tested many ways to find out the problem. Replaced thermo grease on the cooler, reinstalled mac os down to previous catalina or majavi , also have tried to start from external ssd with installed os, but nothing was helped. This effect has probably happened from high temperature of CPU or graphics processing unit GPU, due to the cooling system downgrade for some reason.
It was found by Macfancontrol app that temperature increased on CPU and GPU up to 80 – 90 degrees C. and then SD. Cooling bus was manually tested on the ends during machine working and it was looking good but apparently not and then I decided to set max temp on both fans 50 deg C.
Finally I don’t have any SD anymore, but both fans are working at high speed al the time 4000 rpm -5000 rpm. I’ve tested machine as far as I can but still not any issues:)
So in my case the conclusion that the cooling bus is not working as should be. Thanks
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.
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.
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!
same problem here
See my comment of troubleshooting above
ia have a -102
any ideas?
What is Cause -11 ? I have a macbook pro 2019, shutdown cause -11 happened 5 times today!
Did you ever solve this? It is happening a lot to me on my macbook air 2019, and it’s driving me crazy!
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!
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?
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
I’ve been getting the same one (-20) on a 2019 16″ MBP.
The cursed T2 chip produces BridgeOS induced kernel panics with code -20. Every few days without fail, sometimes more often.
Yes me too with MacBookk Air 2019 and a -20 code. Just happened twice in 15 mins. Anyone know a fix?
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.
I am getting the error on my Mac mini 2018.
My 2018 Mac mini was also having this problem with Monterey 12.1 and it turns out the update to 12.2.1 (which the m/c didn’t tell me about) fixes it!
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.
What versions of macOS are you using?
10.12 – are the two machines that seem to do 0 and 3 or normal restart (limited testing). 10.10 was the one returning 3 as well on a restart (although it is a vm). i need to do a wider test… just didnt know what others see…
Okay so I get repeated -63 on 2018 Mbp.
Getting the -63 too. Any help on what this issue can be would be awesome.
Also getting repeated -63 on 2018 – any tips would be helpful
Could be T2-related kernel panics. Check kernel logs to confirm.
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.
I’m getting repeated -63 on a Mac Pro cylinder that was previously stable but is now rebooting daily.
Timestamp Thread Type Activity PID TTL
2022-11-27 17:52:36.870397-0700 0xd2 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -63
2022-11-28 18:08:29.840169+0000 0xd2 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -63
2022-11-28 11:10:52.950670-0700 0xd2 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -63
—————————————————————————-
Any ideas for this one: “Previous shutdown cause: -11”
For others reference, I got a “Previous shutdown cause: 8” when resetting the SMC while the macbook was booting up.
I got 8 on a 2019 MacBook air, anyone know what that means?
I got 8 on a macbook air, anyone know what that means?
I just noticed that on the day that I upgraded my Mac from 11.6 to 11.7, there were two shutdowns (the system restarted a few times during the upgrade).
I have code 1 at the start of the upgrade. I think that is from clicking the “Reset” button from the software update dialog.
Then a few hours later (toward the end of the upgrade), there is a code 7. I don’t think this is an error condition. I think it is more likely to be the software-initiated restart after the upgrade completed.
I’ve been having my Mac shutdown overnight in sleep mode pretty much every day recently, most of which had code 5 (although I neither triggered it nor had a shutdown schedule), but now I found that I have a code -20 (which makes sense because I have a T2 chip Mac, but I don’t know why it happened) and a code 1 (which isn’t on the list) happen yesterday. Code 1 is likely the MacOS Ventura Beta upgrade (so you can add that to the list), but that leaves the other -20 one. The code 5 shutdown still happened last night (after the upgrade). Any tips?
-11 = power button was held down for greater than 8 seconds while the machine was already powered down.
Mine is gettting a “previous shutdown cause” of -2
I have gotten -128 a few times. It seems to happen more frequently when installing something. I received the computer with the issue and it did not have an operating system. after several attempts to install, it would always shut down and not be able to finish. I thought it may be temperature related, so I put it in the freezer to update. Then I became concerned of condensation, so I took it out, but it had gotten further than ever before! I put some ice in a plastic bag and alternated putting the computer on the bag and on the table so that it would not get too cold or too hot. By doing this I was finally able to finish the install which was mountain lion. I then tried to upgrade to yosimite, but ran into the same issues. Then using the ice technique, I was able to update, and then I tried to update to high sierra without the ice, and I had one shutdown, but it was able to complete. I actually wasn’t able to run the command until I got to high sierra, but I am guessing it was the same issue before.
We’ve had a case with multiple “-20″codes – but the T2 settings were already disabled!! Can the T2 chip still issue shutdowns/reboots?
Mac Pro 7,1, Catalina
I also get this -20 shutdown cause which happens every 2nd day. I need more info as to why the T2 told the machine to shut down. I have 2x thunderbolt 4 docks using their own bus per dock, studio display so another thunderbolt device also using its own bus. Internally I have 2x WD Black AC1500 SSDs in slots 6 and 7 running at 8x each. I have manually set my bandwidth in the PCIe Lane assignment. Pool A is 100% with both the WD Blacks. If I have on auto it runs pool A at 50% and B at 100% with half of B dedicated to thunderbolt lanes. If I plug in another thunder device on different bus B goes 125-150% some times. It never puts the WD AIC into pool A. Driving me nuts. Also have 2 SATA SSDs in the 2 SATA ports inside and iLok USB key in the USB port inside. I don’t know if I’m using way too much bandwidth with the thunderbolt devices. I have the W5700 Pro Gpu so I might try one of the WD AICs in slot 3 which is dedicated 16x lanes to cpu. I can’t remember if this issue happened before I installed the second WD card or not. Cheers, Adam P.
My last 96 hr report from terminal:
Timestamp Thread Type Activity PID TTL
2022-10-10 18:45:43.685440+1100 0x122 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5
2022-10-10 19:37:52.696620+1100 0x122 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 3
2022-10-12 18:02:32.525260+1100 0x122 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5
2022-10-12 19:33:23.526366+1100 0x122 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -20
-63 here … I have a 2013 Dustbin with an LG 27MD5KL display attached. Spotted on here that someone suggested that no HDMI connection might indicate a problem so trying that after trying pretty much every suggestion on here … I’ll update if anything gets fixed.
Hello
random but persistent -63 on 2013 dustbin seems more prevalent if i leave tabs open
Since upgraded to macOS 12.3 we see -63. Only with iMac 27″ 8 core i7. All 10 iMacs have these shutdowns, a variety of mostly -20 and as mentioned more and more -63
Maybe the 12.3->12.3.1 Update has fixed it: Problems with USB-C attached Displays
for anyone with a Mid-2014 Retina MacBook Pro randomly powering down with code -128: all of the solutions to disable various Thunderbolt devices did not work for me (Big Sur 11.6.5). though they never worked at all, even going back as far as 10.13.
what worked was a simple $5 HDMI dummy load from Amazon. sounds ridiculous but any of them should work, just pick whatever one is cheapest/best reviews/arrives soonest. no working theory on why this works, other than it might be keeping a software process busy which otherwise causes the crash with. as soon as I plugged it in, all the crashes stopped. computer works like it is brand new with a fresh OS install. kind of annoying to have a little dongle hang off the HDMI slot, but it’s a price worth paying to have the machine work reliably. if disabling the Thunderbolt device kext did not work for you, try this.
on a related note, i doubt code -128 is RAM related. the Windows partition on my laptop never randomly shuts down, and all memory testing i have done exposes no issues at all. likely the shutdown code is a signed 8-bit integer, -128 is the lowest possible value. i would wager that it just means an unknown reason. what could cause the OS to not be aware of what caused a shutdown, I don’t know, but it would most likely be a sudden loss of voltage (I think some people theorize random shutdowns with -128 are due to a faulty FDMF 6808 CPU mosfets, which would support this theory)
just dropping some extra information here since others have asked if this is battery-related. the macbook i am using has the original battery, 1,628 load cycles and 63% of the original capacity. in other words, this battery is extremely worn out. yet, the HDMI dummy plug fixes the problem. so i would try HDMI dummy plug before replacing your battery…
today Macbook air shut down unexpectedly. I was on a whatsapp call, the battery was 80%, unplugged. Mac shut down suddenly and it felt like an electric shock. It made the same noise is if it was plugged (but it wasn’t).
What could have this been?
Hello, and thanks for posting this. What does shutdown cause “-5” mean, please?
Any idea about code 1? Happened during maOS 12.2->12.3 update
On macOS 12.3 I see this value which isn’t on the list…
Previous shutdown cause: 1
experimenting to help someone
Shut down normally
got “kernel (AppleSMC) Previous Shutdown cause: 5”
held down power button until machine powered off
got “kernel (AppleSMC) Previous Shutdown cause: -11”
on MacBook Air (retina, 13 inch, 2018) running Big Sur 11.6.3
I have had my logic board replaced after Apple accepted that a large number of restarts with a -20 result. Then getting the computer back the restarts happening again. It happened whilst in Apple’s possession. I am starting to get quite disappointed.
Hi, has anyone been able to report what -2 indicates? I have a 2008 Mac Pro which has now become unusable because it shuts down randomly. Another symptom is that the power LED remains lit, even after shutdown. Any help would be much appreciated. Thanks.
I have the -63 error
Anyone know what -8 represents for previous shutdown cause?
I got -11 and the list doesn’t show that… could you tell me what it might be?
2022-01-24 09:09:00.640286-0500 0xd1 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -2
mac pro late 2013, monterey 12.2
Timestamp Thread Type Activity PID TTL
2022-02-07 13:09:27.681973+0300 0xd2 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -63
2022-02-08 12:13:41.722147+0300 0xd1 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5
2022-02-08 12:31:12.653234+0300 0xd1 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 3
Thanks very much for this invaluable resource. Great work!
Any more information about the -20 fault. Called Apple and the telephone support person hung up on me when I told him that I have logged the forced shutdowns and found the error code.
MacBook Pro 2019 16″, been getting -63 for the last 2 weeks. At some points it would keep making the reboot sound but not actually restart, needing the alt-cmd-shift-power reset.
Took it to Mac and they don’t know what is going on either. Their solution was to wipe my computer to a factory reset which failed, so now they’re ordering a new logic board in.
Hello,
error 6 here, te terminal shows this output:
kernel: (AppleSMC) Previous shutdown cause: 6
what is the solution for -81
I get the -128 shutdown, can replace my ram, any idea of what is needed to do?
If I push the power button on the back of my 2018 Mac Mini and hold it until it shuts down I randomly get either the shutdown cause of -11 or 3.
Late 2009 MacBook Pro, El Capitan
I get 6 (unknown) very frequently. It seems to be temperature-dependent, and occurs less frequently when the machine is hot or being kept busy. It occurs whatever software I am running. I have no reason to suspect a corrupted operating system, disk or memory problems.
What does “Previous shutdown cause: 1” indicate? I can’t find that one anywhere. macOS 10.15.7.
-11?
I have shutdown cause -2! I have run Apple Diagnosis Test and it says I have no hardware problem, even though my Mac randomly shuts off! Can you help?
Hi,
I have a Mac Pro (late 2013) Intel Xeon 12 core 2.7ghz. I have the following shutdown cause (not listed), can u help me?
2021-08-25 13:54:50.157871-0700 0xf4 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -2
2021-08-25 18:07:17.210510-0300 0xf4 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -2
2021-08-25 18:15:52.169876-0300 0xf4 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -2
2021-08-25 18:28:16.149385-0300 0xf4 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -2
2021-08-25 21:01:34.122175-0300 0xf4 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -2
2021-08-26 04:09:22.149923-0300 0xf4 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 0
Just got this one:
2021-07-29 07:48:42.262496-0600 0xc4 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1
my Mac button is stuck (issue 3) and I have issue -60(bad master directory block) can u pls help
lastDskErr = -64, /I/O System Errors/
noDriveErr = -64, /drive not installed/
You never saw me here.
These are part of Carbon Core enumerations, very old. Are they relevant as shutdown cause codes?
I have been having random shutdowns on my iMac20,2 running Mac OS 11.4
Apple just replaced my logic board for the issue. I got it home last night and have had the issue persist. Received shutdown cause 7, 1, -20, and another -20.
Have you found any solution with the new logic board?
I have a MacBookPro15,4 running macOS 10.15.7. In the last month, I keep having kernel errors with irregular shutdowns with the cause -20. It even happens in safe mode. It most of the time happens when I turn off the display with hot corner and then close the lid.
My last solution before contacting Apple engineers is to re-install MacOS.
It only happens to my computer when the displays are in sleep mode
I’ve got a code -63 on a MacPro (2013). Couln’t figure out what was the cause.
-5 Shutdown Cause
ok
I too have shutdown cause 6 (and -62) in the logs. This has been ongoing and persisted throughout different versions of Mac OS X and macOS on the same Mac Pro; different and new users accounts as well.
Current version of macOS: 10.15.7 (19H1030)
Hardware Overview:
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: 428.0.0.0.0
SMC Version (system): 2.20f18
Recent log view:
2021-05-03 06:27:25.058316-0400 0xd6 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 6
2021-05-03 17:23:18.993050-0400 0xd6 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -62
Hi,
I have Apple PowerPC G4 QS and have another error code I would love to know the value of:
localhost kernel[0]: ApplePMU::PMU forced shutdown, cause = -122
Many thanks,
Anton
All of the sudden my machine started to behave differently.
I get error -60 in my macbook air 2015.
Machine is being shut down and starting again.
Firstly upgraded software then cleaned whole mac re-uploaded IOS. Still same problem happing.
Hi, I am getting shutdown cause as 8 and -11, any idea what those are
Any idea on -82 please?
Hi, I’ve got -82 error from my MacBook air mid-2013 after finally using it after almost 6 months.
i have a code o, code 1 code 9
MacBook Pro (16-inch, 2019)
why do i sometimes get 16 or 12 and it not even on here
What model of Mac? What version of macOS? What are you doing when the issue occurs?
I get 0 on my MacBook Air 2017 I checked the cycles and it s about 250 I don’t think that’s bad ,should I replace the battery resetting smc doesnt work
Has anyone ever got -2? I’ve got any old mac mini that randomly shut off without warning. Pretty sure it’s not a temperature issue but who knows one of the sensors could be bad.
I have received -63 7 and 1 — I have a screenshot if needed of crash report. I have not been able to read report when it happens, it just goes away. I am not sure if Duck Duck Go has something to do with it because it has reverted back to Yahoo as my primary browser. These crashes do not happen at startup. Computer has been on awhile and then just crashes. New Macbook Pro only a week old. Used migration assistant from old Macbook Pro (2014) and upgraded to big sur.
I’m seeing a lot of 0 codes being assigned to user initiated reboots in a Mac Pro 3,1 running a patched version of Catalina. Not sure if this is because the OS is running on an unsupported system, or if it’s a hardware issue. Anyone else with an MP3,1 getting a 0 instead of a 5 for reboots/shutdowns?
Hi George,
I have a late-2013 Mac Pro that keeps restarting. I checked the log using the instruction you provided and found this:
Thread: 0xd2
Type: Default
Activity: 0x0
PID and TTL: 0
kernel: (AppleSMC) Previous shutdown cause: -2
The cause -2 is not listed in the above table. Could we still find out what it means?
For -128, I run Apple diagnosis and it tells me the battery is at fault but I recently changed that. Called them up and the guy on the phone says that if the diagnosis tell you it’s a battery issue then it’s a battery issue but I am not convinced. Will update if I get that addressed.
Got A MACbook pro 13″ 2019 (Catalina 10.15.7) which randomly reboots with
localhost kernel[0]: (AppleSMC) Previous shutdown cause: 6
and
localhost kernel[0]: (AppleSMC) Previous shutdown cause: -63
in the previous shutdown cause log.
it might be linked to the google drive synch app and spotlight. has anyone any info on these two error codes.
I have got error -6, what that’s mean
what I have to do to avoid unexpected shut down of my Mac
Hi. I am also getting -6, did you find any solution for the same?
Hi Amar, I’m also having -6 error. how did you fix the issue??
Please share what you did.
receiving -63
Late 2013 – MBP 15″
Random Shutdown and after running the aforementioned code give -128 error. I tried resting SMC, NVRAM and also as apple diagnostics suggested – replaced WiFi card (I did DIY for $40 – they were asking $260) – after replacing the card – in 40-45 minutes again this randomly shutdown – Black screen>Keyboard light shuts off in 4-5 seconds and shutdown.
Also ran Apple Diagnostic using “Power on and D Key (Intel processor)” – No hardware issue – ADP000. Just want to try everything before I give up.
Is it Motherboard/Logic Board RAM issue?
Thanks!
I got code 8 after spilling water on my macbook air, don’t know if it’s related but probably is rip. Anyone know the meaning?
I keep getting this. My macbook pro 2020 has been shuting down randomly ever since i got it
I have got error -6, what does mean?
me too! Please let me know if you figure out the issue.
same here, please let me know if any solution you guys have!
Hi Amarjeet, same error for me. can you please share what you did to fix the issue??
error -11 on Mac book pro 15″ – Year 2018 with T2 Chip,
AND ERROR – 14 , What to do for random shut down
-67 previous shutdown reason?
Hi Paul, I’ve not heard of that one before. What happened when you got that shutdown? What’s your Mac model and specs? Thanks
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
me too, someone help, please
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.
I got -128 and -5 reading what should I do now
what does -11 indicate and I am using macbook pro 2020
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 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$
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???
please give more information on -128 code I am facing serious problems in my MacBook Pro 15 inch retina
What problems, what happens when you get this shutdown? What year MacBook do you have?
I have the same problem …mine is MacBook Air 2015
my readings are 5, -128 and -5 ….what to do help me out
Me too, someone please help. I have the exact same MacBook.
did you find any fix for this? I have a -128 and -5 error too with my macbook pro 2017 13 inch
I got cause “1”. What is that?
I also got code 1. Those shutdowns occured while my mac was updating operating system. Were you doing something similar?
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.
My MBP 2019 showed many Previous shutdown cause: -20, when running Grapher. Why?
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
Hi ACloseShave,
Were you able to identify what the code 1 means ?
Regards,
Killian
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.
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.
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
Does anyone know what -59 means?
I get a -113 while my MacBook Pro retina mid-2012 sleeps. Works fine however when it wakes up. Any clue?
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.
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
Hi George – I keep getting a -20 shutdown cause. What does that mean? My MacBook Air keeps crashing with no warning… Thanks 🙂
What year was your MacBook Air made?
Hey, I got a -1 as a result. Can you please tell what is it?
-14 on Catalina/Mac Pro : electricity surge or spike shutdown
Great, do you have a source for this?
Ich denke dass der normale Shutdown 1. ist. Aber was ist 6 und was 63 ?
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
Any solution for -128? I have been trying to understand the cause on my Mac mini 5.1 for days
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
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.
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.
Thanks,
I’ll get that fixed ASAPFixed!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.
I am seeing this on an Early 2019 Mac Mini with OS X 10.11.6, overheating seems likely in my case as well. I had a noisy fan but it’s quieted down, though I’m not sure if that’s because it has failed outright…
Hi! I got -20. Any idea on this one?
Error code 6 – Do not know what it was :/ But it was after waking up from sleep. As I opened lid, it restarted.
that list is kinda hard to read, seems broken
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.
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.
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?
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
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
What does -64 represent?
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.
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.
I got the shutdown cause -11. Any idea, what this means?
Me too! Did you solve it? I’m getting it a lot lately and it’s driving me crazy!
Got the same problem!
Has anyone seen “Previous shutdown cause: -1”?
Anyone knows about -20 cause?
I’m having that exact issue, but I’m not sure but I think It may be a kernel panic though
Why do you think this? This might help narrow down the issue.
I got a restart with -20 as the reason. in the log for the crash, I see
“macOSOtherString” : “\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 1230304 **\n”,
“macOSPanicFlags” : “0x4”,
“macOSPanicString” : “panic(cpu 4 caller 0xffffff800384aa3a)
And the log is named “panic-full-.ips”
Hi, in Catalina I have ” Previous shutdown cause: 1 “.
Never seen 1. Anyone know what it means?
Thanks
Anyone knows about -59?
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.
I am having the same issue did you ever find out what’s going on? I have the same machine MacBook Air 2018.
I’m getting cause -40, after a bunch of -128. Don’t know what it is.
I’, gettimg -40, too. No-one seems to have the faintest clue what it means.
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
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.
Did you ever solve this? I’m also getting a lot of -11 shutdowns!
Today I got a cause: 1 also….
1 comes up for me if I did a restart instead of a shutdown. But only on Mojave
Hello George: I am often getting Previous shutdown cause: 0 even though i shut down my iMac properly from the apple menu. can you please tell why does it occur