MacBook Pro 2016 touch bar randomly crashes

I just purchased a MacBook Pro 13-inch 2016 touch bar.

I have problem trying to back-up the internal SSD into Time Machine. It is not a problem of external disk type, already changed 4 different to try. It seems to encounter her problems in a specific location of internal SSD data transfer. After 240 GB the Macbook disconnects the external disk and it crash. Trying to restart a next session of Time Machine it chars quite immediately, it cannot forward on the data transfert.

I am already using macOS Sierra 10.12.2 but still having same problem and same error message:

*** MCA Error Report ***

CPU Machine Check Architecture Error Dump (CPU: Intel(R) Core(TM) i7-6567U CPU @ 3.30GHz, CPUID: 0x406E3)

CATERR detected! No MCA data found.

Good news !!!!!

I had same problem with my MacBook Pro 13-inch 2016 touch bar.

Crashes happened during time machine and I was already using macOS Sierra 10.12.2. because the full system was restored from my previous MacBook.

I have simply re-installed the OS directly from Apple Store.

It works !!!!!!

Now everything is fine, I could back-up with time machine e and no more crashes.

I hope it could be helpful for other users.

Ciao

Having the same issue. But it has nothing to do with timemachine backup as far as I know. Mostly happens on work where I have no Time Machine backup. Mostly it happens after waking the computer after sleep/screensaver.

Trackpad gets unresponive and I can't log in. After a couple of seconds screen goes black.

Also having daily crashes and re-starts with the same error message. Contacted Apple support...they were basically clueless and told me to take the machine back to the store and exchange for another.

$3,000 laptop that is having this many issues right out of the box.....not good. Might just get a refund and get something else. For this much money I (we) deserve a better system.

I'm having similar issues. Randomly I wake my MacBook Pro 13" Touch Bar from sleep and find it has crashed. I have a Seagate drive attached as a Time Machine backup. I also have a new LG 5k display. The crashes have been happening since I connected the display. I've turned off power nap and wake for network access to see if that helps.

I see another person in this thread says they have their TM backup drive connected with an Apple TB 3 to USB 3 adapter. I have that too. I may test with the drive connected with another brand adapter.

I have this issue too on my wife's MBP: https://s.natalian.org/2017-01-15/version.png

https://s.natalian.org/2017-01-15/crash.png

The overall stability of the machine is pretty bad. FCPX & Chrome crashes.

I haven't quite understood how to examine the crashes under console but I do send crash reports given the option, so I am assume Apple knows I am going through ****?

I haven't had an unattended crash (while the computer is supposed to be sleeping) since I turned off power nap, and I checked Notifications/Turn on Do Not Disturb:/When display is sleeping. That's not to say I haven't had quirky behavior of the entire system that requires a reboot to correct.

I truly believe this is related to the AMD GPU and how it is handling the 5K monitor, look at one of my Panic logs:

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)

I've gotten this twice today - and I never got this error a single time UNTIL my laptop updated to macOS 10.12.3. I was never on the beta path on this laptop.

edit: MBP 15" 2.7GHz i7, Radeon Pro 4096MB. Was not connected to an external monitor either time.

My 2016 MacBook Pro Touchbar has also randomly but consistently crashing. Have to hard power down & restart kind of crashes. Apple Engineers are digging into it but it occurs most often (only?!) when plugged into my LG Ultrafine 5k Display (single USB-C cable over thunderbolt). So it may be graphic card or thunderbolt issue but ultimately a system crash means a system (software) bug not a hardware problem. Once Apple isolates the issue I'm sure there will be a software fix, not a hardware recall. ***** though, haven't experienced full system crashes on any Mac since the 90s. 😟

I have the same issue using 2x DELL P2715Q Display with https://www.amazon.com/Plugable-DisplayPort-Chromebook-Thunderbolt-3840x2160/dp/ B01EXKDRAC/ref=sr_1_2?ie=UTF8&qid=148573…. Consistently when I wake the laptop from sleep while connected to these monitors I find that it has rebooted itself. When I close the lid and disconnect the monitors and take it to the office I notice that it's crashed and rebooted in my bag. I'm using 10.12.3 (16D32).

Same problem for me with MBP TB 15' i7 2.9 Radeon 460 4GB. When waking up from sleep mode the computer automatically reboots and gets a panic. Only my Mac is not connected to anything else except for the power cable. Here is the .panic log:

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

Anybody solved this problem in ANY way? Including changing the Mac?

Anybody else experiencing that without a 5k screen?

Thanks

I have Radeon 460 but I do not have the 5K display and I've had it happen twice. At the times it happened, I was not on an external display at all.

I think it's too strongly tied to the 5K release. It shipped nearly the same time that the macOS patch to "improve graphics stability" shipped. I never got this issue until I upgraded to that.

I would like to know if in your opinion it could have any meaning to format the device or change of the computer.

The Mac, except for this problem, works perfectly. Formatting it would mean another half day of work lost in installing software and transferring data in addition to the time for formatting. If the problem is in the new update it will not solve the problem and I would have lost time for nothing. The same reasoning for a change of the Mac, which will make me lose even more time.

Thanks