Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

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

Jun 23, 2017 12:38 AM in response to logicito

It's been 5 months since this article was written.

Has anyone got it fixed?


I recently bought LG 27UD88 for my MacBook pro 13" with touch bar.

And I'm having daily kernel panics with USB-C connections.

I guess there is a common problem for USB-C monitor with charging.



Fri Jun 23 11:13:40 2017



*** Panic Report ***

panic(cpu 1 caller 0xffffff80127ff2dd): Kernel trap at 0xffffff7f94f04b92, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0x00000000000000dc, CR3: 0x0000000452746033, CR4: 0x00000000003627e0

RAX: 0x0000000000000000, RBX: 0xffffff80352f8600, RCX: 0x00000000c4082030, RDX: 0xffffff81afa3d000

RSP: 0xffffff92132f3950, RBP: 0xffffff92132f3960, RSI: 0x00000000041f052b, RDI: 0x0000000000080000

R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000001fd3

R12: 0xffffff81afa39000, R13: 0x00000000041f0000, R14: 0x000000000fdf1fd3, R15: 0x00000000041f052b

RFL: 0x0000000000010206, RIP: 0xffffff7f94f04b92, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0x00000000000000dc, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 0



Backtrace (CPU 1), Frame : Return Address

0xffffff92132f35e0 : 0xffffff80126ea53c

0xffffff92132f3660 : 0xffffff80127ff2dd

0xffffff92132f3840 : 0xffffff801269b593

0xffffff92132f3860 : 0xffffff7f94f04b92

0xffffff92132f3960 : 0xffffff7f94f5192b

0xffffff92132f39c0 : 0xffffff7f94f5124b

0xffffff92132f3a10 : 0xffffff7f94f24378

0xffffff92132f3ae0 : 0xffffff7f93c8cead

0xffffff92132f3b20 : 0xffffff8012ce3371

0xffffff92132f3b80 : 0xffffff8012cec391

0xffffff92132f3cc0 : 0xffffff80127be2f8

0xffffff92132f3dd0 : 0xffffff80126ef7bc

0xffffff92132f3e30 : 0xffffff80126cbfb1

0xffffff92132f3e80 : 0xffffff80126e0777

0xffffff92132f3f10 : 0xffffff80127eb1d8

0xffffff92132f3fb0 : 0xffffff801269bdb6

Kernel Extensions in backtrace:

com.apple.iokit.IOGraphicsFamily(515.3)[A423518D-758D-3021-A111-A59F44D760A8]@0 xffffff7f93c7f000->0xffffff7f93cbafff

dependency: com.apple.iokit.IOPCIFamily(2.9)[BD9FCDEF-30CB-3911-B247-EE51DD069C76]@0xffffff 7f92fbe000

com.apple.driver.AppleIntelSKLGraphicsFramebuffer(10.2.5)[B8793C18-FD78-3FF2-85 0D-524C18390510]@0xffffff7f94f03000->0xffffff7f950cdfff

dependency: com.apple.iokit.IOPCIFamily(2.9)[BD9FCDEF-30CB-3911-B247-EE51DD069C76]@0xffffff 7f92fbe000

dependency: com.apple.iokit.IOACPIFamily(1.4)[4F7FB6AD-2498-3F71-827C-ED7AA4BF2511]@0xfffff f7f93292000

dependency: com.apple.iokit.IOAcceleratorFamily2(311.13)[4E8ED752-4109-3D72-9C13-D26BD3B108 CF]@0xffffff7f94e58000

dependency: com.apple.iokit.IOReportFamily(31)[B14DC3D3-7250-3DA3-BF50-C666EBEDAF4C]@0xffff ff7f93bbd000

dependency: com.apple.AppleGraphicsDeviceControl(3.14.47)[396A06E0-FB78-3045-AD37-F21ED2172 191]@0xffffff7f94ef7000

dependency: com.apple.iokit.IOGraphicsFamily(515.3)[A423518D-758D-3021-A111-A59F44D760A8]@0 xffffff7f93c7f000

Jul 10, 2017 12:11 PM in response to logicito

I too have issues with the MacBook Pro 2016 15" AMD 460 model, it often crashes with kernel and/or gpuRestart System Reports. I've had several replacement laptops thus far.


The problem is being blamed by Apple on my software, despite happening out of the box with sod all on the machine.


This is with the latest 10.12.5 release.


Issues include:


(a)

Total crash and lock up requiring hard power off/on to reboot


(b)

Soft Crash where the machine does self-restart and reload the OS without me doing anything


(c)

dull red images on in-built display when opening lid with monitors connected to try and resolve (a) or (b) - but not always red or displaying anything


I have many other issues beyond these monitor/crash issue with this model, but wanted to add my voice to this issue.

Aug 3, 2017 7:02 PM in response to damon.youngjin

From my recent observation,

It's likely to crash when I connect USB-C to USB-C cable or USB-C to DP cable on the right side USB-C port.

I'll be only using the left side for monitors to see if the issue recreated.


I think there might be a defect with the I/O bus handling the right side peripherals or MacOS software.

Is there any member of Apple technical support team reads this thread?


My Mac is 2016 MBP 13" with touch bar.

Sep 25, 2017 6:05 AM in response to damon.youngjin

I've been having this same issue, not with a monitor, but with the Other World Computing Thunderbolt 3 dock. I've found that I only get the crash when I plug in my iphone or anything else that requires charging. As I kept testing, I've noticed it happens with ANY USB-C adapter that I plug my phone into the charge. The USB3 dock itself does not crash the system (even though it draws power), but anything I plug into it to charge starts a crash if I sleep the computer.


I took it in once already to the Apple store and they told me it was a software issue, so I erased the machine and did a clean install of the software with the same results. I'm on 10.12.6.

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 6, 2017 8:21 PM in response to patballosu

As soon as I brought mine in and explained the problem, and told them I have been having it since the day I purchased the laptop (10 months old) and that I have tried all the macOS version, plus replaced the 5K monitor four times, they immediately said they will replace the logic board, when I asked what version they said 2017, currently is in service, so I cannot confirm what version they will actually install,

Nov 21, 2017 11:35 AM in response to logicito

I think that I found the problem.


My MacBook Pro (15",early 2016, with Touch Bar / High Sierra 10.13.1) has deleted my Touch IDs. Its the third time now that it happened - did somebody else have this problem? Anyway... since my Touch ID are again deleted it seems that my MacBook don't crash anymore in combination with my UltraFine 5k (LG Screen Manager 2.08 / Software Version of Monitor 3.04.....).


So just deactivate your Touch ID and you will have no longer this issue. I report this bug to apple.
And I also write an post at macrumors -> https://forums.macrumors.com/threads/lg-ultrafine-5k-issues-bugs.2024679/page-30 #post-25500911

Nov 21, 2017 12:22 PM in response to Shareef Yousef

After 1 year of issues I took my MBP to the Apple Store, they sent the laptop to repair for 1 week, it came back with scratches and marks, I complained and they said that's normal, they replaced the logic board and other components, the problem is still the same, I no longer have time to keep doing this.


I just purchased the new Surface Book 2 laptop and I will move away from Apple, I am extremely disappointed with this product (MacBook Pro) and their lack of accountability and good service. I have assumed that the 5K invested in the laptop and accessories are gone.

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.

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.