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
Question marked as Best reply

Jan 23, 2017 7:12 PM in response to logicito

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.

Feb 3, 2018 9:16 PM in response to logicito

UPDATE 2 - NO CRASHES AFTER 3 DAYS OF COMING BACK FROM APPLE CARE - Replaced logic board, 2 x IO boards and cables..

I have been using with Dell curved 4K Monitor at work and dual dell non-4k at home (one HDI and other DP)


My 2016 MBP with Radeon 460 has not crash in 3 days.


I've continued to do sleep, open clamshell, unplug monitors, re-plug monitors, etc. etc. in various combos of clamshell closed and opened..


I had one small glitch this agternoon where the top right (where the time is) had a red bar.. but I unplugged to monitor and re-plugged it and it went away..


So far no crashes.. And no more "Red and Yellow" screens.. (Prior it used to crash on pretty much all of the above actions)


User uploaded file

Dec 30, 2017 12:01 PM in response to Shareef Yousef

I also have this problem. I posted this on a different thread on dec 20:

I'm also having problems with my configuration:

- MacBook Pro with Touch Bar (15 inches, 2016)

- macOS High Sierra, 10.13.2

- Thunderbolt 3 dock connected to 27' LG UltraFine (USB-C) and 24' Led Cinema Display (Mini DisplayPort), ethernet and keyboard (usb-a)


The mac freezes after sleep most of the times. As a brute force measure, I changed the configuration to enter the sleep mode after 3h of inactivity (on Power adapter). Last night I tested to disconnect only the Mini DisplayPort and, this morning the macbook woke up without problems. I'll check again this night and see if this is reproducible. I have the impression that it has to do with the GPU, so I unchecked the "automatic graphics switching" on the Energy Saver section of the System Preferences.


Now, reading this thread, I'm thinking that the problem is not only due to the Mini DisplayPort connection, but most likely due to the LG 5K display. I'll be able to evaluate different configurations starting on January 8th when I'll be back at the office where I have both displays.

Jan 21, 2018 1:26 AM in response to Rob Designs

I shipped my MBP directly to Apple. I got an email at 7am this past Thursday that they received it. Then another email just 12 hours later that they're shipping it back. I've had it for 24 hours and already had it crash 3 times (they had supposedly replaced the logic board). Beyond aggravating. All I could say is that we all need to open cases for this issue and keep sending them these defective laptops!

Jan 27, 2018 9:03 AM in response to timcooks

I think simply this is a compability problem. The new MacBook Pros doesn’t support external displays, but they are kind of good on their own.


This marketing blurb shows a MacBook Pro connected to *two* 5k monitors. Is there something I'm not getting?


MacBook Pro - Apple


Yes, it's certainly a compatibility problem. I think Apple can ameliorate this by posting best practices and gotchas, much like they do with the battery.


I know that the Hong Kong guys who make some of these monitors don't have the hardware practices that Apple does, that's fine. I want a way to deal with the issue so that I don't keep crashing.

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

Jun 13, 2018 6:14 AM in response to Shareef Yousef

Shareef Yousef wrote:

So it looks like I'm getting consistent crashes every ~20days. Suppose I have to live with that, as that's the Apple of today. Absolutely no focus on quality, just focus on getting emojis and other garbage out the door to make their profit quota!

Or you could file a bug report, so that Apple is aware of your specific configuration of Mac, macOS, video adapter, cable, and monitor.


BugReporter (Free ADC (Apple Developer Connection)) account needed for BugReporter

<http://bugreporter.apple.com>

Anyone can get a free ADC account at:

<https://developer.apple.com/register/index.action>


Telling Apple is better than assuming someone else is looking at this.

Feb 22, 2017 5:26 AM in response to logicito

still having the random hang and crash with my maxed out 2016 15 inch mbp & lg ultrafine 5k.


i'm on the latest public beta of 10.12.4 16E163f


at this point i'm starting to feel really irritated, because my other asus laptop seems to be working super fine with the exact same monitor, albeit only in 4k.


what's going on with apple and mac? i've been using mac for over a decade and never had so many issues in one single product. here're just a few i've encountered:


  • doesn't charge out of the box. It took a full SMC/NVRAM reset to get it working. (scared the shxx out of me cuz i didn't realize it wasn't being charged until the battery's totally drained.)
  • constant random graphic glitches. Still on-going
  • constant wake-sleep freeze/crash. Still on going
  • bluetooth also doesn't seem to be very stable. but compared to other issues, it's not even worth mentioning..

Jan 17, 2017 9:43 AM in response to logicito

Today I had the same problem, I left the laptop connected to the 5K monitor during the night in sleep mode, in the morning without turning on the laptop I will just disconnect it from the 5K monitor and take it to the office, then in the office I will plug it to the standard Apple AC adapter, I do not have an external monitor at the office, open the lid (resume from sleep) to find out is has crashed or had a panic error, I've been able to reproduce the problem two days in row now.

Tue Jan 17 08:17:34 2017


*** MCA Error Report ***

CPU Machine Check Architecture Error Dump (CPU: Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz, CPUID: 0x506E3)

CATERR detected! No MCA data found.


I just installed 10.12.3 Beta 4 on a external drive to test if the new Beta resolves the problem. Without the monitor I haven't had a single crash or panic, everything started when I got the 5K monitor over the weekend.

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.