Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Protein0064

macrumors newbie
Original poster
Repeatable 180-Second System Deadlock — iPhone 16 Pro Max (iPhone17,2) | iOS 26.4–26.5 Beta

I’ve been dealing with a consistent, reproducible system deadlock that has persisted across multiple software versions, including iOS 26.4 (beta and stable) and now 26.5 beta. The last version where my device behaved normally was 26.4 beta 1, which is no longer signed.

The Behavior
∙ Device freezes completely for exactly 180 seconds
∙ After that interval, it performs a hard reboot
∙ This is not random — it is fully reproducible
Reliable Triggers
∙ Adding or editing Home Screen widgets
∙ Browsing media-heavy websites in Safari
∙ UI transitions involving ProMotion or GPU-intensive rendering

Technical Details
Panic logs consistently report:
∙ Error: Userspace Watchdog Timeout (0x8badf00d)
∙ Cause: No successful check-ins from SpringBoard within 180 seconds (service: backboardd)
Stack traces point to a deadlock involving:
∙ com.apple.driver.AppleAVD
∙ com.apple.iokit.IOSurface
This suggests a lower-level issue in the media pipeline or GPU/accelerated rendering stack.

Troubleshooting Already Attempted
∙ Multiple clean DFU restores
∙ Device set up as new each time — no backups restored, no user data carried over
∙ Issue persists regardless

What Makes This Hard to Isolate
∙ Survives clean restores, ruling out typical software corruption
∙ Cannot isolate a specific widget — the system destabilizes before reliable testing is possible
∙ Boot loops require a full PC restore each time, which is extremely time-consuming
∙ Panic logs show no third-party bundle ID, making culprit identification difficult

Questions
1. Has anyone encountered this exact 180-second SpringBoard watchdog timeout on iPhone17,2?
2. Is this a known regression involving the media engine or rendering pipeline?
3. Are there specific diagnostics, settings, or workarounds worth trying?
4. Is there a reliable method to extract the responsible bundle ID from logs in cases like this?

I’ve gone through repeated restore cycles, attempted variable isolation, and submitted feedback — without meaningful progress. This forum is genuinely my last real avenue. Any insight, confirmation of a similar experience, or guidance would be deeply appreciated.

TL;DR: iPhone 16 Pro Max consistently freezes for exactly 180 seconds then reboots due to a SpringBoard watchdog timeout tied to AppleAVD/IOSurface. Persists after clean DFU restores. Cannot isolate the trigger. Exhausted all other options.
 
Think you have a faulty device as the issue persists when device is reset and setup as a new device. I would reach out to Apple Support and see what troubleshooting they want you to perform.
 
Think you have a faulty device as the issue persists when device is reset and setup as a new device. I would reach out to Apple Support and see what troubleshooting they want you to perform.
All of the analysis regarding the hardware has been impeccable; everything is in place and the device is healthy. But this thing just drives me nuts. I've been trying to contact developer support and Apple support, but it looks like they're not very interested.
 
Think you have a faulty device as the issue persists when device is reset and setup as a new device. I would reach out to Apple Support and see what troubleshooting they want you to perform.


I’m on a 16 Pro Max on 26.4 and am not seeing these issues. If it’s not a software problem, its a hardware problem.

And given the problem is persistent across reboots, resets and different OS versions - it’s not a software problem.
 
I’m on a 16 Pro Max on 26.4 and am not seeing these issues. If it’s not a software problem, its a hardware problem.

And given the problem is persistent across reboots, resets and different OS versions - it’s not a software problem.
Thank you for your firsthand report. This started happening from beta version number 3 (first version 26.4). Every single time I would update from that version to any other version of iOS, whether stable or not, I would end up with the same problem.

It looks like there was some change from the first beta that could have influenced Launcher, Springboard, or whatever the name of that thing is.
 
To be clear, have you reset/re-installed the OS on the device via DFU mode (as opposed to just restoring it to backup and re-upgrading / factory reset from within the phone)?

I would think that should wipe out any beta hangover weirdness?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.