Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Black screen after login / after sleep

Hoping somebody can help, I've spent like the last two days straight at the genius bar without success. When I boot up I see my profile and the guest, it boots as normal (not the delayed boot with black screen others have mentioned), but then I log in, see my desktop, icons, and then the screen goes black.


If I let it sleep for a few hours, when I wake it up the screen is also black and there's nothing I can do except hold the power till it shuts down.


In both cases I can tell the computer is still on because the backlit keyboard stays lit.


I've tried resetting nvram, smc, deleting the library cache file, doing a is reinstall without wipe, and I only have one partition/HD so it's definitely the default boot disc.


I can boot into safe mode, and occasionally boot up regularly after being in safe mode for a bit.


I had the display replaced due to a physical defect just before this happened, but I also got 10.10.3, which I know has caused graphics glitches for other people.



Hope you guys have some ideas! Thank you!

MacBook Pro (Retina, 15-inch, Late 2013), OS X Yosemite (10.10.3)

Posted on Apr 18, 2015 7:29 AM

Reply
13 replies

Apr 18, 2015 8:34 AM in response to isaiah1991

When the screen goes black, note the exact time: hour, minute, second.

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any 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.

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.

Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.

Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.

Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

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.

Some private information, such as your name, may appear in the log. Anonymize before posting.

When you post the log extract, 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.

Apr 19, 2015 1:29 PM in response to Linc Davis

Please find the log attached! thank you so much!
4/19/15 4:17:15.000 PM kernel[0]: Wake reason: EC.LidOpen (User)

4/19/15 4:17:15.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000320

4/19/15 4:17:15.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

4/19/15 4:17:15.000 PM kernel[0]: AppleCamIn::wakeEventHandlerThread

4/19/15 4:17:15.000 PM kernel[0]: Previous sleep cause: 5

4/19/15 4:17:15.001 PM watchdogd[353]: [watchdog_daemon] @( pm_callback) - ref=0x0 msg_type=0xe0000320 msg=0x0

4/19/15 4:17:15.000 PM kernel[0]: AppleThunderboltNHIType2::prePCIWake - power up complete - took 2 us

4/19/15 4:17:15.005 PM discoveryd[75]: Basic DNSResolver UDNSServer:: PowerState is FullWake

4/19/15 4:17:15.000 PM kernel[0]: AppleThunderboltGenericHAL::earlyWake - complete - took 1 milliseconds

4/19/15 4:17:15.007 PM com.apple.backupd-helper[66]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc

4/19/15 4:17:15.000 PM kernel[0]: AppleUSBMultitouchDriver::validateChecksum - 64-byte packet checksum is incorrect (expected 0x7ca, checksum bytes were 0xdab)

4/19/15 4:17:15.000 PM kernel[0]: IOThunderboltSwitch<0xffffff803c2a1600>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0

4/19/15 4:17:15.000 PM kernel[0]: IOThunderboltSwitch<0xffffff803c2a1600>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0

4/19/15 4:17:15.000 PM kernel[0]: TBT W (2): 0x0040 [x]

4/19/15 4:17:15.000 PM kernel[0]: en0: channel changed to 1

4/19/15 4:17:15.000 PM kernel[0]: AirPort: Link Up on awdl0

4/19/15 4:17:15.000 PM kernel[0]: en0: channel changed to 1

4/19/15 4:17:15.000 PM kernel[0]: IO80211AWDLPeerManager::setAwdlOperatingMode Setting the AWDL operation mode from AUTO to SUSPENDED

4/19/15 4:17:15.000 PM kernel[0]: IO80211AWDLPeerManager::setAwdlSuspendedMode() Suspending AWDL, enterQuietMode(true)

4/19/15 4:17:15.000 PM kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized

4/19/15 4:17:15.311 PM hidd[96]: MultitouchHID: device bootloaded

4/19/15 4:17:15.000 PM kernel[0]: en0: 802.11d country code set to 'US'.

