Apple’s Worldwide Developers Conference to kick off June 10 at 10 a.m. PDT with Keynote address

The Keynote will be available to stream on apple.com, the Apple Developer app, the Apple TV app, and the Apple YouTube channel. On-demand playback will be available after the conclusion of the stream.

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

MacBook Pro 15" (2016) Crashing while connecting/disconnecting the LG 5K Monitor

I have the 2016 MBP 15" with 2.9 CPU, 2TB and 460 GPU with 4GB. I am using Mac OS X 10.12.2.


In one single day I have had 2 Mac OS Crashes and 2 Panic Errors, it has always happened after connecting or disconnecting the new LG 5K monitor. Here are the scenarios.


MBP closed in sleep mode, connect the 5K monitor through the Thunderbolt 3 cable (providing data and power) to use only the 5K monitor, the MBP will remain closed, after plugging it in I will press a key in the external keyboard or move the mouse to resume from sleep mode and the LG 5K Monitor screen will be black, and after 5-10 seconds I will get the panic message "You need to restart your computer, hold the power button for several seconds........." on the middle of the screen and the MBP will self reboot shortly after. I've been able to repeat this error by simply following the steps above 2 times within 15min. To me clearly seems to be something related to the Thunderbolt 3 connection or the handling of the external monitor when resuming from sleep. These is the information from the Console on the Panic errors, both Panic logs look the same:


Mon Jan 16 17:40:19 2017

*** Panic Report ***

Kernel Extensions in backtrace:

com.apple.iokit.IOGraphicsFamily(513.1)

dependency: com.apple.iokit.IOPCIFamily(2.9)

com.apple.kext.AMDSupport(1.4.8)

dependency: com.apple.iokit.IOACPIFamily(1.4)

dependency: com.apple.iokit.IOPCIFamily(2.9)

dependency: com.apple.iokit.IOGraphicsFamily(513.1)

dependency: com.apple.AppleGraphicsDeviceControl(3.13.78)

com.apple.kext.AMD9500Controller(1.4.8)

dependency: com.apple.iokit.IOACPIFamily(1.4)

dependency: com.apple.iokit.IOPCIFamily(2.9)

dependency: com.apple.kext.AMDSupport(1.4.8)

dependency: com.apple.iokit.IOGraphicsFamily(513.1)

com.apple.kext.AMDFramebuffer(1.4.8)

dependency: com.apple.iokit.IOACPIFamily(1.4)

dependency: com.apple.iokit.IOPCIFamily(2.9)

dependency: com.apple.kext.AMDSupport(1.4.8)

dependency: com.apple.iokit.IOGraphicsFamily(513.1)


The second problem caused the computer to crash, here is the description of the situation: Last night I had the MBP closed connected to the 5K monitor using only the monitor, no internal display. I put it to sleep before going to bed. Today in the morning I did not open the MBP, I just unplugged the Thunderbolt 3 cable to disconnect the LG 5K monitor and take the MBP with me to the office. Once I got there I just plugged (at 8:11AM) the laptop the the AC via the Apple USB-C cable and the Apple 87W AC adapter, the MBP was still closed, in sleep mode I would assume. The around 8:15AM I opened the laptop to find out it has crashed and the login screen after a restart was there, no resume from sleep. Same thing happened later in the day after I came home, this is the information from the Console:


Crash at 8:11AM Today (look at the AmbientDisplayAgent):


Process: com.apple.AmbientDisplayAgent [15057]

Path: /System/Library/PrivateFrameworks/AmbientDisplay.framework/Versions/A/XPCServic es/com.apple.AmbientDisplayAgent.xpc/Contents/MacOS/com.apple.AmbientDisplayAgent

Identifier: com.apple.AmbientDisplayAgent

Version: 1.0 (1)

Code Type: X86-64 (Native)

Parent Process: launchd [1]

Responsible: com.apple.AmbientDisplayAgent [15057]

User ID: 0

Date/Time: 2017-01-16 08:11:26.029 -0600

OS Version: Mac OS X 10.12.2 (16C67)

