About 1 month ago, my MacBook Pro started crashing. The screen locks up and then it hard crashes. At this point, it is after about 2 minutes of activity. I recently took it in to a repair shop and they upgraded the OS and reinstalled apps from scratch. When I re-login I get the Panic Report, but not any useful information to do more troubleshooting.
If your Mac spontaneously restarts or displays a ... - Apple Support
https://support.apple.com/en-us/HT200553
You can post your Kernel Panic report in their entirety here, preferable three separate reports in three separate "Additional Text" box (see menu below) for ease of reading and comparison. A single report may be useful but does not establish a trend for a meaningful diagnosis.
Kernel Panic reports can be found /Library/Logs/DiagnosticReports
From the Finder>Go>Go To Folder, copy and paste:
/Library/Logs/DiagnosticReports
ends in .panic post the whole report if it meets that.
If your Mac spontaneously restarts or displays a ... - Apple Support
https://support.apple.com/en-us/HT200553
You can post your Kernel Panic report in their entirety here, preferable three separate reports in three separate "Additional Text" box (see menu below) for ease of reading and comparison. A single report may be useful but does not establish a trend for a meaningful diagnosis.
Kernel Panic reports can be found /Library/Logs/DiagnosticReports
From the Finder>Go>Go To Folder, copy and paste:
/Library/Logs/DiagnosticReports
ends in .panic post the whole report if it meets that.
I was able to get my issue resolved through an Apple Repair. The logic board and flash storage were replaced. Fortunately, my Mac is still under warranty through Apple Care and it was fully covered.
Thanks everyone for your input. I am back up and running like new!
What is the exact model of your laptop? You can get this information by clicking the Apple menu and selecting "About this Mac" or by entering the system serial number here.
To test the memory for an extended time you can create a bootable Memtest86 USB drive using Etcher (Mac/Windows/Linux). Option Boot the Memtest86 drive and select the orange icon labeled "EFI". Once Memtest86 finishes booting it is safe to remove the USB drive. By default Memtest86 only runs for four loops, but this can be extended in the Test Options menu. Sometimes you may have to let the tests run for a day or two or even more before a failure may appear especially if you have a large amount of memory to test.
FYI, there is another option to run Memtest86 tests in parallel using other CPU cores, but this is disabled by default.
Normally using the "A" model designations is not recommended for identification because they can cover multiple models over several years. In this case it shows you have a 2016 or 2017 13" MBPro without a touchbar. This particular model has several free Apple repair programs associated with it. The most important one is for the SSD. See if you qualify for the free SSD repair program and keep the other programs in mind for any future issues. If you qualify for the SSD repair make sure to back up all your data as Apple will erase and reinstall macOS.
You have succeeded is posting the name of the file, but not the file contents.
You need to open the file, select its text, copy and paste into the reply.
Please do not post more than 20 lines of text from those other report types -- they are helpful for the developer, but not for debugging, and they are interminable.
The photo of the screen and the posted panic report are caused by completely different issues. This is the start of a NON-Trend, where panics happen "all over the Map" for apparently unrelated issues. This correlates strongly with RAM Memory problems.
The reason this gives wonky symptoms is that MacOS slightly randomizes the load point of certain key routines as a hedge against fixed-address malware attacks. so the Bad memory cell moves into a completely different routine, and when if fails causes completely different havoc (or sometimes no havoc at all).
To get more evidence, you should try to run a memory test. It may take an overnight test to catch this failure in the act. The reason for the RAM soldered in place is that in portable computers, it increases the reliability (of the entire fleet of these machines) enormously. The downside is that when a problem does occur, a mainboard swap is required to fix it.
If Apple can be convinced to swap the mainboard, you will NOT be getting your same drive back, as the boot drive components are soldered to the mainboard as well. You need to make a full backup, and preferably two, and use Setup Assistant or Migration Assistant or be prepared to do a Restore when your Mac comes back to you.
2nd Report:
Mon Jul 1 18:40:56 2019
*** Panic Report ***
panic(cpu 2 caller 0xffffff80152db92d): Kernel trap at 0xffffff80152d43e3, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000029, CR3: 0x000000007f2c213d, CR4: 0x00000000003626e0
RAX: 0x0000000000000001, RBX: 0xffffff8030445770, RCX: 0x000000000bebc200, RDX: 0xffffff8030445520
RSP: 0xffffff8021dbbc28, RBP: 0xffffff8021dbbc70, RSI: 0x0000000000000021, RDI: 0x0000000000000021
R8: 0x000000003b5dc100, R9: 0x00000000195fb09d, R10: 0x0000000000000000, R11: 0x0000023606e7c552
R12: 0x0000000000000021, R13: 0x0000023612d38752, R14: 0xffffff80304457b0, R15: 0x0000000000000001
RFL: 0x0000000000010002, RIP: 0xffffff80152d43e3, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000029, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 4, VF: 0
Backtrace (CPU 2), Frame : Return Address
0xffffff8021dbb6f0 : 0xffffff80151aea2d
0xffffff8021dbb740 : 0xffffff80152e9e95
0xffffff8021dbb780 : 0xffffff80152db70a
0xffffff8021dbb7f0 : 0xffffff801515bb40
0xffffff8021dbb810 : 0xffffff80151ae447
0xffffff8021dbb930 : 0xffffff80151ae293
0xffffff8021dbb9a0 : 0xffffff80152db92d
0xffffff8021dbbb10 : 0xffffff801515bb40
0xffffff8021dbbb30 : 0xffffff80152d43e3
0xffffff8021dbbc70 : 0xffffff80151f558d
0xffffff8021dbbd30 : 0xffffff80151fb5e3
0xffffff8021dbbda0 : 0xffffff801519393b
0xffffff8021dbbe10 : 0xffffff8015193584
0xffffff8021dbbe50 : 0xffffff80151a346e
0xffffff8021dbbef0 : 0xffffff80152c1957
0xffffff8021dbbfa0 : 0xffffff801515c326
BSD process name corresponding to current thread: mdworker_shared
Mac OS version:
18F132
Kernel version:
Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64
Kernel UUID: 7C8BB636-E593-3CE4-8528-9BD24A688851
Kernel slide: 0x0000000014e00000
Kernel text base: 0xffffff8015000000
__HIB text base: 0xffffff8014f00000
System model name: MacBookPro13,1 (Mac-473D31EABEB93F9B)
System uptime in nanoseconds: 631052459001
last loaded kext at 246345231235: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7f98966000, size 69632)
last unloaded kext at 312954555843: com.apple.driver.AppleFileSystemDriver 3.0.1 (addr 0xffffff7f95dae000, size 8192)
loaded kexts:
3rd Report:
Sun Jun 30 19:02:37 2019
*** Panic Report ***
panic(cpu 2 caller 0xffffff8001edb92d): Kernel trap at 0xffffff8001deddb0, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00007ff24ad3e000, CR3: 0x000000025f6c2027, CR4: 0x00000000003626e0
RAX: 0x0000000000000000, RBX: 0x40ffffff80154c84, RCX: 0x0000000000000000, RDX: 0x0000000000000000
RSP: 0xffffff81044d37b0, RBP: 0xffffff81044d3800, RSI: 0xffffff800260abf0, RDI: 0xffffff8016c05f50
R8: 0x00000001066d80c6, R9: 0x00000000000f4240, R10: 0x0000000000000000, R11: 0x000000000000003a
R12: 0xffffff800260ac10, R13: 0x00000001065e3e86, R14: 0xffffff800260abf0, R15: 0xffffff8016c05f50
RFL: 0x0000000000010007, RIP: 0xffffff8001deddb0, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00007ff24ad3e000, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 1, VF: 0
Backtrace (CPU 2), Frame : Return Address
0xffffff8001b52290 : 0xffffff8001d
EOF
System Profile:
Network Service: Wi-Fi, AirPort, en0
Boot Volume File System Type: apfs
Memory Module: BANK 0/DIMM0, 4 GB, LPDDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424A544D4C41522D4E5544
Memory Module: BANK 1/DIMM0, 4 GB, LPDDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424A544D4C41522D4E5544
USB Device: USB 3.0 Bus
Thunderbolt Bus: MacBook Pro, Apple Inc., 41.1
Model: MacBookPro13,1, BootROM 233.0.0.0.0, 2 processors, Intel Core i5, 2 GHz, 8 GB, SMC 2.36f97
Graphics: kHW_IntelIrisGraphics540Item, Intel Iris Graphics 540, spdisplays_builtin
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x159), Broadcom BCM43xx 1.0 (7.77.61.2 AirPortDriverBrcmNIC-1305.8)
Bluetooth: Version 6.0.12f1, 3 services, 27 devices, 1 incoming serial ports
Thats a pretty good NON-Trend going.
But when you contact Apple, they are going to want you (or them) to run diagnostics. memory problems are notoriously difficult to find, but maybe you will get lucky and it will fail right away.
If it does, try to save the report.
Here is my latest panic report.
Here is the contents of the panic report.
I also have files labled .crash and .awd
It’s a MacBook Pro model A1708. I will try the memory test.
MacBook Pro Keeps Crashing
