MacBook Pro shuts down randomly

Hi,


I have a late 2013 Macbook Pro, Retina, with a decent spec (all specs below).


Recently (in the last 2-3 weeks), even though all my software is all up to date, the machine will randomly freeze for 10 seconds, and then shut down (power off).


I have to power it up to bring it back up, which it does with no problems. There's nothing in the logs that's consistent, nothing that indicates a crash or error. Recent changes to preferences or disk may be missing too, like startup choices, when it comes back. I will say it seems to occur more often with high CPU. Recently installed something to monitor temperatures, and the CPU cores do seem to get warm and the fans kick in (Temperature Gauge 4.1). There doesn't seem to be super high temps when it occurs, but usually there's been high CPU sometime before the crash. I've had this happen with the machine plugged into power, or on battery, and even when it's not really doing a lot (so CPU not high), and when fans have been low, slow, running, and fast.


Here's what I've done to try to resolve the issue:


  1. Reset the SMC and PRAM.
  2. Booted into Safe Mode, then restarted.
  3. Done a HW diagnostic myself (no issues).
  4. Taken it to the Genius bar - no issues with the diagnostic(s) there, including an all day run (still have Applecare extended).
  5. Had the top case replaced because the Touchpad was on the fritz - this means there's a new battery installed recently (the restarts happened before this, and since this).
  6. Run the machine as a different user entirely, with a new profile.
  7. Run the machine from an SD card, which I installed OSX on. I didn't run any of my already installed software except a couple of items, including Minecraft just to ramp some CPU. Played for ages, quit, and opened something I never really run, and boom. Shutdown.


To me, this means it's not a software issue, as I wasn't running anything except a freshly installed OS, pretty much. None of these things has made a blind bit of difference. Still experiencing this.


I would appreciate any help or advice on this, I've no idea where to go next. This is my main machine and I use it for my business, so this is becoming a huge problem for me. I'm going to try Apple again, but I'm hoping someone can suggest something. Thanks in advance, and thanks for reading,


John


Full specs:

MacBook Pro (Retina, 15-inch, Late 2013)

Processor: 2.6 GHz Intel Core i7

Memory: 16 GB 1600 MHz DDR3

Graphics: Intel Iris Pro 1536 MB

Number of Processors: 1

Total Number of Cores: 4

L2 Cache (per Core): 256 KB

L3 Cache: 6 MB

Boot ROM Version: MBP112.0138.B16

Running OS X El Capitan, version 10.11.3 (15D21)

Macbook Pro 15"

Posted on Feb 16, 2016 12:37 AM

Reply
14 replies

Apr 4, 2017 4:05 AM in response to voidstring

Hi John


I have exactly the same machine, exactly the same problem and I solved it by not listening to the advice which Apple support gave me.


I'm very cynical about Apple because they're in the business of making money for their shareholders, so it's in their interests if their computers suddenly stop working after a few years forcing people to buy new ones.


I was pulling my hair out by the roots and spent ages working out what was wrong, but my Macbook now works well, with no random shutdowns and with the only expense being a tube of Arctic Silver thermal compound and a Penta Screw driver set ~ $40 all up.


The problem is a cooling issue and is very widespread in Macbooks, both pro and air. What happens is that Apple use a Thermal compound on the heatsink which connects to the CPU and GPU.


Good work trying to diagnose the problem, I did the same stuff as you and the key here is looking in the Diagnostic logs for a "Cause -128" shutdown command. If you do a search in the diagnostic logs after the machine randomly shut s down, I'm guessing you'll find a -128 shutdown. This indicates a Hardware shutdown not a software shutdown which is a "Cause 5". If you see a "Cause 3", that's a power button shutdown.


On mine I found a Cause-128 and knew the problem was harware related. I had two different random shutdown modes. The first and most common, was that the computer wouldn't completely shut down, but the screen would go dark grey and the computer would stay on but be totally unresponsive to mouse or keyboard commands. I usually then held the power button down to turn it off and rebooted.


One thing I noticed is that this problem got worse over time and the random shutdowns became more and more frequent during each session, to the point where I would just get to the login screen and it would shut down.


The second shutdown mode was that the computer just turned off.


The other thing I found was that when you boot up into SAFE mode, the random shutdowns disappear. Apple told me this was probably because of a bad 3rd party driver. This was not the case as I'm very careful about what I put on the computer and I did reinstall OSX from scratch after finding my hard drive had corrupted files on it as well.


What I eventually worked out after extensively testing the RAM and SSD was that the hardware was fine. The reason for the file corruption was the sudden shutdown at the moment something was being written to disk. Again supporting the hardware shutdown cause.


