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 Top-ranking reply

Posted on Jan 16, 2018 2:30 AM

Update to my previous comment:
I went to the Apple store to test an identical LG 5k display with my own MacBook and it worked without any issues. Likewise, I asked one of my friends to come around to test my monitor with his MacBook and the outcome was the same. My monitor didn’t switch on and it also crashed my friend’s MacBook. I can safely conclude that in my case the fault is in the monitor. I contacted LG and they refused to take the monitor in for a fix. Also, since the problem doesn't seem to be with the laptop, Apple won't be able to fix it either. I contacted an LG partner that deals with fixes and they told me that the problem is most likely in the monitor's mainboard. They suggested to replace it and charged me £360 including pickup and delivery. It's expensive. Should I go for it?

265 replies

Jan 31, 2018 7:26 PM in response to logicito

Apple Support documents HT202824 and HT201635 talk about deep sleep.


Last year, when the issue was most prevalent. It was little over an hour, when it was in sleep mode then an immediate crash when connecting to an external monitor. The machine would automatically restart and once I login - it would indicate a Sleep Wake Failure report - 7-8 out of 10 times. The remaining times there'd be no report.

Feb 8, 2018 1:37 PM in response to kdupreez

Kdupreez, my machine finally crashed - going into a screen saver, while connected to the USB C monitor; and after running some heavy video editing software.

Can you run an experiment in your setup and see if it crashes.

laptop is in clamshell mode; connected to the 4K or 5K monitor.

Run a few heavy intensive applications - getting the fans on the machine to run; for about 15 - 30 mins.

Close the intensive applications and leave the machine to go into screen saver mode (could be 10 - 20 mins later) while connected to the monitor.


Mine crashed with that scenario; and I remember it crashing almost every time last November with the scenario. This year, I haven't been doing much intensive work like the above yet.

Feb 15, 2018 5:50 AM in response to logicito

I think the problem is with the AMD graphics card. It becomes very apparent when connected to 5K monitor, but it remains problematic even if not connected to one...


After 5 years Apple will recall these devices, as they did with the Nvidia 2012 MBP. The problem is that when this happens your computer will have no value any more... and thus the replacement will be cheap for Apple as well...

Mar 13, 2018 2:59 PM in response to Shareef Yousef

8:28 up 11 days, 14:23, 2 users, load averages: 1.94 2.44 2.55


Still working with 2 4K monitors with the laptop in clamshell mode; and I'm able to connect / disconnect it without a crash. However, I do make sure to close any intensive applications that I may be running before doing so. The strange thing is that, - at times the USB C does not come alive at first when connected to the laptop; and I would have to connect the DP monitor - that would come alive - and I would log in; then unplug and replug the USB-C monitor for it to come alive.


If you'd like to run an experiment to see whether the machine would crash. Open up Lightroom or Photos with a large photo; then have a few applications running in the background (mail, safari with a few windows / tabs, notes, stickies, etc); then have a virtual machine running windows using up 4-8GB ram and a couple of apps within Windows. See how that goes when you connect the machine / disconnect it to the monitors, and the machine would have been in sleep mode.

Jun 6, 2018 4:12 AM in response to timcooks

So what happened Tim? did they replace the Motherboard and it's all working good now?


Since the release of 10.13.4 I haven't had a single crash; I'd have the occasional lag of a screen steadying itself at connecting / disconnecting, and thankfully no crashes. The machine works great now - as expected of a $4K machine.


I'm slightly concerned that when 10.14 comes out later in the year, - it'll be buggy and won't handle the 4K / 5K monitors and crashes the machine. I think I may hold off the update till 10.14.2 or so.

Nov 4, 2017 10:35 PM in response to logicito

I experience the same issue since upgrading to High Sierra, previously I never experienced this issue. My MacBook is the 15 inch first gen from fall 2016. I was quite surprised to find out many people experienced the issue earlier before High Sierra, I assumed it's related to the OS release. I have a LG 5k display at home and at the office and both give me crashes, so it's definitely not related to the screen hardware. Using latest High Sierra version and latest LG 5K firmware.


Does anyone know for certain if it's a hardware issue or a software issue?


I am always plugging my monitor on the right side of the MacBook Pro and will try to plug in on the left side now to see if that solves the issue. Already got 2 keyboard replacements and would hate to bring in my MacBook for a third repair...


Edit: I think I noticed it already crashes when I open from clam shell mode, rather than simply unplugging the cable. Will observe that closer too.

Nov 6, 2017 11:17 AM in response to Simmenfl

I had crash issues from earlier version of Sierra but they fixed that since 10.12.3. Now the issue comes back again in High Sierra (10.13.1). I'm inclined to think that it's a software issue but you never know. It could be related to certain hardware or firmware. It's getting quite annoying now as this problem seems to be worse than those found in the initial version of Sierra (10.12.1 - 10.12.2).

Nov 21, 2017 7:07 PM in response to logicito

I got a new logic board from Apple, which means I had to reinstall everything from scratch which took me half a day. Unfortunately the problem is not solved and my Mac keeps crashing when I unplug and replug the screen. It's less frequent than before (Before it was like 75% of the time, now only 25%) but it still ridiculous that it happens 2-3 times per day still. I will try deactivating Touch ID and yes mine was gone several times too... this computer is a disaster


PS: Unlike the other poster I got a 2016 logic board so maybe that's why the problem still exists

Nov 22, 2017 4:13 AM in response to OviOvi

Removing LG manager does not help...

The engineering team send me a message that they have fixed this problem in 10.13.2 beta 4.

I installed beta 4 yesterday and it happened again. I think the problem is the 460 GPU. I had this problem even before with the Sierra. I know other people with the same computer and they have same problem irrespective of the OSthey are running in their system.

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

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

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