This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Garmin 1030 Firmware 4.0 Strava Segment Crashing

Former Member
Former Member
I installed the new firmware this morning and took a test ride to see if the live Strava segments was fixed - it's not. I setup a new segment, close to the start of my ride, and almost instantly when the segment started it shut down. After stopping and turning the unit back on I continued the ride... Again, about 5 minutes later on another segment it did the same, crashing this time about 5 seconds into the ride. Stopped, restarted and off I went. On the third segment of the ride it worked perfectly. Same exact setup I've been using but this time it seems that it's crashing more than just the first segment - I'm pretty sure it was only crashing on the first segment attempted on the earlier firmware. I don't know if it will help but I'll post the ride file later. Anyone else have same issue or resolved?
  • Did you read the post at the very top of the page?
  • Former Member
    0 Former Member over 7 years ago
    Yah now I did. Thanks bloom34.. I'll post up my file to them there.
  • FWIW - I did quite a few Strava segments today on v4.00. I had no shut down related to segments...

    I had shutdowns, but it was in the start of my ride. I created a separate thread about v400 Feedback...
  • Once it just the first time after the updated that it crashed? There were multiple updates. Unit update, touch screen update, GPS update. Maybe one of the updates had not been fully applied.
  • They are asking us for information, files, time, logs... because they don’t have clue on what’s happening with the shutdowns. (among other things).

    This is unbelievable.
  • Or maybe it's because each user seems to have the crash happen under different circumstances and Garmin is not able to recreate each users shut down off of a poor description of the events leading to the shut down, if everyone was sending in their error logs our issues would most likely get solved quicker :) So I will continue to send any and every error log I get, so they can fix my issue!
  • Former Member
    0 Former Member over 7 years ago
    "so they can fix my issue!"
    People still believe that some devices work and others do not ?
    They are all broken in the same way.
    How much Garmin pay for an hour of being a beta tester ?
  • Former Member
    0 Former Member over 7 years ago
    I've had crashes on several different firmwares usually at the start of a ride (on 2 1030s). Every time it has happened I have been able to restart my 1030 and it has continued to record including the data before a crash. This is way better than my 810.
    My 810 crashed all the time but more often in Europe than Australia. I can't help but think it had something to do with the maps. The Europe maps have way more information on them than the Australian ones, so perhaps the amount of issues people are seeing depends upon where they are and which maps they are using
  • "so they can fix my issue!"
    People still believe that some devices work and others do not ?
    They are all broken in the same way.
    How much Garmin pay for an hour of being a beta tester ?


    Totally agreed.

    If garmin want me to be a beta-tester, first they have to send me a 1030 for free.


  • Former Member
    0 Former Member over 7 years ago
    Well, WTF... Today about 4 minutes into my ride the unit completely locked up and had to do a hard reset to get it back working. Good news is even on hard resets it still picks up from where it locked up (looks like I lose 45 seconds from when it locked up to when I noticed it had locked up though). After the hard reset I went about my ride and all was great, including dreaded Strava segments. Not one Strava segment crash (out of 4-5 of them on an hour ride) after the crash. I'll take that as progress.