Report Version: 12

Anonymous UUID: 5C048B2B-4801-AEE4-C57A-202B6A1E3822

Sleep/Wake UUID: B9B2EB86-667C-4404-8556-9870749821DD

Time Awake Since Boot: 150000 seconds

Time Since Wake: 6 seconds

System Integrity Protection: enabled

Crashed Thread: 3 Dispatch queue: com.apple.root.default-qos.overcommit

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: EXC_I386_GPFLT

Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [0]

Application Specific Information:

objc_msgSend() selector name: isEqual:

Thread 0:: Dispatch queue: com.apple.main-thread

0 libsystem_kernel.dylib 0x00007fffe729e38a mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fffe729d7d7 mach_msg + 55

2 com.apple.CoreFoundation 0x00007fffd1c1fc94 __CFRunLoopServiceMachPort + 212

3 com.apple.CoreFoundation 0x00007fffd1c1f121 __CFRunLoopRun + 1361

4 com.apple.CoreFoundation 0x00007fffd1c1e974 CFRunLoopRunSpecific + 420

5 com.apple.Foundation 0x00007fffd3633612 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 277

6 com.apple.Foundation 0x00007fffd36334ea -[NSRunLoop(NSRunLoop) run] + 76

7 libxpc.dylib 0x00007fffe73db89b _xpc_objc_main + 731

8 libxpc.dylib 0x00007fffe73da2e4 xpc_main + 494

9 com.apple.AmbientDisplayAgent 0x0000000103c528a5 main + 298

10 libdyld.dylib 0x00007fffe7177255 start + 1


Crash at 5:50PM today (same AmbientDisplayAgent):


Process: com.apple.AmbientDisplayAgent [209]

Path: /System/Library/PrivateFrameworks/AmbientDisplay.framework/Versions/A/XPCServic es/com.apple.AmbientDisplayAgent.xpc/Contents/MacOS/com.apple.AmbientDisplayAgen t

Identifier: com.apple.AmbientDisplayAgent

Version: 1.0 (1)

Code Type: X86-64 (Native)

Parent Process: launchd [1]

Responsible: com.apple.AmbientDisplayAgent [209]

User ID: 0

Date/Time: 2017-01-16 17:50:05.171 -0600

OS Version: Mac OS X 10.12.2 (16C67)

Report Version: 12

Anonymous UUID: 5C048B2B-4801-AEE4-C57A-202B6A1E3822

Sleep/Wake UUID: 74BCEADF-96E1-4B71-BA28-93E605DA9C0B

Time Awake Since Boot: 100 seconds

System Integrity Protection: enabled

Crashed Thread: 2 Dispatch queue: DispEventQueue

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018

Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [0]

VM Regions Near 0x18:

-->

__TEXT 000000010239e000-00000001023a5000 [ 28K] r-x/rwx SM=COW /System/Library/PrivateFrameworks/AmbientDisplay.framework/Versions/A/XPCServic es/com.apple.AmbientDisplayAgent.xpc/Contents/MacOS/com.apple.AmbientDisplayAgen t

Application Specific Information:

objc_msgSend() selector name: isEqual:

Thread 0:: Dispatch queue: com.apple.main-thread

0 libsystem_kernel.dylib 0x00007fffb2c5838a mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fffb2c577d7 mach_msg + 55

2 com.apple.CoreFoundation 0x00007fff9d5d9c94 __CFRunLoopServiceMachPort + 212

3 com.apple.CoreFoundation 0x00007fff9d5d9121 __CFRunLoopRun + 1361

4 com.apple.CoreFoundation 0x00007fff9d5d8974 CFRunLoopRunSpecific + 420

5 com.apple.Foundation 0x00007fff9efed612 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 277

6 com.apple.Foundation 0x00007fff9efed4ea -[NSRunLoop(NSRunLoop) run] + 76

7 libxpc.dylib 0x00007fffb2d9589b _xpc_objc_main + 731

8 libxpc.dylib 0x00007fffb2d942e4 xpc_main + 494