4/19/15 4:17:15.000 PM kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165

4/19/15 4:17:15.000 PM kernel[0]: ARPT: 16771.038041: MacAuthEvent en0 Auth result for: 04:a1:51:10:18:e8 MAC AUTH succeeded

4/19/15 4:17:15.000 PM kernel[0]: AirPort: Link Up on en0

4/19/15 4:17:15.000 PM kernel[0]: en0: BSSID changed to 04:a1:51:10:18:e8

4/19/15 4:17:15.000 PM kernel[0]: en0: channel changed to 149,80

4/19/15 4:17:15.000 PM kernel[0]: en0::IO80211Interface::postMessage bssid changed

4/19/15 4:17:15.000 PM kernel[0]: ARPT: 16771.043610: AWDL Sync Enabled 0

4/19/15 4:17:15.603 PM configd[48]: LINKLOCAL en0: parent has no IP

4/19/15 4:17:15.607 PM networkd[196]: +[NETLedBelly stopFastFail] Clearing ledbelly failure cache

4/19/15 4:17:15.607 PM UserEventAgent[38]: Captive: CNPluginHandler en0: Inactive

4/19/15 4:17:15.608 PM configd[48]: network changed: v4(en0-:192.168.1.5) DNS- Proxy-

4/19/15 4:17:15.000 PM kernel[0]: AirPort: RSN handshake complete on en0

4/19/15 4:17:15.611 PM discoveryd[75]: Basic WABServer NetResolverEvent no resolvers, resetting domains

4/19/15 4:17:15.612 PM discoveryd[75]: AwdlD2d AwdlD2dStartAdvertisingPair: 'isaiahs-macbook-pro' Advertising service started

4/19/15 4:17:15.612 PM discoveryd[75]: AwdlD2d AwdlD2dStartAdvertisingPair: 'isaiahs-macbook-pro' Advertising service started

4/19/15 4:17:15.613 PM discoveryd[75]: AwdlD2d AwdlD2dStartAdvertisingPair: 'eccb60efff2f224100000000000008efip6arpa' Advertising service started

4/19/15 4:17:15.671 PM netbiosd[244]: network_reachability_changed : network is not reachable, netbiosd is shutting down

4/19/15 4:17:15.673 PM networkd[196]: +[NETLedBelly stopFastFail] Clearing ledbelly failure cache

4/19/15 4:17:15.674 PM configd[48]: network changed: DNS* Proxy

4/19/15 4:17:15.675 PM UserEventAgent[38]: Captive: [CNInfoNetworkActive:1709] en0: SSID 'It's bigger on the inside' making interface primary (cache indicates network not captive)

4/19/15 4:17:15.676 PM UserEventAgent[38]: Captive: CNPluginHandler en0: Evaluating

4/19/15 4:17:15.678 PM networkd[196]: +[NETLedBelly stopFastFail] Clearing ledbelly failure cache

4/19/15 4:17:15.680 PM configd[48]: network changed: v4(en0!:192.168.1.5) DNS+ Proxy+ SMB

4/19/15 4:17:15.681 PM UserEventAgent[38]: Captive: en0: Not probing 'It's bigger on the inside' (cache indicates not captive)

4/19/15 4:17:15.000 PM kernel[0]: en0: BSSID changed to 04:a1:51:10:18:e8

4/19/15 4:17:15.000 PM kernel[0]: en0: channel changed to 149,80

4/19/15 4:17:15.683 PM UserEventAgent[38]: Captive: CNPluginHandler en0: Authenticated

4/19/15 4:17:15.000 PM kernel[0]: en0: BSSID changed to 04:a1:51:10:18:e8

4/19/15 4:17:15.000 PM kernel[0]: en0: channel changed to 149,80

4/19/15 4:17:15.000 PM kernel[0]: en0: BSSID changed to 04:a1:51:10:18:e8

4/19/15 4:17:15.000 PM kernel[0]: en0: channel changed to 149,80

