Crash reports collection Q1 2026

OutdoorMan

R2 booted up after I woke up and pressed a button. For some reason it stopped recording sleep at 2:30 in the night and turned itself off or crashed, I am not sure.

EzioAuditore

@dimitrios-kanellopoulos can this be related to the crashes. https://forum.suunto.com/topic/15193/activities-end-by-itself-when-the-destination-reached-message-appears

SergioB

Suunto Race 1 rebooted after I woke up, prior to show morning report. After rebooting, morning report appeared, telling me that my sleep ended roughly 2 hours before.

Logs sent on 07/06/2026 at 07:50 CET

PhilBee

and another crash/restart today - no HR strap or ZoneSense fields this time

Reddit comment here

*yep have had 4 or 5 of these glitches on 7 week old Vertical 2 so far - on only some runs, after a long while it seems to get slow to respond, then freezes, then restarts the watch (except for 1 time when it just exited the activity). Generally most of the run GPS/HR data is still there, except maybe the last 400-500m when the slowness started. What’s missing is the total ascent/descent calculation and some other calculated data. have submitted support ticket & logs thru app each time. no response so far. I first thought it was something to do with ZoneSense, because they only happened when I was using an HR strap & ZoneSense fields in custom Running mode, but today’s glitch/restart was without the HR strap & ZoneSense fields… so that leaves… touch screen, media controls, or 2 other basic S+ apps (HR Zone Duration and Last km/mile)… or it’s just the whole watch OS … maybe it needs a more regular reboot than just at recharge time

Trying a more basic Custom Run Mod with none of the above (touch screen, media, S+ apps) to see if it still eventually fails

Getting less happy with my purchase :/*

Gilles D.

@PhilBee During a race (IronMan), I got a reboot with my V1 yesterday (https://forum.suunto.com/topic/15356/watch-shut-down-and-re-started-during-activity?_=1781556120294)
Basic triathlon mode, no guide or Suunto plus. Not to mention I have the latest watch update, SA also. Even worse, I did a soft reset the day before the race, to make sure the memory leak risk would be minimized…
Seriously, who wants to wear a watch which is not able to record an activity from its start to its very end ? This FW version is a shame. I have shared my logs to the Suunto as recommended by the CM. If I don’t have answers to this bug, I will change for a reliable brand (despite I am a 10 years users and fan of Suunto, with Ambit 3 peak + 9 Baro before).

skifast12

Ah…I see there are several similar threads…perhaps the admin can link them together or at least reference each other?

3 crashes on Vertical2 in 3 weeks. Posted the details in one of the other threads (in the Vertical 2 section). Logs uploaded and info sent. Hope this gets sorted soon.

sky-runner

@dimitrios-kanellopoulos, here are reproducible crash steps. I crashed my V2 twice today by following these steps - first time by accident and second time intentionally by trying to reproduce it.

Start an activity with navigation and S+ guide. In my case it was Trail Run activity with a simple Training Peaks S+ guide with one field - remaining time
Make sure that the navigation is on route - without that I didn’t succeed reproducing the crash
Realize that the originally selected guide was wrong. Go to the menu by pressing and holding the lower button, go S+ sub-menu, unselect the previous guide and select another guide.
Exit the menu - the watch promptly crashes, then reboots

Even though the steps are quite specific, my intuition tells me that there is a deeper underlying issue, perhaps a race condition of some sort which depends on timing. The fact that it crashes while being on route but doesn’t crash without that specific condition tells me that perhaps the reason for the crash isn’t straightforward. I suspect that the root cause can be common with crashes reported by others.

Other specific details:

I used a custom Train Run mode - not sure if that is relevant.
HR sensor doesn’t seem to matter - the first time I crashed with an external HR sensor, the second time with the built-in sensor
I tried multiple times without having navigation and couldn’t reproduce the crash
I also tried starting navigation but not being on-route, and couldn’t reproduce the crash
Climb guidance was enabled
At the time of the crash the watch showed a black screen with a single white down arrow shown next to the lower button. I also see the same black screen with white arrow flashing briefly when trying to reproduce the crash without navigation

EzioAuditore

@sky-runner you might be on something here. I too was starting activity with wrong S+ (due to the fact it resets everytime you do a guide) and had a crash. now that I leave only one s+ (2 including the guide) I haven’t had restart.
There were a couple of times though that my watch crashed without going to the menu but I always had on route navigation!

skifast12

@sky-runner Interesting that your crashes (if I read it correctly) happen before you even start the activity? I would like to ask this group how much of their watch memory is filled up with maps? I recently downloaded a lot of map areas and then the crashes began to happen a few days later….thoughts?

Gilles D.

Hello @skifast12 , where do you check the % of used memory? Watch? SA?

Gilles D.

On SA :

But with almost 20 GB left on my Watch, it does not gives credit to your assumption