MacBook Pro 15" (2016) Crashing while connecting/disconnecting the LG 5K Monitor

Discussion in 'MacBook Pro' started by brosenz, Jan 16, 2017.

  1. brosenz macrumors regular

    brosenz

    Joined:
    Apr 26, 2011
    #1
    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/XPCServices/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/XPCServices/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 [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/XPCServices/com.apple.AmbientDisplayAgent.xpc/Contents/MacOS/com.apple.AmbientDisplayAgent
    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
     
  2. olivelawn, Jan 16, 2017
    Last edited: Jan 16, 2017

    olivelawn macrumors newbie

    Joined:
    Mar 6, 2009
    Location:
    San Francisco
    #2
    I am having a slew of problems with my '16 13" MBP connected to to my LG Ultrafine 5K as well, including 2 kernel panics (see below). Are you having the same distortion problems as I am when you wake from sleep?



    Here is my crash info:


    Code:
    Anonymous UUID:       35000306-1902-8864-3265-1B32A08A1A23
    
    Sun Jan  8 17:48:14 2017
    
    *** MCA Error Report ***
    CPU Machine Check Architecture Error Dump (CPU: Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz, CPUID: 0x406E3)
    CATERR detected! No MCA data found.
    
    
    *** Device Tree ***
    {
        "pcie_cfg_base" : 3758096384,
        "pci_devices" :
        {
            "0x0" : "MCHC@0",
            "0x10000" : "IGPU@2",
            "0xa0000" : "XHC1@14",
            "0xaa000" : "pci8086,9d62@15,2",
            "0xa8000" : "pci8086,9d60@15",
            "0xb0000" : "IMEI@16",
            "0xe0000" : "RP01@1C",
            "0xe4000" : "RP05@1C,4",
            "0x100000" : "RP01@1C/IOPP/SSD0@0",
            "0xe8000" : "RP09@1D",
            "0xe9000" : "RP10@1D,1",
            "0xf0000" : "URT0@1E",
            "0x300000" : "RP10@1D,1/IOPP/CMRA@0",
            "0xf3000" : "SPI1@1E,3",
            "0xfa000" : "PMCR@1F,2",
            "0xfb000" : "HDEF@1F,3",
            "0xf8000" : "LPCB@1F",
            "0xfc000" : "SBUS@1F,4",
            "0x400000" : "RP05@1C,4/IOPP/UPSB@0",
            "0x200000" : "RP09@1D/IOPP/ARPT@0",
            "0x500000" : "RP05@1C,4/IOPP/UPSB@0/IOPP/DSB0@0",
            "0x508000" : "RP05@1C,4/IOPP/UPSB@0/IOPP/DSB1@1",
            "0x510000" : "RP05@1C,4/IOPP/UPSB@0/IOPP/DSB2@2",
            "0x520000" : "RP05@1C,4/IOPP/UPSB@0/IOPP/DSB4@4",
            "0x8300000" : "RP05@1C,4/IOPP/UPSB@0/IOPP/DSB1@1/IOPP/UPS0@0",
            "0x8408000" : "RP05@1C,4/IOPP/UPSB@0/IOPP/DSB1@1/IOPP/UPS0@0/IOPP/pci-bridge@1",
            "0x8500000" : "RP05@1C,4/IOPP/UPSB@0/IOPP/DSB1@1/IOPP/UPS0@0/IOPP/pci-bridge@1/IOPP/pci1b73,1100@0",
            "0x600000" : "RP05@1C,4/IOPP/UPSB@0/IOPP/DSB2@2/IOPP/XHC2@0",
            "0x700000" : "RP05@1C,4/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0"
        },
        "device_mmio" :
        {
            "PCI0@0" :
            [
                { "a" : 3320, "s" : 8 }
            ],
            "PCI0@0/AppleACPIPCI/IGPU@2" :
            [
                { "a" : 548145201152, "s" : 16777216 },
                { "a" : 547876765696, "s" : 268435456 }
            ],
            "PCI0@0/AppleACPIPCI/XHC1@14" :
            [
                { "a" : 548162043904, "s" : 65536 }
            ],
            "PCI0@0/AppleACPIPCI/pci8086,9d60@15" :
            [
                { "a" : 548162142208, "s" : 4096 }
            ],
            "PCI0@0/AppleACPIPCI/pci8086,9d62@15,2" :
            [
                { "a" : 548162138112, "s" : 4096 }
            ],
            "PCI0@0/AppleACPIPCI/IMEI@16" :
            [
                { "a" : 548162134016, "s" : 4096 }
            ],
            "PCI0@0/AppleACPIPCI/RP01@1C/IOPP/SSD0@0" :
            [
                { "a" : 2456813568, "s" : 16384 }
            ],
            "PCI0@0/AppleACPIPCI/RP05@1C,4/IOPP/UPSB@0/IOPP/DSB0@0/IOPP/NHI0@0" :
            [
                { "a" : 2459959296, "s" : 262144 },
                { "a" : 2460221440, "s" : 4096 }
            ],
            "PCI0@0/AppleACPIPCI/RP05@1C,4/IOPP/UPSB@0/IOPP/DSB2@2/IOPP/XHC2@0" :
            [
                { "a" : 2458910720, "s" : 65536 }
            ],
            "PCI0@0/AppleACPIPCI/RP09@1D/IOPP/ARPT@0" :
            [
                { "a" : 2453667840, "s" : 32768 },
                { "a" : 2449473536, "s" : 4194304 }
            ],
            "PCI0@0/AppleACPIPCI/RP10@1D,1/IOPP/CMRA@0" :
            [
                { "a" : 2455764992, "s" : 65536 },
                { "a" : 547608330240, "s" : 268435456 },
                { "a" : 2454716416, "s" : 1048576 }
            ],
            "PCI0@0/AppleACPIPCI/URT0@1E" :
            [
                { "a" : 548162129920, "s" : 4096 }
            ],
            "PCI0@0/AppleACPIPCI/SPI1@1E,3" :
            [
                { "a" : 548162125824, "s" : 4096 }
            ],
            "PCI0@0/AppleACPIPCI/PMCR@1F,2" :
            [
                { "a" : 2458009600, "s" : 16384 }
            ],
            "PCI0@0/AppleACPIPCI/HDEF@1F,3" :
            [
                { "a" : 548162109440, "s" : 16384 },
                { "a" : 548161978368, "s" : 65536 }
            ],
            "PCI0@0/AppleACPIPCI/SBUS@1F,4" :
            [
                { "a" : 548162146304, "s" : 256 }
            ],
            "DMAC" :
            [
                { "a" : 0, "s" : 32 },
                { "a" : 129, "s" : 17 },
                { "a" : 147, "s" : 13 },
                { "a" : 192, "s" : 32 }
            ],
            "FWHD" :
            [
                { "a" : 4278190080, "s" : 16777216 }
            ],
            "IPIC" :
            [
                { "a" : 32, "s" : 2 },
                { "a" : 36, "s" : 2 },
                { "a" : 40, "s" : 2 },
                { "a" : 44, "s" : 2 },
                { "a" : 48, "s" : 2 },
                { "a" : 52, "s" : 2 },
                { "a" : 56, "s" : 2 },
                { "a" : 60, "s" : 2 },
                { "a" : 160, "s" : 2 },
                { "a" : 164, "s" : 2 },
                { "a" : 168, "s" : 2 },
                { "a" : 172, "s" : 2 },
                { "a" : 176, "s" : 2 },
                { "a" : 180, "s" : 2 },
                { "a" : 184, "s" : 2 },
                { "a" : 188, "s" : 2 },
                { "a" : 1232, "s" : 2 }
            ],
            "MATH" :
            [
                { "a" : 240, "s" : 1 }
            ],
            "LDRC" :
            [
                { "a" : 46, "s" : 2 },
                { "a" : 78, "s" : 2 },
                { "a" : 97, "s" : 1 },
                { "a" : 99, "s" : 1 },
                { "a" : 101, "s" : 1 },
                { "a" : 103, "s" : 1 },
                { "a" : 128, "s" : 1 },
                { "a" : 146, "s" : 1 },
                { "a" : 178, "s" : 2 },
                { "a" : 65535, "s" : 1 },
                { "a" : 6144, "s" : 128 },
                { "a" : 2048, "s" : 128 }
            ],
            "RTC" :
            [
                { "a" : 112, "s" : 8 }
            ],
            "TIMR" :
            [
                { "a" : 64, "s" : 4 },
                { "a" : 80, "s" : 4 }
            ],
            "SMC" :
            [
                { "a" : 768, "s" : 32 },
                { "a" : 4277141504, "s" : 65536 }
            ],
            "EC" :
            [
                { "a" : 98, "s" : 1 },
                { "a" : 102, "s" : 1 }
            ],
            "PDRC" :
            [
                { "a" : 4275109888, "s" : 32768 },
                { "a" : 4275142656, "s" : 4096 },
                { "a" : 4275146752, "s" : 4096 },
                { "a" : 3758096384, "s" : 268435456 },
                { "a" : 4244635648, "s" : 25165824 },
                { "a" : 4275175424, "s" : 131072 },
                { "a" : 4275634176, "s" : 16384 },
                { "a" : 4275326976, "s" : 307200 },
                { "a" : 4278190080, "s" : 16777216 },
                { "a" : 4276092928, "s" : 1048576 }
            ],
            "MEM2" :
            [
                { "a" : 536870912, "s" : 2097152 },
                { "a" : 1073741824, "s" : 2097152 }
            ]
        }
    }
    
    
    Model: MacBookPro13,1, BootROM MBP131.0205.B07, 2 processors, Intel Core i5, 2 GHz, 16 GB, SMC 2.36f96
    Graphics: kHW_IntelIrisGraphics540Item, Intel Iris Graphics 540, Built-In
    Memory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 1867 MHz, 0x802C, 0x4D5435324C31473332443450472D31303720
    Memory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 1867 MHz, 0x802C, 0x4D5435324C31473332443450472D31303720
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x159), Broadcom BCM43xx 1.0 (7.21.171.68.1a4)
    Bluetooth: Version 5.0.2f4, 3 services, 27 devices, 1 incoming serial ports
    Network Service: USB 10/100/1000 LAN, Ethernet, en5
    Network Service: Wi-Fi, AirPort, en0
    PCI Card: pci1b73,1100, USB eXtensible Host Controller, Thunderbolt@133,0,0
    USB Device: USB 3.0 Bus
    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: Hub
    USB Device: USB Controls
    USB Device: USB Audio
    Thunderbolt Bus: MacBook Pro, Apple Inc., 12.17
    Thunderbolt Device: UltraFine 5K, LG Electronics, 3, 9.4
    
     
  3. rklinkhammer macrumors newbie

    rklinkhammer

    Joined:
    Nov 23, 2016
    #3
    I have noticed some similar quirky behavior related to the sleep functions independent of clamshell mode. They do seem related to doing a manual sleep rather than just letting the machine sleep without intervention. Have not rigorously investigated but avoiding manual sleep seems to be helpful. I have 15", 460, LG 5k. I also have a bunch of peripherals connected, including TM disk. I suspect it's hub related but who knows.
     
  4. brosenz thread starter macrumors regular

    brosenz

    Joined:
    Apr 26, 2011
    #4
    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.
     
  5. brosenz thread starter macrumors regular

    brosenz

    Joined:
    Apr 26, 2011
    #5
    I think the problem is with the sleep functionality, there is something wrong there, if you combine that with the LG 5K monitor things get ugly, right now to mitigate the issue I always connect/disconnect the 5K monitor with the laptop turned on, never in sleep mode until this issue will be fixed, it is a guaranteed crash or panic if the MBP is sleeping.
    --- Post Merged, Jan 17, 2017 ---
    I tested yesterday, I do not have this problem, but I have a MBP 15" with an AMD GPU, completely different hardware,
     
  6. sohilpandya macrumors member

    sohilpandya

    Joined:
    Nov 26, 2013
    Location:
    London
    #6
    I am having a similar issue with the 15" and a 4K display (Iiyama).

    I don't even get a kernel panic, my screen doesn't turn on and I have to restart the laptop everytime! I'm taking it to the apple store on Monday. (I've also been having bluetooth issues (disconnects often))
     
  7. spacebro macrumors 6502

    Joined:
    Oct 1, 2015
    #7
    So much negativity. Using external displays isn't really a common use-case. You can't complain when you want to do a weird thing and it doesn't work flawlessly.
     
  8. sohilpandya macrumors member

    sohilpandya

    Joined:
    Nov 26, 2013
    Location:
    London
    #8
    I don't know what you use your laptop for, but unfortunately, my job needs a monitor on a daily basis. Also never had a problem on an older mac, just this one....
     
  9. kartcrg macrumors member

    kartcrg

    Joined:
    Dec 7, 2016
    Location:
    Los Angeles
    #9
    The UltraFine monitors are literally made for, & only work with, the new MacBook Pros.. It's a well recognized & fairly common use-case.
     
  10. RivalR macrumors newbie

    Joined:
    Jan 13, 2017
    #10
    Exotic or not, as an officially documented feature one may expect this to 'just work': https://support.apple.com/en-us/HT201834 . It has been a macbook (pro) feature for a very long time.

    I have a similar problems, but with another monitor connected over thunderbolt (usb-c), the LG 38UC99, see: New LG 38UC99-W compatibility with Macbook Pro?

    I have the macbook pro 15" 2016 (460) model, currently awaiting word from AppleCare as well since they've collected information form my laptop last week.
     
  11. spacebro macrumors 6502

    Joined:
    Oct 1, 2015
    #11
    I'm sorry, I'm just trolling because I have a max 2015 MacBook pro (and 2012 before that) and I have these display bugs. At first I was confident apple would fix it eventually but now I think they might only fix it for the 2016 if at all. I use it in clamshell mode 99% of the time, so its a common use case for me. In 2012 apple pitched the MacBook pro as a desktop replacement but they have not taken good care of their laptop as desktop customers and I'm bitter at how much of my money they got.
     
  12. DGoethe macrumors newbie

    Joined:
    Jan 28, 2017
    #12
    I have the non-touchbar MacBook Pro 2016 and the Ultrafine 4K. I had similar issues when using either clamshell mode or the Ultrafine as the primary monitor (by going into System Preferences → Monitors → arrangement and dragging the white bar on top onto the external monitor). When I have the internal monitor as main monitor, the issue does not happen for me! It seems that it is happening if and only if the Ultrafine is set as the primary one.
     
  13. jozero macrumors regular

    Joined:
    Sep 14, 2009
    #13
    Damn, I really was hoping 10.12.3 fixed the external monitor crash issue.

    I still get the hard crash. I have a MacBook 13" and the new LG 4K. I have to disconnect the monitor, hard power down the MacBook, and then restart.

    10.12.3 did NOT fix the issue for me.
     
  14. stevoid macrumors newbie

    stevoid

    Joined:
    Jan 28, 2017
    #14
    Non a common thing? Really, are you a moron? People use external monitors all the time and when Apple touts they "worked" with LG in the design, they clearly meant for people to buy the 5k monitor and use it. Get with it.
     
  15. sguser macrumors regular

    Joined:
    Aug 12, 2010
    #15
    Same issue here with 13'' and LG 4K. It's my second 2016 13''. The first one had the same issue.
     
  16. spacebro macrumors 6502

    Joined:
    Oct 1, 2015
    #16
    Calm down, I've been dealing with this bug for a year and a half and I'm mad as hell. Apple cannot be trusted to provide equipment that "just works" even though they charge a **** ton of money. All the bugs in the 2015 MacBook I assumed would be fixed by now are not fixed- they've only added new bugs. I built a PC for less than 1/4th the price that kicks the **** out of any mac that has ever existed. OS X isn't that good anymore with all its bugs when now its windows 10 that "just works". I hated on microsoft for many years but that was immature of me because things have changed. I was a big apple fan and bought max apple everything, even use a mac mini AND apple tv on my tv. I thought apple was the most high tech company so I used their stuff whenever possible. Still no 4k on both the apple tv and the mac mini?! Why is apple keeping me in the 1080p stone age? Even if they release 4k apple tv and 4k mac mini tomorrow, apple cannot be trusted anymore to release new technology in a timely manner. Old people, children, non-tech people are all buying 4k tvs but not apple fans! Thats just negligence or something. Whatever. I'm finished with apple and selling all of this garbage.
     
  17. m7a7r2c3 macrumors newbie

    Joined:
    Jan 16, 2017
    #17
    same problem here with MBP TB 13" and a 4K Samsung Displays (actually two times, as my gf has the same setup and it happens for her too). Macbook will randomly restart after waking up from sleep and connected to the display. Usually no warning at all.
     
  18. BWhaler macrumors 68020

    BWhaler

    Joined:
    Jan 8, 2003
    #18
    I have same problem with crash with mbp13 and 5k lg display

    Last week I unplugged my MVP to go to meeting with CEO. Laptop just blank screen. Had to reboot looking like idiot.

    I get Apple doesn't care about mac anymore. Mac team folded into iOS team. But either stop selling it or make it work. Apple is pretty pathetic nowadays, and I'm sick of Tim talking about this amazing pipeline when they ship crap that doesn't work.
     
  19. nycgeo macrumors member

    nycgeo

    Joined:
    Apr 12, 2005
    Location:
    Brooklyn
    #19
    I switched to using DisplayPort (from HDMI) and my sleep/wake problems in clamshell mode went away. See if your monitor has the option and try it. I bought a DisplayPort to USB-c cable from amazon.
     
  20. planetf1 macrumors 6502

    planetf1

    Joined:
    Aug 8, 2014
    Location:
    Hampshire, UK
    #20
    Continuing to get lots of crashes here on MBP 2016 15 TB.
    Lots = avg 1/day. Sometimes escape ok. Have had 3 some days
    Consistent offender from the .panic is com.apple.kext.AMDRadeonX4100(1.6)

    The crash occurs when connecting/disconnecting
    But also when left connected and going for a 15-20 min cup of coffee
    Happens both at home on a USB-C connected LG 27UD88 (with power, downstream usb) and via a USB-C-HDMI startech adaptor to an old Lenovo HD display.
     
  21. kingjames1970 macrumors regular

    kingjames1970

    Joined:
    Mar 18, 2008
    Location:
    Hampshire, UK
    #21
    Just adding my voice to the crowd. So incredibly frustrating that it was another plus in the getting an iMac Pro column. Constantly have to unplug and plug back in with fingers crossed. Now I use my 2016 MBP for home stuff and purely on the go, can't be trusted in the middle of a project not to constantly crash.
     
  22. Samuelsan2001 macrumors 604

    Joined:
    Oct 24, 2013
    #22
    I wish people would stop using hdmi with monitors it’s just rubbish, the support is rubbish, the drivers don’t work well adaptors and connectors are poor quality and software generally hates it.
    Use a display port cable wherever possible it’s that simple. Never buy a monitor without a display port input especially a 4K or 5k and always use a display port cable, that’s a usb c to display port cable for a new MacBook or MacBook Pro, and a Mini DisplayPort to DisplayPort for anything with a thunderbolt 1 or 2.


    To be honest your usb c to hdmi for your 1080p monitor should be fine but even then I would buy a cable solution rather than an adapter.
     
  23. planetf1 macrumors 6502

    planetf1

    Joined:
    Aug 8, 2014
    Location:
    Hampshire, UK
    #23
    Actually when I said HDMI in fact the monitor I se 2nd after my USB-C one is indeed mini-DP :) Anyway this issue occurs regardless of connectors …

    Though at home USB-C offers much more convenience over either DP or HDMI - such as integrated charging, and downstream USB(2)
     
  24. scott_donald, Jan 25, 2018
    Last edited: Jan 26, 2018

    scott_donald macrumors regular

    Joined:
    Nov 2, 2016
    #24
    well since the update last night to 10.13.3(fresh install) my computer has lasted 16 hours of use with no crashes...

    do have sleep turned off on the SSD but put the monitors to sleep when I am not using the computer... I had it turned off all night...

    I am expecting a crash tomorrow though...
     
  25. brosenz thread starter macrumors regular

    brosenz

    Joined:
    Apr 26, 2011
    #25
    What happened today? No crash?
    --- Post Merged, Jan 27, 2018 ---
    Is there any confirmation if the issue has been resolved in the 2017 MacBook Pro?
     

Share This Page