-
All replies
-
Helpful answers
-
-
Apr 24, 2016 4:17 AM in response to OGELTHORPEby saskiao,EtreCheck version: 2.9.11 (264)
Report generated 2016-04-24 14:15:28
Download EtreCheck from https://etrecheck.com
Runtime 1:28
Performance: Excellent
Click the [Support] links for help with non-Apple products.
Click the [Details] links for more information about that line.
Problem: No problem - just checking
MacBook Pro (Retina, 13-inch, Early 2015)
[Technical Specifications] - [User Guide] - [Warranty & Service]
MacBook Pro - model: MacBookPro12,1
1 2,7 GHz Intel Core i5 CPU: 2-core
8 GB RAM Not upgradeable
BANK 0/DIMM0
4 GB DDR3 1867 MHz ok
BANK 1/DIMM0
4 GB DDR3 1867 MHz ok
Bluetooth: Good - Handoff/Airdrop2 supported
Wireless: en0: 802.11 a/b/g/n/ac
Battery: Health = Normal - Cycle count = 106
Intel Iris Graphics 6100
Color LCD 2560 x 1600
OS X El Capitan 10.11.4 (15E65) - Time since boot: about 2 hours
APPLE SSD SM0256G disk0 : (251 GB) (Solid State - TRIM: Yes)
EFI (disk0s1) <not mounted> : 210 MB
Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
Macintosh HD (disk1) / : 249.78 GB (203.33 GB free)
Encrypted AES-XTS Unlocked
Core Storage: disk0s2 250.14 GB Online
Broadcom Corp. Bluetooth USB Host Controller
Apple Inc. thunderbolt_bus
Mac App Store and identified developers
[not loaded] 7 Apple tasks
[loaded] 156 Apple tasks
[running] 75 Apple tasks
[not loaded] 46 Apple tasks
[loaded] 154 Apple tasks
[running] 88 Apple tasks
[loaded] com.adobe.fpsaud.plist (2016-04-16) [Support]
iTunesHelper Application (/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)
[loaded] 391 Apple tasks
[running] 183 Apple tasks
FlashPlayer-10.6: 21.0.0.226 - SDK 10.6 (2016-04-23) [Support]
QuickTime Plugin: 7.7.3 (2016-03-29)
Flash Player: 21.0.0.226 - SDK 10.6 (2016-04-23) [Support]
Default Browser: 601 - SDK 10.11 (2016-03-29)
Momentum - Momentum Dashboard Corp. - http://momentumdash.com (2015-09-07)
Flash Player (2016-04-16) [Support]
Time Machine not configured!
11% kernel_task
5% WindowServer
2% hidd
2% fontd
0% cloudpaird
1.33 GB com.apple.WebKit.WebContent(7)
768 MB kernel_task
410 MB Safari
156 MB Mail
106 MB mds_stores
2.08 GB Free RAM
5.92 GB Used RAM (1.65 GB Cached)
0 B Swap Used
Apr 24, 2016, 11:37:31 AM Self test - passed
-
Apr 24, 2016 4:28 AM in response to saskiaoby OGELTHORPE,There is nothing in the Etrecheck report indicating any problems.
Run Apple diagnostics and see if that provides any clues:
https://support.apple.com/en-us/HT202731
Also run the MBP in safe mode and see if there is any difference:
https://support.apple.com/en-us/HT201262
Ciao.
-
Apr 24, 2016 4:47 AM in response to OGELTHORPEby saskiao,It said "No issues found".. everything seems to be fine, so I have no idea why it freezes sometimes...
-
Apr 24, 2016 6:21 AM in response to saskiaoby Linc Davis,These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Please launch the Console 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.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Enter "BOOT_TIME" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.
If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Some private information, such as your name, may appear in the log. Anonymize before posting.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Step 2
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.
When you post the log extract or the crash report, 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 forum software. Please post the text 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.
-
Apr 24, 2016 7:15 AM in response to Linc Davisby saskiao,I hope I understood correctly.
1)
24/04/16 14:53:11,000 kernel[0]: Kernel requests now disabled.
24/04/16 14:53:11,000 kernel[0]: Process launchd [1] disabling system-wide I/O Throttling
24/04/16 14:53:11,000 kernel[0]: Process launchd [1] disabling system-wide CPU Throttling
24/04/16 14:53:11,408 com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.system) System shutdown initiated by: shutdown.479<-sessionlogoutd.478<-launchd.1
24/04/16 14:53:37,000 bootlog[0]: BOOT_TIME 1461498817 0
24/04/16 14:55:29,000 kernel[0]: Kernel requests now disabled.
24/04/16 14:55:29,523 shutdown[399]: SHUTDOWN_TIME: 1461498929 522771
24/04/16 14:55:29,000 kernel[0]: Process launchd [1] disabling system-wide I/O Throttling
24/04/16 14:55:29,000 kernel[0]: Process launchd [1] disabling system-wide CPU Throttling
24/04/16 14:55:29,523 com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.system) System shutdown initiated by: shutdown.399<-sessionlogoutd.398<-launchd.1
24/04/16 14:55:54,000 bootlog[0]: BOOT_TIME 1461498954 0
2) I don't know if it's correct but I only saw "kernel" and I copied that report.
-
Apr 24, 2016 7:33 AM in response to saskiaoby Linc Davis,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.8 ("Mountain 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 the text of a particular web page (not this one) 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 ("Terminal") 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 startedPart 1 of 4 done at: … sec
…
Part 4 of 4 done at: … secThe 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—again, usually within a few minutes. If you don't see that message within about 30 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.
In order to get results, the test must either be allowed to complete or else manually stopped as above. If you close the Terminal window while the test is still running, the partial results won't be saved.
11. When the test is complete, or if you stopped it manually, 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. When you're done with the test, it's gone. There is nothing to uninstall or clean up.
14. 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 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.
15. 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.