So once I worked out it was a hardware error then I tried to figure out what it was, by running every diagnostic test I could lay my hands on, including the ones you tried. All to no avail, everything checked out fine.


The lightbulb turned on one day as I went out and had left the Mac on. I came home and the part of the aluminium case near the back of the Macbook nearest the screen was really hot, and the fans were going flat out and making a **** of a noise. The computer of course had gone into shut down mode 1, where the screen went dark grey but it was still on. The fans were the key to diagnosing the fault because even though you mentioned running minecraft, which I did too 😉 to test performance, for some reason it did not necessarily break the computer.


What I did then was to pull the Macbook apart and pull off the heatsink and like a good detective story I founf that all of the Thermal compound which Apple used on the heatsink had turned to dust !!! So


So I cleaned it all off carefully with alcohol ( use isopropyl) and I got a small tube of Arctic Silver heatsink thermal compound. I put a drop on the GPU and one on the CPU and bolted down the heatsink again.


Prior to putting the heatsink compound on I cleaned out the fans and heatsink fins under the fans with compressed air, being careful not to let the fans rotate when I forced air through the blades so as not to blow up the motherboard with reverse voltage generated by spinning the fans.


Once back together, I tested the Mac with every manner of computer game I could find and no problems. Not one more random shutdown. Until a few weeks later.


It seems that some permanent damage had occured to the CPU / GPU because of the constant overheating. Apparently the internal components electrical resistance increases slightly with time, resulting in ilder CPUs generating more heat than new ones. The cooling system on Macbooks is very minimalist to put it mildly and I think what happens is over time, it has insufficient capacity to effectively cool the Mac down.


What I eventually did is anstall a fan controller called Mac Fan Control and set it to start on boot up. I set the trigger temperature at about 33 degrees celsius, so that the fans turn on above that temperature. I found that on boot up, the fans speed up really fast. They then slow down but always make a tiny bit of noise.


since I put the fan controller app on, I have had no more shutdowns and I have run the machine for 2 months, every day with no issues. So it's fixed !!


To get into your macbook, you'll need a Penta screw driver set, with a penta head ( 5 star instead of the older 6 star Torque screws used on pre 2012 Macbooks) Computer shops will have both the penta set and arctic silver paste.


There are videos on youtube which show how to do all this in great detail. I hope this helps you solve your problems with your Mac.


Apple's solution by the way was idiotic and involved deleting cache files, which I do every week as part of normal maintenance. They offered no other solution other than spending an obscene amount of money to replace the Motherboard and Battery, which were not to blame.


Cheers

Theo

Jun 6, 2017 5:49 PM in response to John Galt

Hello John,


I have had same issue with my MacBook Pro (2010) and followed your instructions to check the Console app to get more information. Below is the read out provided:


Jun 6 09:02:44 Paulas-MBP-2014 GoogleSoftwareUpdateDaemon[2131]: 2017-06-06 09:02:44.427 GoogleSoftwareUpdateDaemon[2131/0x7fffd25043c0] [lvl=2] -[KeystoneDaemon main] GoogleSoftwareUpdateDaemon inactive, shutdown.

Jun 6 14:16:39 Paulas-MBP-2014 GoogleSoftwareUpdateDaemon[464]: 2017-06-06 14:16:39.456 GoogleSoftwareUpdateDaemon[464/0x7fffa21253c0] [lvl=2] -[KeystoneDaemon main] GoogleSoftwareUpdateDaemon inactive, shutdown.


Would you please give me insight as to what to do please?


Paula

Feb 16, 2016 5:08 AM in response to voidstring

To me, this means it's not a software issue,

That's almost certainly correct.


Wait until the Mac shuts down unexpectedly, then examine your system.log file to identify the numeric code associated with the shutdown. Read below.


Find the Console app - it is in your Utilities folder and looks like this


User uploaded file


You can find it by selecting Utilities from the Finder's Go menu.


Open Console.


If the log list column on the left is not already displayed, show the log list by selecting Show Log List from Console's View menu.


Locate system.log in the list and select it. Many date and time-stamped entries will appear, hundreds of them, and you must find the entries relevant to your Mac's problem.


To do that type the words shutdown cause in the Filter field at the upper right of the Console window.


That will cause all log entries to be hidden, except for the entries containing those words. There will be a numeric code associated with the log entry starting with "Previous shutdown cause". What is that code?

Feb 16, 2016 5:18 AM in response to John Galt

Thanks John, I'd been looking to see if anything was logged, I didn't know about this among all the noise in the console. Not sure why the Geniuses at the store didn't check this.


