Multiple Displays have problems with El Capitan

The safe mode reboot actually made mine work, for now.

Hello All,

I have the 2nd Display Malfunction - can anyone help? I have done all the usual even reinstalling El Capitan. I have pasted my EtreCheck. Any help would be much

appreciated.

Thanks,Andy

EtreCheck version: 2.9.12 (265)

Report generated 2016-06-18 20:18:58

Download EtreCheck from https://etrecheck.com

Runtime 1:33

Performance: Excellent

Click the [Support] links for help with non-Apple products.

Click the [Details] links for more information about that line.

Problem: Other problem

Description:

second monitor does not work

Hardware Information: ⓘ

iMac (27-inch, Late 2013)

[Technical Specifications] - [User Guide] - [Warranty & Service]

iMac - model: iMac14,2

1 3.5 GHz Intel Core i7 CPU: 4-core

16 GB RAM Upgradeable - [Instructions]

BANK 0/DIMM0

8 GB DDR3 1600 MHz ok

BANK 1/DIMM0

8 GB DDR3 1600 MHz ok

BANK 0/DIMM1

Empty

BANK 1/DIMM1

Empty

Bluetooth: Good - Handoff/Airdrop2 supported

Wireless: en1: 802.11 a/b/g/n/ac

Video Information:ⓘ

NVIDIA GeForce GTX 775M - VRAM: 2048 MB

iMac 2560 x 1440

System Software:ⓘ

OS X El Capitan 10.11.5 (15F34) - Time since boot: less than an hour

Disk Information:ⓘ

APPLE SSD SD0128F disk0 : (121.33 GB) (Solid State - TRIM: Yes)

EFI (disk0s1) <not mounted> : 210 MB

Boot OS X (disk0s3) <not mounted> : 134 MB

Macintosh HD (disk2) / : 1.11 TB (1.03 TB free)

Core Storage: disk0s2 120.99 GB Online

Core Storage: disk1s2 999.35 GB Online

APPLE HDD ST1000DM003 disk1 : (1 TB) (Rotational)

EFI (disk1s1) <not mounted> : 210 MB

Recovery HD (disk1s3) <not mounted> [Recovery]: 650 MB

Macintosh HD (disk2) / : 1.11 TB (1.03 TB free)

Core Storage: disk0s2 120.99 GB Online

Core Storage: disk1s2 999.35 GB Online

USB Information:ⓘ

Apple Inc. BRCM20702 Hub

Apple Inc. Bluetooth USB Host Controller

Apple Inc. FaceTime HD Camera (Built-in)

Thunderbolt Information:ⓘ

Apple Inc. thunderbolt_bus

Configuration files:ⓘ

/etc/sysctl.conf - File exists but not expected

Gatekeeper:ⓘ

Mac App Store and identified developers

System Launch Agents:ⓘ

[not loaded] 7 Apple tasks

[loaded] 161 Apple tasks

[running] 70 Apple tasks

System Launch Daemons:ⓘ

[not loaded] 47 Apple tasks

[loaded] 158 Apple tasks

[running] 85 Apple tasks

Launch Agents:ⓘ

[not loaded] com.adobe.AAM.Updater-1.0.plist (2016-06-18) [Support]

[failed] com.adobe.ARMDCHelper.cc24aef4a1b90ed56a...plist (2016-05-26) [Support]

[running] com.adobe.AdobeCreativeCloud.plist (2016-05-26) [Support]

Launch Daemons:ⓘ

[loaded] com.adobe.ARMDC.Communicator.plist (2016-05-26) [Support]

[loaded] com.adobe.ARMDC.SMJobBlessHelper.plist (2016-05-26) [Support]

[running] com.adobe.adobeupdatedaemon.plist (2016-06-13) [Support]

[loaded] com.adobe.agsservice.plist (2016-05-26) [Support]

[loaded] com.adobe.fpsaud.plist (2016-06-13) [Support]

[loaded] com.apple.installer.osmessagetracing.plist

User Launch Agents:ⓘ

[loaded] com.adobe.AAM.Updater-1.0.plist (2016-05-26) [Support]

User Login Items:ⓘ

iTunesHelper Application (/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)

Other Apps:ⓘ

[running] com.adobe.CCLibrary.95072

[running] com.adobe.CCXProcess.94752

[running] com.adobe.acc.AdobeDesktopService.67872.0A6C28C6-4461-4333-B848-2D269F531116

[running] com.adobe.accmac.93152

[running] com.etresoft.EtreCheck.96672

[loaded] de.milchimgemuesefach.Display-Menu-Helper

[loaded] 399 Apple tasks

[running] 180 Apple tasks

Internet Plug-ins:ⓘ

AdobeAAMDetect: 3.0.0.0 - SDK 10.9 (2016-06-13) [Support]

FlashPlayer-10.6: 22.0.0.192 - SDK 10.9 (2016-06-18) [Support]

QuickTime Plugin: 7.7.3 (2016-05-05)

