Kernel Panics on MacBook 12" (9,1)

FYI: Today at the Apple Store: Very short and competent talk with the technician at Genius Bar, printed this thread and the Kernel Panic:

Logic board is ordered, will be replaced in about 2 days.

I let you know after one or two weeks how it's going on.
 
Let us know after some serious stress testing if it is fixed. I am not sure either way. I know all my mac issues were hardware and centered around the soldering to the board with weak brittle solder. So I hope this works out of you
 
Been seeing kernel panics on my Macbook 2016 (base model) as well. Happen overnight and the laptop is hot the next morning (if plugged in) or battery completely drained.

Code: 
*** Panic Report ***
panic(cpu 0 caller 0xffffff80161ce5fa): Kernel trap at 0xffffff7f985467b5, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000000000ac, CR3: 0x0000000019494000, CR4: 0x00000000003627e0
RAX: 0x0000000000000000, RBX: 0x0000000000000001, RCX: 0x0000000000000020, RDX: 0x0000000000000002
RSP: 0xffffff81208b3db0, RBP: 0xffffff81208b3df0, RSI: 0x0000000000000000, RDI: 0xffffff802a42c000
R8:  0x000000000000001f, R9:  0xffffff80faaa9c01, R10: 0x0000000000000000, R11: 0x0000209c90328109
R12: 0x0000000000000001, R13: 0xffffff802a486800, R14: 0x0000000000000001, R15: 0xffffff7f985cc4a1
RFL: 0x0000000000010212, RIP: 0xffffff7f985467b5, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00000000000000ac, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0

Backtrace (CPU 0), Frame : Return Address
0xffffff81208b3a40 : 0xffffff80160dab12
0xffffff81208b3ac0 : 0xffffff80161ce5fa
0xffffff81208b3ca0 : 0xffffff80161ec463
0xffffff81208b3cc0 : 0xffffff7f985467b5
0xffffff81208b3df0 : 0xffffff7f9856470c
0xffffff81208b3e30 : 0xffffff7f9856e701
0xffffff81208b3ea0 : 0xffffff7f984356de
0xffffff81208b3ec0 : 0xffffff7f984351be
0xffffff81208b3ef0 : 0xffffff80166b50b6
0xffffff81208b3f40 : 0xffffff80166b2f21
0xffffff81208b3f80 : 0xffffff80166b3016
0xffffff81208b3fb0 : 0xffffff80161c9017
      Kernel Extensions in backtrace:
         com.apple.iokit.IOAcceleratorFamily2(205.10)[949D9C27-0635-3EE4-B836-373871BC6247]@0xffffff7f9842b000->0xffffff7f98496fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[D8216D61-5209-3B0C-866D-7D8B3C5F33FF]@0xffffff7f9692c000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[172C2960-EDF5-382D-80A5-C13E97D74880]@0xffffff7f96a0e000
         com.apple.driver.AppleIntelSKLGraphics(10.1.4)[2105CAB9-A7BE-3456-8422-F10D189DAF24]@0xffffff7f98531000->0xffffff7f985e7fff
            dependency: com.apple.iokit.IOSurface(108.2.1)[B5ADE17A-36A5-3231-B066-7242441F7638]@0xffffff7f97312000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[D8216D61-5209-3B0C-866D-7D8B3C5F33FF]@0xffffff7f9692c000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[172C2960-EDF5-382D-80A5-C13E97D74880]@0xffffff7f96a0e000
            dependency: com.apple.iokit.IOAcceleratorFamily2(205.10)[949D9C27-0635-3EE4-B836-373871BC6247]@0xffffff7f9842b000

BSD process name corresponding to current thread: kernel_task

Code: 
*** Panic Report ***
panic(cpu 0 caller 0xffffff8000fce6fa): Kernel trap at 0xffffff7f8334c7dd, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000000000ac, CR3: 0x00000002446ae0fc, CR4: 0x00000000003627e0
RAX: 0x0000000000000000, RBX: 0x0000000000000001, RCX: 0x0000000000000020, RDX: 0x0000000000000002
RSP: 0xffffff810b303310, RBP: 0xffffff810b303350, RSI: 0x0000000000000000, RDI: 0xffffff8014de2000
R8:  0x000000000000001f, R9:  0x0000000000000001, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000001, R13: 0xffffff8014dfbe00, R14: 0x0000000000000001, R15: 0xffffff7f833d24a1
RFL: 0x0000000000010212, RIP: 0xffffff7f8334c7dd, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00000000000000ac, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0

