Zwift crashing

Hi,

Can anyone help?

Zwift has crashed on me twice the past two days. The first time when I was heading up Alpe du Zwift and the second, this morning, when I was doing the El Giro de Rigo. I’ve looked at the log files and they both look very similar. Below is the text from the time around the crash happened. What’s going wrong?

Really appreciated any help anyone can offer!

[6:28:36] NETCLIENT:[INFO] Sending telemetry…

[6:28:36] NETCLIENT:[INFO] UDP metrics {StC Rx: 1102, Rx error: 0, CtS Tx: 302, Tx error: 0}

[6:28:37] NETCLIENT:[INFO] Telemetry successfully sent

[6:28:39] [BLE KICKR] SIM (-0.00)

[6:28:40] Starting critical power curve search job (2480166) mTimeStamp = 1605.26965 m_lastSearchTime = 1605.26965 calculating=false

[6:28:41] [BLE KICKR] SIM (-0.00)

[6:28:42] NETCLIENT:[INFO] World clock offset updated from +1870363404ms to +1870363404ms (+0ms)

[6:28:43] FPS 57, -83898, 9383, 27112

[6:28:43] [BLE KICKR] SIM (-0.00)

[6:28:45] [BLE KICKR] SIM (-0.00)

[6:28:58] Unhandled characteristic HRM-Dual:004573 for “0x2a19”

[6:29:28] NETCLIENT:[WARN] UDP connection timeout (1 so far), reconnection attempt 1

[6:29:28] NETCLIENT:[INFO] Connecting to UDP server…

[6:29:36] NETCLIENT:[INFO] Sending telemetry…

[6:29:36] NETCLIENT:[INFO] UDP metrics {StC Rx: 709, Rx error: 0, CtS Tx: 56, Tx error: 0}

[6:29:36] NETCLIENT:[INFO] Telemetry successfully sent

[6:29:38] NETCLIENT:[WARN] UDP connection timeout (2 so far), reconnection attempt 2

[6:29:38] NETCLIENT:[INFO] Connecting to UDP server…

[6:29:48] NETCLIENT:[WARN] UDP connection timeout (3 so far), reconnection attempt 3

[6:29:48] NETCLIENT:[INFO] Connecting to UDP server…

[6:29:58] Unhandled characteristic HRM-Dual:004573 for “0x2a19”

[6:30:18] NETCLIENT:[WARN] UDP connection timeout (4 so far), reconnection attempt 4

[6:30:18] NETCLIENT:[INFO] Connecting to UDP server…

[6:30:36] NETCLIENT:[INFO] Sending telemetry…

[6:30:36] NETCLIENT:[INFO] UDP metrics {StC Rx: 0, Rx error: 0, CtS Tx: 0, Tx error: 0}

[6:30:37] NETCLIENT:[INFO] Telemetry successfully sent

[6:30:48] NETCLIENT:[WARN] UDP connection timeout (5 so far), reconnection attempt 5

[6:30:48] NETCLIENT:[INFO] Connecting to UDP server…

[6:30:58] Unhandled characteristic HRM-Dual:004573 for “0x2a19”

[6:31:18] NETCLIENT:[WARN] UDP connection timeout (6 so far), reconnection attempt 6

[6:31:18] NETCLIENT:[INFO] Connecting to UDP server…

[6:31:36] NETCLIENT:[INFO] Sending telemetry…

[6:31:36] NETCLIENT:[INFO] UDP metrics {StC Rx: 0, Rx error: 0, CtS Tx: 0, Tx error: 0}

[6:31:36] NETCLIENT:[INFO] Telemetry successfully sent

[6:31:48] NETCLIENT:[WARN] UDP connection timeout (7 so far), reconnection attempt 7

[6:31:48] NETCLIENT:[INFO] Connecting to UDP server…

[6:31:58] Unhandled characteristic HRM-Dual:004573 for “0x2a19”

[6:32:18] NETCLIENT:[WARN] UDP connection timeout (8 so far), reconnection attempt 8

[6:32:18] NETCLIENT:[INFO] Connecting to UDP server…

[6:32:28] BLE : Crank power 3sec timeout

[6:32:29] BLE : Crank power 3sec timeout

[6:32:30] BLE : Crank power 3sec timeout

[6:32:39] NETCLIENT:[INFO] Sending telemetry…

[6:32:39] NETCLIENT:[INFO] UDP metrics {StC Rx: 0, Rx error: 0, CtS Tx: 0, Tx error: 0}

