Hi Rob,
Are you still running smoothly since your graphics driver update? I’m having the same issue you were with the below issues coming up in my logs before crashing:
[16:23:04] BLE : Crank power 3sec timeout
[16:23:12] BLE : Crank power 3sec timeout
[16:23:13] BLE : Crank power 3sec timeout
[16:23:14] BLE : Crank power 3sec timeout
[16:23:15] BLE : Crank power 3sec timeout
[16:23:19] NETCLIENT:[INFO] Failed one leg latency threshold test. [min: 1659, avg: 1677, max: 1696, n: 2]
[16:23:19] NETCLIENT:[INFO] UDP metrics {StC Rx: 940, Rx error: 0, CtS Tx: 174, Tx error: 0}
[16:23:19] NETCLIENT:[INFO] Sending telemetry…
I’m running Windows 10 with an Intel(R) UHD Graphics card built in to my laptop (with the driver up to date). RAM is 8GB, so all spec should be enough to run Zwift but I’m getting Bluetooth error messages like yours. I have a Wahoo Kickr Core, and am using a Bluetooth 4.0 adapter with a USB extension so it’s closer to the trainer.
Some days Zwift can run without freezing mid ride at all, some days I can’t even get through to load up the game without a crash, and some days it will crash mid ride. I’ve found that on my last few rides Zwift will crash 5 mins or so in with the Crank Power message, but if I restart the computer and try again, it then runs fine.
Last note is that I find Zwift generally crashes on group rides (checked my FPS on Zwiftalizer and numbers are ok and average around 45fps per ride). Couple of screenshots from my Zwiftalizer from my previous crashes.
If you anyone can help in any way it would be greatly appreciated.
N.B. I just did a firmware update on my laptop, so that may resolve the issue but will report back over the next few days to see if issue persists.
Thanks,
Ross
