Freeze with FW 5.00!

same here :( froze mid-ride after sensors stopped showing data...

I had the same experience Sunday. My HR and PM both stopped showing data towards the end of my ride. Whole unit froze up a few minutes later, and required a force reboot. Both batteries are fine, everything worked OK today.

  

I had the same thing happen on Sunday.  All the sensors dropped suddenly, the computer froze and re-booted and then started working again about a minute later. 

Anything the err_log.txt file for the time period in question?

My 830 is now in some reboot loop since upgrading to 5.00 firmware

Quick update...I wanted to do a  couple more rides before responding.  On my last three rides I have had ALL of my sensors drop out ANYTIME I stop for more than, say a minute.  Once I start riding again I have to go into each sensor (power, HR, Cadence, Lights) and toggle enable on and off, and usually the Garmin "refinds" all of them.  Here is the err file from yesterday

[
{
"unit_id":"3998101736",
"product_name":"Edge 830",
"software_part_number":"006-B3122-00",
"ms_since_epoch":1572315763000,
"system_version":"5.00",
"build_type":"PRODUCTION",
"backtrace":" - Error type ( 8 ) err( 8 )",
"error_cause":"8",
"proprietary_info":{
"Commit ID":"577fa9444fa8f04aa1830745a1f86a9dfd5288c4",
"Time":"2019-10-28 19:22:43",
"Project Specific":"
M4 SSRS: 0x6
M4 SRS: 0x6
A7 SSRS: 0x6
A7 SRS: 0x6",
"Task ID":"0",
"Task Name":"",
"R[0]":"00000000",
"R[1]":"00000000",
"R[2]":"00000000",
"R[3]":"00000000",
"R[4]":"00000000",
"R[5]":"00000000",
"R[6]":"00000000",
"R[7]":"00000000",
"R[8]":"00000000",
"R[9]":"00000000",
"R[10]":"00000000",
"R[11]":"00000000",
"R[12]":"00000000",
"R[13]":"00000000",
"R[14]":"00000000",
"R[15]":"00000000",
"cpsr":"00000000"
}

}
]

And the debugging log as well (in case it  helps)

File Name: 0:/Garmin/Debugging/EventLogs//0000008E.TXT

>>>>> EVL_CURR_LOGS <<<<<

verNum: 8/13/2014 (00)
ownerID: 00000000
OwnerName: GFS
status: 03
pri_thresh: 2
archived: 20
max_arch: 20
num_recs: 20
rec_size: 40
next_evnt: 0E
timeDay: 2019/11/ 3 16:50:51
cycle_cnt: 194

0E: DF 05 00 00 0:00:02.206 HWM GFS JEFF Vol:0 Journal entries: 0

0F? FF 00 00 00 0:00:00.989 SYC main ---Invalid Time--- C:0
10: FE 01 00 00 0:00:03.036 SYC main ---Invalid Time--- V:0

11: FF 00 00 00 0:00:00.989 SYC main ---Invalid Time--- C:0
12: E8 00 00 00 0:00:01.335 HWM_main Epwr:00 Eprv:00 mV:0
13: DF 05 00 00 0:00:02.204 HWM GFS JEFF Vol:0 Journal entries: 0
14: E2 00 00 00 0:00:05.943 HWM GFS CHKDSK Lost Clusters - vol_idx:0 cnt:0
15: E0 00 00 00 0:00:05.948 HWM GFS CHKDSK Report: Vol:0 Time:0msec Dirs:0 Files:0 Free:0 Diff:0
16* 57 03 00 00 0:00:07.548 SYC main 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 ................................................
17: FE 01 00 00 0:00:18.603 SYC main ---Invalid Time--- V:0

18: FF 00 00 00 0:00:00.993 SYC main ---Invalid Time--- C:0
19: FE 01 00 00 2:00:03.375 SYC main ---Invalid Time--- V:0

1A: FF 00 00 00 0:00:00.988 SYC main ---Invalid Time--- C:0
1B: FE 01 00 00 0:00:03.037 SYC main ---Invalid Time--- V:0

1C: FF 00 00 00 0:00:01.010 SYC main ---Invalid Time--- C:0
1D: DF 05 00 00 0:00:02.212 HWM GFS JEFF Vol:0 Journal entries: 0
1E: FE 01 00 00 0:00:41.428 SYC main ---Invalid Time--- V:0

1F: FF 00 00 00 0:00:01.009 SYC main ---Invalid Time--- C:0
00: DF 05 00 00 0:00:02.208 HWM GFS JEFF Vol:0 Journal entries: 0
01: FE 01 00 00 0:00:22.644 SYC main ---Invalid Time--- V:0

02: FF 00 00 00 0:00:01.000 SYC main ---Invalid Time--- C:0
03: DF 05 00 00 0:00:02.204 HWM GFS JEFF Vol:0 Journal entries: 0
04: FE 02 00 00 0:01:26.520 PWR main ---Invalid Time--- V:0

05: FF 02 00 00 0:01:27.560 PWR main ---Invalid Time--- C:0
06* CD 0B 00 00 0:04:04.224 BTF main 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 ................................................
07: FE 02 00 00 0:09:25.033 PWR main ---Invalid Time--- V:0

I have also had the Garmin re-boot itself on the same rides

Heard from Garmin Tech Support today. They're working on this issue., and wanted more information on my sensors.