Need help understanding crash log

[linkmaster6]

Hey folks,
I have a relative with a MacBook Pro that has been giving them some issues. It seems to be restarting at random and giving them the following error log, I'm not certain what its pointing to for being the cause of crash. Does it appear to be a hardware issue or is it software?



Thanks in advance, I haven't had my hands on this yet so I haven't had the chance to troubleshoot it yet

 

[Randy B. Singer]

I very rarely find a panic log to be helpful in diagnosing a kernel panic. However, this article may help with that a bit:

How to recognise and diagnose kernel panics

Recognition, immediate action including capturing the panic log, discovering clues as to cause, further investigations to diagnose and address the cause.

eclecticlight.co

In my experience, I'd say that about 80% to 90% of the time kernel panics are due to a hardware problem. In order of likelihood, that problem is usually:

- bad third party RAM
- a problematic USB hub
- a peripheral that your Mac doesn't like for some reason (sometimes just a poorly attached cable, or a bad cable, is the problem)

If you have very recently added new software, especially something that alters the system at a low level, such as anti-virus software, or something that changes the look and/or function of the Mac interface, I would suspect that first. Uninstall that software and see if things get better. (This type of software typically requires an uninstaller to completely disable. Just dragging the application, or the application's folder, to the Trash won't disable it.) I'd go so far as to say that if you are running commercial fully interactive anti-virus software that the first thing that you should try is fully uninstalling it with the developer’s uninstaller.

If that isn't it, I would restart the Mac with the Shift key held down (invoking a Safe Boot, with all kernel extensions disabled) and see if the problem is gone while running in Safe mode. If the problem is gone while in Safe mode, the Kernel Panics are probably due to a software problem. If it persists while in Safe mode, the problem is most likely hardware related.

To test for hardware problems, you can run Apple's Apple Diagnostics:

Use Apple Diagnostics to test your Mac - Apple Support

Apple Diagnostics, formerly known as Apple Hardware Test, can check your Mac for hardware issues.

support.apple.com

Unfortunately, it's easily possible to have a hardware problem that this utility doesn't identify.

If you suspect a hardware problem, the next thing that I would do is to shut down your Mac, uninstall all peripherals other than the Apple-supplied keyboard and mouse, restart and see if that helps. If it does, you can re-attach one peripheral at a time, restarting each time, until you isolate the offending peripheral.

Apple's tech note about this:

About kernel panics

If your Mac restarted because of a problem - Apple Support

Learn what to do if your computer restarts or shuts down unexpectedly, or you get a message that your computer restarted or shut down because of a problem.

support.apple.com

 

[MacBiter]

Most of the time, most of us don't understand crash reports!

However, if you know more or less to the minute when the crash occurred, launch Console (Applications / Utilities) and in the sidebar on the left look for an item described as 'kernel' (or 'panic' or similar). The contents won't be any easier to understand, but if you paste the few lines corresponding to that particular time, someone here might be able to decipher exactly or roughly what (might have) happened..

 

[Raz0rEdge]

Logd is the Logging Daemon. Unix/Linux based systems use a number of log files to track the behavior of the systems and services. macOS has it's own way of doing the same way.

A daemon is a backend service that needs to be monitored to ensure that is functions properly. When the daemon stops "checking in", the OS will usually try to restart the service to get back in business.

In this case, it looks like logd failed repeatedly and as such that was deemed a panic triggering event.

First and foremost, ensure that the MBP is running the latest version of macOS. Also, check with them to see if they can determine when this started happening and if it was related to any particular change.

We'll need a lot more info about the Mac, OS, connected devices, and so on to help. Otherwise, you'll just get the generic help already stated above.