Daily crash - MPB 2012 retina

[TheHangMan]

Hi there,

Last year I stopped using my 2012 Retina MBP due to its unreliability. It still runs really well, Adobe suite with no problem, etc, but battery is old obviously (7 years almost) and it just crashes almost every time I close the lid (sleep). Also, it's normal to boot at least twice to see the Apple logo during startup. Most "first boot"s show the "?". I got used to it and just reboot it. As the ssd loads so fast it doesnt really bother me as it has become my second machine.

The thing is, I can't really sell it like that. The ssd is an OWC 480GB that I upgraded couple years ago. DriveDX says it's always running hot and the max recorded temp kind of scares me.

Anyway, here is the log I get mostly when it crashes after sleeping:

Process: mds_stores [196]
Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mds_stores
Identifier: mds_stores
Version: 1191.53
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: mds_stores [196]
User ID: 0

Date/Time: 2019-03-19 14:03:27.495 -0300
OS Version: Mac OS X 10.14.3 (18D109)
Report Version: 12


Time Awake Since Boot: 87 seconds

System Integrity Protection: enabled

Crashed Thread: 4 Dispatch queue: com.apple.metadata.spotlightindex.Set Attributes scheduler for index at /.Spotlight-V100/Store-V2/6ABA2232-669D-4256-A835-6DC4D

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000bad
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [196]

VM Regions Near 0xbad:
-->
__TEXT 000000010cdd8000-000000010ce1d000 [ 276K] r-x/rwx SM=COW /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mds_stores

Application Specific Information:
dyld3 mode
[0x70000d086000] FileTree.c:909: failed assertion 'getNum16(page->depth)==(unsigned)depth' /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T (apfs, t: 0x19, st: 0x1, f: 0x480d000) Expected depth 1; page has 42142
Initializing

Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff7449617a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff744966d0 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff47077158 __CFRunLoopServiceMachPort + 336
3 com.apple.CoreFoundation 0x00007fff470766a6 __CFRunLoopRun + 1661
4 com.apple.CoreFoundation 0x00007fff47075dd6 CFRunLoopRunSpecific + 467
5 mds_stores 0x000000010cddb4d8 0x10cdd8000 + 13528
6 libdyld.dylib 0x00007fff7435ced9 start + 1

Thread 1:
0 libsystem_pthread.dylib 0x00007fff7454f3f8 start_wqthread + 0
1 ??? 0x0000000054485244 0 + 1414025796

Thread 2:
0 libsystem_kernel.dylib 0x00007fff7449617a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff744966d0 mach_msg + 60
2 com.apple.spotlight.index 0x00007fff6dce5f9c _handleExceptions + 111
3 libsystem_pthread.dylib 0x00007fff74550305 _pthread_body + 126
4 libsystem_pthread.dylib 0x00007fff7455326f _pthread_start + 70
5 libsystem_pthread.dylib 0x00007fff7454f415 thread_start + 13

Thread 3:
0 libsystem_pthread.dylib 0x00007fff7454f3f8 start_wqthread + 0
1 ??? 0x0000000054485244 0 + 1414025796

Thread 4 Crashed:: Dispatch queue: com.apple.metadata.spotlightindex.Set Attributes scheduler for index at /.Spotlight-V100/Store-V2/6ABA2232-669D-4256-A835-6DC4D
0 com.apple.spotlight.index 0x00007fff6dd4ad3e directoryStorePageFindItemOffset + 766
1 com.apple.spotlight.index 0x00007fff6dd4a5ea directoryStoreReaderTreeFindItemOffset + 202
2 com.apple.spotlight.index 0x00007fff6dd4a292 directoryStoreGetPath + 722
3 com.apple.spotlight.index 0x00007fff6dd49f03 si_perform_livequeries_reassignments + 301
4 com.apple.spotlight.index 0x00007fff6ddff018 transferAttributes + 2547
5 com.apple.spotlight.index 0x00007fff6ddb7694 setattr_runLoop + 105
6 com.apple.spotlight.index 0x00007fff6dd9d2f6 work_fun + 684
7 libdispatch.dylib 0x00007fff7430edcf _dispatch_client_callout + 8
8 libdispatch.dylib 0x00007fff74315124 _dispatch_lane_serial_drain + 618
9 libdispatch.dylib 0x00007fff74315c0c _dispatch_lane_invoke + 436
10 libdispatch.dylib 0x00007fff74314fc9 _dispatch_lane_serial_drain + 271
11 libdispatch.dylib 0x00007fff74315c0c _dispatch_lane_invoke + 436
12 libdispatch.dylib 0x00007fff74316a37 _dispatch_workloop_invoke + 917
13 libdispatch.dylib 0x00007fff7431e090 _dispatch_workloop_worker_thread + 603
14 libsystem_pthread.dylib 0x00007fff7454f60b _pthread_wqthread + 409
15 libsystem_pthread.dylib 0x00007fff7454f405 start_wqthread + 13

