restart without warning

Discussion in 'MacBook Pro' started by project_2501, Aug 20, 2017.

  1. project_2501 macrumors 6502

    Jul 1, 2017
    My brand new MacBook Pro 13" non-TB 2017 has restarted itself without warning at least 3 times in the last few days.

    The screen tells me it has restarted due to a problem.

    There is a kernel panic log that corresponds to the time of the last one. It starts like this (below) and all the kexts are .. nothing else from other vendors. There is no VMware kext as I guess it only loads when I run the app. There doesn't appear t be a link between what I'm doing (web-based working, no other apps). I think I may have previously used a USB memory stick but not sure if that happens before every restart.

    I did a Diagnostic check (power on, press D) and it reported no issues found.

    I use an external 4K NEC monitor over USB-C/TB3 directly to the DisplayPort on the monitor.

    Any ideas? My best guess is the apple NTFS driver is problematic?

    *** Panic Report ***

    panic(cpu 0 caller 0xffffff800abfe39d): Kernel trap at 0xffffff800ab22ba5, type 14=page fault, registers:

    CR0: 0x000000008001003b, CR2: 0xffffff800ab22b2e, CR3: 0x000000044ae000fd, CR4: 0x00000000003627e0

    RAX: 0xffffff800ab22ba5, RBX: 0xffffff803fe81660, RCX: 0xffffff800ab24e20, RDX: 0x0000000000000036

    RSP: 0xffffff9229e5bd20, RBP: 0xffffff9229e5bd90, RSI: 0x0000000000000002, RDI: 0xffffff803fe81288

    R8: 0x0000000000000000, R9: 0xffffff9229e5bdec, R10: 0x0000000000000000, R11: 0xffffff7f8b76e010

    R12: 0x0000000000000000, R13: 0xffffff803fe81288, R14: 0x0000000000020000, R15: 0x0000000000000006

    RFL: 0x0000000000010087, RIP: 0xffffff800ab22ba5, CS: 0x0000000000000008, SS: 0x0000000000000010

    Fault CR2: 0xffffff800ab22b2e, Error code: 0x0000000000000003, Fault CPU: 0x0, PL: 1, VF: 5

    Backtrace (CPU 0), Frame : Return Address

    0xffffff9229e5b9b0 : 0xffffff800aae953c

    0xffffff9229e5ba30 : 0xffffff800abfe39d

    0xffffff9229e5bc10 : 0xffffff800aa9a593

    0xffffff9229e5bc30 : 0xffffff800ab22ba5

    0xffffff9229e5bd90 : 0xffffff800ab27892

    0xffffff9229e5be50 : 0xffffff800ab27aee

    0xffffff9229e5be90 : 0xffffff7f8b7698fe

    0xffffff9229e5bed0 : 0xffffff7f8b7691e6

    0xffffff9229e5bf30 : 0xffffff800aff3582

    0xffffff9229e5bf50 : 0xffffff800b0240f5

    0xffffff9229e5bfb0 : 0xffffff800aa9ad96

    Kernel Extensions in backtrace:[225C22A5-813D-3651-9C40-FDEEAB0D78E1]@0xffffff7f8b762000->0xffffff7f8b770fff

    BSD process name corresponding to current thread: plugin-container

    Mac OS version:


    Kernel version:

    Darwin Kernel Version 16.7.0: Thu Jun 15 17:36:27 PDT 2017; root:xnu-3789.70.16~2/RELEASE_X86_64

    Kernel UUID: D3314D98-5D40-3CD8-98A4-F1DD46C20E03

    Kernel slide: 0x000000000a800000

    Kernel text base: 0xffffff800aa00000

    __HIB text base: 0xffffff800a900000

    System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

    System uptime in nanoseconds: 6512111085287

    last loaded kext at 4492095888207: 3 (addr 0xffffff7f8dcb2000, size 32768)

    last unloaded kext at 4695831844667: 131.60.1 (addr 0xffffff7f8dc6c000, size 184320)

    loaded kexts: 92 1.0 3.1.2 1.70

    .. etc etc etc..
  2. TofSanity macrumors 6502a


    Oct 29, 2010
    is this happening with anything connected? I was having a similar problem and it was due to a short in the cable I was using to charge my iPhone or iPad Pro. Got a new cable and my MacBook Pro hasn't shut down. oh I have a 15" 2016
  3. project_2501 thread starter macrumors 6502

    Jul 1, 2017
    Thanks for your reply.

    I don't have anything connected other than the official power supply and the connector to the monitor.

    I have used a usb-C hub but not always and it hasn't been connected when the restart happens.
  4. maflynn Moderator


    Staff Member

    May 3, 2009
    New computer - I wouldn't mess with it, but rather call apple and get it exchanged.
  5. treekram macrumors 65832

    Nov 9, 2015
    Honolulu HI
    The task that was running when the crash occurred was plugin-container which could mean that a plugin could be causing the issue. You can try running in safe mode to see if that helps. If the crash doesn't occur in safe mode, then there likely is a plugin or some other 3rd-party software causing the issue.

    If you have kernel panic logs from the other restarts and they have a different cause of the crash, then it could be hardware as the previous poster suggested.
  6. project_2501 thread starter macrumors 6502

    Jul 1, 2017
    happened again - this time the apple reporting tool showed me the issue was related to the Intel GPU.

    maybe it doesn't like driving a 4k external display?

    maybe it doesn't like the heat generated ... it was HOT!

Share This Page