9 com.apple.AmbientDisplayAgent 0x00000001023a08a5 main + 298

10 libdyld.dylib 0x00007fffb2b31255 start + 1


Please any help or advice on what could be the root cause will be appreciated, thanks

MacBook Pro with Retina display, macOS Sierra (10.12.2)

Posted on Jan 16, 2017 5:50 PM

Reply
Question marked as Best reply

Posted on Jan 23, 2017 7:12 PM

I am having the exact same issue. The integration of the new MacBook Pro and the Ultrafine monitor his HORRIBLE. Throughout the day, if the computers go to sleep, the LG UltraFine will not come back on. Or, the MacBook will just restart, and the error report is SleepWakeFailure.


Not only that, but hot swap plugging (unplugging the monitor or vice versa) to pick up the laptop and take with you rarely works, causing one or the other to go blank and not come back.


Also sleep in general is very inconsistent with the new MacBook Pro 2016 with Touchbar.


All in all, the whole integration of the OS, the sleep/wake, and the new LG monitors seems like the old days when I was using a Windows laptop where none of those things were reliable.


I was always amazed at how well the Mac could hotswap on and off with Apple's Thunderbolt Display, how reliable and fast Sleep/Wake were, etc.


Now it's an utter disaster.


I am really wishing I hadn't sold top of the line MacBook Pro 2015 Retina and 27" Apple Thunderbolt Display. Those were reliable and worked perfectly all the time. The new LG and new MacBook Pro Touchbar - not so much.


So Apple, before I start wanting a refund, is this hardware or software related? Hoping software, but if not, you've got a computer and 2 LG 5K displays on their way back to you.

265 replies

Nov 29, 2017 5:00 PM in response to Coregts

I'm just replying in general. I have a 2016 also with two LG 5K monitors. One at work and one at home. Both cause my mac book to crash when plugging them in. I typically have to wake the computer from sleep wait a few minutes to settle it down and then plug it into the cable and even then I have a 20% chance of my mac book crashing. I am running 10.13.1. This is not acceptable! We need to really start hammering apple about this. I paid for stability and since it's not stable I'll take 1/2 my money back.

Nov 29, 2017 5:39 PM in response to bab5139

I’ve opened yet another case with Apple about this issue. We realized that the issue is when the MBP goes to sleep with the integrated graphics in use. Plugging in an external display while it’s sleeping causes it to sit in limbo between the integrated and dedicated graphics. Wether Apple does anything to actually fix this is another story.

Nov 30, 2017 6:52 PM in response to bab5139

I called apple support and they claim they have no information about this. Ridiculous. If this isn't fixed in the next release i am going to force a full hardware replacement and sell the monitors. Maybe even drop the macbook all together. The machine barely works with usb-c to display port without having to plug and unplug the monitor repeatedly to get the external display working. Maybe fine for a lightly used consumer product but not for a work machine.

Dec 1, 2017 6:04 AM in response to Coregts

I just got off with Apple support, they claim they have no info about it either, Norwegian support. First representative didn't understand basics, but the next one was understanding. Got the classic, "an engineer has to look into it", which means troubleshooting and uploading system logs with timestamps.


I've already started switching back to Windows 10 and haven't really used a PC as my main computer since 2006 when Intel got introduced to the Mac. It was hard, but now I prefer Windows 10 and since I've had six or seven MacBook Pro 2016, both 15" and 13", with or without touch bar, and all of them are affected or had other defects, there isn't much of an alternative as I've tried all Apple Pro laptops on the market. Different batches and bought in separate stores. Tried all versions from 10.12.4 to 10.13.1 of macOS. Clean installs as well. SMC and PRAM resets. Nothing will make it more stable. It always happened after some extensive usage and when I unplug it from the external monitor I get the black screen, frozen keyboard and touch bar.


