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

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

kdupreez

Level 1

8 points

Feb 15, 2018 6:30 AM in response to Coregts

I agree - mine doesnt crash anymore after apple-care, but it still does weird stuff.

The external monitor still turns solid blue or picture distorts every now and again when plug it in or wake from sleep. but at least it doesnt crash anymore and I can just unplug and re-plug external and it works.

Although I am starting to get normal wake from sleep hangs and have to hard-reboot.. i.e. clamshell gets closed and go to work, when get to work and I open clamshell there (no external monitor) it wont wake up.. i have to hard-reboot..

Feb 27, 2018 7:14 AM in response to Shareef Yousef

So if I don't use clamshell mode I don't really have any issues with screens going blank, but I do get sleep/wake failures. .

No samples for specified time interval

================================================================

status: 0x40003

Code: 0x340753004000031

Stackshot reason: Watchdog

Model: MacBookPro13,3, BootROM MBP133.0238.B00, 4 processors, Intel Core i7, 2.9 GHz, 16 GB, SMC 2.38f7

Graphics: Intel HD Graphics 530, Intel HD Graphics 530, Built-In

Graphics: Radeon Pro 460, AMD Radeon Pro 460, PCIe, 4 GB

Memory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x80CE, 0x4B3445424533303445422D45474347202020

Memory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x80CE, 0x4B3445424533303445422D45474347202020

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x15A), Broadcom BCM43xx 1.0 (7.77.37.5.1a3)

Bluetooth: Version 6.0.2f2, 3 services, 27 devices, 1 incoming serial ports

Network Service: Home Wired, Ethernet, en10

Network Service: Wi-Fi, AirPort, en0

PCI Card: pci1b73,1100, USB eXtensible Host Controller, Thunderbolt@196,0,0

PCI Card: pci1b73,1100, USB eXtensible Host Controller, Thunderbolt@70,0,0

USB Device: USB 3.0 Bus

USB Device: iBridge

USB Device: USB 3.0 Bus

USB Device: USB3.1 Hub

USB Device: USB 10/100/1000 LAN

USB Device: Hub

USB Device: LG UltraFine Display Camera

USB Device: USB2.1 Hub

USB Device: AirPod Case

USB Device: Hub

USB Device: USB Controls

USB Device: USB Audio

USB Device: USB 3.0 Bus

USB Device: USB3.1 Hub

USB Device: Hub

USB Device: LG UltraFine Display Camera

USB Device: USB2.1 Hub

USB Device: Hub

USB Device: USB Controls

USB Device: USB Audio

Thunderbolt Bus: MacBook Pro, Apple Inc., 23.1

Thunderbolt Device: UltraFine 5K, LG Electronics, 1, 9.4

Thunderbolt Bus: MacBook Pro, Apple Inc., 23.1

Thunderbolt Device: UltraFine 5K, LG Electronics, 3, 9.4

tigo13

Level 1

4 points

Feb 27, 2018 8:27 PM in response to Shareef Yousef

I hadn't actually noticed that option - "prevent computer from sleeping automatically when the display is off". I'll disable it and see whether that crashes the system. If it does, then Apple has a weird-way of remedying the problem by keeping the machine always on; and putting it to sleep when on battery only.

Will let you know if it crashes; and if it does, - I'll re-enable the option of prevent the machine from sleeping!

timcooks

Level 1

4 points

May 22, 2018 4:40 AM in response to Shareef Yousef

After I got a new motherboard, battery and top-case, the fun lasted for a 20 day period, then it came back with a vengeance. Daily reboots when unplugged from external monitor. Sleep/wake issue. It no longer states that the computer crashed, it just looks like it takes a long time to wake up, but by looking at the uptime, you can clearly see that the computer has been rebooted.

I also got an additional bug in the form of my screen flickering. Happens on and off when not using an external monitor.

IMG 0649 - YouTube

Going back to Apple for a second time with this computer.

BobHarris

Level 9

56,819 points

Jun 6, 2018 5:50 AM in response to tigo13

tigo13 wrote:

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.

You can always create a 25 to 50GB partition, install 10.14 in that partition and see how Mojave works. Or install it on an external disk and boot from the external (will be slower, just because it is an external disk, but it should tell you how it works with your external monitors)

Jun 13, 2018 6:30 AM in response to BobHarris

I, and many others on this thread as well as outside this thread, have told Apple many times. I've opened no less then half a dozen tickets in the past year about this issue. Each time I'm told it's a known issue. Apple obviously has "more important" things to do then fix a problem on a $5k setup that they flaunted in their Keynote.

BobHarris

Level 9

56,819 points

Jun 13, 2018 5:55 PM in response to Shareef Yousef

when it comes to bug reports the higher the count the more likely it gets attention. Speaking as a software developer (for several other Fortune 100 computer companies).

Also different reports from different users often times give different information, and sometimes that can give the key bit of information to solve a problem.

BobHarris

Level 9

56,819 points

Jun 14, 2018 5:36 AM in response to Shareef Yousef

Shareef Yousef wrote:

This is Apple we're talking about. Unless it has iOS in the report it gets shuffled to the back of the queue.

If there was just one person writing all the software, then that might be a true statement, but software development groups are not structured that way. So there are developers focused 100% on macOS. Maybe not as many developers as everyone would like, but still there are dedicated teams of developers.

So if you want to get their attention for your specific issue, you need to either be an 800 Pound Gorilla Customer (who can call the CEO or a senior VP directly), or you get lots of fellow users to file lots of bug reports on the same issue, with each user filing their information in a unique way so that all angles of the issue are covered, such that maybe this combination will help the developer assigned to the bug(s) insight on how to craft a working solution.

Again, I'm speaking as someone that has worked in software development for Fortune 100 computer companies for many many years. You want to "Game the System", this is how you can do it.

logicito Author

Level 1

52 points

Oct 16, 2017 4:32 PM in response to Shareef Yousef

I think the problem is in the sleep/wake up process, if I connect/disconnect the MBP in clamshell mode is when it will crash, open will always be fine

Coregts

Level 1

12 points

Oct 31, 2017 5:54 PM in response to Doug F.

Same computer running OSX 10.13.1.

If connected to the LG 5K and open the clamshell the Macbbok pro becomes a brick!

I really started to think that the 460 AMD card is defective

Coregts

Level 1

12 points

Nov 5, 2017 3:05 AM in response to Simmenfl

Both sides crash. It is the same GPU regardless of the side you plug it...

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