AdobePDFViewerNPAPI: 15.016.20039 - SDK 10.11 (2016-05-03) [Support]

AdobePDFViewer: 15.016.20039 - SDK 10.11 (2016-05-03) [Support]

Flash Player: 22.0.0.192 - SDK 10.9 (2016-06-18) [Support]

Default Browser: 601 - SDK 10.11 (2016-05-05)

3rd Party Preference Panes:ⓘ

Flash Player (2016-06-13) [Support]

Time Machine:ⓘ

Time Machine not configured!

Top Processes by CPU:ⓘ

3% kernel_task

3% WindowServer

3% fontd

1% com.apple.WebKit.WebContent(14)

0% hidd

Top Processes by Memory:ⓘ

837 MB kernel_task

737 MB com.apple.WebKit.WebContent(14)

131 MB node(2)

131 MB Adobe CEF Helper(2)

115 MB mdworker(7)

Virtual Memory Information:ⓘ

12.00 GB Free RAM

4.01 GB Used RAM (2.47 GB Cached)

0 B Swap Used

Diagnostics Information:ⓘ

Jun 18, 2016, 08:08:22 PM Self test - passed

Jun 18, 2016, 12:02:01 PM /Library/Logs/DiagnosticReports/com.apple.WebKit.WebContent_2016-06-18-120201_[ redacted].cpu_resource.diag [Details]

/System/Library/Frameworks/WebKit.framework/Versions/A/XPCServices/com.apple.We bKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContent

I don't see any obvious red flags in your Etrecheck report.

You say you did all the usual things, but did not specify.

Did you do all of these:

- unplug/replug the cable

- try a different monitor/cable

- detect displays in System Preferences->Displays (you have to hold down the option key for that button to appear...)

- restart in Safe Mode

- plug the monitor at boot/only after booting is complete

- reset NVRAM (hold down command-option-P-R simultaneously at boot)

- reset SMC (details depend on particular mac)

Luis has been a rockstar helping on this. I believe there was one more thing that helped me -- DisplayLink has offered an upgrade in their software online. Since I used the DisplayLink connection from the USB to the TVs, once I upgraded, things seemed to work fine ever since. I have three monitors hooked up to my Macbook Pro. Hope this helps

I have a solution that is a variation on the theme. I have a late 2014 model mac mini with two 23" cinema displays. The older models with the DVI connectors. I have one plugged in to the thunderbolt port through an adapter and the other plugged in to the hdmi port through an adapter. It was all working with Yosemite but when I upgraded to El Capitan I was disappointed to discover that only one monitor would work. It did not matter which monitor or which port I plugged it into. After restart only one would fire up. I tried resetting the SMC and I tried the NVRAM to no avail. I tried the detect displays bit also failed. I tried the SMC reset exactly as described here with no luck. I called a local apple reseller's service department and the fellow suggested that when resetting the SMC, during the first power up with only one monitor plugged in I should hold down the control-option-shift keys and the power button, and leave them all pressed during startup. I got to the login screen before I let them go. I logged in, and then when the desktop came up I plugged my second monitor in. It fired up and I now have two monitors. I tried to google the key combination but couldn't find it. The fellow from the store said it was supposed to make the computer start up, and then after a bit shut down and startup again. He implied that it is the most thorough way to reset the SMC. I don't know if that is true, but it worked and I am happy.

I use a Mac Pro 2013, running El Capitan 10.11.5. I have 2 LG monitors (model: 27mb85z) and connect them using Apple brand thunderbolt cables.

I've been dealing with this issue for over a year now. Every morning, it takes me 5 minutes to turn my F'ing monitors on. Turn off, turn on, turn off, turn on. Randomly it starts working... until later in the day when they sleep again.

Using it with one monitor always works. It's when I have 2 monitors connected and turned on that one of them doesn't receive a signal until I power cycle it enough times to get it to recognize.

I've also used my friend's dell monitor (their high quality 27 inch led model), and I had the same issues. I believe it to be an issue with either OSX or the Mac Pro firmware.

I have no idea how to compel Apple to fix this. But it seems pretty absurd to have wasted so much money on such a crappy experience.

Note: I've reset my SMC dozens of times. It does absolutely nothing to solve this issue.

SMC reset is our only hope in getting the 2nd monitor to work. We've been doing this since we upgraded to El Capitan and it's freaking happening to more than 10 macs in our office including ours, the IT guys. At first we thought it was the new 24" samsung monitors we bought from our trusted reseller but the monitors worked individually. This needs to be fixed. We are administering more than 70 macs and this is preventing us in upgrading all of our macs to El Capitan! We haven't had this issue in Yosemite though.

You probably install the same software on all the macs you manage.

Odds are some of that software is involved in the problem. Or maybe it is specific to some mac models?

I have used many different monitors and projectors with my mac (rMBP 2014) using EC.

