Best macOS 13 Console Logs for Diagnosing Errors

Diagnosing software crashes, system freezes, and background process failures on macOS 13 (Ventura) requires navigating Apple's unified logging system via the Console app. By focusing on specific sections within the Console sidebar—including Crash Reports, Spin Reports, System Log, and the live log stream—you can quickly isolate whether an issue stems from a faulty third-party application, an unresponsive system daemon, or a critical kernel panic.

1. Crash Reports (/Library/Logs/DiagnosticReports)

Located under the Crash Reports category in the sidebar, these files (typically ending in .ips) are the primary resource for troubleshooting applications that quit unexpectedly.

  • What to look for: Look for the name of the failing application followed by the timestamp of the crash.
  • Key data points: Open the report and check the Exception Type (e.g., EXC_BAD_ACCESS or EXC_CRASH) and the Crashed Thread. The backtrace of the crashed thread reveals the exact function or binary that caused the failure.

2. Spin Reports (/Library/Logs/DiagnosticReports)

Located directly beneath Crash Reports, Spin Reports record instances where an application hung or caused the spinning wait cursor (beachball) without crashing outright.

  • What to look for: Look for entries labeled with the unresponsive process.
  • Key data points: Look at the CPU usage and the thread call stacks to identify infinite loops, deadlocks, or blocked I/O operations preventing the application from responding to the window server.

3. System Log (/var/log/system.log)

Located under Log Reports, system.log contains legacy Unix-style messages from system-level daemons, security agents, and command-line utilities.

  • What to look for: Search for fatal, error, or the name of a specific service (such as launchd).
  • Key data points: This log is particularly useful for diagnosing background service failures, launch daemon aborts, and peripheral connection problems that occur before or outside user sessions.

4. Kernel Panic Logs

When macOS 13 reboots spontaneously due to a critical hardware or kernel-level fault, the system records the event under Diagnostic Reports.

  • What to look for: Search for files ending in .panic.
  • Key data points: Identify the Kernel Extensions in backtrace (kexts). If a third-party kernel extension or specific driver is listed, that component is often responsible for the hardware restart or memory corruption.

5. Live Unified Log Stream

Clicking your Mac under the Devices section in the left sidebar opens the live Unified Log stream. Because macOS generates thousands of events per second, you must use Console's search filters to isolate actionable errors.

  • Filter by Message Type: In the search bar, type type:error or type:fault to hide routine status messages and display only actionable failures.
  • Filter by Process: Type process:[AppName] to isolate logs generated solely by the problematic application.
  • Filter by Subsystem: Enter subsystem:com.apple. followed by the relevant framework (such as subsystem:com.apple.TimeMachine for backup failures or subsystem:com.apple.Bluetooth for connectivity issues).