Anyone have issues with crashing?

sgtcoder 9 days ago

Anyone have issues with their Garmin crashing? Here are a few cases

Whenever I ride to 60 ish miles my Edge 1040 crashes and restarts. Luckily the route restores, but sometimes it loses a couple miles, that's annoying. Happened to me 2x already.
Sometimes when I plug my Edge 1040 in, the device freezes and the only way to get it to function again is to hold down the power button for like 10 seconds.
Sometimes when I do a map update, once the update is done and it tries to load the map, but it sits there forever. I have to restart the Edge 1040.

I had crashing issues on the Edge 1030 as well. I would honestly think that the flagship devices from Garmin wouldn't have all these issues.

0 DennisF 9 days ago

I had sudden crashes/reboots during an activity with 1030+ before, and now having with 1040, but very rarely.

I raised it in another topic for 540, it seems Garmin is willing to look into that in more detail - forums.garmin.com/.../edge-540---25-24---so-now-it-reboots-during-activity-and-loses-track

0 Martinhjensen77klb 4 days ago

Same here. One day it stop to count distance and speed freecing. Other time when i stop and save a ride, and will start new, i have blank screen and could only press power 10 sekund and restart my 1040.

0 Martinhjensen77klb 4 days ago

I have sometimes blank screen when i will make a new ride shorts time after a other ride. I can only hold power buttom 10 second to reboot. I have also one time when a ride suddenly get stuck and odometer not counting but the speed was 7 kmph. also when i was stop riding. Also here i reboot device

0 TexasChip 3 days ago

I haven't had crashes, but I've had freezes. First time I'm seeing freezes on the 1040, and I've had it for over 2 years. The freezes happen seemingly randomly, when I switch to the map screen, or when I hit the lap button, or when I stop a ride and try to save it. The device eventually comes to its senses 5-10 seconds later, but it's annoying to say the least. Not sure when this all started, probably after the upgrade to v24.55, but it has continued in v25.24.