[6:32:40] NETCLIENT:[INFO] Telemetry successfully sent

[6:32:48] BLE : Crank power 3sec timeout

[6:32:48] NETCLIENT:[WARN] UDP connection timeout (9 so far), reconnection attempt 9

[6:32:48] NETCLIENT:[INFO] Connecting to UDP server…

[6:32:49] BLE : Crank power 3sec timeout

[6:32:58] Unhandled characteristic HRM-Dual:004573 for “0x2a19”

[6:33:18] NETCLIENT:[WARN] UDP connection timeout (10 so far), reconnection attempt 10

[6:33:18] NETCLIENT:[INFO] Connecting to UDP server…

Looks like major networking problems on your device. The connection to Zwift is having big problems, and also your Bluetooth is dropping out.

Could be major radio interference (microwave oven, baby monitor, video sender) or yout PC running out of resources badly so that everything starts failing. I suspect the latter if it actually crashed the client.

All just my own guesses, of course.

Thanks for getting back to me- much appreciated.

My network connection is over a wifi powerline adapter in my shed. I’ve just tested the speed and it’s showing up as slow and is the same if I use an ethernet cable. The powerline adapter is quite old so I could get a newer one but I think I’m going to go for a long ethernet cable. Inside the house the speed is over 100 Mpbs.

Be careful with LONG Ethernet cable - I am no expert, but there are different cable types (here in the EU called Cat5, 6, 7; higher numbers more speed. I think Cat5 should not be longer than 10m).

cat5 limit is 100m.

But why is my 5m long patchcable showing only 10 Mbit/s in my network? I have a short one on another PC with 1 Gbit/s, Wi-Fi with 860 Mbit/s.
As I wrote - not an expert…

I question whether the problem is at the user’s end - I’ve been on Zwift for 10 months with no crashes. I just had my first crash (in a race) and it’s got a similar log details to what Mark reported - problems connecting to the UDP server. I’ve got exactly the same computer setup I’ve always had.

Let’s hope Zwift is looking into this. I could be seeing coincidences where there are none but I get the impression there have been a few more people experiencing crashes lately…?

Log notes:

[19:22:17] LIVESEG: Sending Active Segments.

[19:22:17] TimingArch: crossed arch start line Jungle Loop

[19:22:18] FPS 19, -500131, 9883, -265146

[19:22:24] NETCLIENT:[INFO] UDP metrics {StC Rx: 859, Rx error: 0, CtS Tx: 277, Tx error: 0}

[19:22:24] NETCLIENT:[INFO] Sending telemetry…

[19:22:25] NETCLIENT:[INFO] Telemetry successfully sent

[19:22:34] NETCLIENT:[INFO] World clock offset updated from +2081432561ms to +2081432559ms (-2ms)

[19:22:59] NETCLIENT:[WARN] UDP connection timeout (3 so far), reconnection attempt 3

[19:22:59] NETCLIENT:[INFO] Connecting to UDP server…

[19:23:24] NETCLIENT:[INFO] UDP metrics {StC Rx: 392, Rx error: 0, CtS Tx: 0, Tx error: 0}

[19:23:24] NETCLIENT:[INFO] Failed one leg latency threshold test. [min: 505, avg: 1124, max: 1729, n: 34]

[19:23:24] NETCLIENT:[INFO] Sending telemetry…

[19:23:25] NETCLIENT:[INFO] Telemetry successfully sent

[19:23:29] NETCLIENT:[WARN] UDP connection timeout (4 so far), reconnection attempt 4

[19:23:29] NETCLIENT:[INFO] Connecting to UDP server…

Having the exact same issues here. Driving me nuts. Log files always show UDP connection timeouts right before Zwift freezes. I’ve tried virtually everything, opening ports in router and firewall, making exemptions for Zwift as a program in firewall. Disabling OneDrive sync, removing and then installing the latest version of my graphics drivers, connecting my ANT+ dongle through a USB extension cable instead of directly into the laptop. Tried it with ethernet cable, without, on my 2,4Ghz network, the 5Ghz, hotspot through my phone. It’s just extremely random. Sometimes it’s fine for an hour, other times it will crash 5 times in 20 minutes.

Tried it with my dad’s tablet this weekend and that all went without issues, but my laptop is giving me so much trouble. Completely lost whether it’s Zwift, my laptop, my network, or whatever.

1 Like

Faulty cable? Port set to only use 10Mbit? Connected to an old switch which only supports 10Mbit? Driver problem?

Could be lots of things, but something in that part of the network is dragging down the speed.