Level 1

52 points

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

Top-ranking reply

Rob Designs

Level 1

4 points

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?

View in context

265 replies

tigo13

Level 1

4 points

Mar 29, 2018 9:10 PM in response to Shareef Yousef

they've just released 10.13.4 - perhaps this could be the proper winner....

Jan 10, 2018 7:41 AM in response to kitster101

This interesting in that I have a different problem with a 2016 MBP and LG 5K where the LG would not come up after sleep. After plugging the LG into the left side instead of the right side, the problem seems to have gone away. I am hopeful a future OS update will resolve this issue.

logicito Author

Level 1

52 points

Jan 10, 2018 5:47 PM in response to Coregts

I agree, I think the root cause is in the discrete graphics card.

I've tried connecting to a different monitor using a different interface, USB-C to HDMI vs Thunderbolt 3 to a 4K Dell Monitor, the same situation, it will crash if I connect the MBP to any of them in clamshell mode.

tigo13

Level 1

4 points

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.

tigo13

Level 1

4 points

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.

Coregts

Level 1

12 points

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

tigo13

Level 1

4 points

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.

tigo13

Level 1

4 points

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.

kdupreez

Level 1

8 points

Jan 17, 2018 4:49 PM in response to Coregts

Send it to Edgadget, MacRumors and all the other high footprint tech geek news/blog sites you can think of..

Jan 31, 2018 6:39 PM in response to logicito

My crashes have been 100% during deep sleep (plugging in my 5K while my Mac is hibernating). Wonder if there's a way to turn that off to see if my machine stops crashing.

logicito Author

Level 1

52 points

Feb 4, 2018 9:09 AM in response to tigo13

It is around 12 days when Apple released the latest version of macOS High Sierra 10.13.3, Mayne they fixed the problem with this release?

tigo13

Level 1

4 points

Jan 16, 2018 2:37 AM in response to Rob Designs

hey Rob,

2 things you'd want to consider. 1) at the apple store, the laptop did not crash, as you weren't really in a real-life-case scenario of using the machine. (the laptop crashes when waking it up after connecting it to a USB-C monitor, and the laptop had been in sleep mode for more than an hour). When you select the sleep option on the laptop, it goes to normal sleep initially, then after 1 hour it changes into deep sleep. Further, at home or at the office, you would have multiple applications running simultaneously that would get the graphics card-working. While at the apple store, it may have been just the OS alone.

Connect that LG 5K monitor to a Windows laptop, and it wouldn't crash!

Coregts

Level 1

12 points

Jan 26, 2018 4:08 AM in response to timcooks

Can you please try the issue with the external monitor with your computer?

I have the feeling that the sleep issue and the freeze when opening the clamshell while connected to external monitor are two different things. The first is software issue and the second hardware.

For example, I have the 2016 TB MBP and I only have the issue with the external monitor. Also another 5 laptops of the same model I've tested had only the external monitor problem.

Please check and let us know...

Coregts

Level 1

12 points

Jan 30, 2018 7:09 AM in response to tigo13

The problem exist even after a fresh restart with no application open. This was confirmed also at the Apple Genius Bar that they reproduced the issue after fresh restart. I have a MacBook Pro 2016 with Radeon Pro 460

logicito Author

Level 1

52 points

Jan 31, 2018 7:22 PM in response to Shareef Yousef

This is the statement at the Apple website regarding sleep modes, deep sleep (aka Standby) is only after 3 hours of sleep:

For Mac computers that start up from an internal SSD, macOS includes a deep sleep mode known as Standby Mode.

Mac computers manufactured in 2013 or later enter standby after being in sleep mode for three hours. Earlier models enter standby after just over an hour of sleep. During standby, the state of your session is saved to flash storage (SSD). Then, the power turns off to some hardware systems such as RAM and USB buses.

Standby extends how long a notebook computer can stay asleep on battery power. A notebook with a fully charged battery can remain in standby for up to thirty days without being plugged in to power.

Interesting article:

https://computers.tutsplus.com/tutorials/how-to-hibernate-a-mac--cms-23235

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