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

Shut Downs during an Activity

We appreciate the passion and feedback that the community has been providing. We will be rolling software 4.00 over the next few days and I have listed an advanced preview of the items addressed below.

In addition, we have more updates planned in the near future and are looking for specific feedback in regard to the Edge 1030 shutting down during an activity. I will accept all of the current logs that you may have and would greatly appreciate any logs that you can collect with the 4.00 version. The feedback that we are looking for would include the following:
  • Link to the activity (if available)
  • Most recent error log (Garmin Folder>Debugging>Saved>Most recent err_log_#.txt)
  • An approximate time when the shutdown occurred, the more specific the better
  • Any details about the ride before the shutdown (started a segment, turn prompt, ect.)
If you would like to email versus posting please email the information to directly to our Product Support teams with the subject line of Edge 1030 Forum Feedback


Improvements with 4.00 – this will be rolling out over the next two days.
  • Added enhanced support for Varia RTL510 radar tail light.
  • Updated touchscreen firmware to 85.11 to fix responsiveness in low temperatures.
  • Added CIQ 2.4.4 support.
  • Improved device stability.
  • Added the ability to discard the current ride at any time. This requires several interactions to avoid accidental discards.
  • Fixed text conversion issues.
  • Fixed issues with the Varia Vision data screen setup causing the Edge and Varia vision to be out of sync.
  • Fixed issue preventing a BLE sensor from being added if it was the first sensor.
  • Fixed issue where the ANT generic channel used by CIQ data fields would not reconnect when the device resumes from sleep.
  • Fixed issue where searching for a long address would not provide a proper result.
  • Fixed issue where battery save mode would turn on GPS in the Indoor activity profile.
  • Fixed issue preventing some iPhones from staying connected during the pairing process.
  • Fixed issue preventing activity uploads after saving a ride.
  • Fixed issue where the ascent remaining and ascent to next course point data field values did not match the total ascent for the course.
  • Fixed various issues with sharp bend warnings.
  • Fixed issue where FTP would be reset after recording an activity with a CIQ app.
  • Fixed issue preventing battery save mode if the timer is auto-paused.
  • Fixed issue where calories would be incorrectly calculated for BLE power meters.
  • Fixed navigation audio prompts.
  • I'm sure shutdowns are due to Strava segments: even yesterday, for the second time, in the same point, both on the outward and on the return, the device went off right in the proximity of a Strava segment. Just at the beginning and at the end of my training. I'll delete that segment and try again, but it's not a good behavior. Firmware 5.0.
  • Here we go again, similar to many of the previous shutdowns. Memory allocation / pointer errors seem like a problem with buggy system code, likely not being properly bounds checked.

    8/10: https://connect.garmin.com/modern/activity/2922358969
    "RTL Error Number":"6E5D8017",
    "Error Message":"......TSKgarmin-ostsk_malloc_mmu.c 2190, Invalid next memory block pointer. rtrn=0x00117B91, mblk=0xC0A49F68, next_mblk=0x00000000",
    "Task Name":"CDP main",

    Shutdown at 19:13, came back online at 21:31 after a manual restart.

    Firmware version 5.0.0, yada yada yada...

    I'm sure shutdowns are due to Strava segments: even yesterday, for the second time, in the same point, both on the outward and on the return, the device went off right in the proximity of a Strava segment. Just at the beginning and at the end of my training. I'll delete that segment and try again, but it's not a good behavior. Firmware 5.0.


    IDK, I was nowhere near a segment when my 1030 shutdown tonight.
  • Former Member
    0 Former Member over 7 years ago
    The 1030 is complete garbage! I just wish I would have known of these issues prior to spending $600+ on something that doesn't work. I've used it 5 times and have had issues every time with it shutting down on me. It usually happens within 5 minutes of starting, but happened three hours into a long, hard effort last week and completely corrupted the file and I lost hard-earned power data I really need! I am training for a 200 mile race in four weeks and purchased the 1030 because I need the extra battery life and I like the display size. I guess I'll just return the damn thing. Very very disappointing.
  • I never had such kind of problems (well, only remote disconnects and livetrack odd behavior, but this one is a global problem..). Just disable these stupid strava segments and it would be better...
  • Former Member
    0 Former Member over 7 years ago
    Just got sent a 1030 as a warranty replacement for my 1000 where the power button rubber perished.

    Unit turned itself off 3 times during set-up.

    All FW up to date according to the unit. (btw, why won't it work with 5GHz wifi???)

    Think I'll sell the unit and buy a Wahoo. Garmin you keep adding loads of we don't need before you've made the damn thing reliable. You deserve to fail.
  • We appreciate the passion and feedback that the community has been providing.


    First random shutdown with firmware 6.0.0 yesterday.

    Though TBH, it would seem that you have long since checked out of the discussion. Let me know if that’s not the case and I’ll post the details.
  • Former Member
    0 Former Member over 7 years ago
    Also got my first shutdown last Friday with fw 6.0.0. After 2,5km , in the middle of a segment (Garmin segment)
    never had shutdown prior to that.
    the edge restart and automatically restart activity.
  • Me too, first time, with firmware 6.0 :(
  • Same here. First time shut down on FW 6 before the first starred segment of the ride. Routing was enabled via Strava route app to import route.
  • Yesterday the first ever shut down during an activity with FW 6.
    Been riding a Strava segment some 8k before and had no problems, so not sure it is connected to the Strava segments.

    The Edge 1030 restarted and continued the tracking, but a couple of meters later the same again - shut down and restart.

    I finally turned my phone (which was conencted to the Edge) into Flight mode and had no further problems >>> something wrong with the BT connection Smartphone/GCM - Edge 1030.

    Funny thing though, last Sunday I did a 172k tour with the phone connected and had absolutely no issues - since then there was also no update of the Garmin Connect App...