Zwift Hard Crash to Desktop (No error) - Win10 after 3/18/2021

Symptom: Hard Crash to desktop, no warning, no error, just gone. Zwift continues to run in the background (i.e. can re-launch/systray installed). Multiple people in the group rides I was in today and yesterday said they had similar issues.

Details below, sharing because I think this hard crash may be related to chat/messaging. See info.

Zwift Info
Launcher Version Number 1.0.51
Patcher Version Number: “1.3.0”
Local version is “1.0.64913”
Win10 Pro ver 2004 | OS Build: 9041.804
ANT+ for pairing using powered USB hub + extension cable

Symptom Began: Started in last 3 days.

Note: Had Companion running in background / other PC first time, closing that out let me ride longer yesterday. Today, same thing. However, i noticed 2 out of 3 crashes in the past 2 days were the moment it hit “enter” to send a chat Yesterday I simply stopped chatting/using messaging (direct or group) and never crashed again.

Steps taken:

  1. Reboots/power offs (multiple)
  2. Windows Updates - though still have 1 pending
  3. Hadn’t updated graphics drivers (doing that now)
  4. Hadn’t fully reinstalled Zwift (doing that now)

Hardware Specs:
GeForce GTX 970
Logitech K400 wireless keyboard w/ touchpad

Wahoo Bike via ANT+
Wahoo Headwind
Wahoo Tickr (white/blue one) via ANT+

Crash Error in Win10 Application Event Logs:
Faulting application name: ZwiftApp.exe, version:, time stamp: 0x604eaa9b
Faulting module name: ntdll.dll, version: 10.0.19041.804, time stamp: 0x4544b4a1
Exception code: 0xc0000374
Fault offset: 0x00000000000ff099
Faulting process id: 0x2994
Faulting application start time: 0x01d71d852f1c4a02
Faulting application path: C:\Program Files (x86)\Zwift\ZwiftApp.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 37e63340-6ad0-4a1c-9ede-751707592aa9
Faulting package full name:
Faulting package-relative application ID:

I have had 4 crashes in past few days since new Zwift update. These are first crashes ever in around 3yrs and countless zwifting hours
Will try and figure out how to get windows error logs but zwiftalizer doesn’t show any network drops or generally any weirdness.
Reloaded Zwift launcher but then had avatar flickering so rolled back to 1.5.0 version and full Zwift delete and reinstall.
I did notice nvidia driver update around same time so as a precaution have uninstalled and reinstalled that
Haven’t given a test again after the full reinstalls as still dirty about it crashing out half way through the fondo ride :frowning:
Only thing I use the keyboard for is changing camera views and had done a bike swap in the jungle on last crash. It didn’t crash immediately on using keyboard but was within 5 mins. It’s a corded USB keyboard though.

Zwift crashes appear to be the virtual equivalent of a flat tyre I guess

Hmmm, I suffered the first crash ever today on PC in years of regular Zwifting. I was 30km into a London Pretzel group ride, went to type a message in chat and then blip, crash to desktop.

I’m having the same issue. It’s really frustrating when you are in the middle of a training or a race. Zwift crashed during every session I had open. I have the latest update of Windows 10.

Just replicated this several times. Often but not always, when you hit close to or at the character limit of chat messages the app instantly crashes to desktop. Re-launched the game several times and tried it in different worlds - roughly half the time the game crashes once you have opened up a chat box via “m” on the keyboard and then hold down a key until at or close or repeatedly hitting the character limit. Might stay completely away from keyboard chat for a few days…


Fairly major and fundamental bug here @shooj, is it known and being worked on? Several mentions in the main update thread and elsewhere too. Causing crashing on systems that are otherwise very stable.


Direct capture of what happens.

1 Like

This is great. Have killed the task 2 times and restarted the computer just lags when it is loading the map. Wow

Sounds like the same problem I’ve run into since Thu/Weds? Crash straight to desktop, zwiftalizer looks perfectly clean, Windows error log indicates ntdll.dll (which is basically the haystack in the old analogy), there’s no network issue I can detect elsewhere either.

Not instantly related to a chat message that I wrote or can see, at least.

Win10, up to date, i9 + RTX2080, gigabit lan, gigabit fiber. (Has occurred both on the current and previous nvidia driver, clean install.)

Hmmm, wait wait. I have not been on the chat in every instance, but I have been moving the 0 camera (by pressing keys) at least on two occasions. Lemme see if I can confirm.

I don’t know how to say this but you kiiinda suck Zwift when bugs aren’t your priority which I guess it is not. I wish there was an alternative to your program. If new feature or something have made it impossible for us with worse specs or if it just is a bad bug…

Edit: This is how I made it work… I uninstalled and installed but this wasn’t enough. Then I choose “just watch” and it made it work then I exited and it worke as usual FOR NOW.

I stand by my words, please don’t make anything better now, it is all good as it is. It’s perfect now! :smiley:

I’ll just add my voice/vote to help get this bug flagged. As @Dave_ZPCMR mentioned, I definitely think this is one that, if it’s not already being worked on, needs addressing as a priority @shooj!

I’m aware of at least 2 instances over the weekend that have resulted in our ride leaders having system crashes … both linked to messaging at the time of the crash and both have systems that are normally extremely capable/stable.

A bug that directly impacts the social element of Zwift and causes riders/ride leaders to have concern of an unstable platform is in need of a priority fix and should be accompanied with regular (I.e. Daily) updates in my eyes.

Thanks :+1:t3:


I wonder if the keyboard related bug - everyone is using wireless keyboards (odds are, yes, but some may be using laptops). Could help isolate that one possibly.

I do know one crash happened the moment I sent a message on companion, as well, but that may have been a character limit bug or i could’ve been switching to the keyboard just as it happened, too. Fuzzy memory there.

Can’t confirm this directly (after reinstalling everything once again). Tried moving the camera in and out of event, and while the chat popup was open, no crash.

same issue here on Sunday morning 10u00 CET in Team Valhalla ride. Was typing as usual and mid sentence Zwift crash to desktop. After I found out about this bug I no longer type messages during group rides. During yesterdays Pack social ride it was obvious Zwifts social element is much lower as messaging is only a fraction of wat it used to be.
Please adres this bug as it is directly affecting Zwifts social element as @Jon_Wakefield pointed out.


I’m hoping a fix is coming pretty quickly on this one! @Libby_Behrens has mentioned here that it is being worked on so fingers crossed!

Worrying that typing a message is going to crash your ride is something that none of us want!

1 Like

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 :+1:


Perfect! Good news @Hybrid_Noob

Just seen the updated bug fix notes on the main game update thread! - [Version 1.11.1 Update - 3-23-2021]

1 Like

Great stuff :+1: …just note Eric’s note here 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."

The keyboard bug may have been fixed, but I am still getting frequent crashes straight to desktop. This time it was right under a banner and there was confetti — it could be there’s something in the graphics layer that gets triggered, or it could be something about the banner events, or it could’ve been random because it’s not a banner every time.

Nothing in Zwiftalizer. ntdll.dll as location in Windows logging.

Win10, i9, 32 GB, RTX 2080 w/ latest, gigabit wired.