Thread 5:
0 libsystem_pthread.dylib 0x00007fff7454f3f8 start_wqthread + 0
1 ??? 0x0000000054485244 0 + 1414025796

Thread 6:
0 libsystem_pthread.dylib 0x00007fff7454f3f8 start_wqthread + 0

Thread 7:
0 libsystem_pthread.dylib 0x00007fff7454f3f8 start_wqthread + 0
1 ??? 0x0000000054485244 0 + 1414025796

Thread 4 crashed with X86 Thread State (64-bit):
rax: 0x0000000000005a07 rbx: 0x000000011d4a2f00 rcx: 0x0000000000000000 rdx: 0x00000000000c51e0
rdi: 0x00000000a6b2fa84 rsi: 0x00007f86bed00000 rbp: 0x000070000d081b50 rsp: 0x000070000d081ae0
r8: 0x0000000000000006 r9: 0x0000000000000000 r10: 0x0000000000000007 r11: 0x0000000000000007
r12: 0x0000000000000001 r13: 0x0000000000000001 r14: 0x00007f86bed36a50 r15: 0x000070000d081bd0
rip: 0x00007fff6dd4ad3e rfl: 0x0000000000010202 cr2: 0x0000000000000bad

Logical CPU: 0
Error Code: 0x00000006
Trap Number: 14




External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 284
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=388.5M resident=0K(0%) swapped_out_or_unallocated=388.5M(100%)
Writable regions: Total=388.8M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=388.8M(100%)

VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Activity Tracing 256K 2
Dispatch continuations 16.0M 2
Kernel Alloc Once 8K 2
MALLOC 346.4M 68
MALLOC guard page 112K 28
Memory Tag 241 44K 2
Memory Tag 243 6144K 2
Memory Tag 244 4288K 6
Memory Tag 246 (reserved) 2048K 2 reserved VM address space (unallocated)
Memory Tag 250 2240K 9
STACK GUARD 56.0M 9
Stack 11.6M 9
VM_ALLOCATE 192K 5
__DATA 29.0M 250
__FONT_DATA 4K 2
__LINKEDIT 216.2M 4
__TEXT 172.4M 251
__UNICODE 564K 2
mapped file 193.3M 38
shared memory 28K 5
=========== ======= =======
TOTAL 1.0G 678
TOTAL, minus reserved VM space 1.0G 678


I deleted that mid part, thought it doesnt matter. If it does, I can post the whole thing.

Sometimes I also get this:



Wed Mar 13 13:29:59 2019

*** Panic Report ***
panic(cpu 2 caller 0xffffff802a4b86cf): initproc exited -- exit reason namespace 2 subcode 0xa description: none

uuid info:
0x113b47000 uuid = <289ab27e-f09f-3384-a14a-100431139559>
0x10bee1000 uuid = <81c04efd-b06a-32aa-bf73-51f4d442fc58>

Thread 1 crashed

RAX: 0xa556cb4aeaa70068, RBX: 0x0000000000000000, RCX: 0x0000000000000000, RDX: 0x00007000048b9560
RSP: 0x00007000048b9360, RBP: 0x00007000048b9430, RSI: 0x000000010bf02cb0, RDI: 0x00007fff682edb5e
R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0x00007fff684c7aa3, R11: 0x0000000000000202
R12: 0x00007000048b9560, R13: 0x000000010bef0fe4, R14: 0x000000010bf02cb0, R15: 0x000000010bf4c000
RFL: 0x0000000000010246, RIP: 0x00007fff682c474b, CS: 0x000000000000002b, SS: 0x0000000000000023

Thread 0: 0xffffff804bec4950
0x00007fff684170a2
0x00007fff6829b8a0
0x0000000000000000

Thread 1: 0xffffff8051903f30
0x00007fff682c474b
0x00007fff682d8455
0x00007fff682d8397
0x00007fff68337e74
0x000000010bf02cb0
0x000000010bf1346f
0x00007fff6828bdcf
0x00007fff6828e5dc
0x00007fff6829d8ed
0x00007fff68291fc9
0x00007fff68292bdc
0x00007fff6829b090
0x00007fff684cc60b
0x00007fff684cc405
0x8000120000000000

Thread 2: 0xffffff80520f0cc0
0x00007fff684322a6
0x00007fff6828e5dc
0x00007fff6829d8ed
0x00007fff68291fc9
0x00007fff68292bdc
0x00007fff6829b090
0x00007fff684cc60b
0x00007fff684cc405
0x0000000000000000

Thread 3: 0xffffff804c62f440
0x00007fff684cc3f8


Mac OS version:
18C54

Kernel version:
Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64
Kernel UUID: 56B30885-F9BA-30E8-AD1C-5D59EC243BA9
System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)
Root disk errors: "Could not recover SATA HDD after 5 attempts. Terminating."