It has always been plug and play. Not only that; the mac correctly recognizes the way they are organized (e.g. when I connect the iMac at the office in target display my rMBP knows to use it as extended desktop, to the right of the rMBP screen, whereas several projectors in classrooms work in mirror mode, etc); it has never failed.

Same experience with several of my coworkers, and all the macs at home (wife and three grown up children).

I suggest you try on a clean install, smc reset, nvram reset and see how that goes.

Worked!!! How I wish I would have done your 15 seconds of uplugged power before I spent what seems hours on the phone with Apple and at the Genius Bar coming up empty... Thank you!

Not to discourage apple, because I think the NSA leaked exploit is what's to blame. That and Apple can't stop Kanye loving their iPhone. Sadly, we have work to do Apple, I don't care about Kanye's iPhone 7. My Cintiq has been glitching with the last two El Capitan releases. I almost sent it back, that is BAD MANAGEMENT. Tim Cook, let me take over. (Cintiq 24HD works by unplugging the monitor FROM the power supply – the power supply stays powered for a while so unplug the MONITOR from the POWER SUPPLY)

I found that upgrading cables and multi-plexing issues are having a problem with the latest stable code base.

For instance this problem started in 10.11.5 and persists in 10.11.6 but I also have a 4K Displayport cable in one end, and a cheapo-cable Rev. 1.1 Mini DisplayPort cable. Rev 1.2 Mini DisplayPort Cable is current. Use the same together and make sure they are backward compatible, kaptain out.

It seems this issue with the multiple screens is ongoing since 2011 or so. After much research about it, I think the best solution is what some users have shared in this post: switch off everything, wait 30 seconds, turn on mac, then plug second screen in.

Same type of problem here, with interesting variation that implies the issue originates from the mac.

Computer: Macbook Pro mid-2012, 2.6GHz, 16G RAM, intel HD graphics 4000+Nvidia GeForce GT650M, El Capitan

Monitor: HP 2210i

Cable: TB to DVI

External display works fine when I turn on the MBP, first time I connect the monitor. So monitor and cable are ok.

If I disconnect the external display cable and then reconnect: it doesn't work. The monitor shows an overlay message "Input Signal Out of Range. Change Settings to 1920 x 1080 - 60Hz", then goes to sleep. The background image is the desktop, however the image is shifted to the right, with a black area one or two inches on the left. The System Preferences/Monitor shows two options for refresh rate: 60Hz and 60Hz (two times the same!), which don't make a difference. I tried SwitchResX and checked that the settings are actually what the monitor is asking for, all I could do is change some settings that will make the image shift to the left instead of right.

I tried to unplug the cable, turn off (even unplug) the monitor for 30 seconds: the problem is back when I connect again. However, if I reboot the mac then the external display works fine (until I unplug/replug the cable). So: this is absolute proof that the issue comes from the Mac. Furthermore I had been using the same monitor and cable with Mavericks and it worked just fine. So we can clearly say that something is wrong with El Capitan: when an external display is unplugged and plugged back in something is not properly reset. Apple wake up!

The issues have not been resolved with MacOS Sierra... Apple should address this ASAP.

My latest scope of the situation is, sometimes you have to flush the whole thing, unplug the machine. Reboot get rid of memory loops, been finding a lot with EIE Pro Drivers and Serato DJ. Sometimes those things need a good 20 minutes off the power grid to fully flush. When there's been a big storm coming I usually unplug everything from the wall. Everything is off the grid, to prevent back-up disk from dying. Usually after the storm (could be due to electrostatic discharge or humidity) or my machine being completely reset and all the RAM of all types cleared, and potentially scrambled because of electromagnetic interference? I found a DisplayPort connector on my Wacom 24HD and bought a 4K DisplayPort to Mini-DisplayPort cable which is Version 1.2 of cable, or something like that. I bought a 4K Belkin HDMI -> MiniDisplayPort also 1.2 version of cable.

After major power down (talking like 3-8 hours) of all devices completely off the grid. I power on the machine, the Wacom 'flickers', AKA it's just told to go to Power Saving Mode because the OS or ThunderBolt Bus is doing something wacky. I then unplug the external power ballast from the monitor, leaving the ballast/AC Adapter running, go make the bed or something that takes like 2-5 minutes, brush my teeth. Then make sure that the machine is alive and active not in screen-saver and plug it back in. It usually works after a full power-down like that. Akai's EIE Pro Driver is so jacked too, hopefully I upgrade to Sierra and their driver makes it better (they don't have one yet ) that driver *****. CoreAudio got messed with and a whole bunch of licensing issues came up right around Mavericks or El Capitan. Either drivers just had to be signed to work or CoreAudio had a really strange mishap with deprecated code in CoreAudio or the engineers at Akai did a really bad job of "figuring it out". I also had them pry open this iMac and put a 1TB solid state drive in it as the master disk, with 32GB of RAM, pretty good for an old Mac 😉

I have discussed with Wacom Support how messing with Display's Power Saving settings and maybe turning them off when you are debugging your work-around might give you the answer you need.