Zwift closes the application on the PC, almost 100% of the races

Bugs and Support
1

Please help.

Zwift is closing the PC application in almost 100% of arrivals.
Reinstalling the app completely doesn’t help. Initially (there was no similar problem a few months ago)

Log:
[14:45:50] Setting activity local fit file name to 2020-11-28-13-42-19.fit

[14:45:50] Uploading activity to server – fit file name = C:\Users\Константин\Documents/Zwift/Activities/inProgressActivity.fit

[14:45:50] NETCLIENT:[INFO] Activity Upload: load fit file from path C:\Users\Константин\Documents/Zwift/Activities/inProgressActivity.fit

[14:45:50] NETCLIENT:[INFO] Activity Upload: fit file is length 134229

[14:45:53] Phone requested profile. We know about player 809096 but don’t have the profile yet. Still waiting on the server

[14:45:57] NETCLIENT:[INFO] UDP metrics {StC Rx: 286, Rx error: 0, CtS Tx: 314, Tx error: 0}

[14:45:57] FPS 143, 395120, 10816, 37962

[14:45:58] NETCLIENT:[INFO] Sending telemetry…

[14:45:58] NETCLIENT:[INFO] Telemetry successfully sent

[14:46:00] Starting critical power curve search job (1365613781) mTimeStamp = 3855.12524 m_lastSearchTime = 3855.12524 calculating=false

[14:46:05] FPS 143, 394513, 11019, 32310

[14:46:06] Route Decision: Staying on same road

[14:46:08] BLE : Starting Native BLE search

[14:46:08] Device List:

[14:46:08] ==========================================================

[14:46:08] Cadence: Tacx Flow 56528 119 (0x14D4D177) [BLE]

[14:46:08] Controllable Trainer: Tacx Flow 56528 119 (0x14D4D177) [BLE]

[14:46:08] Power: Tacx Flow 56528 119 (0x14D4D177) [BLE]

[14:46:08] ==========================================================

[14:46:09] Starting critical power curve search job (1365623679) mTimeStamp = 3865.13745 m_lastSearchTime = 3865.13745 calculating=false

[14:46:13] FPS 143, 395312, 11292, 26968

[14:46:14] Registered segment 71 with hash id 1614768

[14:46:15] “44782-161” adding component type: 4 (BLE)

[14:46:15] Device List:

[14:46:15] ==========================================================

[14:46:15] Cadence: Tacx Flow 56528 119 (0x14D4D177) [BLE]

[14:46:15] Controllable Trainer: Tacx Flow 56528 119 (0x14D4D177) [BLE]

[14:46:15] Power: Tacx Flow 56528 119 (0x14D4D177) [BLE]

[14:46:15] Heart Rate: 44782-161 248 (0x14065AF8) [BLE]

[14:46:15] ==========================================================

[14:46:17] Unhandled characteristic 44782-161 for “0x2a19”

[14:46:18] Unhandled characteristic 44782-161 for “0x2a19”

[14:46:19] Starting critical power curve search job (1365633577) mTimeStamp = 3875.14917 m_lastSearchTime = 3875.14917 calculating=false

[14:46:21] FPS 143, 399985, 11636, 25881

[14:46:23] TimingArch: (Box Hill) passed checkpoint 0

2

Need to know your PC specs as a start (GPU, CPU, RAM etc.) if you can.

3

Did you look at your logs in zwiftalizer.com.

Did you look at your windows crash logs.

My first guess will be nvidia drivers, completely uninstall all nvidia drivers and reinstall.

1 Like
4

Core i7-9700K @ 3.60GHz
GeForce GTX 1080 Ti/PCIe/SSE2
32GB

5

Next you should follow Gerrie’s advice by using zwiftalizer and update all of your drivers.

1 Like
6

I updated the drivers by completely reinstalling them. I can unload the log, what exactly there to pay attention to?

7

Look at your p5 and average frame rate. If they drop below 5 you might crash Zwift