I just rode Tour De Zwift Stage 5, or well I tried to but gave up after 3 crashes…
I joined the B group on Richmond. First weird thing that hapened is it started loading New York to then send me from New York to Richmond. The same thing hapened on sunday when I wanted to ride Stage 4 on Innsbruck it first sent me to France (where the A ride was taking place) to then send me straight through to Innsbruck. Why? I have never noticed this hapening before & it only adds to the already absurd loading times from launching the game to the point where everything is finally paired & you’re ready to ride.
So… Richmond. I got there, it was a ride like every other. About 6-7km in all of a sudden my screen completely froze. A few seconds later Zwift just closed down. Ok, a random crash can happen I figured. I launched the game again got dropped back into the ride (all the way in the front group??? Fix this while you’re at it, late joiners should be dropped somewhere halfway, not in the front), 0,6km in… screen freezes, and Zwift closed down again. Then I just quit.
I started thinking about it and the game had actually already crashed earlier when I first wanted to launch Zwift today. As soon as the game got to the blue loading screen it shut down. So that brings the total number of crashes to 3 for the day.
I’ve been running the game on the same hardware since 2020 so nothing changed there.
Is there any way I could provide maybe a log file or something like that so you guys can figure out exactly why the game crashed. It’s annoying enough as a one of event, I’m not looking to have this be a repeat event.
We’ve also got club championships coming up on thursday so I want the game to work as it should…
Also you could send a log file to support@zwift.com, and that is not a bad idea, but if you share all the details about your system running Zwift I may be able to provide some suggestions more quickly than you can get a useful answer from support.
That CPU will get the Video Screenshots feature enabled by default in Zwift settings. I would turn that off.
Your laptop should support using either Intel integrated graphics or the Nvidia GPU. This is managed in Windows display settings. By default it should be set to “let Windows decide” which may cause it to use the Intel graphics if you are running on battery power when you launch Zwift. You can tell by uploading a Zwift log file to zwiftalizer.com - it will tell you which GPU was used. I would set it to use the Nvidia GPU, but if Zwiftalizer says you are using the Nvidia GPU when you are experiencing crashes, you could also try using Intel integrated graphics to see if it’s more stable.
When using the Nvidia GPU, the driver provided by Microsoft is usually stable and newer drivers will not improve performance or stability when running Zwift.
When using Intel integrated graphics, an updated driver often resolves stability problems. I would try the latest release provided by Intel:
Normally I’m booting my laptop & Zwift on net power but it’s attached to a Wifi socket which I sometimes forget to enable before launching Zwift. Probably explains why I sometimes notice the screen stuttering notably when I turn on the Wifi socket after launching Zwift.
I’ll try to play with the settings & see where that takes me.
Not sure if anything unusual is in those. It was definitely the RTX2060 doing the work in both cases. Guess I’ll check for any potential driver updates etc.
Looks OK. Frame rates are not great but you are running in 4K. Turning off that Video Screenshots setting would probably help a little.
If you click on the Search tab on the Zwiftalizer site and search for “i7-9750H 2060” you will see what other people are getting on similar hardware. Most of them are not running in 4K though.
I’m not sure which Nvidia driver you are using, but you could try either the one delivered by Microsoft or whatever Nvidia is shipping these days. The Microsoft provided driver is usually safe.
Zwift just looks so much more polished in 4K, I wouldn’t wanna go back. Frame rate is not really an issue for me tbh. I did just update to the latest driver in the Nvidia app. Come to think of it, I probably hadn’t done that in like… ever.
I did disable the Video Screenshot thing in the Zwift settings. While there I also noticed Zwift running version 1.83. The logs from earlier today showed 1.82… maybe they did kind of a hotfix or something as well, I don’t know. I’ll notice soon enough.
I peeked at your server logs and actually - your Windows11 machine got a patch in recent days.
Your January 31 session was on Win 11 build 22621. By the next session on February 2, it was on Win11 build 26100.
You may want to roll back the Windows update and see if this might help.
In the meantime, I’ve flagged up your report with the team in case we here more reports like this from Windows 11 users.