Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Kernel Panics During and After 10.10.3 upgrade

I have recently experienced two Kernel Panics on my MacBook Pro (13 inch, mid-2012). The first one happened during the upgrade process to 10.10.3 right at the end. The second happened today while browsing the web. Apple Hardware Test and Memtest turned up nothing. An Apple support rep guided me through deleting chaches, lauchdeamons, startup items and some other stuff. Can anyone tell from the logs pasted below what the cause of the problem might be. Is it at all likely to be a bad 10.10.3 update?


I haven't been able to post the whole report because of an error in the forum "the message contains invalid characters"


First Report (end of upgrade to 10.10.3):

Anonymous UUID: 2F268169-983A-6C24-0051-DA8D97195C57


Wed Apr 8 19:37:02 2015

*** Panic Report ***

panic(cpu 1 caller 0xffffff802f61a46e): Kernel trap at 0xffffff802f593078, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0xffffff81392d4ff8, CR3: 0x00000000110f8028, CR4: 0x00000000001626e0

RAX: 0xffffffffffffffff, RBX: 0x0000000000000000, RCX: 0xffffff81392d5000, RDX: 0x0000000000000000

RSP: 0xffffff81388b3b10, RBP: 0xffffff81388b3b70, RSI: 0xffffff8052c9a044, RDI: 0xffffff802fcd9904

R8: 0xffffff80421ec5b0, R9: 0xfffffffffffff000, R10: 0xffffff80421ec5a0, R11: 0xffffff8042226ba0

R12: 0xffffff802fcd9904, R13: 0x0000000000000000, R14: 0xffffff8052c9a000, R15: 0x0000000000000003

RFL: 0x0000000000010296, RIP: 0xffffff802f593078, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0xffffff81392d4ff8, Error code: 0x0000000000000000, Fault CPU: 0x1

Backtrace (CPU 1), Frame : Return Address

0xffffff81388b37c0 : 0xffffff802f52fe41

0xffffff81388b3840 : 0xffffff802f61a46e

0xffffff81388b3a00 : 0xffffff802f636683

0xffffff81388b3a20 : 0xffffff802f593078

0xffffff81388b3b70 : 0xffffff802f5938be

0xffffff81388b3bd0 : 0xffffff802f5bf8f0

0xffffff81388b3c10 : 0xffffff802f5bf65e

0xffffff81388b3c40 : 0xffffff802f5b6a95

0xffffff81388b3c80 : 0xffffff802f5b063a

0xffffff81388b3d90 : 0xffffff802f5a697c

0xffffff81388b3dc0 : 0xffffff802f5523d7

0xffffff81388b3e00 : 0xffffff802f9c16ff

0xffffff81388b3e70 : 0xffffff802f9d8fc2

0xffffff81388b3ef0 : 0xffffff802f9d9497

0xffffff81388b3f30 : 0xffffff802f52c376

0xffffff81388b3f60 : 0xffffff802f61ab8e

0xffffff81388b3f80 : 0xffffff802f63664f

BSD process name corresponding to current thread: blued

Mac OS version:

14C1514

Kernel version:

Darwin Kernel Version 14.1.0: Thu Feb 26 19:26:47 PST 2015; root:xnu-2782.10.73~1/RELEASE_X86_64

Kernel UUID: 270413F7-3B44-3602-894F-AC0D392FCF8E

Kernel slide: 0x000000002f200000

Kernel text base: 0xffffff802f400000

__HIB text base: 0xffffff802f300000

last loaded kext at 117432601792451: com.apple.driver.AppleUSBCDC 4.2.2b5 (addr 0xffffff7fb1e00000, size 20480)

last unloaded kext at 117493781525860: com.apple.driver.AppleUSBCDC 4.2.2b5 (addr 0xffffff7fb1e00000, size 16384)

loaded kexts:




Second report (browsing the web with Firefox):


Anonymous UUID: 2F268169-983A-6C24-0051-DA8D97195C57


Mon Apr 27 14:59:15 2015

*** Panic Report ***

panic(cpu 0 caller 0xffffff8002617cc2): Kernel trap at 0xffffff7f8447c6ff, type 6=invalid opcode, registers:

CR0: 0x0000000080010033, CR2: 0x000000010cac1008, CR3: 0x00000001f5f670f4, CR4: 0x00000000001626e0

RAX: 0xffffff8002c80020, RBX: 0xffffff810b84b8a8, RCX: 0xffffff802e4a1b00, RDX: 0x0000000000002000

RSP: 0xffffff810b84b828, RBP: 0xffffff810b84b890, RSI: 0x0000000000000001, RDI: 0x0000000013000001

R8: 0xffffff8020ce00c0, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0xffffff8013e4e168

R12: 0x0000000000000850, R13: 0xffffff8002c80020, R14: 0xffffff80244ab2d0, R15: 0x0000000013000001

RFL: 0x0000000000010206, RIP: 0xffffff7f8447c6ff, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0x000000010cac1008, Error code: 0x0000000000000000, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address

0xffffff810b84b4d0 : 0xffffff800252bda1

0xffffff810b84b550 : 0xffffff8002617cc2

0xffffff810b84b710 : 0xffffff8002634b73

0xffffff810b84b730 : 0xffffff7f8447c6ff

0xffffff810b84b890 : 0xffffff800276f2b7

0xffffff810b84b8f0 : 0xffffff8002762dd6

0xffffff810b84b990 : 0xffffff800274e5b8

0xffffff810b84bbd0 : 0xffffff800274f190

0xffffff810b84bf50 : 0xffffff8002a4ba86

0xffffff810b84bfb0 : 0xffffff8002635376

Kernel Extensions in backtrace:

com.apple.filesystems.autofs(3.0)[B2C3E47B-4270-3D65-86AF-1AA7EB8B509B]@0xfffff f7f84478000->0xffffff7f84480fff

dependency: com.apple.kext.triggers(1.0)[F36ADAAF-ADCB-3EE7-B040-4B7C45A1CCEB]@0xffffff7f83 137000

BSD process name corresponding to current thread: osascript


MacBook Pro, OS X Yosemite (10.10.3)

Posted on Apr 27, 2015 12:18 PM

Reply
Question marked as Best reply

Posted on Apr 27, 2015 3:24 PM

In case anyone else has this issue: it seems like an outdated version of Soundflower was the culprit.

4 replies

Kernel Panics During and After 10.10.3 upgrade

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.