Issue is still here. Zwift crashed during a long event ride (after about 90 minutes, still about the same time tag as in my previous report) while I was writing a long message. Have the log file if required.
Zwift & Soft & Hardware Info :
Launcher 1.0.52
Game 1.0.65416
W8.1 64b
Ant+
Intel Core i7 6700 @ 3.40GHz
2047MB NVIDIA GeForce GTX 1060 6GB
Forceware drivers v461.92
RAM 32.0GB
I have exactly the same problem. I am a ride leader and I lead or sweep over 3 rides a week. Since the recent March 2021 Zwift App update the Zwift app just crashes spectacularly during rides, especially during the act of mid-messaging and it seems to be also when I’m using the ‘back-delete’ key. Before that update Zwift was absolutely stable.
I have tried to contact Zwift support but with little feedback. Disappointing as I lead rides and this affects 300+ riders when I’m leading a community ride.
I have tried to troubleshoot myself. My network is stable, I have tried 3…yes three…different machines (2 new modern Win 10 laptops, and a 2019 iMac 27" Retina); I have replaced Ant+ and USB cables; I have replaced keyboards etc. I have turned Bluetooth OFF on the Zwift machine also. It is really frustrating.
I do message a lot so could it be a message buffer size issue?
I have now reverted to looking at the Zwift logs and dump logs. On area I found was the text ‘com.apple.audio.IOThread.client’ in the dump and read somewhere that it could be a BlueTooth issue. I do have my iPhone on with Wireless Bluetooth Bose ear buds. This is what I will try and eliminate next.
Has anyone experienced any similar issues or have any troubleshooting tips? I am IT literate (Very) so please be as technical as need be to help.
Help!!!
Happens to me as well.
However, its only when I use the keyboard with the windows PC. If I stick to “typing” on the ipad (Companion app), it never crashes.
zwift has been stable on win 10 using BT 4.0, kickr v5 and ticker, I had too many dropouts using ANT+, but if I use my wireless keyboard zwift will crash after chatting for a while.
i have a ticket in with zwift and they are looking at the logs…
also hoping that zwift will implement the kickr direct connect soon, although BT has been stable
Log Name: Application
Source: Application Error
Date: 4/22/2021 8:57:43 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ANIMAL
Description:
Faulting application name: ZwiftApp.exe, version: 0.0.0.0, time stamp: 0x6079e84b
Faulting module name: ntdll.dll, version: 10.0.19041.928, time stamp: 0x9bed63d6
Exception code: 0xc0000005
Fault offset: 0x0000000000025bb6
Faulting process id: 0x2844
Faulting application start time: 0x01d737ec12dc5e51
Faulting application path: C:\Program Files (x86)\Zwift\ZwiftApp.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 48238e2a-6dfc-4a58-b968-20c58850907e
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
1000
0
2
100
0
0x80000000000000
41655
Crashed for me today as well, thought this was fixed already but I guess I should know better.
Bonus bug: the fence controls are no longer there if you end up having to late join as the ride leader.
I have received an email from Zwift acknowledging a keyboard in-game messaging issue that causes Zwift to crash. Here are the salient points…
“Steve, I’ve checked with our team and they’re working on a fix for a known issue where the Zwift app will sometimes crash when sending chat messages in-game from the computer keyboard…
…There’s no time frame as to when a fix can be expected but again, our development team is working towards a solution. I’ve asked that they escalate the issue and get it resolved as quickly as possible.
…consider using the Zwift Companion app for chat/messaging instead as potential alternative to the in-game messaging.”
Great to know there is an issue (and that I’ve not gone mad) and also that a fix is in the backlog pipeline.
Appreciation and Kudos to Zwift support team. Look forward to the fix.
RideOn
I think this issue first showed up months ago and since the complaints stopped, I naïvely thought it had been fixed. I must be new here.
Expect very short
chat messages from
me from now
on if/when I
am the
ride leader (maximally
awkward breaks not
guaranteed).
Very frustrating to see that this is still an issue.
As a ride leader, its critical not to get booted from an event, due to being social.
I host the DBR Endurance ride every Thursday and Zwift has crashed on me in almost all of them in the past couple of months. Some I have been “lucky” that I’ve been booted early enough to get back as late join.
Yesterday it happened at 29 mins into the ride. I dont hold back. I send quite a few messages. I have started to keep them short (or shorter), but little does it help.
Zwift wants every ride to have a ride leader. But its really frustrating when you, as a ride leader, get booted for doing your job.
It seems to be OK, when I only use the Companion App for chatting. But I think that may be because I really keep the messages short. Really dislike chatting on the ipad.
I do plenty of other events without issue. But on those I dont blabber away continously.
Please Zwift, get some focus on these devastating bugs.
I support this with the frustrating feeling. During events I am now behaving arrogantly by not even answering questions / comments addressed to me in order to avoid a crash (I’m not using the Companion App).
I tested this again with the latest version (1.12.1) and could no longer reproduce the crash, including in event mode. Will probably still try to keep the messages short just to be safe, though.
I still experienced a crash a week or so ago (Zwift Hard Crash to Desktop (No error) - Win10 after 3/18/2021 - #28 by rue)
Short story short: graphics stutter and typing at the same time. Always both, sometimes there are stutters that don’t crash, and generally typing is fine.
I have not encountered this crash since one software iteration back - I am on 1.16.0 (78621) now of ZwiftApp.- I think this is resolved, but I want Zwift to respond.
Any input is appreciated as nothing was mentioned in the changelog. I have no crashes yet!!!
Only two rides since I got back on Zwift last week, but no crashes either time. Fingers crossed, but it’d be good to hear if there was something specific done to address these crashes. I don’t see anything in the release notes — @shooj any info on this?
It was fixed in the 1.15.0 release.