Suunto Race 2 constantly rebooting — firmware 2.56.18, confirmed via device logs

viduc

Hi all,

My Suunto Race 2 has been rebooting constantly — roughly every 10–40 minutes, sometimes as often as every 7 minutes. I pulled the diagnostic logs off the watch’s internal storage to investigate, and the cause is clear and consistent.

Findings:

29 crashes recorded in a single 17-hour period
Every crash is the identical firmware hard fault: HardFault (task:ui), unaligned memory access, at the exact same code address (PC 0x004A0A38) every single time
Currently running firmware 2.56.18, HW version 1428B4
A full factory reset did not resolve it — the crashes resumed with the same signature afterward, which rules out a settings/data corruption issue
A firmware update/rollback attempt around the same time also triggered a separate one-time crash (an internal assertion in the update flasher)
Given the identical crash address across every occurrence, this looks like a reproducible bug in firmware 2.56.18 itself, not a hardware fault or something caused by my settings.

Has anyone else on 2.56.18 seen this? Suunto support — happy to share the full log files if useful; I have detailed timestamps, fault codes, and stack traces ready to send. I tried through the app, but I have been sending since the last firmware but they appear to not be fixed so I suspect the ticket is not monitored there.

Thanks.

Suunto_Race2_Reboot_Report.pdf

isazi

@viduc I would contact support and ask for a replacement.

Thorlap71

@viduc Hi,

I got my Race 2 4 days ago and I had two crashes as well. On getting the watch I updated it to 2.56.18 immediately. I had my first crash on Friday just before my 100km race therefore I was worried it could happen again med race, but it didn’t. The second crash happened today. In comparison with your crashes they are not so frequent, but there must be some kind of issue here to resolve. I have yet to see how the watch will be behave in the future and am a bit worried and I shouldn’t be for the watch of that price tag.

Regards.

viduc

@Thorlap71 I looked at the logs myself, in my case it’s to do with the Always-on-Display function in conjunction with the numbered watch faces, how every minutes the time is rendered at a different position to save the OLED panel burn in. Solution for now until they recognise there is a problem, either turn off AoD function or use a different watch face with hands/needles instead of number. I sent many logs but still they replied in the email that they received none. idk but I hope it helps you

elbee

@viduc said:

I sent many logs but still they replied in the email that they received none.

Did you send the mail from the same account as is configured in your suunto account?

Suunto matches logs on email account. It would be so more convenient if you got a reference number after you sent in a log.

isazi

@viduc @thorlap71 are you both using always on display? Which watch face?