If your Garmin watch reboots, freezes on the triangle logo, or shuts off the moment you press “Start” on a run, ride, or hike, the watch is suffering an abrupt system crash during sensor initialization. This issue is almost always caused by a corrupted satellite ephemeris file (CPE.bin or EPO.bin) causing the processor to fault, or an aging battery that experiences sudden voltage drop when the power-hungry GPS chipset engages.
Quick Answer
Connect your watch to a computer, navigate to the
GARMIN/REMOTESWfolder, and delete theCPE.bin(orEPO.bin) file. Sync the watch with Garmin Express to download a clean satellite cache. If the watch only crashes when the battery is under 50%, the internal battery cell has degraded and requires hardware service.
Device & Signal Snapshot
- Platform: Garmin OS (Forerunner, Fenix, Epix, Enduro, Instinct, Venu, Edge series)
- Trigger Event: Selecting an outdoor activity profile (Run, Bike, Hike) or pressing the Start button to acquire a GPS lock
- Visual Symptom: Immediate blank screen, blue/white Garmin triangle boot loop, or full shutdown that only recovers on a charger
- Data Risk: Low to Moderate (previous synced history remains intact; unsaved workouts will be lost, and system settings may reset if forced into a recovery loop)
What Is Actually Happening?
When you select an outdoor sport profile, your watch does not just open a stopwatch. It simultaneously triggers a high-load hardware sequence:
- Powers on the multi-GNSS / GPS radio receiver.
- Reads the satellite orbit pre-cache file (
CPE.binorEPO.bin) from flash memory into active RAM. - Spikes the optical heart rate sensor LEDs to maximum sampling frequency (25 Hz).
- Initializes the barometric altimeter, digital compass, and internal accelerometer.
- Loads data fields, custom Connect IQ metrics, and topographic maps into memory.
Activity Launch Sequence:
[Select "Run"] ──> [Wake All Sensors] ──> [Read CPE.bin Orbit Data] ──> [Draw Map/CIQ Screen]
│ │ │
Current Spike Corrupt Binary Parse Memory Leak
▼ ▼ ▼
Low Voltage Cutoff Kernel Panic / Reboot Watchdog Crash
If the CPE.bin file contains broken or truncated binary data, the GPS parser encounters a critical memory fault (segmentation violation), triggering an instant watchdog reboot.
Alternatively, powering on these systems creates a sudden draw of several hundred milliamps. If the battery’s internal resistance is high, the battery voltage sags below the power management integrated circuit’s (PMIC) minimum operational threshold, forcing the watch to shut down instantly to protect internal memory.
How to Tell Which Problem You Have
Before deleting files or contacting support, isolate whether the root cause is software corruption or hardware battery failure:
| Observable Behavior | Likely Root Cause | Diagnostic Confirmation |
|---|---|---|
| Watch reboots to the Garmin triangle, boots back up on its own, and battery level remains unchanged | Corrupt CPE.bin or broken activity profile | Crashes even at 100% battery charge; crashes specifically when searching for GPS |
| Watch instantly turns black, will not power back on until plugged into a charging cable | Degraded battery cell (voltage sag) | Review Garmin “Voltage Drop” Issues: Why Your Watch Reboots Under Heavy Load |
| Watch reboots only on a specific profile (e.g., Run crashes, but Bike works) | Corrupt data field, custom route, or profile file | Profile functions normally if GPS is set to “Off” (Indoor Run) |
Step-by-Step Diagnostic & Resolution Protocol
Step 1: Purge the Corrupted Satellite Cache
A corrupted orbit prediction file is the most frequent software culprit.
- Connect your Garmin watch to a computer using its USB data cable. (If your computer fails to recognize the connection, see Garmin Express “Error Transferring Files”: The USB-C Data Cable Check).
- Open the device storage drive:
- Windows: Open File Explorer and navigate to
This PC > [Garmin Device] > Primary > GARMIN. - macOS: Open Android File Transfer or OpenMTP to access the
GARMINfolder.
- Windows: Open File Explorer and navigate to
- Locate and open the
REMOTESWfolder. - Locate
CPE.BIN(on newer models) orEPO.BIN(on older models). - Delete the file.
- Open the
GARMIN/ACTIVITYfolder and ensure no zero-byte (0 KB) files exist. If found, delete them. - Safely eject the watch from your computer.
- Open Garmin Express, reconnect the watch, and perform a full sync. Express will pull a verified, uncorrupted ephemeris file directly from Garmin’s servers.
- For a deeper breakdown of GPS cache failures, review Fixing Corrupted CPE.bin Files: When Your Garmin GPS Takes 10 Minutes to Lock.
Step 2: Strip Custom Connect IQ Data Fields
If an installed third-party data field (such as a custom power curve or continuous heart-rate graph) attempts to access memory addresses blocked by an updated firmware build, launching the activity crashes the operating system.
- On the watch, hold the middle-left Menu button.
- Select Activities & Apps > Run (or the affected sport) > Run Settings > Data Screens.
- Inspect your configured screens. If any custom Connect IQ data fields are installed, edit the screen and replace them with standard Garmin metrics (e.g., Timer, Distance, Pace).
- Return to the home screen and attempt to launch the activity. If it opens cleanly, update or uninstall the offending Connect IQ app via the Connect IQ Store app on your phone.
Step 3: Delete and Rebuild the Activity Profile
If a native activity profile’s configuration file (.FIT) in the internal flash storage becomes corrupt, the operating system cannot initialize the screen layout.
- Connect the watch to your computer.
- Navigate to
GARMIN/SPORTS. - Locate the profile file that crashes (e.g.,
Running.fitorCycling.fit) and move it to your computer’s desktop as a backup. - Eject the watch and restart it.
- On the watch, go to Add Activity, scroll to the bottom, and select the activity you removed. The operating system will generate a fresh, factory-default profile file in the internal storage.
What to Check If That Doesn’t Work
If software and file-system fixes do not stop the crashing:
- Indoor Sensor Test: Open the activity settings and toggle GPS to Off (or launch an Indoor Track workout). If the activity launches and records without rebooting, the fault is isolated to the GPS chip’s power draw or the GNSS firmware layer.
- Master Hardware Reset: Power off the watch. Hold the bottom-right button while pressing the top-left (Light) button to power it on. Release the Light button on the first beep; release the bottom-right button on the second beep. This wipes user settings and clears corrupt system tables. (If your watch gets stuck during restarts, see Garmin Fenix 8/Venu 3: Fixing the “Blue Triangle of Death” Loop).
- Pre-Run GPS Soaking: Once the watch is stable, ensure clean satellite acquisition before starting movement by following “GPS Soaking”: The 2-Minute Pre-Run Ritual for Medical-Grade Tracking.
When It’s Actually a Hardware Problem
If your watch launches an activity cleanly when plugged into a charger or power bank, but instantly dies or reboots when on battery power (especially in temperatures below 45°F / 7°C), the lithium-ion cell has reached chemical exhaustion.
The high internal resistance prevents the battery from delivering the surge current required by the GPS radio. Because Garmin watches have sealed enclosures with structural adhesive, battery replacement requires an out-of-warranty exchange directly through Garmin Support.
The Bottom Line
A reboot upon starting an activity usually means the watch crashed while parsing a corrupted CPE.bin file. Delete the file from the GARMIN/REMOTESW folder via USB and sync with Garmin Express to restore stable tracking.