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

Kernel panic

Hi


Can anyone help me out - what is this kernel panic caused by?


Thanks!


Anonymous UUID: 56CFE5BB-35D2-BA05-FF0E-82A7067E4447


Fri Sep 25 07:40:20 2015


*** Panic Report ***

panic(cpu 2 caller 0xffffff800cfc127e): "launchd died\nState at Last Exception:\n\n"@/SourceCache/xnu/xnu-2782.40.9/bsd/kern/kern_exit.c:363


uuid info:

0x7fff69005000 uuid = <b1b370a5-479f-3533-8ad7-97b687d4f989>

0x10a5b0000 uuid = <c0446878-e8d0-3461-a226-91ff1c2b2da6>

0x10a603000 uuid = <4396b358-725e-3ec0-bcbb-e4bf75fe1fb0>


RAX: 0x0000000002000001, RBX: 0x0000000000000006, RCX: 0x000000010b3920e8, RDX: 0x0000000000000000

RSP: 0x000000010b3920e8, RBP: 0x000000010b392190, RSI: 0x000000010b391f40, RDI: 0x0000000000000001

R8: 0x0000000000000000, R9: 0x000000010a5ef9f0, R10: 0x00007fff9478fb02, R11: 0x0000000000000206

R12: 0x0000000000000000, R13: 0x00007fff8aa277e0, R14: 0x000000010b3925d0, R15: 0x000000010b392790

RFL: 0x0000000000000206, RIP: 0x00007fff9478d95a, CS: 0x0000000000000007, SS: 0x0000000000000023


Thread 0xffffff801ef5ec50

0x00007fff8c5b6dab

0x00007fff8c5b6ec8

0x00007fff8c5b03b4

0x00007fff8ca60a6c

0x000000010a5de907

0x00007fff901a9c13

0x00007fff901ac88f

0x00007fff901bafe4

0x00007fff8be09a9d

0x00007fff8be073dd

0x0000000000000000


Thread 0xffffff801f031000

0x00007fff901aca6a

0x0000000000000000


Thread 0xffffff801f0b45c0

0x000000010a5c7c91

0x00007fff901a9c13

0x00007fff901ad365

0x00007fff901aeecc

0x00007fff901ac6b7

0x00007fff901bafe4

0x00007fff8be09a9d

0x00007fff8be073dd

0x0000000000000000


Thread 0xffffff801f0b3c50

0x00007fff901ba3ad

0x0000000000000000


Thread 0xffffff8020400e28

0x00007fff9631af1a

0x0000000000000000

0x00007fff69011475

0x00007fff8c7bd7b5

0x00007fff8c585648

0x00007fff8aa277e0

0x00007fff8aa29ddf

0x00007fff901a9c13

0x00007fff901aae5e

0x00007fff8aa280a7

0x000000010a5db393

0x00007fff901a9c13

0x00007fff901ad365

0x00007fff901aeecc

0x00007fff901ad154

0x00007fff901aeecc

0x00007fff901ac6b7

0x00007fff901bafe4

0x00007fff8be09a9d

0x00007fff8be073dd

0x0000000000000000


Thread 0xffffff801fcf14b8

0x00007fff901b487e

0x00007fff901ad62b

0x00007fff901ad154

0x00007fff901aeecc

0x00007fff901ac6b7

0x00007fff901ac453

0x00007fff8be0a05a

0x00007fff8be09fd7

0x00007fff8be073ed

0x0000000000000000


Thread 0xffffff801f97ea78

0x00007fff8be073dd

0x0000000000000000


Thread 0xffffff80211335c0

0x00007fff8be073dd

0x0000000000000000


Thread 0xffffff80219c9e28


Mac OS version: 14F27

Kernel version: Darwin Kernel Version 14.5.0: Wed Jul 29 02:26:53 PDT 2015; root:xnu-2782.40.9~1/RELEASE_X86_64

Kernel UUID: 58F06365-45C7-3CA7-B80D-173AFD1A03C4

System model name: MacBookPro11,1 (Mac-189A3D4F975D5FFC)


System Profile:

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x112), Broadcom BCM43xx 1.0 (7.15.166.24.3)

Bluetooth: Version 4.3.6f3 16238, 3 services, 18 devices, 1 incoming serial ports

Thunderbolt Bus: MacBook Pro, Apple Inc., 17.2

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463531323634485A2D314736453120

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463531323634485A2D314736453120

USB Device: Internal Memory Card Reader

USB Device: Apple Internal Keyboard / Trackpad

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

Serial ATA Device: APPLE SSD SM0512F, 500,28 GB

Model: MacBookPro11,1, BootROM MBP111.0138.B15, 2 processors, Intel Core i5, 2.8 GHz, 8 GB, SMC 2.16f68

Network Service: Wi-Fi, AirPort, en0

Graphics: Intel Iris, Intel Iris, Built-In

MacBook Pro, OS X Yosemite (10.10.5)

Posted on Sep 26, 2015 2:07 AM

Reply
3 replies

Sep 26, 2015 10:04 AM in response to Linc Davis

Yes, it happens frequently.


My Macbook Pro crashes efter being on standby for several hours. Typically overnight. When I open the screen to use it, the computer has crashed and needs to be rebooted. The logfile then reports "kernel panic".


The local Apple service provider has changed the logic board. The error still occurs...

Sep 26, 2015 11:31 AM in response to npnimb

The panics are caused either by a hardware fault or by an obscure bug in OS X.

Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. You may have to leave the machine there for several days.

Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional—ask if you need guidance.

If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.

Keeping your confidential data secure during hardware repair

Apple also recommends that you deauthorize a device in the iTunes Store before having it serviced.

*An SSD doesn't need to be zeroed.

Kernel panic

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