4/19/15 4:17:15.000 PM kernel[0]: ARPT: 16771.163583: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

4/19/15 4:17:15.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340

4/19/15 4:17:15.000 PM kernel[0]: AppleCamIn::wakeEventHandlerThread

4/19/15 4:17:15.723 PM WindowServer[160]: CGXDisplayDidWakeNotification [16771165247068]: posting kCGSDisplayDidWake

4/19/15 4:17:15.723 PM WindowServer[160]: handle_will_sleep_auth_and_shield_windows: Deferring.

4/19/15 4:17:15.746 PM discoveryd[75]: Basic DNSResolver UDNSServer:: PowerState is FullWake

4/19/15 4:17:15.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000300

4/19/15 4:17:17.296 PM discoveryd[75]: Basic Warn DD_Warn: Corrupt NSEC RDATA size

4/19/15 4:17:17.387 PM apsd[76]: Illegal subject name missing 'courier.push.apple.com' (2.5.4.3): ({

label = "2.5.4.6";

"localized label" = "2.5.4.6";

type = string;

value = US;

}, {

label = "2.5.4.8";

"localized label" = "2.5.4.8";

type = string;

value = California;

}, {

label = "2.5.4.7";

"localized label" = "2.5.4.7";

type = string;

value = Cupertino;

}, {

label = "2.5.4.10";

"localized label" = "2.5.4.10";

type = string;

value = "Apple Inc.";

}, {

label = "2.5.4.3";

"localized label" = "2.5.4.3";

type = string;

value = "courier.sandbox.push.apple.com";

})

4/19/15 4:17:17.464 PM CalendarAgent[245]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

4/19/15 4:17:17.541 PM CalendarAgent[245]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

4/19/15 4:17:18.809 PM CalendarAgent[245]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/plain; charset="utf-8"].]

4/19/15 4:17:18.911 PM CalendarAgent[245]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/plain; charset="utf-8"].]

4/19/15 4:17:19.081 PM discoveryd[75]: Basic NATTServer Got device info URL: http://192.168.1.1:5000/Public_UPNP_gatedesc.xml

4/19/15 4:17:19.709 PM discoveryd[75]: Basic NATTServer Got control URL: http://192.168.1.1:5000/Public_UPNP_C3 (ip)

4/19/15 4:17:20.000 PM kernel[0]: AppleCamIn::handleWakeEvent_gated

4/19/15 4:17:20.000 PM kernel[0]: AppleCamIn::handleWakeEvent_gated

Apr 20, 2015 3:09 PM in response to isaiah1991

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, 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 a couple of 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 with the necessary skill 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 thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. 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 sometimes, but not always, 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. If you can only test in safe mode, do that.

6. If you have more than one user, and the one affected by the problem 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.") The title of the page is "Diagnostic Test." Below the title is a text box headed by three small icons. The one on the right represents a clipboard. Click that icon to select the text, then copy it to the Clipboard on your computer by pressing the key combination command-C.

If the text doesn't highlight when you click the icon, select it by triple-clicking anywhere inside the box. Don't select the whole page, just the text in the box.

8. Launch the built-in Terminal application in any 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 see an error message in the Terminal window such as "Syntax error" or "Event not found," enter

exec bash

and press return. Then paste the script again.

10. 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 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.

11. 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:

[Process started]

Part 1 of 8 done at … sec

Part 8 of 8 done at … sec

The test results are on the Clipboard.

Please close this window.

[Process completed]

The intervals between parts won't be exactly equal, but they give a rough indication of progress. The total number of parts may be different from what's shown here.

Wait for the final message "Process completed" to appear. If you don't see it within about ten 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 and go to the next step. You'll have incomplete results, but still something.

12. When the test is complete, or if you stopped it because it was taking too long, quit Terminal. The results will have been copied 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 "Process completed" message to appear in the Terminal window. 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.

13. 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 forum software. Please post the test results on Pastebin, then post a link here to the page you created.

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'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.

