Multiplied display during activity on Forerunner 165 Music

Except the new beta doesn't actually fix the issue.

Mine is also Glitching - Forerunner 165 Music Software Version 22.24. Has anyone been able to solve yet?

Absolutely zero response to my support ticket from Garmin two weeks ago…?
My wife has also bought a 165 - updated to 22.24 and it doesn’t happen on hers during a workout run - so is this specific watches only…?
When does this become a warranty return issue if 23.09 doesn’t fix it..?  Watch is basically unusable. 

If this isn't fixed within the next couple of weeks, or version 23.1, I am making it a warranty return issue.

Time for a positive note: Garmin-Sierra has reached out to me regarding my bug report on 23.09, so I am looking forward to crunching this annoying bug together.

That sounds like progress.  I'm not an expert in this area but please let us know if we can all help you both try and get to the cause of the bug and identify what scenarios it occurs with. 

For example my screen crashes have occured on the "Run" event - once when music was playing on the watch while operating a Run/Walk alert - once when no music was playing while operating a workout that I had uploaded to the watch. 

Both occasions had bluetooth headphones attached. 

Another instance was on the Bike Indoor event (so no GPS this time) and pretty basic for the watch as essentially just a timer running, and the heart rate - no music, no bluetooth headphones, no external sensors connected, minimal movement of the watch on arm. 

However all instances take at least 10 mins before the screen corrupts - like an overload - it is fine up to that point in time.

Hope this helps with Garmin discussions.

Yes, for me this appears as a memory overflow, it occurs after 15-20 minutes running only, and mostly on the Garmin coach Jeff drills, where there are 10 to 20 intervals in the workout plan.  The workout data is recorded correctly after saving, but the display is corrupted until the activity is saved.

exactly described! this is exactly how my watch behaves. after about 20 minutes or 4k of running the display will be corrupted, the content will not be fixed for a while, after a while it will be corrupted again. it does this when I run and when I walk for a long time.

I know it's not always that simple, but the developers should be able to look at the source code history to see what changed and caused the issue.

Let's see, what happened this week...:
-Dutch customer support gave a sign of life again, with an incomprehensible email.  I think they were saying they passed the problem on to the software developers.

-Garmin-Sierra asked me if she could add my name to the bug report, so I told her she had already done so 3 days prior.

-Last wednesday I did a run with a manually created workout with only one block with just a pace goal. The screen glitched on the 1KM-mark, but relatively short.

-Last thursday I did very comparable workout, with only a different pace goal. The screen did not glitch during the run, bu it did as soon as I hit save.

-Today I did a short and slow recovery run. No goals or anything else. The screen glitched for probably 60 to 70% of the time.

I really hope a fixing update is released within the next few days, so I can rely on my watch when I run the Rotterdam Marathon, but I am afraid I will have to start the process of claiming warranty after the race.