I would still like to have an Apple laptop, but I won't settle for a fully priced 2015 15" that has a CPU from 2013 in it. My MacBook 12" from 2015 actually is stable connected to the same display, a Dell UP3216Q, even though not officially supported by Apple. It does have some interface transition lags, but it doesn't go black and freeze. Neither did my 2014 MBP 13" or MBP 15" AMD 370 2015, when I had them earlier. I have considered an iMac, but that means I can't use it around freely like I would with a laptop.


I uploaded a video of a classic example of the crash

Macbook pro 2016 - radeon pro 450 - sleep wake failure - YouTube

Dec 7, 2017 5:29 AM in response to logicito

Hi all,


Got the same issue with the MBP Late 2016 crashing when sleeping and connected to the 5K Ultrafine.


My logic board has been replaced and so has the I/O ports. I've been told by the Apple store, that replacing the I/O ports has made the issue go away/no crashes detected. Anyway Apple had my MBP for nearly 3 weeks and also filed a report to the Engineering team. The Engineering team has sent back a reply acknowledging the fault with sleeping MBP and Ultrafine displays. The message also says a software fix is in development.


I don't have a copy of the message is it was read out to me over the phone. I'm collecting the MBP tonight, I'll see if they will give me a copy.

Dec 14, 2017 1:54 AM in response to pemell

The 2017 doesn't crash as often as the 2016, but it did crash.


I'm currently using the 2016 15" model, and I've labeled it as my crash-machine. I'm not sure whether it's a hardware or software problem. But the issue persists. Connecting this laptop - whether it was to the left side or right hand side to a USB C monitor or a DP monitor will crash the machine. It may crash it on connecting and it may crash it on disconnecting. If the computer is not running any applications whatsoever, and it is only the OS - then perhaps it may not crash. If you leave applications running and do the connect / disconnect to an external monitor. It will crash. It loves to crash when it is in clamshell mode as well. I had wasted 2 months - collecting logs - sending screen shots, video clips - etc, with Apple Care technical support on the phone, before giving up and going to the Genius Bar. The genius bar, said we'll take in your machine for testing and if we can verify it's a hardware fault - we'll replace the logic board. 1 week later, they confirmed it was the logic board, and they went ahead with replacing it. Yet again, the computer continues to crash. During that interim week, I picked up a 2017 with thought of perhaps keeping it if it doesn't crash and selling off my 2016 machine on eBay. Yet after a couple of crashes, I concluded either a hardware design fault or a bad software programming fault.


So take your pick - either it is a faulty design in the hardware - it does not like external monitors. Or, it is a faulty piece of software code that they're unable to decipher - how to fix. Apple has sold a super expensive laptop that cannot be connected to external monitors.


Disappointed. Apologies for the long whinge.

Dec 20, 2017 9:53 PM in response to tigo13

I have a 2016 and it crashes at LEAST twice a day... I have a Dell wide/curved monitor at work connected through displayport and when I unplug that to go home, it crashes..


when I get home I plug it into dual Dell 27" displays (one HDMI and one DisplayPort) and when I disconnect that in the mornings to go to work.. it crashes..


I am also pretty disapointed in Apple for not supporting displayport daisy chaining.. I dual booted windows on this mac and it worked perfectly!! its a n OSX limitation that they acknowledged as a "known issue".. but wont fix it..


This thing crashes more and Panic's more that any of my windows sytems ever did 😟

Dec 24, 2017 9:53 PM in response to damon.youngjin

About 4 months back, I found it hadn't been crashing if I didn't use the right hand side USB-C ports.

And it hasn't crashed until now, but I see many people having issues no matter which side.

So it was my only workaround...


- Macbook pro 13" with touch bar 2016

- Experienced issues with LG 27UD88, Prism M280PU monitors

- Logic board replaced but issue persisted.

- Issue only seen when connecting right hand side USB-C ports with external display.


Hope it helps.

Dec 25, 2017 12:47 PM in response to logicito

All I can say is that after Apple's conspiracy with the iPhone batteries, I was motivated to sign in and leave this first-time reply on the Apple Discussion Forum.


I have this SAME PROBLEM. I've written Apple with no response. I'm keeping track of my crash's to build a case against this problem and the lack of interest Apple has in addressing it in the event that it should turn into a legal matter.


