My Macbook has been hanging recently and have to force shut down

Question

emmanuelite4 Author

Level 1

4 points

My Macbook has been hanging recently and have to force shut down

-------------------------------------

Translated Report (Full Report Below)

-------------------------------------

Process: launchservicesd [367]

Path: /System/Library/CoreServices/launchservicesd

Identifier: launchservicesd

Version: ???

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

User ID: 0

Date/Time: 2024-04-05 05:24:32.7124 +0100

OS Version: macOS 14.4.1 (23E224)

Report Version: 12

Anonymous UUID: BACD33A9-64A8-9DB3-9AF0-3BD9C81E348D

Sleep/Wake UUID: B152B752-1CEF-4E34-9737-E9BC73CBC5FF

Time Awake Since Boot: 240000 seconds

Time Since Wake: 18612 seconds

System Integrity Protection: enabled

Crashed Thread: 1

Exception Type: EXC_GUARD

Exception Codes: GUARD_TYPE_USER

Exception Codes: 0x6000000000000012, 0x0000000000000005

Termination Reason: Namespace LIBSYSTEM, Code 5 Application Triggered Fault

Thread 0:

0 libsystem_kernel.dylib 0x194d15944 __sigsuspend_nocancel + 8

1 libdispatch.dylib 0x194bb1564 _dispatch_sig_thread + 60

Thread 1 Crashed:

0 libsystem_kernel.dylib 0x194d1ced8 os_fault_with_payload + 8

1 libsystem_trace.dylib 0x194a9fbc0 _os_log_impl_flatten_and_send + 8060

2 libsystem_trace.dylib 0x194a9dc2c _os_log + 168

3 libsystem_trace.dylib 0x194a9db7c _os_log_impl + 28

4 launchservicesd 0x100788358 0x100744000 + 279384

5 launchservicesd 0x100748290 0x100744000 + 17040

6 launchservicesd 0x100788100 0x100744000 + 278784

7 libdispatch.dylib 0x194b9e3e8 _dispatch_client_callout + 20

8 libdispatch.dylib 0x194bad8d8 _dispatch_lane_barrier_sync_invoke_and_complete + 56

9 launchservicesd 0x100788070 0x100744000 + 278640

10 launchservicesd 0x100748290 0x100744000 + 17040

11 launchservicesd 0x100784fa8 0x100744000 + 266152

12 libdispatch.dylib 0x194b9e3e8 _dispatch_client_callout + 20

13 libdispatch.dylib 0x194ba18ec _dispatch_continuation_pop + 600

14 libdispatch.dylib 0x194bb57f0 _dispatch_source_latch_and_call + 420

15 libdispatch.dylib 0x194bb43b4 _dispatch_source_invoke + 832

16 libdispatch.dylib 0x194ba5898 _dispatch_lane_serial_drain + 368

17 libdispatch.dylib 0x194ba6578 _dispatch_lane_invoke + 432

18 libdispatch.dylib 0x194bafea8 _dispatch_root_queue_drain + 392

19 libdispatch.dylib 0x194bb06b8 _dispatch_worker_thread2 + 156

20 libsystem_pthread.dylib 0x194d4afd0 _pthread_wqthread + 228

21 libsystem_pthread.dylib 0x194d49d28 start_wqthread + 8

Thread 2:

0 libsystem_pthread.dylib 0x194d49d20 start_wqthread + 0

Thread 1 crashed with ARM Thread State (64-bit):

x0: 0x0000000000000012 x1: 0x0000000000000005 x2: 0x0000000129015e30 x3: 0x000000000000010f

x4: 0x0000000100799ad3 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000092

x8: 0x0000000000000514 x9: 0x000000016f859518 x10: 0x0000000001017000 x11: 0x0000000000016000

x12: 0x0000000000016000 x13: 0x0000000001017000 x14: 0x000000007fffffff x15: 0x0000000000016000

x16: 0x0000000000000211 x17: 0x0000000206dc71d8 x18: 0x0000000000000000 x19: 0x0000000129104220

x20: 0x000000016f85a7b0 x21: 0x000000016f8594e8 x22: 0x000000000000010f x23: 0x0000000129015e30

x24: 0x0000000129015e61 x25: 0x0000000000000004 x26: 0x00000000000000de x27: 0x0000000000180003

x28: 0x00055ad316021104 fp: 0x000000016f859430 lr: 0x0000000194aaf008

sp: 0x000000016f8593f0 pc: 0x0000000194d1ced8 cpsr: 0x40001000

far: 0x0000000000000000 esr: 0x56000080 Address size fault

MacBook Pro 13″, macOS 14.4

Posted on Apr 5, 2024 1:48 AM

Reply

Answer 1

John Galt

Level 10

141,180 points

Apr 5, 2024 12:14 PM in response to emmanuelite4

All you can do is follow the suggestions in If your Mac restarts and a message appears - Apple Support. For example, sometimes reinstalling macOS will fix things.

If your Mac continues to hang and freeze after following all those suggestions, you might consider downloading and running EtreCheck. Instructions: How to use the Add Text Feature When Posting Large Amounts of Text, i.e. an Etrecheck Report - Apple Community.

The crash report does not indicate anything specific that you can act upon. In the end it could be a macOS bug, or it could be hardware fault. Both are rare. Post the EtreCheck report if you like, but you may need to contact Apple Support about it. Should you choose to do that use the Support link at the bottom of these pages.

Reply

Answer 2

John Galt

Level 10

141,180 points

Apr 13, 2024 6:24 PM in response to emmanuelite4

Uninstall "AVG" in accordance with its instructions. Your Mac will never work properly with it installed.

Antivirus software: Apple and AVG

That EtreCheck report element should be exactly the following:

Antivirus software: Apple

... and nothing else.

Fix it.

Configuration Files:

/etc/hosts - Count: 2

That's not right either, although extraneous Hosts entries will not directly cause a Mac to crash. It's just a symptom of a larger problem, quite possibly a result of installing the utterly useless "AVG" garbage.

Regarding the altered Hosts file, EtreCheck's author contributed the following very informative User Tip: Fixing a hacked /etc/hosts file - Apple Community

Reply

Answer 3

emmanuelite4 Author

Level 1

4 points

Apr 15, 2024 4:45 AM in response to John Galt

I've removed everything relating to avg

Also for the /etc/hosts, the content of it returns this

$ cat /etc/hosts

##

# Host Database

#

# localhost is used to configure the loopback interface

# when the system is booting. Do not change this entry.

##

127.0.0.1 localhost

255.255.255.255 broadcasthost

::1 localhost

# Added by Docker Desktop

# To allow the same kube context to work on the host and the container:

127.0.0.1 kubernetes.docker.internal

# End of section

192.168.49.2 express.local

EtreCheckPro

Reply

Answer 4

John Galt

Level 10

141,180 points

Apr 15, 2024 4:38 PM in response to emmanuelite4

Fixing the recurring crashes will probably take some iterative efforts. First, refer to If your Mac restarts and a message appears - Apple Support. One of its suggestions is to "Uninstall any plug-ins or other enhancement software from manufacturers other than Apple." A number of those modifications are present, for example some from github / homebrew, and and you will need to determine if one or more of them may be contributing factors by eliminating each one methodically.

Another suggestion from that Support document is to disconnect any external devices not essential for basic operation, in the same manner and for the same reasons. Examples include DEMO Mobile Boardband (?) and those usbmodem "preloader" interfaces. I don't know what their purpose may be, but most KP events are caused by hardware or the software interfaces required for their use.

For what it's worth I don't believe those extraneous Hosts entries are a concern.

Reply