You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Two MacBook Air laptops (M2/M3) were collected from Apple today after complete firmware and OS reset

We collected two MacBook Air laptops today from apple (directly from Apple Store) and I have to say is fascinating to watch this playing out. Device details:

Laptop A:

Model Name: MacBook Air

Model Identifier: Mac15,12

Model Number: MRXP3X/A

Chip: Apple M3

Total Number of Cores: 8 (4 performance and 4 efficiency)

Memory: 8 GB

System Firmware Version: 10151.81.1


and


Laptop B:

Model Name: MacBook Air

Model Identifier: Mac14,2

Model Number: MN703X/A

Chip: Apple M2

Total Number of Cores: 8 (4 performance and 4 efficiency)

Memory: 16 GB

System Firmware Version: 11881.1.1


Within 2 minutes of opening the M3 it is literally fully owned by people that seem to enjoy this. What is going on here and how are they able to do this?


This is the system.log:


------------------------------------- Translated Report (Full Report Below) -------------------------------------

Process: mds_stores [518]

Path: /System/Library/Frameworks/CoreServices.framework/Versions/ A/Frameworks/Metadata.framework/Versions/A/Support/mds_stores

Identifier: Version:

Code Type: Parent Process: User ID:

mds_stores ???

ARM-64 (Native) launchd [1]

0

Date/Time:

OS Version: Report Version: Anonymous UUID:

2024-10-22 04:50:26.1123 -0700 macOS 14.3 (23D2057)

12

Time Awake Since Boot: 270 seconds System Integrity Protection: enabled

Crashed Thread:

Exception Type: Exception Codes: Exception Codes:

3 Dispatch queue: */Sto

EXC_BAD_ACCESS (SIGBUS) KERN_MEMORY_ERROR at 0x000000011865801c 0x000000000000000a, 0x000000011865801c

Termination Reason: Terminating Process:

Namespace SIGNAL, Code 10 Bus error: 10 exc handler [518]

5029DFEA-409A-622D-1165-9819CCB8EEB8

VM Region Info: 0x11865801c is in 0x118658000-0x118758000; bytes after start: 28 bytes before end: 1048547

REGION TYPE REGION DETAIL

START - END [ VSIZE] PRT/MAX SHRMOD

mapped file

A ...t_id=42c84251

---> mapped file

SM=PRV ...t_id=4415de51

mapped file 118758000-118768000 SM=PRV ...t_id=441cba51

[

64K] rw-/rw-

11849c000-118658000 118658000-118758000

[ 1776K] r--/r-- SM=S/ [ 1024K] rw-/rw-

Kernel Triage:

VM - (arg = 0x0) Object has no pager because the backing vnode was force

unmounted

VM - (arg = 0x0) Object has no pager because the backing vnode was force unmounted

VM - (arg = 0x0) Object has no pager because the backing vnode was force unmounted

Thread 0:: Dispatch queue: com.apple.main-thread

0 libsystem_kernel.dylib 1 libsystem_kernel.dylib 2 libsystem_kernel.dylib 476

0x18d4ad874 mach_msg2_trap + 8 0x18d4bfcf0 mach_msg2_internal + 80 0x18d4b64b0 mach_msg_overwrite +

0x18d4adbf8 mach_msg + 24 0x18d5cbb84 __CFRunLoopServiceMachPort

0x18d5ca44c __CFRunLoopRun + 1208 0x18d5c993c CFRunLoopRunSpecific + 608 0x100e081e4 0x100e04000 + 16868

0x18d16d0e0 start + 2360

0x18d4ad874 mach_msg2_trap + 8 0x18d4bfcf0 mach_msg2_internal + 80 0x18d4b64b0 mach_msg_overwrite +

0x18d4adbf8 mach_msg + 24 0x1a64dfef4 _handleExceptions + 116

0x18d4ee034 _pthread_start + 136 0x18d4e8e3c thread_start + 8

0x18d4e8e28 start_wqthread + 0

3 4 + 5 6 7 8

libsystem_kernel.dylib

CoreFoundation 160

CoreFoundation CoreFoundation mds_stores dyld

Thread 1:

0 libsystem_kernel.dylib 1 libsystem_kernel.dylib 2 libsystem_kernel.dylib 476

  1. 3 libsystem_kernel.dylib
  2. 4 SpotlightIndex
  3. 5 libsystem_pthread.dylib
  4. 6 libsystem_pthread.dylib

Thread 2:

0 libsystem_pthread.dylib

Thread 3 Crashed:: Dispatch queue: */Sto

0 SpotlightIndex 0x1a67c4224 db2_get_field_tags_for_id_locked + 124

  1. 1 SpotlightIndex
  2. 2 SpotlightIndex
  3. 3 SpotlightIndex
  4. 4 SpotlightIndex
  5. 5 SpotlightIndex
  6. 6 SpotlightIndex
  7. 7 libdispatch.dylib

_dispatch_block_async_invoke2 + 148

  1. 8 libdispatch.dylib 0x18d33c910 _dispatch_client_callout + 20
  2. 9 libdispatch.dylib 0x18d343ea4 _dispatch_lane_serial_drain +

748

0x1a67c38c4 _inflateDBO + 3244 0x1a656388c db2_get_obj_callback + 2952 0x1a65c433c moveDirectoriesInner + 1336 0x1a65c3de4 moveDirectories + 32 0x1a6561e60 setattr_runLoop + 148 0x1a650d6fc work_fun + 816

0x18d34b860

10 libdispatch.dylib 11 libdispatch.dylib 368

12 libdispatch.dylib 13 libdispatch.dylib 768

14 libdispatch.dylib _dispatch_root_queue_drain_deferred_wlh + 288 15 libdispatch.dylib 0x18d34ee90 _dispatch_workloop_worker_thread + 404

16 libsystem_pthread.dylib 17 libsystem_pthread.dylib

Thread 4:

0 libsystem_pthread.dylib

0x18d4ea114 _pthread_wqthread + 288 0x18d4e8e30 start_wqthread + 8

0x18d4e8e28 start_wqthread + 0

0x18d344a08 _dispatch_lane_invoke + 432 0x18d343d28 _dispatch_lane_serial_drain +

0x18d344a08 _dispatch_lane_invoke + 432 0x18d3458dc _dispatch_workloop_invoke +

0x18d34f61c



The whole log is here:


[Re-Titled by Moderator]

MacBook Air, macOS 15.0

Posted on Oct 22, 2024 7:16 AM

Reply
3 replies

Oct 22, 2024 8:14 AM in response to knock_knock88

You have some process that crashed. There is no reason to think that your mac was hacked. It wasn't.


If you want us to assist, please tell us what exactly happened that was not expected.



As noted by muguy already, looking at system logs you are always going to find lots and lots of stuff, and most of them are meaningless for most of us, and do not indicate that anything is wrong.

Two MacBook Air laptops (M2/M3) were collected from Apple today after complete firmware and OS reset

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