Kernel Panic MacBook Pro Retina / How to Read Crash Log?

Discussion in 'MacBook Pro' started by HeroofTime231, Jan 22, 2014.

  1. HeroofTime231 macrumors newbie

    Oct 24, 2013
    Arlington, VA
    Alright Mac gurus, I've got one for you.

    My inquiry involves my mid 2012 15-inch MacBook Pro with Retina Display and its frequent, inconsistent kernel panics, which started occurring shortly before Mavericks launched (which I hope rules out anything OS specific). For the record, I have brought it to the Apple Store twice, the second time of which they ran one of their "extensive" tests on it overnight only to find nothing wrong with it.

    I am about to bring it in again, but before I do, I thought I might try to use this ordeal as a learning experience, as I am quite intrigued with the nature and persistence of the issue, so I thought I might ask the community. I have done quite a bit of research, and can say that I have a basic understanding of what a kernal panic is and what some of the primary causes are. I am slowly moving through all the different troubleshooting methods, but this is a slow process because, again, the panics themselves are seemingly random. While I understand that the majority of panics are software related (caused by a troublesome third-party driver), I am being led to the conclusion that the issue might be hardware related. Though I won't go into extreme detail, here is a quick list of all the main trouble shooting methods I've done:

    • Reformatted and reinstalled OS X completely multiple times (10.8 and 10.9), and started fresh (no Time Machine Backups).
    • Reset PRAM
    • Moving through 3rd party drivers I do use, of which there are not many. I've already ruled out a few by experiencing a crash while the driver wasn't installed.
    • Removed all external peripherals (and have had panics during those times)
    • Booted in Safe Mode (and experienced a crash)
    So here is the question: sure, I'd love it if one of you with more knowledge than I on this subject could tell me what's wrong, but what I'm really curious about is if any of you know how to REALLY read and extract all the useful information possible from a crash log. Again, I'd love to learn how to read them for the sake of extending my knowledge of OS X. Here is an example of one below:


    Anonymous UUID: 2878D613-1BA7-8011-F936-AA53CEC376C0

    Wed Jan 22 11:56:11 2014
    panic(cpu 0 caller 0xffffff7fa791afac): "GPU Panic: [<None>] 3 0 a0 d9 9 8 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x102c00000 0xffffff81fcf3e000 0x0e7150a2, D0, P1/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.12/src/AppleMuxControl/kext/GPUPanic.cpp:127
    Backtrace (CPU 0), Frame : Return Address
    0xffffff81f8db3540 : 0xffffff8025622f69
    0xffffff81f8db35c0 : 0xffffff7fa791afac
    0xffffff81f8db3690 : 0xffffff7fa5ff7cf8
    0xffffff81f8db3750 : 0xffffff7fa60c4e26
    0xffffff81f8db3790 : 0xffffff7fa60c4e84
    0xffffff81f8db3800 : 0xffffff7fa62eff31
    0xffffff81f8db3870 : 0xffffff7fa60e8011
    0xffffff81f8db3890 : 0xffffff7fa5ffe841
    0xffffff81f8db3940 : 0xffffff7fa5ffc362
    0xffffff81f8db3b40 : 0xffffff7fa5ffd3cd
    0xffffff81f8db3c20 : 0xffffff7fa5faa65a
    0xffffff81f8db3db0 : 0xffffff7fa5fa93e4
    0xffffff81f8db3dd0 : 0xffffff7fa78ed812
    0xffffff81f8db3eb0 : 0xffffff7fa78ed6ee
    0xffffff81f8db3f00 : 0xffffff7fa78ec55e
    0xffffff81f8db3f20 : 0xffffff802564a15a
    0xffffff81f8db3fb0 : 0xffffff80256d6aa7
    Kernel Extensions in backtrace:[A4934A66-0E30-36E9-984A-650481102449]@0xffffff7fa790d000->0xffffff7fa791ffff

    BSD process name corresponding to current thread: kernel_task

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
    Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
    Kernel slide: 0x0000000025400000
    Kernel text base: 0xffffff8025600000
    System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)

    System uptime in nanoseconds: 48059107507936
    last loaded kext at 47359669569243: 4.2.1b2 (addr 0xffffff7fa7a69000, size 20480)
    last unloaded kext at 47467406989685: 4.2.1b2 (addr 0xffffff7fa7a69000, size 16384)
    loaded kexts: 2.0.0 1.9.5d0 1.60 3.0 4.2.0f6 124 2.0.9d1 100.14.11 1.0.0 1.0.0d1 3.5.13 2.5.3fc1 2.5.3fc1 8.1.8 4.2.0f6 8.1.8 7.0.0 1 1.7.0 8.1.8 1.0.0 2.0.4d1 1.1.12 3.4.12 1.0.10 240.2 240.2 1.0.0d1 1.0.0d1 35 404 2.4.0 650.4.4 1.4.0 700.20.22 2.9.5 650.4.1 650.4.3 161.0.0 2.0 2.0 1.8 2.0 2.0 1.7 216.0.0 153 3 216.0.0 1.0 10.0.7 3.6.0 2.5.3fc1 1.0.0 1.9.4fc11 1.14 4.2.0f6 91 4.2.0f6 98.7.1 8.1.8 8.1.8 1.0.0 1.0.12d1 98.7.1 3.4.12 5.5.1d27 2.5.3fc1 2.5.3fc1 1.0.11d1 3.1.6d1 1.0.4 2.3.6 3.4.12 2.3.6 240.6 650.4.4 2.5.0 2.5.0 1.4.0 650.4.0 650.4.0 1.9.2 2.8.5 600.34 3.2 650.4.4 2.6.0 650.4.4 2.0 2.0 2.0.0 1.1 278.10 1.0.0d1 7 2 371.1 1.9 21 28.30 2.0 2.8 1.4 1.0 1


    It's always a "GPU panic" and from the list of kexts, it's never constantly one particular kext that is the last to be loaded or unloaded. Is it possible to discern if it's hardware related from a crash log, and if so, why wouldn't the computer report the issue (which seems to be GPU related) when we ran Apple's hardware test on it at the Genius Bar?

    I recognize that this might be a complex issue that simply can't be diagnosed by any crash report, so I'm okay with hearing that answer if it's the case. I also accept the fact that understanding how to read a crash report might simply require a much deeper knowledge of UNIX than I have. I thought I just might try to learn as much as I could and then share it with others who might have the same problem. Any help you guys could give would be super-appreciated. Thanks! :D
  2. durkkin macrumors regular

    Sep 23, 2013
    Kernel panics are actually typically hardware related issues, not software, although like you said software does play a part.

    If you haven't come across it in your research, the kernel is a low level portion of the operating system that allows the OS to communicate with the hardware (see attached picture courtesy of Wikipedia). You're getting info over USB, the kernel tells the OS the USB is in use, and then the OS determines what to do with said info while the kernel handles it (more or less). what happens in a kernel panic is that the external hardware and the third party driver accesses that low level kernel, something does wrong; either the hardware malfunctions and produces an error or the driver incorrectly handles a hardware signal and then the OS malfunctions. Either way, the communication between hardware and software breaks down resulting in a kernel panic.

    Anyway, back to your issue.

    Those portions at the top of the full Console report indicate it was the GPU that caused the panic.

    These are the kexts in the backtrace that are not dependencies (the dependencies are the kexts that are loaded because these 3 rely on them).

    From this we can conclude it is a GPU issue related to the Nvidia discrete graphics card that is causing the kernel panic. Because you have booted it in safe mode which disables all but the necessary kernel extensions, and you have started with a fresh install thereby eliminating mutation/modification of OSX kexts, it is logical to conclude it is a hardware issue relating to the Nvidia discrete graphics card (if it was a software kernel issue for the Nvidia GPU everyone would be having the problem, not just you).

    I would recommend taking your machine to the Genius Bar and showing them the kernel panic log. They should be able to figure out the same thing. Intermittent issues are notoriously hard to reproduce so it's not necessarily surprising their stress test didn't make it crash. Their hardware test also only shows whether or not the GPU is working, and it is, just not all the time.

    Hope this helps.

    Attached Files:

  3. Dragynfyre macrumors member

    Oct 22, 2010
    I've been getting this problem a lot starting last week and after doing some research it does seem like it could be hardware related. After searching on Google it seems like the two Macbook models that have this problem the most often are the Mid-2010 MBP and Mid-2012 rMBP. Apple acknowledged there was a flaw with the GPU in the mid-2010 MBP and offered free repairs for 3 years after the purchase date.
  4. HeroofTime231 thread starter macrumors newbie

    Oct 24, 2013
    Arlington, VA
    durkkin, that was a fantastic response! Thank you for taking all that time to answer me. Your explanation was honestly more clear and informative than 10 pages worth of Google's links! :)

    Not that there is any doubt left that it's my GPU, but just today I hooked my MacBook up to a Thunderbolt Display and it would crash with a panic every time I attempted to log in -- at one point, even displaying the prohibitory symbol on boot up (scary). The second I unplugged it, though, it seemed to work fine.

    I will definitely be taking it in to the Genius Bar in the next couple of days, and as you recommended, I'm going to bring up one of the logs and really push them to take a closer look at the hardware side of things. They where the ones who told me that panics where usually software related, though given how relatively rare they are combined with the fact that a majority of their customers probably have installed some random driver that's causing it, I suppose I shouldn't be surprised.

    If you have the time to respond, I was wondering if I could pick your brain just a tad more on how you came to some of the conclusions you did. Specifically, I was wondering if you could explain what it is about the non-dependand kexts that helps to diagnose the issue. Is it just the kexts’ names, or is there some additional information evident in the kind of kexts present in the list? Also, would you have a recommendation for a source where I can educate myself more about this kind of stuff?

    In any case, thanks again TREMENDOUSLY for your help! I’ll update the post again with any new developments.

    Oh, and Dragynfyre, I also think you are right. After posting this I researched this issue specifically targeting my same model computer and, sure enough, there seem to be quite a few threads in Apple’s support communities complaining about more or less the same thing. I would love to hope that this would be recognized and addressed by Apple, but I won’t hold my breath (haha!). Best of luck to you as well!
  5. Zyiros macrumors member


    Jan 23, 2014
    For a short term fix, I suggest fixing the disk permissions. Here's how you do that:

  6. Wuiffi macrumors 6502a


    Oct 6, 2011
    it looks like a GPU problem. I fail to see how fixing the disk permissions could help?
  7. Zyiros macrumors member


    Jan 23, 2014
    Ah, I see! Yeah, take it in and see how it goes. A GPU replacement with Apple can cost a pretty penny, so I'm hoping your computer is under warranty still!
  8. HeroofTime231 thread starter macrumors newbie

    Oct 24, 2013
    Arlington, VA
    Hey Zyiros, thanks for the earlier suggestion. Unfortunately, I opted out of Apple Care this time around, partly because American Express pledged that the would cover my MacBook an additional year after Apple's warranty expires. So hopefully that works out. Or perhaps the Geniuses will be nice and make the repair free of charge considering that I used to work there :)

    I can dream, can't I?
  9. durkkin, Jan 24, 2014
    Last edited: Jan 25, 2014

    durkkin macrumors regular

    Sep 23, 2013
    Glad my answer was helpful!

    For your computer that's a bad thing, for you it might be a good thing. Most Apple stores have a Thunderbolt Display on the floor, so you can show the Genius exactly what is happening. Plus, since it's been crashing so much you'll now have plenty of logs to show them the issue. If the TBD crashes happen in safe boot or with a new OS, that's even more convincing of it being hardware related.

    Honestly, it's just the name. The latter two pointed to Nvidia, and the first one references the Apple Mux Control. Mux is shorthand for multiplexer, which is a tiny piece on the logic board that controls signal flow. Think of it like a meter on a freeway on ramp. Just as the meter only lets certain lanes onto the single lane on ramp at one time, the mux controls which signal lanes get passed around. There are several muxers on a logic board because it handles so many signals at one time, but with everything else pointing to the GPU I think we can safely assume it's the muxer controlling the signals out of the GPU.

    Honestly, the wikipedia article on the kernel is pretty good and fairly lengthy:
    The Apple Developer Library has a great PDF on kernel programming. Quite technical at times, and not all of it is relevant to what you want to know, but it's worth browsing through:

    Beyond that most of what I know was bits and pieces picked up here and there.

    Hope that it all works out for you.
  10. vmflapem macrumors 6502

    Dec 27, 2013
    Is it normal to get kernel panics on a brand new MacBook Pro..?
    I have no idea what the problem is on my new Macbook
  11. durkkin macrumors regular

    Sep 23, 2013
    No, it is not normal. If it is brand new chances are you are downloaded something that is causing an issue when you went through the whole setup process of getting your old info on there. There is a program called Console under the Utilities folder in your Applications. You can check it for kernel panic logs to see what is happening, similar to what HeroofTime231 did here.
  12. HeroofTime231 thread starter macrumors newbie

    Oct 24, 2013
    Arlington, VA
    Alright, so for anyone interested in this issue, here's what happened...

    I took my MacBook to the Apple Store for the third time and thoroughly explained the situation to the Genius. After one more hardware test, they decided to ship it out to Apple to have it fixed. I didn’t purchase Apple care with my MacBook, so I incurred a flat charge of $ 310.00, which, while kind of sucky, was actually good because it probably would have costed more to pay for the individual components. It was then returned to me in a little less than a week with a new logic board and a new hard drive. It has been about two weeks since then, and I have not had a single crash. So, (knock on wood) I think it's safe to say that the issue was certainly hardware-realated.

    I have a strong feeling that this is a problem on Apple's end (much like the very similar issue with the 2010 MacBook Pro). Regardless, if you are experiencing this issue with your MacBook Pro with Retina Display (Mid 2012), this seems to be the solution. And of course, if you have AppleCare, you should walk away from this unscathed. Hopefuly, if this is in fact a widespread defect, Apple will realize it and set up a replacement program, not unlike how they've done in the past.

    Thanks again to everyone, especially durkkin, for their input and advice; I definitely learned a lot in the process about kernel panics, which was what I was hoping for :)
  13. pips7000 macrumors newbie


    Jan 29, 2012
  14. johnnysmoke macrumors newbie

    Aug 8, 2014
    I HAD the same problem... with Macbook pro 15" Retina, Mid 2012

    1) Went to apple store who proposed to change logic board ($$$$$$ !!!!!)
    2) Since many time in the past i had computer that failed / crashed just because there was to much dust in them, i told to myself I just need to make sure there is not to much dust in the laptop
    3) I bought a Pentalobe screwdriver
    4) Once opened it was obvious that my macbook pro was clogged by dust
    5) removed dust
    6) Macbook pro now works perfectly

    Attached Files:

  15. pianodude123 macrumors 6502a


    Mar 1, 2005
    in the internet
    I too, am having this GPU panic crashing error. It seems like hundreds of others on Apple's own forums are as well.

    I had to pay $360 to get this repaired by apple out of warranty. This seems a little shady to me, given that there are all these people having this problem for no reason
  16. webbernz macrumors newbie

    Nov 14, 2016
    --- Post Merged, Nov 14, 2016 ---
    Hi - help! I have an early 2011 macbook which keeps crashing sometimes every 5 minutes despite me sending it back for replacement motherboard as part of the service recall. I've researched a bit about kernel panics and crash reports with no consistency in what I can see about the panic reports. It's taken me so long to find out what's going on the repairer warrantee is expired so don't know what to try next. In case it helps I've posted the last kernel panic below

    Tue Nov 15 11:40:37 2016
    panic(cpu 0 caller 0xffffff802a6dc43e): Kernel trap at 0xffffff802a6a4196, type 13=general protection, registers:
    CR0: 0x0000000080010033, CR2: 0x000000000dc3d000, CR3: 0x000000011da79078, CR4: 0x00000000000606e0
    RAX: 0xffffff802acd2ac8, RBX: 0x0000000000000000, RCX: 0x000000000039b2ae, RDX: 0x0000000000000019
    RSP: 0xffffff8228ecbd00, RBP: 0xffffff8228ecbd20, RSI: 0x0000000000004000, RDI: 0xffffff805fbd47e0
    R8: 0x0000000000000000, R9: 0xffffff8228ecbed0, R10: 0x0000000000000000, R11: 0x0000000080033d80
    R12: 0x0000000000000000, R13: 0xffffff805fbd47e0, R14: 0x0000000000004000, R15: 0x7fffff803a5987e8
    RFL: 0x0000000000010206, RIP: 0xffffff802a6a4196, CS: 0x0000000000000008, SS: 0x0000000000000000
    Fault CR2: 0x000000000dc3d000, Error code: 0x0000000000000000, Fault CPU: 0x0

    Backtrace (CPU 0), Frame : Return Address
    0xffffff81eb381c50 : 0xffffff802a622f79
    0xffffff81eb381cd0 : 0xffffff802a6dc43e
    0xffffff81eb381ea0 : 0xffffff802a6f3976
    0xffffff81eb381ec0 : 0xffffff802a6a4196
    0xffffff8228ecbd20 : 0xffffff802a6a4f65
    0xffffff8228ecbd50 : 0xffffff802a679033
    0xffffff8228ecbf20 : 0xffffff802a6dc87c
    0xffffff8228ecbfb0 : 0xffffff802a6f387b

    BSD process name corresponding to current thread: iMovie

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64
    Kernel UUID: 9477416E-7BCA-3679-AF97-E1EAAD3DD5A0
    Kernel slide: 0x000000002a400000
    Kernel text base: 0xffffff802a600000
    System model name: MacBookPro8,2 (Mac-94245A3940C91C80)

    System uptime in nanoseconds: 592005349799
    last loaded kext at 296067313823: 1.9 (addr 0xffffff7facf7d000, size 65536)
    last unloaded kext at 385438180361: 1.9 (addr 0xffffff7facf7d000, size 57344)
    loaded kexts: 1.60 1.9.5d0 100.14.34

Share This Page