My MacBook Pro 15" with Touch Bar crashes and must restart every time it sleeps and I come to wake it.


I - like many of you I'm guessing - am a "power user." Meaning, I don't own this monitor because it's high tech and cool. I work in the film/entertainment/video/photo business.


I understand why this may not be a priority - Those with a MacBook Pro, that is a 15 inch, with a Touch Bar, and also an external display that is specifically the LG 5K Ultrafine plug-and-play monitor are a very small and niche group of people.


Nonetheless, it's unacceptable that it is a glitch preventing the usability of the products they're selling.

Dec 30, 2017 4:20 PM in response to rasenjop

I have the same issue on my Dell UP3216Q as well, tried a variety of adapters, dongles and docks, they all seem to crash upon wake or on disconnect. So many dongles, adapters and docks are only 30hz in 4K as well, even the ones they sell in authorized Apple stores, you are most likely to find something compatible from third parties on Ebay or Amazon rather than in an actual store where you can buy a mac.


Next year it will be three years since USB C got released with the MacBook 12" in 2015, still there is nothing clear about the new standard. Cables, docks and adapters all seem to run their own show. One will lack charging capability, and the other will not give you proper speeds or resolution on your screen. In its current state it is a mess, at least if you compare it to earlier generations and adaptions of the Thunderbolt port, where the process was plug and play with official adapters.


There is no official USB-C to displayport cable from Apple either.

Jan 8, 2018 12:54 PM in response to tigo13

The issue has been resolved. Either by Apple directly with a software update (running OS X 10.13.2) or by myself as I'm now using Startech and A-logic USB-C cables as opposed to the cables that came with the 4K monitors that I use from Dell and Acer. It has not crashed - unless I accidentally make a mistake in the sequence of connecting / disconnecting it with the external monitors.

I think (hypothesis) that the issue with the laptop crashing is due to how the OS handles the power / signalling with the external monitors that it gets confused and crashes unless you follow sequence when connecting / disconnecting.

When the laptop is connected to an external monitor and the user wants to disconnect it from the external monitors, either to transport it (go to work) or to use it independently then they'd need to do the following.

1) If going to work, and the laptop is to remain in clamshell, - then put the machine to sleep BEFORE turning off the external monitor or disconnecting the cable.

2) if you plan on working with the laptop directly after disconnecting it from the external monitor. Then, open the laptop screen from clamshell, - make sure that it is working fine, - then disconnect the external monitor.

If you've returned from work and want to connect it to the external monitor. Either keep the laptop in clamshell, connect the cables, then turn on the monitor and bluetooth / wireless keyboard mouse and wait for it to send a graphics signal the monitor. If nothing happens, - then try opening the laptop screen to see if the laptop screen has your login details, etc.


I think (hypothesis) that the crashes were an issue with the OS - Graphics card - power management. If the laptop had been in clamshell - connected to external monitor. And you just disconnect the monitor, - the OS would believe it needs to go to sleep - it had just lost power, and if you then open the laptop screen directly. It would crash. Similarly when connecting the laptop to the external screen - it suddenly starts to receive a signal and it is trying to identify the accessory now connected to it.


Acer / Dell, and non-Apple hardware monitors have pretty basic accessories that do not have power management / communication chips in them to communicate with the computer. When a windows laptop connects to these monitors - they would work fine - as the OS is built to handle them. However, when it comes to an Apple laptop, - they require / expect the accessories (monitors) to have some sort of advanced - power management / signalling in them.


Also, its worth noting that the Dell / Acer etc monitors, are not Thunderbolt 3 monitors, - that they are a DP monitor with USB-C input interface labelled as ALT-DP. A thunderbolt 3 monitor would have the power management chip that I mentioned.


My laptop now does not crash - as long as I'm following the right sequence, and it automatically crashes if I don't follow the sequence. Feeling a lot better that I understand how to avoid crashes to not lose my work.

MacBook Pro 15" (2016) Crashing while connecting/disconnecting the LG 5K Monitor

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