It looks like here are all my previous shutdown messages (greped from system.log files). The one that's occurring after an unexpected shutdown (I check the one I remembered from last night) is -128. I found an outdated apple article that states that this is caused by Menu Manager Errors:

-128 userCanceledErr User canceled an operation

I found this here, and the article states it's not up to date (most of the reasons below are missing): Mac OS System Error Codes: 0 to -261 - Apple Support

I would appreciate any suggestions as to what might cause this or what to do next! At least I have something to go back to Apple with. I'll also reboot shortly into my SD card OS and see if the log file contains the same shutdown cause, although as I rebooted into my HD instance after my crash, I'm guessing it's one of these errors anyhow, but as I interrupted startup to change boot disks, I might have lost that information.

Here's the complete grep of the errors:

system.log.0:Feb 16 03:17:28 localhost kernel[0]: Previous shutdown cause: -128

system.log.0:Feb 16 03:06:29 localhost kernel[0]: Previous shutdown cause: -128

system.log.10:Dec 31 19:00:06 localhost kernel[0]: Previous shutdown cause: 0

system.log.12:Feb 11 14:37:40 localhost kernel[0]: Previous shutdown cause: -128

system.log.12:Feb 11 15:24:47 MacBook-Pro kernel[0]: Previous shutdown cause: 3

system.log.14:Feb 10 13:06:48 localhost kernel[0]: Previous shutdown cause: 3

system.log.14:Feb 10 15:45:53 localhost kernel[0]: Previous shutdown cause: -128

system.log.14:Feb 10 16:28:01 localhost kernel[0]: Previous shutdown cause: -128

system.log.14:Feb 11 00:40:01 localhost kernel[0]: Previous shutdown cause: -128

system.log.15:Dec 31 19:00:05 localhost kernel[0]: Previous shutdown cause: 0

system.log.17:Feb 9 21:59:51 MacBook-Pro kernel[0]: Previous shutdown cause: -128

system.log.18:Feb 9 09:23:00 MacBook-Pro kernel[0]: Previous shutdown cause: -128

system.log.18:Feb 9 09:32:14 localhost kernel[0]: Previous shutdown cause: -128

system.log.18:Feb 9 09:38:48 localhost kernel[0]: Previous shutdown cause: -128

system.log.18:Feb 9 11:04:24 localhost kernel[0]: Previous shutdown cause: -128

system.log.19:Feb 8 18:55:59 localhost kernel[0]: Previous shutdown cause: -128

system.log.2:Feb 15 21:14:58 MacBook-Pro kernel[0]: Previous shutdown cause: 5

system.log.2:Feb 15 22:18:43 MacBook-Pro kernel[0]: Previous shutdown cause: -128

system.log.4:Feb 15 15:21:23 localhost kernel[0]: Previous shutdown cause: -128

system.log.4:Feb 15 16:44:48 localhost kernel[0]: Previous shutdown cause: -128

system.log.4:Feb 15 17:43:31 localhost kernel[0]: Previous shutdown cause: -128

system.log.4:Feb 15 19:21:20 localhost kernel[0]: Previous shutdown cause: -128

system.log.4:Feb 15 19:31:48 localhost kernel[0]: Previous shutdown cause: -128

system.log.6:Feb 14 01:08:20 MacBook-Pro kernel[0]: Previous shutdown cause: -128

system.log.6:Feb 14 09:47:35 localhost kernel[0]: Previous shutdown cause: -128

system.log.8:Feb 13 22:17:34 localhost kernel[0]: Previous shutdown cause: 5

system.log.8:Feb 13 22:20:34 MacBook-Pro kernel[0]: Previous shutdown cause: 5

system.log.8:Feb 13 22:20:56 localhost kernel[0]: Previous shutdown cause: 5

system.log.8:Feb 13 22:21:47 localhost kernel[0]: Previous shutdown cause: 0

system.log.9:Feb 12 13:09:46 MacBook-Pro kernel[0]: Previous shutdown cause: 5

system.log.9:Feb 12 16:59:49 localhost kernel[0]: Previous shutdown cause: 5

system.log.9:Feb 12 17:07:14 localhost kernel[0]: Previous shutdown cause: 3

system.log.9:Feb 13 11:54:13 localhost kernel[0]: Previous shutdown cause: 5

system.log.9:Feb 13 17:38:20 localhost kernel[0]: Previous shutdown cause: 3

system.log.9:Feb 13 22:00:11 localhost kernel[0]: Previous shutdown cause: -104


Thanks again and best regards.

Feb 16, 2016 8:56 AM in response to voidstring