Backtrace (CPU 0), Frame : Return Address
0xffffff810b302fa0 : 0xffffff8000edab52
0xffffff810b303020 : 0xffffff8000fce6fa
0xffffff810b303200 : 0xffffff8000fec563
0xffffff810b303220 : 0xffffff7f8334c7dd
0xffffff810b303350 : 0xffffff7f8336a744
0xffffff810b303390 : 0xffffff7f83386f80
0xffffff810b3033b0 : 0xffffff7f83386690
0xffffff810b303460 : 0xffffff7f833878d8
0xffffff810b3034b0 : 0xffffff7f8336a44b
0xffffff810b3034f0 : 0xffffff7f83233e30
0xffffff810b303520 : 0xffffff7f8337143d
0xffffff810b303740 : 0xffffff7f833af074
0xffffff810b3037b0 : 0xffffff7f8325a929
0xffffff810b3037e0 : 0xffffff7f833aee19
0xffffff810b303810 : 0xffffff7f8325a98a
0xffffff810b303840 : 0xffffff7f833aedba
0xffffff810b303890 : 0xffffff7f8325ad9a
0xffffff810b303b10 : 0xffffff7f8325a407
0xffffff810b303b50 : 0xffffff7f8325a2b3
0xffffff810b303b80 : 0xffffff7f8325992c
0xffffff810b303bc0 : 0xffffff7f833af251
0xffffff810b303be0 : 0xffffff80014dfed7
0xffffff810b303d20 : 0xffffff8000f97f90
0xffffff810b303e30 : 0xffffff8000edf2c3
0xffffff810b303e60 : 0xffffff8000ec28f8
0xffffff810b303ea0 : 0xffffff8000ed26a5
0xffffff810b303f10 : 0xffffff8000fb8eca
0xffffff810b303fb0 : 0xffffff8000fecd86
      Kernel Extensions in backtrace:
         com.apple.iokit.IOAcceleratorFamily2(205.11)[AE224148-CFD1-3A17-943F-E42B98EB06DC]@0xffffff7f83231000->0xffffff7f8329cfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[F51AA3D6-EC2F-3AD3-A043-06DB79027AA2]@0xffffff7f8172c000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[A360453D-2050-3C49-A549-AC0DD5E87917]@0xffffff7f8180e000
         com.apple.driver.AppleIntelSKLGraphics(10.1.4)[6925A1F6-0381-30C9-9AC8-B0197206D546]@0xffffff7f83337000->0xffffff7f833edfff
            dependency: com.apple.iokit.IOSurface(108.2.3)[354FC780-7EA4-3C3F-A9E1-2658F63663A9]@0xffffff7f82118000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[F51AA3D6-EC2F-3AD3-A043-06DB79027AA2]@0xffffff7f8172c000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[A360453D-2050-3C49-A549-AC0DD5E87917]@0xffffff7f8180e000
            dependency: com.apple.iokit.IOAcceleratorFamily2(205.11)[AE224148-CFD1-3A17-943F-E42B98EB06DC]@0xffffff7f83231000

BSD process name corresponding to current thread: com.apple.WebKit
 
This is troubling to see. There are to many of these coming up with this machine for it to be just random. I doubt this is all just a few bad machines.

Strapping in for a REP on MacBooks for bad CPU's.

I know intel was having issues with Sky Lake earlier in the year with errors in manufacturing i though that had been fixed with the M series.
 
sziehr said:
This is troubling to see. There are to many of these coming up with this machine for it to be just random. I doubt this is all just a few bad machines.

Strapping in for a REP on MacBooks for bad CPU's.

I know intel was having issues with Sky Lake earlier in the year with errors in manufacturing i though that had been fixed with the M series.
Click to expand...

"Too many of these coming up"

This is literally the only thread where I've seen this being reported. I even tried googling about this and I didn't find anything. This is definitely just a few bad machines.

I'm still surprised that people are trying to fix this issue themselves rather than take it to the Apple Store for a replacement. New computers should not be doing this.
 
This is exactly how the GPU issue showed up in the 2012 machines just a small thread that grew. The fact CPU are at the root of the issue is kinda scary.

If i do pick one of these up i will be on the look out for this.

Sorry I am a bit jaded. I drew the apple lottery for bad computers. I had a 2011 iMac 27 GPU issue , then my 2012 decided it wanted to have the GPU issue as well. I am just one unlucky apple owner so that is the hue i see it in.

your correct we would need to see vastly more to say it is starting down the road of the 2012
 
