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

Crash on connecting to PC (0x00400028)

Hi there, I've got probably the same issue as described here with my Forerunner 735XT. Since there hasn't been any activity in that thread for a while (especially no solution) and my device is not the same model, I decided to start another topic here.

I received my Forerunner in January (as a replacement product for a FR without the problem described here) and have since then experienced multiple crashes when connecting the watch to my PC. The watch then reboots and afterwards, when detaching the cable, reboots again. Each time this happens, all my fitness tracking data (steps, heart rate, sleep etc.) of the respective day is lost.

My ERR_LOG.txt looks as follows:

2158 (Forerunner 735XT) SW ver: 710
Build Type: RELEASE
Commit:9fd18643a5cfd0b088c63bed61532a0161baea67
ESN: 3937781666
01/25/17 13:19:05
AP
PWR RST CTRL: 0x00400028
POR

2158 (Forerunner 735XT) SW ver: 710
Build Type: RELEASE
Commit:9fd18643a5cfd0b088c63bed61532a0161baea67
ESN: 3937781666
01/25/17 13:19:05
AP
PWR RST CTRL: 0x00400028
POR

2158 (Forerunner 735XT) SW ver: 710
Build Type: RELEASE
Commit:9fd18643a5cfd0b088c63bed61532a0161baea67
ESN: 3937781666
03/15/17 15:25:27
AP
PWR RST CTRL: 0x00400028
POR

2158 (Forerunner 735XT) SW ver: 710
Build Type: RELEASE
Commit:9fd18643a5cfd0b088c63bed61532a0161baea67
ESN: 3937781666
03/16/17 11:06:00
AP
PWR RST CTRL: 0x00400028
POR

2158 (Forerunner 735XT) SW ver: 710
Build Type: RELEASE
Commit:9fd18643a5cfd0b088c63bed61532a0161baea67
ESN: 3937781666
03/16/17 14:38:02
AP
PWR RST CTRL: 0x00400028
POR

2158 (Forerunner 735XT) SW ver: 710
Build Type: RELEASE
Commit:9fd18643a5cfd0b088c63bed61532a0161baea67
ESN: 3937781666
03/16/17 15:51:44
AP
PWR RST CTRL: 0x00400028
POR

2158 (Forerunner 735XT) SW ver: 710
Build Type: RELEASE
Commit:9fd18643a5cfd0b088c63bed61532a0161baea67
ESN: 3937781666
03/20/17 18:25:49
AP
PWR RST CTRL: 0x00400028
POR

2158 (Forerunner 735XT) SW ver: 710
Build Type: RELEASE
Commit:9fd18643a5cfd0b088c63bed61532a0161baea67
ESN: 3937781666
03/22/17 08:38:12
AP
PWR RST CTRL: 0x00400028
POR


After reading a couple of similar-sounding topics, I've already tried a master reset a couple of days ago - obviously to no avail.
There are no custom apps/widgets/data fields installed.

Has anyone found a soulution yet or got any more ideas?
  • Did you try on different computers to sort out if it's a computer issue or a watch issue?
    Maybe also try a different usb cable if you have access to one to rule that out too.
  • Not yet, will try both though: certainly the computer idea, maybe a different cable if I can find (an affordable) one. Couldn't find any on the official Garmin website so I guess I'll have to look elsewhere.
    I'll report back if I find out anything new that way, although it would probably only be possible to confirm a watch issue, not one related to the computer or cable, since so far I haven't found a way to reliably reproduce the problem.
  • Have you updated your firmware since the crash? If so do you have the crash on the latest firmware? If yes, post the ERR-LOG
  • Had the same issues a few days ago, actually it was 6.12, after restart date was 3.12 ..

    2158 (Forerunner 735XT) SW ver: 910
    Build Type: RELEASE
    Commit:285aa1feab5e02f246cd5cc44b4add0b7a83ba52
    ESN: 3954442826
    12/03/17 08:31:55
    AP
    PWR RST CTRL: 0x00400028
    POR

    2158 (Forerunner 735XT) SW ver: 910
    Build Type: RELEASE
    Commit:285aa1feab5e02f246cd5cc44b4add0b7a83ba52
    ESN: 3954442826
    12/03/17 08:31:55
    AP
    PWR RST CTRL: 0x00400028
    POR
  • can you post the file rather than just text?

    Have you tried a hard reset (press and hold the light button)?
  • the only thing seems to work to me it's: Disconnect the device (Shutdown the watch), this action prevent losing data since midnight to that point! Then switch on and wait till the first heart rate monitor point, finally connect to computer!

  • Had the same issue. But only when attached via usb hub. Probably the power of the hub is little too high.power peak?

    I have no problem when directly attached to a usb port of a laptop.