Kernal Panic - does this report say why?

Discussion in 'MacBook Pro' started by iOrbit, Aug 9, 2013.

  1. iOrbit macrumors 6502a

    Mar 8, 2012
    i had a kernal panic about half an hour ago, i just started using the App MakeMKV when it happened.

    can anyone interpret what happened here? i'm worried my hardware is perhaps deteriorating - i run it at high cpu temps frequently for some extended periods and i've notice in the last 3 months that it takes longer to run cooler like it did in its first year, and generally runs hotter. i have a late 2011 MacBook Pro. here is the report:

    Fri Aug 9 10:29:59 2013
    panic(cpu 6 caller 0xffffff8004cb8655): Kernel trap at 0xffffff8004c87eec, type 13=general protection, registers:
    CR0: 0x0000000080010033, CR2: 0x0000000018120000, CR3: 0x00000000573d205d, CR4: 0x00000000000606e0
    RAX: 0x0000000000000001, RBX: 0x01ff8193c24d2cc0, RCX: 0xffffff80266fe618, RDX: 0x0000000000000821
    RSP: 0xffffff81d58e3d70, RBP: 0xffffff81d58e3d90, RSI: 0x0000000020b54117, RDI: 0xffffff8009d6cdf0
    R8: 0xffffff81d58e3ee0, R9: 0xffffff81d58e3ed0, R10: 0x000000000a400000, R11: 0x00000000ffffff00
    R12: 0xffffff8009d6cdf0, R13: 0xffffff802d1f17e0, R14: 0xffffff802d1f17e0, R15: 0x0000000000020000
    RFL: 0x0000000000210206, RIP: 0xffffff8004c87eec, CS: 0x0000000000000008, SS: 0x0000000000000000
    Fault CR2: 0x0000000018120000, Error code: 0x0000000000000000, Fault CPU: 0x6

    Backtrace (CPU 6), Frame : Return Address
    0xffffff81d58e3a10 : 0xffffff8004c1d626
    0xffffff81d58e3a80 : 0xffffff8004cb8655
    0xffffff81d58e3c50 : 0xffffff8004cce17d
    0xffffff81d58e3c70 : 0xffffff8004c87eec
    0xffffff81d58e3d90 : 0xffffff8004c62dbb
    0xffffff81d58e3f20 : 0xffffff8004cb8aa0
    0xffffff81d58e3fb0 : 0xffffff8004cce0a1

    BSD process name corresponding to current thread: makemkv

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 12.4.0: Wed May 1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64
    Kernel UUID: 896CB1E3-AB79-3DF1-B595-549DFFDF3D36
    Kernel slide: 0x0000000004a00000
    Kernel text base: 0xffffff8004c00000
    System model name: MacBookPro8,2 (Mac-94245A3940C91C80)

    System uptime in nanoseconds: 7651502864608
    last loaded kext at 7505938207044: 2.3 (addr 0xffffff7f87287000, size 270336)
    last unloaded kext at 5330413698218: 4.1.23 (addr 0xffffff7f87284000, size 12288)
    loaded kexts:
    com.parallels.kext.prl_vnic 7.0 15107.796624
    com.parallels.kext.prl_netbridge 7.0 15107.796624
    com.parallels.kext.prl_hid_hook 7.0 15107.796624
    com.parallels.kext.prl_hypervisor 7.0 15107.796624
    com.parallels.kext.prl_usb_connect 7.0 15107.796624
    com.eltima.ElmediaPlayer.kext 1.58
    net.telestream.driver.TelestreamAudio 1.0.6
    com.Cycling74.driver.Soundflower 1.5.2
    com.AmbrosiaSW.AudioSupport 4.1.2 2.3 1.8.4 10.0 7.1.0 75.19 1.9.5d0 3.0 4.1.4f2 3.10 100.12.87 122 8.1.2 2.3.7fc4 1.0.8 1.6.0 2.3.7fc4 3.5.10 2.0.3d0 1.0.0 1.60 4.1.4f2 1.1.11 3.0.3d1 3.4.5 1.0.0d1 7.0.0 3.4.5 1.0.0 8.1.2 8.1.2 237.1 237.1 320.15 1.0.0d1 1.0.0d1 34 3.5.5 404 2.3.1 5.5.5 1.4.2 4.9.6 3.6.1b4 615.20.17 2.5.2 5.5.0 1.7 161.0.0 1.7 1.5 1.8 1.9 1.7 1.6 196.0.0 4.0.39 2.1 196.0.0 2.9.0f8 3.5.5 3.5.1 170.2 170.2 1.0 235.29 1.0 10.0.6 2.3.7fc4 74.5.1 8.1.2 8.1.2 2.2.5 4.1.4f2 1.0.11d0 1.0.4 86.0.4 1.8.9fc11 1.6 3.4.5 1.0.11d0 1.0.0 5.3.0d51 2.3.7 3.1.4d2 2.3.7fc4 2.3.7 2.3.7fc4 1.8.9 1.8.9 1.2.6 237.3 4.1.4f2 4.1.4f2 5.2.5 5.5.5 5.2.5 3.5.5 1.7 1.7.1 1.7.1 2.5.1 3.5.5 1.7.8 2.4.0 5.5.5 4.5.5 1.0.2b1 530.4 3.0 2.3.1 5.6.0 1.7 1.8.1 1.1 220.3 1.0.0d1 7 345 1.8 28.21 1.7 2.7.3 1.4 1.0
  2. simsaladimbamba

    Nov 28, 2010
    Does it happen regularly? If not, do not worry.
    Anyway, the reason for the kernel panic was MAKEMKV. It might be just a coincidence and a one-time occurrence though.

    As for the temperature, if you search the fora via Advanced Search or MRoogle you will fin plenty of threads about 2011 MBPs and their heat performance due to the cooling paste applied to the CPU and cooler. Many have reapplied the paste and have fared better. Also know, that the cooling paste may just have dried out and is not working anymore.
  3. iOrbit thread starter macrumors 6502a

    Mar 8, 2012
    i don't experience them often, i think i may have experienced them a total of 3-5 times since i've bought it. likely around 3-4 times.

    the last time was probably over 3-4 months ago at least.

    i have reapplied thermal paste to a computer before, so i suspected it is the case, and my frequest high temp usage of the machine has dried out the crappy paste work apple have the manufacturers do. however, despite upgrading this macbook, i have extended apple care on it and would lack the comfort and confidence in risking taking it apart, as i don't consider myself skilled.

    i'm going to look through that thread and see.

    in my experience, within the first 12-14 months, the macbook pro would always feel cool if i wasnt doing high cpu usage stuff. even after it would be running at 88 C degrees on average for a few hours, it would cool down to how it was pretty much within an hour or after. not anymore though, generally the left upper keyboard area feels hot, and consistently. if i don't use it for maybe near 2 hours or more than it gets nearly as cool as it used to, but warm to hot very quickly again in less than intense cpu usage.

    i know when it dies apple care will sort it out, but i wondered - can i get them to 'improve-repair' the machine to a more optimal state by telling them its running hot? i.e. thermal paste replacement , replacing fans? (sometimes it can make a very slight noise that it didnt before) and that it generally just runs hotter.

    thanks for replying
  4. simsaladimbamba

    Nov 28, 2010
    Not really, unless it is faulty.
  5. MichaelGraubart, Sep 5, 2013
    Last edited: Sep 5, 2013

    MichaelGraubart macrumors newbie


    Apr 13, 2008
    London, UK
    Soundflower and Kernel Panics

    I have a Mac mini (Intel, late 2012) with OS 10.8.4 (Mountain Lion).

    I recently installed Soundflower, which was easy to use and worked well. But then I started having kernel panics. Similarly to the crash report quoted in the posts above, mine implicated "com.Cycling74.driver.Soundflower 1.6.6".

    I then discovered from issue no, 113 on <> that I was not the only one with this problem.

    I uninstalled Soundflower (searching for all hidden as well as visible associated files), but this morning I had another panic. Here is the text that appeared after I had restarted the computer:

    Panic(cpu 3 caller 0xffffff00040b8655): Kernel trap at 0xffffff0004087ca3, type 14=page faul regist rs:

    This time there was no comprehensive crash report, unfortunately, probably because I had to try restarting the computer several times before it worked.

    Either Soundflower had corrupted my operating system (for which there is some evidence on the Google Code page mentioned above) or it was a random accident. I have now downloaded a fresh OS X 10.8.4 operating system from Apple, reinstalled it, checked my S.M.A.R.T status and the partition map of my HD, and am awaiting results.

    I have now had an increasingly acrimonius to-and-fro correspondence with the Cycling 74 people from whose website one obtains Soundflower, the upshot being that they do not develop Soundflower, have no responsibility for it, know nothing about updates that might prevent this disastrous apparent behaviour of Soundflower. If they do not develop it, did they find it growing in a field with other wild flowers?

Share This Page