Zwift freezes/crashes or becomes non-responsive regularly when ending/saving a ride [January 2024]

Hello,
since a couple of weeks I have the issue that Zwift crashes reliably when finishing a ride. After I quit my ride, name it, save it, and seeing my current streak, Zwift crashes when trying to go back to the main menue. It crashes as in “freezes” and will go into a non-responsive state. It usually manages to upload my ride though, but this has also failed once or twice already.

When looking at the logs, two errors/warnings stick out. These are among the last things logged:
[13:45:41] [WARN] Unexpected HTTP response: [429] ‘’ for: GET [link redacted to be allowed to post]

and various iterations of:

[13:46:35] [INFO] Connecting to UDP server…
[13:46:36] [INFO] UDP metrics {StC Rx: 434, Rx error: 0, CtS Tx: 0, Tx error: 0}
[13:47:05] [WARN] UDP connection timeout (4 so far), reconnection attempt 4

Seemingly the connection cannot be established.

I already reinstalled Zwift without success.

Here is basic information from my computer specs. Let me know if you need anything else.
Operating System: Windows 10 Pro 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
Language: German (Regional Setting: German)
BIOS: 4014 (type: UEFI)
Processor: AMD Ryzen 5 2400G with Radeon Vega Graphics (8 CPUs), ~3.6GHz
Memory: 16384MB RAM
Available OS Memory: 15286MB RAM
Page File: 12088MB used, 5501MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.2075 64bit Unicode

Any idea what’s going wrong?

Thanks and cheers
Manuel

I don’t know if the HTTP 429 is related to the crash.

The Ryzen 5 series should have video screenshots enabled by default in settings, so if that’s turned on, try with it off.

1 Like

Thanks Paul! I have changed the setting and will try it on a ride during the weekend. Cheers!

Already happend 2 or 3 times… after a ride the zwift window is “not responding” and seems to hang when “saving the weekly progress”. Not totally sure as my zwift is set to german language.
The logfile does not seem too illuminating:
[11:36:07] [ActionBarV2] Active Actions have changed.
[11:36:07] FPS 41.72, 5150, 22770, 8742
[11:36:34] [INFO] TCP disconnected
[11:36:34] [INFO] TCP host 18.237.72.24:3025 (secure)
[11:36:34] [INFO] Connecting to TCP server…
[11:36:34] [INFO] Saying hello to TCP server (largest wa is 1704623788011621)
[11:36:43] [WARN] UDP connection timeout (7 so far), reconnection attempt 7
[11:36:43] [INFO] Connecting to UDP server…
[11:36:49] [INFO] UDP metrics {StC Rx: 353, Rx error: 0, CtS Tx: 14, Tx error: 0}
[11:37:13] [WARN] UDP connection timeout (8 so far), reconnection attempt 8
[11:37:13] [INFO] Connecting to UDP server…
[11:37:43] [WARN] UDP connection timeout (9 so far), reconnection attempt 9
[11:37:43] [INFO] Connecting to UDP server…
[11:37:48] [INFO] Sending telemetry…
[11:37:49] [INFO] UDP metrics {StC Rx: 0, Rx error: 0, CtS Tx: 0, Tx error: 0}
[11:38:13] [WARN] UDP connection timeout (10 so far), reconnection attempt 10
[11:38:13] [INFO] Connecting to UDP server…
[11:38:43] [WARN] UDP connection timeout (11 so far), reconnection attempt 11
[11:38:43] [INFO] Connecting to UDP server…
[11:38:49] [INFO] UDP metrics {StC Rx: 0, Rx error: 0, CtS Tx: 0, Tx error: 0}
[11:39:13] [WARN] UDP connection timeout (12 so far), reconnection attempt 12
[11:39:13] [INFO] Connecting to UDP server…
[11:39:43] [WARN] UDP connection timeout (13 so far), reconnection attempt 13
[11:39:43] [INFO] Connecting to UDP server…
[11:39:48] [INFO] Sending telemetry…
[11:39:49] [INFO] UDP metrics {StC Rx: 0, Rx error: 0, CtS Tx: 0, Tx error: 0}
[11:40:13] [WARN] UDP connection timeout (14 so far), reconnection attempt 14
[11:40:13] [INFO] Connecting to UDP server…

Hello all,

I’ve flagged this issue up at HQ for additional investigation. It looks like at least some folks are not able to work around this issue by disabling video screenshots, which indicates this may be a new, different issue. One element that was reported was the “Save Timeout” message that appears when a network error or disconnection occurs during the save/upload process.

@Manuel_Geisler , welcome to the Forums! Please let us know if the issue happens again with video screenshots disabled. If it does- please let me know if you see a “Save Timeout” message before the freeze occurs.

@StephanS , thank you for reaching out about this. I recommend making sure video screenshots are disabled in your Zwift settings menu. If you continue to experience a freeze when saving, please let us know if you’re seeing the “Save Timeout” message as well.

As always, please feel free to contact Support for 1 on 1 assistance.

1 Like

Thank you. Since I deactivated video cature I did not have any more crashes, three rides so far (which is the longest no-crash streak since weeks). So currently it’s looking good!

1 Like

Also thanks. I now have deactivated video screenshots but had no time to ride yet. I"ll try to do some rides today or tomorrow and report back…

So far i’ve only had time for one ride but no hang/crash. Maybe disabling video screenshots really helped. I"ll keep you posted if there is a new crash or when i’ve had some more rides without…

I’ve had four more rides and all four times zwift did not hang. Really seem disabling video screenshots helps…

Thank you so much for clarifying, @StephanS! We are working on addressing this issue. I’m glad to hear that the Save Timeout issue that was reported is not occurring for many Zwifters.

1 Like

@Rowdy I know the release notes did not mention anything… should we still have video screenshots disabled to be safe or is 1.57 worth testing with VS enabled?

Constant freezing/crashing for me - I disabled the screenshots and got 1 ride where it didn’t crash, but every ride (apart from that 1) when I end the ride and save, Zwift hangs…need to do some logfile gathering, but HP laptop running Windows 11 and everything is either optimal or 1 level down but better than the minimum level required.

Realize this is an older thread, but I’ve had this happen twice now that I’m trying to use a small AMD-based (Ryzen) mini-PC. The last 2 rides have both locked up Zwift and the point of saving a ride. Has there been any determination of the cause or a known workaround?

Lots of reports like this from Ryzen laptop users since the last update or two. Many get some improvement by installing the latest Radeon driver downloaded from AMD. Since that’s quick and easy I would try that first. Let me know if it helps. Zwift hasn’t said anything about it yet.

Thanks. I actually haven’t experienced a crash during a ride. It’s only been at save time for me. But I’ve only been using this new AMD-based setup for a few day. I’ll give the driver update a try.

Having video screenshots enabled in Zwift settings can also cause problems when saving.