Macbook Pro crashes when using external screen

Discussion in 'MacBook Pro' started by kevers89, Feb 13, 2018.

  1. kevers89 macrumors newbie

    Feb 13, 2018
    I just got back my 15” Macbook Pro with Retina display (mid 2012) from a battery replacement. At first I was really happy, but that only lasted for a short time. When I connected my LG display to my Macbook via HDMI my Macbook suddenly crashed. Black screen.

    Now, every time I connect any display to my Macbook is crashes after a few minutes. Black screen. And the weird thing is it only happens when I use the extended screen option, the sync screen option works just fine.

    I already did a OSX reinstall, tried resetting SMC and NVRAM...

    I really hope this is a software issue and I don’t have to bring back my Macbook again and miss it for a few weeks.

    I really appreciate any help.


    Tue Feb 13 20:41:37 2018

    *** Panic Report ***
    panic(cpu 6 caller 0xffffff7faac339e9): "GPU Panic: mux-regs 5 0 a0 d9 9 8 severity 3 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 9:f power-state 0 3D idle HDA busy : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0xffffff913e451000 0x0e7150a2, D0, P3/4\n"@/BuildRoot/Library/Caches/
    Backtrace (CPU 6), Frame : Return Address
    0xffffff80368fb1f0 : 0xffffff802944f606
    0xffffff80368fb240 : 0xffffff802957c654
    0xffffff80368fb280 : 0xffffff802956e149
    0xffffff80368fb300 : 0xffffff8029401120
    0xffffff80368fb320 : 0xffffff802944f03c
    0xffffff80368fb450 : 0xffffff802944edbc
    0xffffff80368fb4b0 : 0xffffff7faac339e9
    0xffffff80368fb510 : 0xffffff7faa0e467e
    0xffffff80368fb5d0 : 0xffffff7faa1b65be
    0xffffff80368fb630 : 0xffffff7faa1b6668
    0xffffff80368fb660 : 0xffffff7fac287198
    0xffffff80368fb6b0 : 0xffffff7fac286856
    0xffffff80368fb720 : 0xffffff7faa1e161e
    0xffffff80368fb740 : 0xffffff7faa0eb2f4
    0xffffff80368fb7f0 : 0xffffff7faa0e7f4e
    0xffffff80368fb9f0 : 0xffffff7faa0e9e05
    0xffffff80368fbae0 : 0xffffff7faa0797ad
    0xffffff80368fbcc0 : 0xffffff7faa077e3d
    0xffffff80368fbce0 : 0xffffff7fac6afa53
    0xffffff80368fbdb0 : 0xffffff7fac6af592
    0xffffff80368fbe10 : 0xffffff7fac6af966
    0xffffff80368fbe30 : 0xffffff8029a95ecc
    0xffffff80368fbea0 : 0xffffff8029a95df6
    0xffffff80368fbed0 : 0xffffff8029488ec4
    0xffffff80368fbf40 : 0xffffff80294889b5
    0xffffff80368fbfa0 : 0xffffff80294004f7
    Kernel Extensions in backtrace:[B4DB1D7A-D4DE-3965-94DC-05CE8B9F2802]@0xffffff7faac25000->0xffffff7faac37fff

    BSD process name corresponding to current thread: kernel_task

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64
    Kernel UUID: 18D901F1-4A03-3FF1-AE34-C26B2732F13C
    Kernel slide: 0x0000000029000000
    Kernel text base: 0xffffff8029200000
    __HIB text base: 0xffffff8029100000
    System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)

    System uptime in nanoseconds: 727409367508
    last loaded kext at 245325792331: 1.10 (addr 0xffffff7facbe8000, size 69632)
    last unloaded kext at 596075003576: 900.4.1 (addr 0xffffff7fabeb5000, size 12288)
    loaded kexts: 1.9.5d0 1.70 110.23.30 2.7.0d0 1.0.0 3.0 131 280.12 3.16.2 280.12 1 1.0.1 3.6.4 6.0.2f2 10.2.8 1 7.0.0 10.3.0 1 3.1.1 1.0.0 3.1 3.16.2 3.16.21 10.3.0 1 211 4.0.0 1.5.3 254 254 748.41.3 407.30.1 1.0.0d1 40 1.0.0 1.7.6 1220.18.1a2 329 161.0.0 6.1 2.0 1.8 2.1 6.1 1.7 220.0.0 183 8 3 1 220.0.0 1.0 280.12 526 1.0 11 10.2.8 10.2.8 3.16.2 280.12 280.12 206.5 1.2.0 1.0.14d1 3.16.21 376.6 209.2.2 3.16.21 1.0.0 1.0.0 6.0.0d8 1.1.0 517.22 1.0.18d1 517.22 6.0.2f2 6.0.2f2 6.0.2f2 6.0.2f2 261 1.2 5.0.0 1.2 1.2 1 5.0.2 5.0.2 2.1.3 301.40.2 4.5.6 6.6.3 1200.12.2 1.0.1b8 1.0.4 288 1.2 1.2 1.2 1.2 1.0 900.4.1 1.2 2.1 2.1 2.0.0 1.1 300.0 1.0.0d1 1 480.30.2 28.30 1.0 2 439.30.4 1.0.5 140.30.1 404.30.2 404.30.2 2.1 1.0 1 1.2 1.0 1.0 1.0.1 1 31 650.5 3.4 6.1 1.0 3.1.9 2.9 1.4 1 1 1.0

    Model: MacBookPro10,1, BootROM MBP101.00F2.B00, 4 processors, Intel Core i7, 2,3 GHz, 8 GB, SMC 2.3f36
    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
    Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1 GB
    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020
    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (
    Bluetooth: Version 6.0.2f2, 3 services, 27 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en0
    Serial ATA Device: APPLE SSD SM256E, 251 GB
    USB Device: USB 2.0 Bus
    USB Device: Hub
    USB Device: FaceTime HD Camera (Built-in)
    USB Device: USB 2.0 Bus
    USB Device: Hub
    USB Device: Hub
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: BRCM20702 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: USB 3.0 Bus
    Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4
  2. jav6454 macrumors P6


    Nov 14, 2007
    1 Geostationary Tower Plaza
    Since you just got your Mac back from Apple, that means you have a small window where you have AppleCare and phone support. I'd suggest giving them a call to see if they can help diagnose it.
  3. treekram macrumors 68000

    Nov 9, 2015
    Honolulu HI
    Your computer was the subject of a "repair extension program for video issues" - which ended at the end of 2016.

    But there is something unusual going on here. I don't recall many if anybody having reporting issues with the MBP's affected by this repair extension program until just a couple of weeks ago. But in the past couple of weeks, this is the fourth incidence of people reporting a similar issue. 2 of the other people posted their kernel panic logs and they look similar to yours. This is important to note - you don't mention that you have problems outside of connecting external monitors which is different from the other posters (one of these posters has problems when using an external monitor but it's unclear if the problem is also with the laptop monitor).

    The other poster didn't post their kernel panic log but a battery replacement (apparently done after the GPU issues unlike yours) figured into the problems they were having. This may be coincidental but it's just strange.

    What's also strange is that the 3 of you who have posted a kernel panic log are running the same OS - 10.13.3 which was released on Jan. 23, 2018 and subsequently this rash of reported issues. (The 4th poster is running High Sierra as well and likely 10.13.3 as well.) If it's at all possible - try an earlier High Sierra release or another OS from an external disk, that could tell us something.

    What I would also suggest, if it's possible, is to make a visit to Genius Bar. The original post did not state if you got the battery replacement from Apple or not. First, see if the Apple folks can run the test for the GPU issue. Then ask them if there's an issue with High Sierra 10.13.3 and the 2012 15" Retina MBP.

    If you can't make it to an Apple store, call Apple support and mention the problems you're having and that other people seem to be having similar issues and ask them if there is a problem with 10.13.3 with the mid-2012 15" retina MBP's.

    It would be helpful if you can report back what you find out.
  4. treekram macrumors 68000

    Nov 9, 2015
    Honolulu HI
  5. xRYD3Rx macrumors 6502

    Jul 3, 2010
  6. Fishrrman macrumors P6


    Feb 20, 2009
    OP (if you're still checking here):

    Are you using the MBPro's HDMI port to connect to the external display?

    If yes, have you tried using a Minidisplayport (Mac end) to displayport (monitor end)?

    Or... if the display has only an HDMI input, how about a minidisplayport to HDMI converter/adapter cable?
  7. kevers89 thread starter macrumors newbie

    Feb 13, 2018
    Yes, tried it all. Same issue.

    My Macbook Pro 15" mid 2012 is now at an authorised Apple reseller. They told me they have to replace my logic board for €708, I'm not doing that. I asked them to test earlier OS versions to check if it's a software issue. I will let you guys know when I heard back from them.
  8. arogge macrumors 65816


    Feb 15, 2002
    I was not happy about a failure of Apple to inform customers about this recall before they cut off support, but after looking at the complaints suggesting that the repairs didn't solve the problem, I believe that the problem is actually the operating system or the drivers. Similar black-screen problems happen to regular computers, but it's usually related to memory overclocking or a graphics driver. Apple's explanation of lead-free solder overheating doesn't explain why the black-screens became more frequent with each new OS X version update (10.6 to 10.13) or why many applications won't trigger the problem but a few specific applications and actions will trigger it, and even on a cold boot it is reproducible. Apple's own software and HTML5 applets running through Web browsers seem to be the most likely to cause the system crash, while HD video and tasks such as GPU computing can run without trouble.

Share This Page

7 February 13, 2018