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

MacBook Pro crashed

Below is the KP, but I'm pretty new to using Mac's and the OS so not too sure what is going on.


*** Panic Report ***

panic(cpu 2 caller 0xffffff802039d764): launchd exited (signal 9, exit status 0 CS_KILLED)



uuid info:

0x7fff69596000 uuid = <9d05fdf4-65ce-3b53-86d4-abe1a5bf35f3>

0x108d03000 uuid = <f9041ce4-2cdc-350f-8a46-6a8d32a51a2b>



Thread 3 crashed



RAX: 0x0000000000000000, RBX: 0x00007fff695d65f8, RCX: 0x0000000108d03a00, RDX: 0x0000000108d4a790

RSP: 0x0000700000080750, RBP: 0x00007000000807d0, RSI: 0x00000000000001b1, RDI: 0x00007fff695d65f8

R8: 0x00007fff916f0119, R9: 0x0000700000080b40, R10: 0x0000000000001200, R11: 0x0000000108d42170

R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0x0000000108d48839

RFL: 0x0000000000010246, RIP: 0x00007fff695b0350, CS: 0x000000000000002b, SS: 0x0000000000000023



Thread 0: 0xffffff804104a490

0x00007fff9a386d01

0x0000000000000000



Thread 1: 0xffffff804104b240

Could not read LR from frame at 0x0000700000199d48



Thread 2: 0xffffff804104a000

0x00007fff9a3957b6

0x0000000000000000



Thread 3: 0xffffff8057a6d920

0x00007fff6959a063

0x00007fff916f0262

0x0000000108d42170

0x0000000108d2fc72

0x00007fff9a38133f

0x00007fff9a391676

0x00007fff9a3859b7

0x00007fff9a386134

0x00007fff9a38c63b

0x00007fff9a384c87

0x00007fff9a384a34

0x00007fff8f01968f

0x00007fff8f017365

0x0000000000000000



Thread 4: 0xffffff80579d3240

0x0000000108d2d527

0x00007fff9a399324

0x00007fff9a38133f

0x00007fff9a385f6f

0x00007fff9a38c63b

0x00007fff9a384c87

0x00007fff9a384a34

0x00007fff8f01968f

0x00007fff8f017365

0x0000000000000000



Mac OS version: 15D21

Kernel version: Darwin Kernel Version 15.3.0: Thu Dec 10 18:40:58 PST 2015; root:xnu-3248.30.4~1/RELEASE_X86_64

Kernel UUID: DECC9F02-27D7-31F0-9599-A9EF2873902C

System model name: MacBookPro11,5 (Mac-06F11F11946D27C5)

Model: MacBookPro11,5, BootROM MBP114.0172.B07, 4 processors, Intel Core i7, 2.8 GHz, 16 GB, SMC 2.30f2

Graphics: AMD Radeon R9 M370X, AMD Radeon R9 M370X, PCIe, 2048 MB

Graphics: Intel Iris Pro, Intel Iris Pro, Built-In

Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x802C, 0x31364B544631473634485A2D314736453120

Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x802C, 0x31364B544631473634485A2D314736453120

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x152), Broadcom BCM43xx 1.0 (7.21.94.136.1a1)

Bluetooth: Version 4.4.3f4 16616, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

Serial ATA Device: APPLE SSD SM0512G, 500.28 GB

USB Device: USB 3.0 Bus

USB Device: Card Reader

USB Device: Apple Internal Keyboard / Trackpad

USB Device: Bluetooth USB Host Controller

Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1

MacBook Pro with Retina display, OS X El Capitan (10.11.3)

Posted on Jan 30, 2016 6:42 PM

Reply
3 replies

Jan 31, 2016 7:54 AM in response to apetrie91

That kind of panic is caused by a drive failure when FileVault is active.

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.

MacBook Pro crashed

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