______________________________________________________________

Copyright © 2014, 2015 by Linc Davis. As the sole author of this work (including the referenced "Diagnostic Test"), I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Apr 20, 2015 3:45 PM in response to isaiah1991

A

"Avast" is the worst of the whole wretched lot of commercial "security" products for the Mac. Not only does it fail to protect you from any real danger, it may send personal data (such as web browsing history and the contents of email messages) back to the developer without your knowledge, give false warnings, destabilize and slow down the computer, expose you to network attack, and corrupt the network settings and the permissions of files in your home folder. Removing it may not repair all the damage.

Some versions of the product also inject advertising into web pages. In short, apart from the fine print in the license agreement, Avast is indistinguishable from malware, and is arguably worse than any known malware now in circulation.

Back up all data, then remove Avast according to the developer's instructions. Restart.

If you tried to remove Avast by dragging an application to the Trash, you'll have to reinstall it and then follow the instructions linked above.

B

If any USB devices are connected, disconnect them and test.

C

Some of your user files (not system files) have incorrect permissions or are locked. This procedure will unlock those files and reset their ownership, permissions, and access controls to the default. If you've intentionally set special values for those attributes, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it, but you do need to follow the instructions below.

Back up all data before proceeding.

Step 1

If you have more than one user, and the one in question is not an administrator, then go to Step 2.

Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):

sudo find ~ $TMPDIR.. -exec chflags -h nouchg,nouappnd,noschg,nosappnd {} + -exec chown -h $UID {} + -exec chmod +rw {} + -exec chmod -h -N {} + -type d -exec chmod -h +x {} + 2>&-

You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.

The command may take several minutes to run, depending on how many files you have. Wait for a new line ending in a dollar sign ($) to appear, then quit Terminal.

Step 2 (optional)

Take this step only if you have trouble with Step 1, if you prefer not to take it, or if it doesn't solve the problem.

Start up in Recovery mode. When the OS X Utilities screen appears, select

Utilities Terminal

from the menu bar. A Terminal window will open. In that window, type this:

resetp

Press the tab key. The partial command you typed will automatically be completed to this:

resetpassword

Press return. A Reset Password window will open. You’re not going to reset a password.

Select your startup volume ("Macintosh HD," unless you gave it a different name) if not already selected.

Select your username from the menu labeled Select the user account if not already selected.

Under Reset Home Directory Permissions and ACLs, click the Reset button.

Select

Restart

from the menu bar.

D

Back up all data.

Run the following command in the same way as before. It moves to the Trash "semaphore" files that have not been cleaned up by the system and may be interfering with normal operation. The files are empty; they contain no data. There will be no output this time.

find L*/{Con*/*/Data/L*/,}Pref* -type f -size 0c -name *.plist.??????? -exec mv {} .Trash/ \; 2>&-

Log out or restart the computer and empty the Trash.

E

Storing many files on the Desktop may slow down the Finder, especially if the files have custom icons. Move most or all of the files to another subfolder of your home folder.

F

I suggest you get rid of "AppCleaner," which serves no real purpose and may be harmful.

Apr 20, 2015 4:03 PM in response to Linc Davis

