Why does my iPhone restart by itself every 3 minutes?
If an iPhone restarts repeatedly at roughly three-minute intervals, watchdog timing is an important clue, but the symptom does not automatically prove a hardware or logic-board failure. Recent panic-full logs help separate a repeatable sensor or bus signature from software, power and other possible causes.
The 3-minute secret: the 180-second watchdog
iOS includes an internal guardian called the watchdog. Its job is simple: if a vital system component stops responding for 180 seconds — exactly 3 minutes — the watchdog forces a full restart to try to recover the device.
That's why the pattern is so recognizable: the iPhone powers on, works "normally" for a moment, the damaged component stops responding, the 180-second counter runs out… and it restarts. When it powers on again, the cycle repeats. The phone isn't failing at random: it's protecting itself, on schedule, every time, from the same fault.
The most common physical causes
On the workbench, cyclic restarts caused by the watchdog or a kernel panic usually trace back to these origins:
- A missing sensor after an impact or prior repair — a connector, flex or board path may have been affected. Tokens such as prs0 and mic2 must be mapped for the exact model; neither maps universally to the charging flex.
- Liquid damage — corrosion on an FPC connector or on the I2C data lines interrupts the signal of a thermal or battery sensor (such as tg0b).
- AOP coprocessor or SMC faults — the chips that manage sensors and power detect an impossible reading and halt the system.
- PCIe communication failure — the modem, Wi-Fi or NAND storage stop responding on their data bus.
When an iOS restore is or is not justified
A restore is unlikely to resolve a damaged flex, missing sensor path or repeatable hardware-oriented signature. However, software should not be dismissed from the restart interval alone. Preserve data first and use the recent logs to decide whether a software isolation step is justified.
If the issue began after an update and the logs do not repeat a hardware-oriented signature, ruling out software may be appropriate. If several logs repeat the same sensor, bus or service context, prioritize reversible physical checks before destructive work.
How a professional technician diagnoses it
- Extract the panic-full log from the iPhone: Settings → Privacy & Security → Analytics & Improvements → Analytics Data (or with tools like 3uTools/iMazing).
- Read the panic signature:
panicStringrecords the panic family, named service and diagnostic tokens that can narrow the affected subsystem. - Preserve model context: the same token can follow a different physical route on another model, so confirm it before replacing parts.
- Confirm at the bench: diode-mode measurements and inspection of the flagged connector before soldering anything.
Steps 2 and 3 are what separate a shop that "swaps parts blindly" from one that diagnoses with data. And they're exactly the steps that can be automated.
Stop guessing: analyze the complete log
Upload the panic-full to iPanic Analyzer Pro and the CoreMatch™ engine prioritizes a diagnostic route, measurements to check and a guided procedure. The physical cause still requires exact-model bench confirmation. Your first analysis is free.
Try iPanic Analyzer Pro freeWhat if I'm the phone's owner, not a technician?
Back up as soon as the phone provides a stable powered-on window. Then share the restart timing and newest panic-full logs with a qualified repair shop so the technician can confirm the exact model, inspect reversible peripheral paths and measure before replacing components.