Third kernel panic in a week

Discussion in 'MacBook' started by Milchschokolade, Aug 17, 2017.

  1. Milchschokolade macrumors newbie

    Joined:
    Nov 30, 2014
    #1
    Something is seriously not right with my trusty Macbook. This Mid 2010 unibody white has served me for a long time without a single issue.

    I'm running OS X 10.9.5 - the computer is a 2.4 C2D, upgraded to 8 GB of RAM many years ago. Never any problems. Ever.

    Over the weekend I got a kernel panic restart while browsing the web.

    Next day it happened again! And it happened while the laptop was idle. The computer was on the screen saver, about to go to sleep any minute, and then it just restarted.

    I was worried but then not much happened for the next few days. Then just now I was watching Netflix and the computer restarted again (report attached below). And now it's all fine - in fact, I'm writing from this very computer!

    3 kernel panic restarts in less than a week? What the heck is happening? Is my computer about to kick the bucket? :(

    This never happened before. I haven't installed any new software in months. No changes. I have no idea what's going on.

    Only thing I can think of is that I'm a pretty heavy Chrome user (which hogs way more resources than it should). But then again, I used Chrome for years and years and always had way too many tabs open... so this isn't anything new.

    What's the deal? Please help!

     
  2. Erdbeertorte macrumors demi-goddess

    Joined:
    May 20, 2015
    #2
    I would check the SMART status of your old HDD what might be probably failing completely soon or it's the SATA cable. Just search for an app what could do this.


    You could also run this before: http://etrecheck.com and post the protocol here, so we can see if there might be something else wrong with your Mac.


    Apple Hardware Test could also help if it's the RAM or anything else: https://support.apple.com/en-us/HT201257


    And an NVRAM + SMC reset is always worth a try before doing anything else:

    https://support.apple.com/en-us/HT204063

    https://support.apple.com/en-us/HT201295
     
  3. Milchschokolade, Aug 17, 2017
    Last edited: Aug 17, 2017

    Milchschokolade thread starter macrumors newbie

    Joined:
    Nov 30, 2014
    #3
    Thanks for the help. Here's the etrecheck report!

    Code:
    Anonymous UUID:       697A0422-EE22-9694-0ABB-073B5E96F18C
    
    
    
    Thu Aug 17 19:49:02 2017
    
    panic(cpu 1 caller 0xffffff8012edcc1d): Kernel trap at 0xffffff8012ed1b57, type 13=general protection, registers:
    
    CR0: 0x0000000080010033, CR2: 0x000000011554f000, CR3: 0x00000000aa017000, CR4: 0x0000000000000660
    
    RAX: 0xffffffffffffffff, RBX: 0xc0ffeedfe152f30a, RCX: 0xffffff8114c3e000, RDX: 0xc0ffeedfe152f30a
    
    RSP: 0xffffff801fd8bc80, RBP: 0xffffff801fd8bc80, RSI: 0xffffff8028455490, RDI: 0xc0ffeedfe152f30a
    
    R8:  0x0000000000000001, R9:  0x0000000000000100, R10: 0x0000000000051767, R11: 0x000002c4af8c4ed0
    
    R12: 0x0000000000000001, R13: 0xffffff80134cc484, R14: 0x0000000000000001, R15: 0xffffff80134cc494
    
    RFL: 0x0000000000010296, RIP: 0xffffff8012ed1b57, CS:  0x0000000000000008, SS:  0x0000000000000000
    
    Fault CR2: 0x000000011554f000, Error code: 0x0000000000000000, Fault CPU: 0x1
    
    
    
    Backtrace (CPU 1), Frame : Return Address
    
    0xffffff810e9cddf0 : 0xffffff8012e23139
    
    0xffffff810e9cde70 : 0xffffff8012edcc1d
    
    0xffffff810e9ce040 : 0xffffff8012ef4486
    
    0xffffff810e9ce060 : 0xffffff8012ed1b57
    
    0xffffff801fd8bc80 : 0xffffff8012e7073e
    
    0xffffff801fd8bd00 : 0xffffff8012e7062b
    
    0xffffff801fd8bd30 : 0xffffff8012e71e76
    
    0xffffff801fd8bd50 : 0xffffff8012e78db1
    
    0xffffff801fd8bf20 : 0xffffff8012edd05c
    
    0xffffff801fd8bfb0 : 0xffffff8012ef438b
    
    
    
    BSD process name corresponding to current thread: Google Chrome He
    
    
    
    Mac OS version:
    
    13F1911
    
    
    
    Kernel version:
    
    Darwin Kernel Version 13.4.0: Mon Jan 11 18:17:34 PST 2016; root:xnu-2422.115.15~1/RELEASE_X86_64
    
    Kernel UUID: 8926E512-6714-34FC-B27C-6AE90EB51D5E
    
    Kernel slide:     0x0000000012c00000
    
    Kernel text base: 0xffffff8012e00000
    
    System model name: MacBook7,1 (Mac-F22C89C8)
    
    
    
    System uptime in nanoseconds: 140882964405056
    
    last loaded kext at 52589015169554: com.apple.driver.AppleUSBCDC 4.2.1b5 (addr 0xffffff7f95150000, size 20480)
    
    las
     
  4. Frosties, Aug 17, 2017
    Last edited: Aug 17, 2017

    Frosties macrumors 6502a

    Frosties

    Joined:
    Jun 12, 2009
    Location:
    Sweden
    #4
    Reset your ram modules as they can become unseated. It is a mobile computer. Could also be some problem with your graphics card. With my generation mbp late 2010 it was those usual suspects. Last clear your fan and rest of the computer plus check that the fan is running so it's not heat related.
     
  5. Milchschokolade, Aug 17, 2017
    Last edited: Aug 17, 2017

    Milchschokolade thread starter macrumors newbie

    Joined:
    Nov 30, 2014
    #5
    is that the NVRAM + SMC reset mentioned by another poster, or is this something else?

    I did the NVRAM + SMC

    I couldn't do Apple Hardware Test because no matter what I do (D or alt-D) nothing shows up. I tried it several times with different timing, it seems like it delays the apple logo from coming on, but the globe icon does not appear :-/ eventually the computer just boots.
     
  6. Frosties macrumors 6502a

    Frosties

    Joined:
    Jun 12, 2009
    Location:
    Sweden
    #6
  7. auroralaptop macrumors newbie

    auroralaptop

    Joined:
    Oct 22, 2017
    #7
    A kernel panic can also be caused by damaged or incompatible hardware, including external devices attached to your Mac. If removing/replacing your ram modules don't correct the problem, consider having the faulty capacitor replaced, this is a known issue for 2009 - 2010 models.
     
  8. EugW macrumors 68040

    EugW

    Joined:
    Jun 18, 2017
    #8
    RAM modules can actually go bad after all this time too. Try memtest after a RAM reseat and hope it's the RAM and not something else like the GPU, etc.).
     

Share This Page