630      iPhone_iPad_Mac_apple

MacBook Pro 15" (2016) Crashing while connectin...

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

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.

I have this issue too! If I disconnect the LG 5K monitor, and then later open my 15" MacBook Pro (Late 2016), a message is displayed that informs me that the system crashed, and will reboot in a few seconds. Very Frustrating!

I have disabled Power Nap and Wifi access while in sleep mode while connected to the AC adapter and the problem has been almost 100% resolved. I've also read that the latest 10.12.3 Beta 4 solve the problem as well. You can try any of them and see if it works for you, probably the first option is the most straight forward.

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.

10.12.3 released today is the solution, have you tried?

Same issue for me. Still happening after 10.12.3

• Model Name: MacBook Pro
• Model Identifier: MacBookPro13,3
• Processor Name: Intel Core i7
• Processor Speed: 2.9 GHz
• Number of Processors: 1
• Total Number of Cores: 4
• L2 Cache (per Core): 256 KB
• L3 Cache: 8 MB
• Memory: 16 GB

I tried the 10.12.3, now the monitor seems to work better but the bluetooth keyboard is not working, it hangs, and keeps repeating characters when the LG 5K display is attached.

Aditional to last comment, a big mouse cursor keeps in the display

I upgraded to the new OS that is supposed to fix this, seems to have fixed the crash that was always occuring after wake from sleep.

However now the monitor and the laptop will just intermittently start to flicker and come on and off after a few minutes, every few minutes, making it unusable.  THis happens for a while then stops.  Computer seems to be stable after a reboot for a while, but the longer you're up and running (God forbid you stop working and let a power management or screen saver go active), then everything starts to go to ****.

It's almost unusable after a period with the monitors going on and off.  It acts like the monitor is losing connection or similar, or a graphic mode is changing, constantly, on it's own.  Sometimes the LG UltraFine will go blank and no amount of unplugging it and plugging it back in will help - it stays "off" and "disconnected" until a reboot.

Basically the LG UltraFine is a DISASTER.  Whoever put this out in it's current condition as the ONLY Thunderbolt 3 "made for MacBook Pro" monitor should be shot.  I miss the Apple Thunderbolt displays.  My old Macbook 2015 Retina and and Thunderbolt display were rock solid.  Now i feel like i've returned to the world of Microsoft Windows.

I finally bit the bullet and called support, and they seem to know things are pretty majorly screwed up as you get escalated to a manager that tries to troubleshoot and says they already know of issues and also say the LG can't be near a WiFI router (where is my WiFi router they ask?)   Crazy.   I don't have a wi-fi router near, but i have a WiFI phone, I  have fancy studio (audio) monitors next to it (as anyone would in a studio, and as i did with Thunderbolt Display with no issue).

If the LG can't be near office equipment without these issues, then they have a major problem on their hands not just with software, but with hardware.

Now not sure if I should wait around for a hopeful fix or get these back to the store for a refund (i bought 2).

2016 MacBook Pro's Crash daily when connected to the LG 5k Ultrafine display. I find my Macbook (13") will crash while working, while sleeping, with the clamshell open or closed, the cause is consistently random but only when connected to this display. I've tried SMC & PRAM Reset, Clean OS install (10.12.3), etc, etc. Feels like a thunderbolt or video card issue but clearly a interrelated software bug in MacOS. So frustrating for brand new excessively priced hardware. Multiple calls with Apple support but no answers. At this point I'm fully ready to abandon 25 years of Mac life for an inexpensive windows 10 setup.  I mean if it's gonna be a buggy crashing time wasting nightmare anyways, especially on the best of what Apple has to offer, there is zero reason to stay on the platform.

I have the 13" new MacBook Pro and every single time I disconnect the thunderbolt 3 cable from my LG 5K the laptop hangs on a black screen with just the touch bar illuminated, but unresponsive. It takes a full hard reset to reboot the laptop each time.

How has apple not tested this thing with its new laptops!?

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

Same issue except my monitor is an Acer GN246HL. The laptop is a brand new 13" MacBook Pro. The monitor never shows anything and the laptop does not detect it. If I power the monitor off and then turn it back on the kernel will panic and the laptop crashes. Awesome.

I will note that I have essentially the same problems as noted here, except I have a different USB-C monitor, a 38"

Acer XR382CQK. I have the (2016) 13" Touch Bar MBP, maximally configured.

In /Library/Logs/DiagnosticReports today I have three Kernel GPU Restart files from earlier today, when the laptop went totally insane and had to be rebooted due to graphics going crazy.

Additionally, the laptop sometimes stops getting power from the monitor until you switch it to a different port.

Finally, the laptop cannot wake from sleep while connected to the USB-C monitor. I have two "Sleep Wake Failures" in the log directory from earlier today. One of them literally has nothing in it except something about a Watchdog. It's the shortest diagnostic report ever.

What a shame.

I'm going to try a USB-C to DisplayPort cable and see if that fixes it, but that sort of breaks my intended workflow which uses three Thunderbolt 3 connections and a monitor/power connection. I guess I will have to daisy chain some more.

I would love to hear of a fix.

最后更新：2017-10-17 07:56:08

  上一篇： how do i find the display serial number

  下一篇： Folder View Options