Okay, I got rid of Avast (I'd had really good experiences with it when I was a PC user, any suggestions on what I should use instead?), AppCleaner, reset the permissions as instructed, moved all my desktop items to a folder in my documents, and did the semaphore thing. I'll know by tonight / tomorrow if this fixed it, anything else I should do? Seemed like there were driver / device issues per that log?

Apr 20, 2015 4:12 PM in response to isaiah1991

Mac users often ask whether they should install "anti-virus" (AV) software. The usual answer is "no." That answer is right, but it may give the wrong impression that there is no threat from what are loosely called "viruses." There is a threat, and you need to educate yourself about it.

1. This is a comment on what you should—and should not—do to protect yourself from malicious software ("malware") that circulates on the Internet and gets onto a computer as an unintended consequence of the user's actions.

It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the computer, or who has been able to take control of it remotely. That threat is in a different category, and there's no easy way to defend against it. AV software is not intended to, and does not, defend against such attacks.

The comment is long because the issue is complex. The key points are in sections 5, 6, and 10.

OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits.

2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user. Internally Apple calls it "XProtect."

The malware recognition database used by XProtect is automatically updated; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.

The following caveats apply to XProtect:

☞ It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets.

☞ It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.

As new versions of OS X are released, it's not clear whether Apple will indefinitely continue to maintain the XProtect database of older versions such as 10.6. The security of obsolete system versions may eventually be degraded. Security updates to the code of obsolete systems will stop being released at some point, and that may leave them open to other kinds of attack besides malware.

3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't been checked for security by Apple unless it comes from the App Store, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.)

Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following:

☞ It can easily be disabled or overridden by the user.

☞ A malware attacker could get control of a code-signing certificate under false pretenses, or could simply ignore the consequences of distributing codesigned malware.

☞ An App Store developer could find a way to bypass Apple's oversight, or the oversight could fail due to human error.

Apple has taken far too long to revoke the codesigning certificates of some known abusers, thereby diluting the value of Gatekeeper and the Developer ID program. Those lapses don't involve App Store products, however.

For the reasons given, App Store products, and—to a lesser extent—other applications recognized by Gatekeeper as signed, are safer than others, but they can't be considered absolutely safe. "Sandboxed" applications may prompt for access to private data, such as your contacts, or for access to the network. Think before granting that access. Sandbox security is based on user input. Never click through any request for authorization without thinking.

4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is effective against known threats, but not against unknown ones. It notifies you if it finds malware, but otherwise there's no user interface to MRT.

5. The built-in security features of OS X reduce the risk of malware attack, but they are not, and never will be, complete protection. Malware is a problem of human behavior, not machine behavior, and no technological fix alone is going to solve it. Trusting software to protect you will only make you more vulnerable.

The best defense is always going to be your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "Trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and Internet criminals. If you're better informed than they think you are, you'll win. That means, in practice, that you always stay within a safe harbor of computing practices. How do you know when you're leaving the safe harbor? Below are some warning signs of danger.

Software from an untrustworthy source

☞ Software with a corporate brand, such as Adobe Flash Player, doesn't come directly from the developer’s website. Do not trust an alert from any website to update Flash, or your browser, or any other software. A genuine alert that Flash is outdated and blocked is shown on this support page. Follow the instructions on the support page in that case. Otherwise, assume that the alert is fake and someone is trying to scam you into installing malware. If you see such alerts on more than one website, ask for instructions.

☞ Software of any kind is distributed via BitTorrent, or Usenet, or on a website that also distributes pirated music or movies.

☞ Rogue websites such as Softonic, Soft32, and CNET Download distribute free applications that have been packaged in a superfluous "installer."

☞ The software is advertised by means of spam or intrusive web ads. Any ad, on any site, that includes a direct link to a download should be ignored.

Software that is plainly illegal or does something illegal

☞ High-priced commercial software such as Photoshop is "cracked" or "free."

☞ An application helps you to infringe copyright, for instance by circumventing the copy protection on commercial software, or saving streamed media for reuse without permission. All "YouTube downloaders" are in this category, though not all are necessarily malicious.

Conditional or unsolicited offers from strangers

☞ A telephone caller or a web page tells you that you have a “virus” and offers to help you remove it. (Some reputable websites did legitimately warn visitors who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)

☞ A web site offers free content such as video or music, but to use it you must install a “codec,” “plug-in,” "player," "downloader," "extractor," or “certificate” that comes from that same site, or an unknown one.

☞ You win a prize in a contest you never entered.

☞ Someone on a message board such as this one is eager to help you, but only if you download an application of his choosing.

☞ A "FREE WI-FI !!!" network advertises itself in a public place such as an airport, but is not provided by the management.

☞ Anything online that you would expect to pay for is "free."

Unexpected events

☞ A file is downloaded automatically when you visit a web page, with no other action on your part. Delete any such file without opening it.

☞ You open what you think is a document and get an alert that it's "an application downloaded from the Internet." Click Cancel and delete the file. Even if you don't get the alert, you should still delete any file that isn't what you expected it to be.

☞ An application does something you don't expect, such as asking for permission to access your contacts, your location, or the Internet for no obvious reason.

☞ Software is attached to email that you didn't request, even if it comes (or seems to come) from someone you trust.

I don't say that leaving the safe harbor just once will necessarily result in disaster, but making a habit of it will weaken your defenses against malware attack. Any of the above scenarios should, at the very least, make you uncomfortable.

6. Java on the Web (not to be confused with JavaScript, to which it's not related, despite the similarity of the names) is a weak point in the security of any system. Java is, among other things, a platform for running complex applications in a web page, on the client. That was always a bad idea, and Java's developers have proven themselves incapable of implementing it without also creating a portal for malware to enter. Past Java exploits are the closest thing there has ever been to a Windows-style virus affecting OS X. Merely loading a page with malicious Java content could be harmful.

Fortunately, client-side Java on the Web is obsolete and mostly extinct. Only a few outmoded sites still use it. Try to hasten the process of extinction by avoiding those sites, if you have a choice. Forget about playing games or other non-essential uses of Java.

Java is not included in OS X 10.7 and later. Discrete Java installers are distributed by Apple and by Oracle (the developer of Java.) Don't use either one unless you need it. Most people don't. If Java is installed, disable itnot JavaScript—in your browsers.

Regardless of version, experience has shown that Java on the Web can't be trusted. If you must use a Java applet for a task on a specific site, enable Java only for that site in Safari. Never enable Java for a public website that carries third-party advertising. Use it only on well-known, login-protected, secure websites without ads. In Safari 6 or later, you'll see a padlock icon in the address bar when visiting a secure site.

Stay within the safe harbor, and you’ll be as safe from malware as you can practically be. The rest of this comment concerns what you should not do to protect yourself.

7. Never install any commercial AV or "Internet security" products for the Mac, as they are all worse than useless. If you need to be able to detect Windows malware in your files, use one of the free security apps in the Mac App Store—nothing else.

Why shouldn't you use commercial AV products?

☞ To recognize malware, the software depends on a database of known threats, which is always at least a day out of date. This technique is a proven failure, as a major AV software vendor has admitted. Most attacks are "zero-day"—that is, previously unknown. Recognition-based AV does not defend against such attacks, and the enterprise IT industry is coming to the realization that traditional AV software is worthless.

☞ Its design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere. In order to meet that nonexistent threat, commercial AV software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.

☞ By modifying the operating system, the software may also create weaknessesthat could be exploited by malware attackers.

☞ Most importantly, a false sense of security is dangerous.

8. An AV product from the App Store, such as "ClamXav," has the same drawback as the commercial suites of being always out of date, but it does not inject low-level code into the operating system. That doesn't mean it's entirely harmless. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so will corrupt the Mail database. The messages should be deleted from within the Mail application.

An AV app is not needed, and cannot be relied upon, for protection against OS X malware. It's useful, if at all, only for detecting Windows malware, and even for that use it's not really effective, because new Windows malware is emerging much faster than OS X malware.

Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else. A malicious attachment in email is usually easy to recognize by the name alone. An actual example:

London Terror Moovie.avi [124 spaces] Checked By Norton Antivirus.exe

You don't need software to tell you that's a Windows trojan. Software may be able to tell you which trojan it is, but who cares? In practice, there's no reason to use recognition software unless an organizational policy requires it. Windows malware is so widespread that you should assume it's in every email attachment until proven otherwise. Nevertheless, ClamXav or a similar product from the App Store may serve a purpose if it satisfies an ill-informed network administrator who says you must run some kind of AV application. It's free and it won't handicap the system.

The ClamXav developer won't try to "upsell" you to a paid version of the product. Other developers may do that. Don't be upsold. For one thing, you should not pay to protect Windows users from the consequences of their choice of computing platform. For another, a paid upgrade from a free app will probably have all the disadvantages mentioned in section 7.

9. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use in the Sharing preference pane. All are disabled by default.

10. As a Mac user, you don't have to live in fear that your computer may be infected every time you install software, read email, or visit a web page. But neither can you assume that you will always be safe from exploitation, no matter what you do. Navigating the Internet is like walking the streets of a big city. It can be as safe or as dangerous as you choose to make it. The greatest harm done by security software is precisely its selling point: it makes people feel safe. They may then feel safe enough to take risks from which the software doesn't protect them. Nothing can lessen the need for safe computing practices.

Apr 22, 2015 7:24 AM in response to Linc Davis

This is from this morning, I found these logs interesting, wondering if you have input?



4/22/15 9:14:55.773 AM WindowServer[140]: CGXDisplayDidWakeNotification [32311195384079]: posting kCGSDisplayDidWake

4/22/15 9:14:56.003 AM WindowServer[140]: Received display connect changed for display 0x4280882

4/22/15 9:14:56.003 AM WindowServer[140]: Found 1 modes for display 0x04280882 [1, 0]

4/22/15 9:14:56.003 AM WindowServer[140]: Display 0x04280882 changed state to offline

4/22/15 9:14:56.037 AM WindowServer[140]: No display devices are on-line. Switching to virtual display mode

4/22/15 9:14:56.052 AM WindowServer[140]: Display 0x41dc9d01: GL mask 0x2; bounds (0, 0)[1280 x 1024], 2 modes available

off-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 1, Rotation 0

UUID 0xffffffffffffffffffffffffffffffff

4/22/15 9:14:56.052 AM WindowServer[140]: Display 0x41dc9d05: GL mask 0x20; bounds (0, 0)[1280 x 1024], 2 modes available

off-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 5, Rotation 0

UUID 0xffffffffffffffffffffffffffffffff

4/22/15 9:14:56.052 AM WindowServer[140]: Display 0x41dc9d04: GL mask 0x10; bounds (0, 0)[1280 x 1024], 2 modes available

off-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 4, Rotation 0

UUID 0xffffffffffffffffffffffffffffffff

4/22/15 9:14:56.052 AM WindowServer[140]: Display 0x41dc9d03: GL mask 0x8; bounds (0, 0)[1280 x 1024], 2 modes available

off-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 3, Rotation 0

UUID 0xffffffffffffffffffffffffffffffff

4/22/15 9:14:56.052 AM WindowServer[140]: Display 0x41dc9d02: GL mask 0x5; bounds (0, 0)[1920 x 1200], 35 modes available

Main, Active, on-line, enabled, built-in, Vendor 756e6b6e, Model 76697274, S/N 0, Unit 2, Rotation 0

UUID 0xfd6e905353b752245892f9f7ec52cef3, ColorSpace { -1655004991 }

4/22/15 9:14:56.304 AM WindowServer[140]: CGError post_notification(const CGSNotificationType, void *const, const size_t, const bool, const CGSRealTimeDelta, const int, const CGSConnectionID *const, const pid_t): Timed out 0.250 second wait for reply from "nbagent" for synchronous notification type 100 (kCGSDisplayWillReconfigure) (CID 0x1e913, PID 934)

4/22/15 9:14:56.558 AM WindowServer[140]: CGXDisplaysDidReconfigure: Display added

4/22/15 9:14:56.558 AM WindowServer[140]: CGXDisplaysDidReconfigure: Display removed


4/22/15 9:16:34.309 AM loginwindow[107]: ERROR | -[LoginProgress startingProgressRectForMainScreen] | Could not locate the boot display

Black screen after login / after sleep

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