After 40mins of riding as a Sweeper in a group-ride, zwiftapp.exe crashed without further notice - no specific hints in zwiftlog.txt, but an application error in the Windows Logfile - any idea?
Log name: Application
Source: Application Error
Date: 03/19/2021 19:27:06
Event ID: 1000
User: Not applicable
Name of the corrupted application: ZwiftApp.exe, version: 0.0.0.0, timestamp: 0x604eaa9b
Name of the corrupt module: ntdll.dll, version: 10.0.19041.844, timestamp: 0x60a6ca36
Exception Code: 0xc0000374
ID of the faulty process: 0x1a20
Start time of the faulty application: 0x01d71ce412c4fddc
Path of the faulty application: C:\Program Files (x86)\Zwift\ZwiftApp.exe
Path of the faulty module: C:\Windows\SYSTEM32\ntdll.dll
Full name of the corrupted package:
Application ID that is relative to the corrupted package:
C:\Program Files (x86)\ZwiftApp.exe
Mar 19th 2021
1 hr 7 mins
Ryzen 5 3600 6-Core Processor
GeForce GTX 1650/PCIe/SSE2
Edition Windows 10 Home
Installiert am 19.01.2021
Leistung Windows Feature Experience Pack 120.2212.551.0
If you were part of a group ride team I guess you were typing quite a lot?
Do you have a Kyocera Printer installed on this machine?
Install win Update KB5001649 or deinstall KB5000808.
With the March Update KB5000808 (results in version x.868) you get all sorts of weird problems.
Also your version of ntdll.dll doesn’t match with your OS info.
Nvidia driver is not up to date.
Doesn’t matter. I haven’t even bothered manually installing it on builds for ages now. I think this is the same text character issue others have reported.
Hi Dave, what kind of “text character issue” do you mean? I didn’t find any hint…
not even a single printer-driver is installed…
Sure, I’ve typed a lot - nearly every minute - so, what kind of text character issue are you talking about? I didn’t hear about that…
There’s a repeatable bug with the latest update where typing too many characters crashes the game to desktop. Obviously a major problem.
You can probably repeat it, as I did, in a free ride. Open chat pressing “M” then hold down a key on the keyboard while it maxes the character limit and beyond and 50-50 it will crash to desktop. Doesn’t seem to be affecting chat in the companion app, apparently.
Hi Chaps, thanks a lot for all the hints - I was able to reproduce the problem as described: I’ve used a copy-paste text with 124 chars and zwift crashed - but not on companion app… the big question here is: is it dependent on ONE message with too many characters or does zwift summarize the chars of many messages?
Good point, I am just staying away from the keyboard full stop! Especially once I have covered more than a few kms…
Apparently an update has been applied that fixes the chat bug crash. I have just tried to recreate it after the update and it seems to have worked
wow - I’ll leading a big ride today - great news! I can chat as if there would be no tomorrow…
Just note Eric’s aside as a ride leader: Zwift Update Version 1.11.0 (65416) Released - Zwift Insider
- "Fixed a crash when Zwifters would send a very long chat message in game.
Word is there are still problems with ride leaders using AutoHotKey to send messages – if the keystroke rate is too fast, it crashes the Zwift game."
Aaaaaaaagh - just hit this new bug yesterday - no joke. I typed too fast (I’m a typewriter-veteran…) and Zwift crashed again. This is so fXXX annoying… it happend during a group-ride as leader 15 minutes before end - left over 400 riders “leaderless”… This is far away from having fun…
How annoying! At least it’s one you can avoid a little easier but no less frustrating for yesterday’s ride.
I wonder when the time comes (or perhaps it’s already being worked on in parallel?) that Zwift rebuilds things from the ground up to make the base code less messy and largely eliminate these type of widespread issues? As much as I love it, there really does seem to be some fundamental flaws in the way it’s been built.