Want to highlight a helpful answer? Upvote!
Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >
Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >
Macbook pro 11,2 with Retina, 256 SSD, Intel core i7
Macbook shuts down unexpected. I tried to reset SMC, PRAM, but it did not help.
Log file: Previous shuts down cause: -128
Also, I installed Windows 10. If I use Windows 10 then MacBook works correctly. But, if I use Mac OS, Mac still shuts down unexpected.
MacBook Pro, OS X El Capitan (10.11.3)
A negative shutdown code may indicate a hardware problem. The precise meaning of the codes is not publicly documented.
If you haven't already done so, you can try resetting the System Management Controller. Otherwise, or if the reset has no effect, see below.
Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. You may have to leave the machine there for several days.
Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional—ask if you need guidance.
If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
Apple also recommends that you deauthorize a device in the iTunes Store before having it serviced.
*An SSD doesn't need to be zeroed.
In SafeBoot mode, all work correctly.
If it is hardware, why Windows 10 works correctly?
1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
The test works on OS X 10.7 ("Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.
Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
2. If you don't already have a current backup, please back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.
You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.
In this case, however, there are ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone who understands the code can verify what it does.
You may not be able to understand the script yourself. But variations of it have been posted on this website many times over a period of years. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.
Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.
4. Here's a general summary of what you need to do, if you choose to proceed:
☞ Copy a particular line of text to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.
5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is intermittently slow, run the test during a slowdown.
You may have started up in safe mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual before running it. If you can only test in safe mode, do that.
6. If you have more than one user, and only one user is affected by the problem,, and the affected user is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
7. Load this linked web page (on the website "Pastebin.") Press the key combination command-A to select all the text, then copy it to the Clipboard by pressing command-C.
8. Launch the built-in Terminal application in any one of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.
9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.
If the test is taking much longer than usual to run because the computer is very slow, you might be prompted for your password a second time. The authorization that you grant by entering it expires automatically after five minutes.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:
Test started
Part 1 of 4 done at: … sec
…
Part 4 of 4 done at: … sec
The test results are on the Clipboard.
Please close this window.
The intervals between parts won't be exactly equal, but they give a rough indication of progress.
Wait for the final message "Please close this window" to appear. If you don't see it within about 15 minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it. Then go to the next step. You'll have incomplete results, but still something. If you close the Terminal window while the test is still running, the partial results won't be saved and you'll have to start over.
11. When the test is complete, or if you stopped it because it was taking too long, quit Terminal. The results will have been saved to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "close this window" message. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
12. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the software that runs this website. Please post the test results on Pastebin, then post a link here to the page you created.
If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.
13. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you're told to do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.
14. The linked UNIX shell script bears a notice of copyright. Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.
1 Start time: 21:23:11 02/01/16
2
3 Revision: 1473
4
5 Model Identifier: MacBookPro11,2
6 Boot ROM Version: MBP112.0138.B16
7 System Version: OS X 10.9.5 (13F34)
8 Kernel Version: Darwin 13.4.0
9 Time since boot: 4 minutes
10
11 I/O latency (ms/s)
12
13 Total: 146
14 firmwaresync: 118
15 mount_msdos: 28
16
17 Global prefs (system)
18
19 MultipleSessionEnabled = 1
20
21 Tunnel: Yes
22
23 Wi-Fi
24
25 Security: WPA Personal
26
27 Shutdown codes
28
29 -128 2
30
31 Kernel log
32
33 Feb 1 04:32:11 considerRebuildOfPrelinkedKernel com.apple.kext.OSvKernDSPLib triggered rebuild
34 Feb 1 05:11:09 AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
35 Feb 1 05:11:14 SMC::smcIH WARNING: unexpected interrupt: 0x55
36 Feb 1 05:11:14 SMC::smcIH WARNING: unexpected interrupt: 0x54
37 Feb 1 06:18:04 AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
38 Feb 1 06:18:07 SMC::smcIH WARNING: unexpected interrupt: 0x55
39 Feb 1 06:18:07 SMC::smcIH WARNING: unexpected interrupt: 0x54
40 Feb 1 10:14:32 SATA WARNING: IDENTIFY DEVICE checksum not implemented.
41 Feb 1 10:14:32 AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
42 Feb 1 10:14:32 SMC::smcReadKeyAction ERROR: smcReadData8 failed for key LsNM (kSMCKeyNotFound)
43 Feb 1 10:14:32 SMC::smcGetLightshowVers ERROR: smcReadKey LsNM failed (kSMCKeyNotFound)
44 Feb 1 10:14:32 SMC::smcPublishLightshowVersion ERROR: smcGetLightshowVers failed (kSMCKeyNotFound)
45 Feb 1 10:14:32 SMC::smcInitHelper ERROR: smcPublishLightshowVersion failed (kSMCKeyNotFound)
46 Feb 1 10:14:32 Previous Shutdown Cause: -128
47 Feb 1 10:14:32 SMC::smcIH WARNING: unexpected interrupt: 0x55
48 Feb 1 10:14:32 SMC::smcIH WARNING: unexpected interrupt: 0x54
49 Feb 1 21:19:27 SATA WARNING: IDENTIFY DEVICE checksum not implemented.
50 Feb 1 21:19:27 AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
51 Feb 1 21:19:27 SMC::smcReadKeyAction ERROR: smcReadData8 failed for key LsNM (kSMCKeyNotFound)
52 Feb 1 21:19:27 SMC::smcGetLightshowVers ERROR: smcReadKey LsNM failed (kSMCKeyNotFound)
53 Feb 1 21:19:27 SMC::smcPublishLightshowVersion ERROR: smcGetLightshowVers failed (kSMCKeyNotFound)
54 Feb 1 21:19:27 SMC::smcInitHelper ERROR: smcPublishLightshowVersion failed (kSMCKeyNotFound)
55 Feb 1 21:19:27 Previous Shutdown Cause: 5
56 Feb 1 21:19:28 SMC::smcIH WARNING: unexpected interrupt: 0x55
57 Feb 1 21:19:28 SMC::smcIH WARNING: unexpected interrupt: 0x54
58
59 System log
60
61 Feb 1 05:11:09 airportd: _doAutoJoin: Already associated to “WiFiAshrafzyanov”. Bailing on auto-join.
62 Feb 1 05:11:09 airportd: _doAutoJoin: Already associated to “WiFiAshrafzyanov”. Bailing on auto-join.
63 Feb 1 05:11:24 fseventsd: Logging disabled completely for device:1: /Volumes/Recovery HD
64 Feb 1 05:18:06 parentalcontrolsd: StartObservingFSEvents [849:] -- *** StartObservingFSEvents started event stream
65 Feb 1 06:18:04 airportd: _doAutoJoin: Already associated to “WiFiAshrafzyanov”. Bailing on auto-join.
66 Feb 1 10:14:32 fseventsd: event logs in /.fseventsd out of sync with volume. destroying old logs. (6467 2 20651)
67 Feb 1 10:14:32 fseventsd: log dir: /.fseventsd getting new uuid: UUID
68 Feb 1 10:14:34 mDNSResponder: mDNSResponder mDNSResponder-522.92.1 (Jul 27 2014 17:31:49) starting OSXVers 13
69 Feb 1 10:14:34 airportd: airportdProcessDLILEvent: en0 attached (up)
70 Feb 1 10:14:35 mDNSResponder: D2DInitialize succeeded
71 Feb 1 10:14:35 mDNSResponder: 4: Listening for incoming Unix Domain Socket client requests
72 Feb 1 10:14:35 loginwindow: Login Window Started Security Agent
73 Feb 1 10:14:41 airportd: _doAutoJoin: Already associated to “WiFiAshrafzyanov”. Bailing on auto-join.
74 Feb 1 10:14:51 parentalcontrolsd: StartObservingFSEvents [849:] -- *** StartObservingFSEvents started event stream
75 Feb 1 10:15:34 loginwindow: ERROR | -[ApplicationManager quitPrivateProcesses] | Private process did not quit
76 Feb 1 10:15:35 airportd: _doAutoJoin: Already associated to “WiFiAshrafzyanov”. Bailing on auto-join.
77 Feb 1 21:19:30 mDNSResponder: mDNSResponder mDNSResponder-522.92.1 (Jul 27 2014 17:31:49) starting OSXVers 13
78 Feb 1 21:19:30 airportd: airportdProcessDLILEvent: en0 attached (up)
79 Feb 1 21:19:30 mDNSResponder: D2DInitialize succeeded
80 Feb 1 21:19:30 mDNSResponder: 4: Listening for incoming Unix Domain Socket client requests
81 Feb 1 21:19:30 loginwindow: Login Window Started Security Agent
82 Feb 1 21:19:42 airportd: _doAutoJoin: Already associated to “WiFiAshrafzyanov”. Bailing on auto-join.
83 Feb 1 21:19:44 parentalcontrolsd: StartObservingFSEvents [849:] -- *** StartObservingFSEvents started event stream
84 Feb 1 21:19:45 com.apple.imfoundation.IMRemoteURLConnectionAgent: ERROR: __CFURLCache:CreateTablesAndIndexes version create - database is locked. ErrCode: 5.
85 Feb 1 21:19:45 com.apple.imfoundation.IMRemoteURLConnectionAgent: __CFURLCache:RecreateEmptyPersistentStoreOnDiskAndOpen: create tables and index failed.
86
87 launchd log
88
89 Jan 31 23:39:51 com.apple.Kerberos.digest-service: Exited with code: 1
90 Jan 31 23:39:51 com.apple.Kerberos.kdc: Exited with code: 1
91 Jan 31 23:39:52 com.apple.UserEventAgent-System: Could not find stream/token: com.apple.fsevents.matching/3
92 Jan 31 23:39:52 com.apple.UserEventAgent-System: Could not find stream/token: com.apple.fsevents.matching/3
93 Feb 1 04:31:56 com.apple.systemstatsd: Exited with code: 1
94 Feb 1 10:15:12 com.apple.WebKit.Networking.UUID: Exited with code: 1
95 Feb 1 21:20:12 com.apple.WebKit.WebContent.UUID: Could not terminate job: 3: No such process
96 Feb 1 21:20:12 com.apple.WebKit.Networking.UUID: Exited with code: 1
97
98 Agent services loaded
99
100 com.google.keystone.user.agent
101
102 Contents of Library/LaunchAgents/com.google.keystone.agent.plist
103 - mod date: Feb 1 21:20:24 2016
104 - size (B): 809
105 - checksum: 1271508369
106
107 <?xml version="1.0" encoding="UTF-8"?>
108 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
109 <plist version="1.0">
110 <dict>
111 <key>Label</key>
112 <string>com.google.keystone.user.agent</string>
113 <key>LimitLoadToSessionType</key>
114 <string>Aqua</string>
115 <key>ProgramArguments</key>
116 <array>
117 <string>/Users/USER/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bu ndle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftw areUpdateAgent</string>
118 <string>-runMode</string>
119 <string>ifneeded</string>
120 </array>
121 <key>RunAtLoad</key>
122 <true/>
123 <key>StartInterval</key>
124 <integer>3623</integer>
125 <key>StandardErrorPath</key>
126 <string>/dev/null</string>
127 <key>StandardOutPath</key>
128 <string>/dev/null</string>
129 </dict>
130 </plist>
131
132 iCloud services
133
134 MAIL_AND_NOTES
135 CONTACTS
136 CALENDAR
137 REMINDERS
138 NOTES
139 BOOKMARKS
140 MOBILE_DOCUMENTS
141
142 Bad permissions: 4
143
144 Lockfiles: 5
145
146 Applications
147
148 /Users/USER/Applications/Chrome Apps.localized/Default apdfllckaahabafndbhieahigkjlhalf.app
149 - com.google.Chrome.app.Default-apdfllckaahabafndbhieahigkjlhalf
150 /Users/USER/Applications/Chrome Apps.localized/Default blpcfgokakmgnkcojhhkbfbldkacnbeo.app
151 - com.google.Chrome.app.Default-blpcfgokakmgnkcojhhkbfbldkacnbeo
152 /Users/USER/Applications/Chrome Apps.localized/Default coobgpohoikkiipiblmjeljniedjpjpf.app
153 - com.google.Chrome.app.Default-coobgpohoikkiipiblmjeljniedjpjpf
154 /Users/USER/Applications/Chrome Apps.localized/Default pjkljhegncpnkpknbcohdijeoejaedia.app
155 - com.google.Chrome.app.Default-pjkljhegncpnkpknbcohdijeoejaedia
156 /Users/USER/Library/Application Support/Google/Chrome/Default/Web Applications/_crx_aohghmighlieiainnegkcijnfilokake/Default aohghmighlieiainnegkcijnfilokake.app
157 - com.google.Chrome.app.Default-aohghmighlieiainnegkcijnfilokake-internal
158 /Users/USER/Library/Application Support/Google/Chrome/Default/Web Applications/_crx_apdfllckaahabafndbhieahigkjlhalf/Default apdfllckaahabafndbhieahigkjlhalf.app
159 - com.google.Chrome.app.Default-apdfllckaahabafndbhieahigkjlhalf-internal
160 /Users/USER/Library/Application Support/Google/Chrome/Default/Web Applications/_crx_blpcfgokakmgnkcojhhkbfbldkacnbeo/Default blpcfgokakmgnkcojhhkbfbldkacnbeo.app
161 - com.google.Chrome.app.Default-blpcfgokakmgnkcojhhkbfbldkacnbeo-internal
162 /Users/USER/Library/Application Support/Google/Chrome/Default/Web Applications/_crx_coobgpohoikkiipiblmjeljniedjpjpf/Default coobgpohoikkiipiblmjeljniedjpjpf.app
163 - com.google.Chrome.app.Default-coobgpohoikkiipiblmjeljniedjpjpf-internal
164 /Users/USER/Library/Application Support/Google/Chrome/Default/Web Applications/_crx_pjkljhegncpnkpknbcohdijeoejaedia/Default pjkljhegncpnkpknbcohdijeoejaedia.app
165 - com.google.Chrome.app.Default-pjkljhegncpnkpknbcohdijeoejaedia-internal
166
167 Elapsed time (sec): 122
Besides two abnormal shutdowns in the last few days with the same negative code, there is more than the usual amount of latency in the storage subsystem. That measurement points to a failing drive or some other hardware fault. There's nothing else to account for the problem. It's not caused by software.
Today I reinstalled Mac OS from scratch (Version 10.9.5). When I close the lid, the fans are accelerated to the maximum, and continue to work a long time. If I open the lid, nothing happens, the screen is black and the apple does not light
Maybe something wrong with SMC?
Install OSX on an external drive (USB3 or Thunderbolt) - How to install OS X on an external drive connected to your Mac - Apple Support - and test booting and shutdown/startup using this external disk.
I already did, but it did not help.
Run Apple Hardware Test to check if it can identify any issues. Using Apple Hardware Test - Apple Support .
Do you have a second Mac?
I already did Apple Hardware Test. Result is "No issue".
Yep, I have the second Mac.
Are these two Macs the same model?
Boot the problematic Mac in Target Disk Mode, connect it to the working Mac using appropriate working cables (TB/FW) and boot the working Mac from the bad Mac's internal disk. If the working Mac shows the same behavior, your SSD is suspect, but this is not a guarantee that it is bad.
Switch roles and check if the 'bad' Mac behaves the same way with the external boot.
Do you have any abnormal behavior with fans or heat or any environmental factors that are significantly different from normal use?
The second Mac has another model.
About fans I have written above:
When I close the lid, the fans are accelerated to the maximum, and continue to work a long time. If I open the lid, nothing happens, the screen is black and the apple does not light
ashrafzynov wrote:
About fans I have written above:
When I close the lid, the fans are accelerated to the maximum, and continue to work a long time. If I open the lid, nothing happens, the screen is black and the apple does not light
1. Do you have a outer case for the Mac?
2. Does the screen stay completely dark, or does it become lighter? Is this the case with the Power adapter plugged in and removed, both?
3. Does SMC/NVRAM Reset change the behavior?
4. Are there any external devices connected to the Mac when it crashes?
1. No
2. Screen becomes lighter. In both cases
3. No.
4. There is no
My macbook shuts down unexpected