EOF

System Profile:
Network Service: Wi-Fi, AirPort, en0
Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4
Boot Volume File System Type: apfs
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 3.0 Bus
USB Device: G-DRIVE mobile with Thunderbolt
USB Device: Apple Mobile Device (Recovery Mode)
Serial ATA Device: OWC Aura, 480,1 GB
Model: MacBookPro10,1, BootROM 251.0.0.0.0, 4 processors, Intel Core i7, 2,3 GHz, 16 GB, SMC 2.3f36
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (7.21.190.32 AirPortDriverBrcm4360-1315.1)
Bluetooth: Version 6.0.9f2, 3 services, 18 devices, 1 incoming serial ports

Any thoughts? Thank you in advance!

 

[pshufd]

I'd suggest turning off Spotlight Indexing.

 

[treekram]

The most likely culprit is the SSD.

One easy thing you can try is booting in safe mode. I don't think safe mode will work but it is easy to try.
https://support.apple.com/en-us/HT201262

If safe mode doesn't work, do you have the original Apple SSD that the computer had and is it working? If so, you should try that.

If it still isn't working then you should do some legwork. Your MBP model - the 2012 15" Retina, has red flags because the GPU was subject to a warranty extension and for whatever reason, in these forums, people are reporting kernel panics which point the the GPU as a problem. So you need to see what the market for a used model is. And then you need to see what the market is for one without a SSD (if your SSD is faulty and you don't have the original Apple SSD) vs. one with a 3rd-party replacement. A name-brand replacement would be $50 for 250GB, $70 for 500GB, plus an adapter ($13). You should also see if there is a penalty for a 3rd-party replacement vs. the Apple SSD. The used Apple SSD's cost more than a new 3rd-party SSD, from what I see on eBay. For this model, the 3rd-party replacement, if new and a better model from a big-name manufacturer (Crucial, Samsung, SanDisk), will be superior to the used Apple SSD.

To me, you should look at the market before doing further troubleshooting if safe mode doesn't work and if you don't have the original Apple SSD. It will take time and probably money to do further troubleshooting so you need to see what the economics are before proceeding.

 

[pshufd]

The second crash has the error: "Could not recover SATA HDD after 5 attempts. Terminating." which means that you could have a storage device problem. If you have an external drive handy, you could try building an OS on it and running from an external drive. If it runs fine, then it might be an issue with storage.

The first crash exception is in Thread 4 Crashed:: Dispatch queue: com.apple.metadata.spotlightindex.Set Attributes scheduler for index at /.Spotlight-V100/Store-V2/6ABA2232-669D-4256-A835-6DC4D which is one of a bunch of currently executing threads. Spotlight indexing can result in a lot of disk activity (and therefore heat) and the use of a lot of CPU. It could also be causing your storage device to run hot. So turning off Spotlight Indexing might help decrease or eliminate the first type of crash. I have 2014 and 2015 MBPs and sometimes they do that - go crazy with Spotlight Indexing.

 

[TheHangMan]

The most likely culprit is the SSD.

One easy thing you can try is booting in safe mode. I don't think safe mode will work but it is easy to try.
https://support.apple.com/en-us/HT201262

[...]

I'll try with the original SSD! Thank you!

The second crash has the error: "Could not recover SATA HDD after 5 attempts. Terminating." which means that you could have a storage device problem. If you have an external drive handy, you could try building an OS on it and running from an external drive. If it runs fine, then it might be an issue with storage.

The first crash exception is in Thread 4 Crashed:: Dispatch queue: com.apple.metadata.spotlightindex.Set Attributes scheduler for index at /.Spotlight-V100/Store-V2/6ABA2232-669D-4256-A835-6DC4D which is one of a bunch of currently executing threads. Spotlight indexing can result in a lot of disk activity (and therefore heat) and the use of a lot of CPU. It could also be causing your storage device to run hot. So turning off Spotlight Indexing might help decrease or eliminate the first type of crash. I have 2014 and 2015 MBPs and sometimes they do that - go crazy with Spotlight Indexing.

Thanks. I didn't do the terminal "spotlight off", I just unchecked most items in the system prefs menu. I left calc, conversions and documents. Will it still go crazy?
One thing that happens sometimes is after I close the lid, 15min later I hear the fans going crazy and the computer is boiling hot. Very weird.

 

[pshufd]

I'll try with the original SSD! Thank you!

Thanks. I didn't do the terminal "spotlight off", I just unchecked most items in the system prefs menu. I left calc, conversions and documents. Will it still go crazy?
One thing that happens sometimes is after I close the lid, 15min later I hear the fans going crazy and the computer is boiling hot. Very weird.

I've never figured out how to turn off Spotlight Indexing so I just let it run and eventually it stops. It's annoying to have the fans running for a while but it has always eventually stopped. Someday I'll figure out how to do it. I really don't like the idea of the computer running at high CPU while the lid is closed.