While not publicly documented, negative shutdown codes are generally understood to indicate faulty hardware. One possible exception to that might be -128, which I have seen logged subsequent to a firmware update. However, your log indicates multiple instances of that code as well as -104.


That seems to confirm what you already know - a hardware fault is likely, and is not something that can be fixed with software.


Providing those codes to Apple might be helpful for them isolate the cause, and as you wrote the Geniuses should have done that already.

Mar 8, 2016 10:54 PM in response to voidstring

For what it's worth, I thought I would post the outcome to this problem. Thank you again, @John Galt for your help in getting me information to resolve this.


After much back and forth with AppleCare support, and after time machine backing up to a conveniently spare 1TB HD I had available ( ! ), I headed back to the extremely helpful Fairview mall Apple Store (trip 3). I'd already had my top case (keyboard, battery and touchpad - one unit) replaced, and my screen for another issue (dead pixel), all under support. I had now convinced Apple Support and the store that this was a HW issue thanks to the above logs. They also have an apparent policy to replace computers at no charge after three trips and HW replacements under the same issue. This wasn't quite that scenario, but the amazing folks at the store rallied to rush a motherboard, memory, and chip change through for me. Apart from me HD, this is almost completely a new machine now. They got it done extra quickly, realizing my frustration and impact to my job. They were quick, and helpful, getting the part collected from another store through an employee who lived nearby.


Every since then: no issues. The shutdown problem has gone away entirely (well, I have an OSX panic and crash, but that was just a software problem it seems). No more -128.


So all in all, very pleased to have all this resolved, and must again praise the value of AppleCare extended warranty. Over $2K CAD of new parts, labour, and all the additional phone support that would have cost, no charge to me. Thanks, Apple.

Oct 8, 2016 8:50 AM in response to voidstring

I have this exact issue. It appeared after a repair from Apple, they replaced practically everything, then this issue appeared so they replaced the logic board for a 2nd time. The senior advisors and engineers are telling me it's a software issue. I only get the "-128" error message so far. Do you have an Apple case number that I can point Apple to as our situations sound very similar.


Thanks

Alan

Dec 7, 2016 3:13 PM in response to voidstring

Hey Voidstring!


I have exactly the same issue. I purchased my second Macbook Pro, late 2013 Retina 15" two years ago. Since I've purchased it, it's only worked without issue for a year. Basically, the machine shuts down randomly every 3-10 minutes. The screen will flicker (almost like it's electrically shorting out) for 5-10 seconds, then the machine shuts down and restarts on its own. This will happen when fully charged and plugged in, and seems to happen more when the battery level get's below 80 percent, but hard to tell, as it just happens all the time, making it impossible for me to work. I also noticed it only happened AFTER I installed Sierra. I've taken all the troubleshooting steps you listed, including all suggested by Apple support, and nothing works.


  • Reset the SMC (which does not seem to work anymore)
  • Zapped the PRAM
  • Ran the Apple Hardware Test (no Issues found)
  • Ran in Safety Mode
  • Wiped and zeroed the HD and reinstalled 4 different OS's (Lion, Mavericks, Yosemite and Sierra)

I've lost thousands of dollars in work, time and energy because of this issue. Not a happy camper at all! I'm an IT manager who has been using Apple products since the 80's. I def know my way around troubleshooting issues. Frankly, I've always been a HUGE supporter of Apple, but after this, I'm considering switching to a Windows based system. I shouldn't have to shell out over $1600.00+ for a brand new system, only to have these serious hardware issues occur (oddly enough) just after my first year Applecare warranty expires? I have an appointment with Apple to troubleshoot the issue but worry that they are just going to tell me I need to replace the motherboard for another $1000.00+, which is absurd! I've read that Apple recalled earlier 2013 models for this very reason (faulty components and connections on the motherboard) and replaced the systems free of charge. Unfortunately, this only covers early models. Shame on Apple for allowing a known issue like this to persist without offering a viable solution, considering the recall and all the support issues related to this on their site and the internet. On top of this, when I first pulled the machine out of the box, I was getting little electrical shocks off the chassis and could feel a viable electrical buzz when using the machine. I instantly sent it back to Apple and they sent a NEW machine, which has now become my $1600.00 brick. I think when Apple started manufacturing their components in the far east, the quality has just disintegrated. I hate to sound so negative, but when you pay the high prices Apple demands, you should expect the quality that comes with the price, and with the quality and service usually associated with Apple. That is NOT the case. I'm glad you were able to resolve your issue, but honestly, having to replace the motherboard on a computer less that two years old is ridiculous! My PC is 7 years old, cost $600.00 and runs without issue....

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

MacBook Pro shuts down randomly

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.