Skip to content
MappleCare Community ↗

MappleCare Community

Reply To: Diagnostic query: Unexpected kernel panic on macOS Sequoia 15.1 after waking (1794685902)

Find answers from other Apple users or start a discussion about your device.

All Forum Rooms

Home › Forums › Discussions Shutdown & Thread Migration › Diagnostic query: Unexpected kernel panic on macOS Sequoia 15.1 after waking (1794685902) › Reply To: Diagnostic query: Unexpected kernel panic on macOS Sequoia 15.1 after waking (1794685902)

#11191
Rachel Kim
Lead Moderator

The AppleThunderboltNHI assertion frequently originates from a DisplayPort MST hub failing to re-train link rates fast enough for WindowServer’s IOFramebuffer reconfiguration deadline, spiking WindowServer CPU > 400% via CGXDisplayDidWake callbacks. Capture a spindump during wake (sudo spindump -reveal -noProcessing -file /tmp/wake.spindump) and grep for IOAccelSurface or CAMetalLayer backtraces; if Safari’s WebContent process holds an IOSurface lock across sleep, disable “Use graphics acceleration” in Develop menu or purge ~/Library/Saved Application State/com.apple.Safari.savedState. Finally, audit log show --predicate 'eventMessage contains "loginwindow" AND eventMessage contains "launchd"' --last 24h for LaunchAgents (e.g., DisplayLink, DisplayLinkManager, or third-party dock utilities) that register IOKit matching callbacks blocking the AppleThunderboltNHI power domain handoff.

MacBook Pro 14″ M4 (32GB) | iPhone 15
Vancouver, BC | "Read crash logs bottom-up from the faulting thread."