Zwift crash randomly (because of bluethooth?)

Hello Zwift team,

I currently face (again after a longer while) random crashes of the application with a short freeze and afterwards back on the desktop. The system is a windows 10 pc, core i7, 16gb ram, gtx 1050.
I have the slight feeling that other devices like wireless bluetooth headphones are causing this crashes.

System logs are:
Name der fehlerhaften Anwendung: ZwiftApp.exe, Version: 0.0.0.0, Zeitstempel: 0x5cd4ddf0
Name des fehlerhaften Moduls: ZwiftApp.exe, Version: 0.0.0.0, Zeitstempel: 0x5cd4ddf0
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000013c299
ID des fehlerhaften Prozesses: 0x118c
Startzeit der fehlerhaften Anwendung: 0x01d50a86de0296e9
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Zwift\ZwiftApp.exe
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Zwift\ZwiftApp.exe
Berichtskennung: 72be6916-9218-4595-bafb-c6c5b67fc617
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Zwift logs are:
[21:06:01] ANT : Rx Fail on channel 1

[21:06:01] FPS  60, 49808, 11845, 383904

[21:06:01] FE-C 26 received

[21:06:01] ANT  : Transfer Completed.

[21:06:02] ANT  : Rx Fail on channel 1

[21:06:02] ANT  : Rx Fail on channel 3

[21:06:02] ANT  : Rx Fail on channel 3

[21:06:02] FE-C 26 received

[21:06:03] FE-C 224 received

[21:06:03] ANT  : Transfer Completed.

[21:06:03] ANT  : Rx Fail on channel 3

[21:06:03] FPS  52, 49340, 11845, 385802

[21:06:03] FE-C 26 received

[21:06:04] FE-C 17 received

[21:06:05] NETCLIENT:[WARN] Auxiliary Controller failed to shut down tcp socket: 'Eine Anforderung zum Senden oder Empfangen von Daten wurde verhindert, da der Socket nicht verbunden ist und (beim Senden ĂĽber einen Datagrammsocket mit einem sendto-Aufruf) keine Adresse angegeben wurde.' (-1030752896)

[21:06:05] NETCLIENT:[ERROR] Auxiliary Controller failed to connect to socket: 'Der E/A-Vorgang wurde wegen eines Threadendes oder einer Anwendungsanforderung abgebrochen.' (995)

If you need more information to fix this issue please let me know.
Thanks
Simon

Did you fix this as I now have the same issue.

Can you give more info on the system you are using, when it crashes and what trainer interface.

Neo 1 - Win 10, i7 Acer NVIDA 4 gig Graphics.

Interesting Win10 wouldn’t do a reset, I think this was because there was an pending Windows update available, also noticed there was a Windows Defender Update that had also failed.

So Ive turned off completely Windows defender, just rode for 20 mins, no freeze, no crash.

Will do some more testing and update.

Have run same system for 2 years flawlessly then last week this started, random screen freeze for 5 to 10 secs.

What Graphics card do you have? Bluetooth or ant+

It may be that some other program is interrupting Zwift. Look at your task manager to see what other programs is running. I also found the running in Windowed mode give me the best performance. I do use borderless gaming to simulate full screen.

Its an Nvidia 4 Gig, Will try both those things cheers as I do run it full screen. But since I turned defender off its been ok. Fingers crossed.

Lets hope you found the culprit. :grin:

One thing to note Nivida 4gb can be many different Graphic cards, they made the first 4gb GPU in 2008 and trus me that wont run Zwift. LOL

OK, was getting connection refused errors in the zwift log also. So combination of Windows Defender, Dropping the Res and Running it in Windowd Mode in the Settings in Zwift. 10 mile solo, no Freeze! Fingers crossed its sorted. It was doing it every couple of minutes. Thx for the assist.

1 Like

Are there any news to the original ticket? Windowed mode is not an option. I also run Zwift in elevated mode with admin rights which I thought was solving the problem until it started crashing again…

Why is it not an option?

Because the whole bug should only be a permission problem. I am a software developer myself and if I would suggest this as the solution the discussion would be over in no time. Btw. having the program window in windowed mode causes the window to always have a different size and also a different location on screen. This would cause that I have to re-align the windows again every time bevor I start a ride.
Can your dev team please elaborate if the problem is relying on a bluetooth connection used by any different program than zwift itself. It seems like I have the crashes more often with my headphones (Bluthooth) attached.

Bluetooth headphones tend to cause dropouts. Do you have the option to use ant+ for your training and then you have bluetooth for your headphones. I am not a developer but I think that the bluetooth headphones take priority from time to time.

Install borderlessgamimg app you can specify where and how big Zwift should open. But if it is a bluetooth issue then windowed mode won’t help, I suggested that because I thought it might be another program taking priority of the screen.