Kernal Panic Help

Discussion in 'MacBook Pro' started by ryanngreen, Sep 21, 2014.

  1. ryanngreen macrumors newbie

    Joined:
    Sep 21, 2014
    #1
    So I was just playing a game when my computer froze and crashed. When rebooting the screen was dark, but it lit up at the login screen. The application for the game I was playing is now gone. Everything seems to be working normally, but I would like to know what happened in case it's going to happen again. Any help is appreciated. This is what the report said:


    Anonymous UUID: C5BC9720-8700-38BE-D97C-5A024442ACC5

    Sun Sep 21 22:16:27 2014
    panic(cpu 0 caller 0xffffff7f86bf2f7c): "GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00070000: CFG 0x0a2910de 0x00100406 0xd2000000, BAR0 0xd2000000 0xffffff8120dfd000 0x0a5480a2, D0, P2/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.6.22/src/AppleMuxControl/kext/GPUPanic.cpp:127
    Backtrace (CPU 0), Frame : Return Address
    0xffffff810eae2580 : 0xffffff8004822f79
    0xffffff810eae2600 : 0xffffff7f86bf2f7c
    0xffffff810eae26d0 : 0xffffff7f852e3f1b
    0xffffff810eae2790 : 0xffffff7f853ad50a
    0xffffff810eae27d0 : 0xffffff7f8552eb2e
    0xffffff810eae2820 : 0xffffff7f855db0e3
    0xffffff810eae2950 : 0xffffff7f855daad0
    0xffffff810eae2a40 : 0xffffff7f8542217b
    0xffffff810eae2b90 : 0xffffff7f854214f9
    0xffffff810eae2ca0 : 0xffffff7f855de14e
    0xffffff810eae2d40 : 0xffffff7f855f1ff7
    0xffffff810eae2db0 : 0xffffff7f855de4d1
    0xffffff810eae2f50 : 0xffffff7f8562cfad
    0xffffff810eae3090 : 0xffffff7f85626cb5
    0xffffff810eae3130 : 0xffffff7f853d2f47
    0xffffff810eae3160 : 0xffffff7f85626794
    0xffffff810eae3240 : 0xffffff7f853d2f32
    0xffffff810eae3270 : 0xffffff7f85624f0e
    0xffffff810eae32c0 : 0xffffff7f8564d087
    0xffffff810eae3300 : 0xffffff7f854188f9
    0xffffff810eae3360 : 0xffffff7f85418f29
    0xffffff810eae33d0 : 0xffffff7f8564c8be
    0xffffff810eae3410 : 0xffffff7f8562cd92
    0xffffff810eae3550 : 0xffffff7f853d39fd
    0xffffff810eae3590 : 0xffffff7f853d2865
    0xffffff810eae35e0 : 0xffffff7f855e457f
    0xffffff810eae3640 : 0xffffff7f855dcd5c
    0xffffff810eae37d0 : 0xffffff7f855e9ee0
    0xffffff810eae3820 : 0xffffff7f853972d7
    0xffffff810eae3870 : 0xffffff7f852c38b7
    0xffffff810eae3930 : 0xffffff7f852c1672
    0xffffff810eae3970 : 0xffffff7f852be963
    0xffffff810eae39a0 : 0xffffff7f852be8fa
    0xffffff810eae3a40 : 0xffffff7f852e84f0
    0xffffff810eae3c40 : 0xffffff7f852e947d
    0xffffff810eae3d10 : 0xffffff7f861f3a4f
    0xffffff810eae3d30 : 0xffffff7f861f36bf
    0xffffff810eae3d50 : 0xffffff7f861f4c0f
    0xffffff810eae3e90 : 0xffffff7f861e2913
    0xffffff810eae3eb0 : 0xffffff7f8621af3c
    0xffffff810eae3ed0 : 0xffffff7f8621b067
    0xffffff810eae3ef0 : 0xffffff8004cb07f0
    0xffffff810eae3f30 : 0xffffff8004caf292
    0xffffff810eae3f80 : 0xffffff8004caf367
    0xffffff810eae3fb0 : 0xffffff80048d7417
    Kernel Extensions in backtrace:
    com.apple.driver.AppleMuxControl(3.6.22)[32862231-50BC-3AF6-87A2-703321AE4F90]@0xffffff7f86be4000->0xffffff7f86bf7fff
    dependency: com.apple.driver.AppleGraphicsControl(3.6.22)[AA46D551-BE0F-33DA-93A3-8F46197BB36F]@0xffffff7f86bdc000
    dependency: com.apple.iokit.IOACPIFamily(1.4)[045D5D6F-AD1E-36DB-A249-A346E2B48E54]@0xffffff7f851e9000
    dependency: com.apple.iokit.IOPCIFamily(2.9)[4662B11D-2ECA-315D-875C-618C97CDAB2A]@0xffffff7f84dec000
    dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0xffffff7f85241000
    dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[E04639C5-D734-3AB3-A682-FE66694C6653]@0xffffff7f86bdf000
    com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[D61B2BB9-4289-318D-9197-5E1E13B1FF32]@0xffffff7f85294000->0xffffff7f854fcfff
    dependency: com.apple.iokit.IOPCIFamily(2.9)[4662B11D-2ECA-315D-875C-618C97CDAB2A]@0xffffff7f84dec000
    dependency: com.apple.iokit.IONDRVSupport(2.4.1)[D41125CE-69BD-32E7-9B1D-4E83431662DD]@0xffffff7f85284000
    dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0xffffff7f85241000
    com.apple.nvidia.classic.NVDANV50HalTesl
     
  2. Weaselboy Moderator

    Weaselboy

    Staff Member

    Joined:
    Jan 23, 2005
    Location:
    California
    #2
    Looks like the GPU (video chip) crashed. It could just be a bug with the game. Does this ever happen when using the computer normally not playing games? If not, I would not worry too much about it.
     
  3. ryanngreen thread starter macrumors newbie

    Joined:
    Sep 21, 2014
    #3
    It has not ever happened before with our without a game playing. I just wanted to make sure it wasn't anything really serious that I needed to take my computer in for our of playing anymore games would mess it up further.
     
  4. Brian Y macrumors 68040

    Joined:
    Oct 21, 2012
    #4
    Let me guess - 2012 15" Retina by any chance?

    If it's under warranty, take it in for an MLB replacement. It's not the dedicated GPU that stopped responding, it's the onboard/integrated.
     
  5. ryanngreen thread starter macrumors newbie

    Joined:
    Sep 21, 2014
    #5
    It's actually the mid 2010 but you are correct about the 15" MacBook pro. And it hasn't been under warranty for a while now, unfortunately.
     
  6. Brian Y macrumors 68040

    Joined:
    Oct 21, 2012
    #6
    http://support.apple.com/kb/TS4088?viewlocale=en_US&locale=en_US

    Depending on when it was bought - you may still be under this program for GPU failure.
     
  7. ryanngreen thread starter macrumors newbie

    Joined:
    Sep 21, 2014
    #7
    That sounds very much like what I experienced. I've scheduled an appointment with Apple. Thank you very much for the link and information.
     
  8. namethisfile macrumors 6502a

    namethisfile

    Joined:
    Jan 17, 2008
    #8
    That looks like the same issue I was having with my Mid-2010 15" MBP, too. Make a reservation to the Apple Genius Bar and mention that your MBP is exhibiting issues related to the "TS4088" article. With any luck, they will own up to the fact that the machine has a "Latent Manufacturing Defect" and will replace the logic board free of charge. If, not, try to speak to the manager. And, then try again at a later time, if the manager refuses. Maybe try a different store or the same store a couple of weeks later. The KP might be random and few and far between, now. But, my experience with it is that the KP's become more prevalent. Especially, with Mavericks. Mine would KP even if I just clicked on Safari. I was clicking on Safari and Kping each time, while I sat and waited at the Apple Genius Bar. Thankfully, the kind Apple person working there took pity on my wonky MBP and decided to cover the repair, even, though my MBP was pass the 3 year warranty. That was my second time taking it to the Apple Store. The first time was in April earlier this year. But, i just walked out of the store that time since I couldn't afford the logic board replacement fee. On my second time, though, I was a little more insistent and asked to speak to a manager. I don't know if that made the difference or not. But, it worked. So, give it a shot.

    What version OS X are you using? I'm asking because it sounds like it is one of your first experience Kping on that machine. I've always had the KP issue since I got mine in 2010. The video patch Apple release in Snow Leopard sort of made the issue disappear, for a while. But, it was always there and always "latent." It got worse and worse with Mavericks. I thought it was only when pushing the machine. But, as I mentioned, even merely clicking on Safari triggered the KP, for me. So, hopefully, you can get yours fixed. And, free of charge since it is a "Latent Manufacturing Defect" and not something you did or even, parts of the machine failing over time. Like, it came out defective from the factory... so... hopefully, Apple will step up to the plate for you, too.
     

Share This Page