sziehr said:
This is exactly how the GPU issue showed up in the 2012 machines just a small thread that grew. The fact CPU are at the root of the issue is kinda scary.

If i do pick one of these up i will be on the look out for this.

Sorry I am a bit jaded. I drew the apple lottery for bad computers. I had a 2011 iMac 27 GPU issue , then my 2012 decided it wanted to have the GPU issue as well. I am just one unlucky apple owner so that is the hue i see it in.

your correct we would need to see vastly more to say it is starting down the road of the 2012
Click to expand...

I suppose in the coming months we'll be hearing more about this if it's a widespread issue. I hope it's not since I planned on getting one of these soon (and overall, it would be terrible anyway).

I'm not sure how much last year's M series differs compared to this one (in terms of overall hardware construction), but hopefully not enough so that the fact that barely anyone (if anybody at all) complained about this in last years model means that it's limited to a few machines in this years.
 
viperGTS said:
I suppose in the coming months we'll be hearing more about this if it's a widespread issue. I hope it's not since I planned on getting one of these soon (and overall, it would be terrible anyway).

I'm not sure how much last year's M series differs compared to this one (in terms of overall hardware construction), but hopefully not enough so that the fact that barely anyone (if anybody at all) complained about this in last years model means that it's limited to a few machines in this years.
Click to expand...


I am currently stalking one my self. I just do not want to get into another situation where i end up with a laptop from apple that is defective. They have gotten tighter and tighter on there do the right thing.
 
No issues with my m7 machine. Have been running fine since I received it about 3 weeks ago. Fingers crossed.
 
I've had two kernel panics recently on my 2015 1.1Ghz rMB. It is almost 1 year old, and this is the first time I have experienced this problem. I am running the macOS Sierra public beta, and the kernel panics started shortly after I installed the latest version (PB4). From looking at the tracebacks, I'm thinking the problem is in the graphics acceleration - maybe there is a bug in the new drivers.
 
The Apple Store called me after 7 hours (second repair): It's a known issue. Should be a flat cable from the Mainboard to USB-C.

I report after the second repair if it's okay then.
 
I've also experienced a few (probably half-dozen) kernel panics with my 2016 rMB m5. Bluetooth often dies on it as well.

How do I generate these "Panic" reports? I'd like to have a few of them with me when I contact Apple.

Edit: Figured out how to generate the panic report.
 
Last edited:
sziehr said:
Is this what is causing the kernel panics?
Click to expand...
This should be the reason of all this errors

Battery drain
Hot
Kernel panic and 0% energy

Everyone here said the same about the problem. And this cable is the problem. Please wait for my confirmation about it. This is what the Apple Store told me. The Store itself contacted Apple and Apple knows about it. The store change my cable and then I test my MB and let you know.
 
So it is a systemic issue apple knows about and will eventually get around to admitting with a warrant extension for models with given serials.

and who said i was over reacting /S
 
Dominik_iDomiX said:
This should be the reason of all this errors

Battery drain
Hot
Kernel panic and 0% energy

Everyone here said the same about the problem. And this cable is the problem. Please wait for my confirmation about it. This is what the Apple Store told me. The Store itself contacted Apple and Apple knows about it. The store change my cable and then I test my MB and let you know.
Click to expand...

No, it's not the same problem. I don't have battery drain, and it doesn't get hot. The problem started for me only after I installed the latest Sierra public beta. Also note this is a 2015 model, not the new one. I think there may indeed be a hardware issue with some 2016 models, but not everyone is having the same problem.
 
I am going to put a hold on buying one of these until this issue is more define / resolved after getting saddled with two macs that had nothing but issues thanks to design flaws or materials issues.
 
@szier I should not make buying (refraining) decisions based on the panic-related information in this topic. There's very little data.
 
I would say your right. However after getting buggered with two machines with inherently bad build quality. I am not looking to make it a hat trick
 
sziehr said:
I am going to put a hold on buying one of these until this issue is more define / resolved after getting saddled with two macs that had nothing but issues thanks to design flaws or materials issues.
Click to expand...
While I understand your concern, I will say that 95 percent of the time, mine runs just fine with no issues at all. But yeah, the 5 percent of the time I'm dealing with dead bluetooth or kernel panics is very annoying.

grahamperrin said:
@szier I should not make buying (refraining) decisions based on the panic-related information in this topic. There's very little data.
Click to expand...
Even though I'm one of those who has been experiencing kernel panics, I completely agree with you. I personally doubt this is a widespread issue.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Back
Top