Hi , with the latest zwift update in april this graphic card has become support for the ultra-profile.
The graphic now looks very nice, but i noticed that now the world “Innsbruck” crashes after a few kilometers (mostly after 2,1 - 2,4 km) on my windows 10 pc.
On other worlds i’ve noticed that problems not so far.
Latest AMD drivers (21.4.1) are installed.
The zwift log says nothing except that it crashed.
the windows eventlog tells more:
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Zwift\ZwiftApp.exe
Pfad des fehlerhaften Moduls: C:\Windows\System32\DriverStore\FileRepository\u0366490.inf_amd64_c0dea8a43cb81731\B366217\atio6axx.dll
Hi there. Did you update the launcher as part of the April game update? Right-click on the Zwift icon in the system tray and report back what version it says. I expect it will be 1.0.52, in which case it may be worth trying a previous launcher version and seeing if the problems go away.
Hi Dave, yes, i’ve got the new launcher. I do an complete reinstall of zwift with the april-release. But what should fix an old launcher if the mainapp crashes because of errors with the graphic cards driver? The launcher is only to split the login/account-stuff from the mainapp i think.
Yup same problem as on the RX 6700 XT. Just crashes to desktop now after 10-30 mins. Might be latest graphics drivers for the RX 6000 series, or the latest Zwift update. Same error as above - zwiftapp.exe stopped working, then atio6axx.dll as module that failed.
It’s a bit of a joke really. I have been paying for a zwift subscription for about a year. In that time it has crashed on every single device, become unusable on Surface Pro due to crashes, now it crashes on a £2500 new PC. Every time one issue is solved the next update brings another problem. Really at the end of my tether with it. Ruins all the team events as I am constantly letting people down with crashes. Where do I request a refund?
With the latest update the crashes to desktop bug switched from the Innsbruck track to Watopia (and i don’t know where else) The crash happened now always at the same point on the Mountain 8 track (after 2.8 km). For me Zwift it is on my stable running pc hardware not usable anymore, i canceled my subscription.
That’s a real shame. Crashing at the same spot suggests there’s an asset or similar which suddenly creates an unusual spike in load on the GPU, so the driver shits itself and the game dies. If it’s repeatable then there’s no reason why they can’t resolve it.
it took me a long time in communicating this bug to the support. they have all detailed windows eventlogs and because this bug is always at the same point it is exactly how you say, it is repeatable and this should be no rocket science to find and to fix it.
but i think zwift’s main focus is to apple tv / tablets. that is how most people are using this application.
still disappointing for pc users.
Based on this, it’s probably not necessarily related to the GPU, but could be permissions issues (i.e., accessing files during certain parts of interacting with Zwift) and/or failing, loose, or faulty hardware. It could also be related to RAM, based on the articles I’ve come across in my time seeing these.
Hi Cosmos. I just struggled with the same issue (freeze on Sand and Sequoias/Tempus Fugit/Dust in the Wind lead-in). I have a 5600xt.
For me, the solution was to roll back my AMD drivers to 20.8.2. Unfortunately, I’m not sure whether these drivers will work with a 6800XT. I haven’t tried any newer drivers yet but might work through them to see if any of them work. It won’t let me include the link, but my post is on the front page here in bugs describing the freezing when loading Tempus Fugit (same starting point for Sand and Sequoias).
I am encountering an odd bug I cannot figure out. When on ocean boulevard, with the ocean to your right my Zwift crashes just as you start going up the incline. I am able to ride in london without any issue, and I am able to ride in Watopia going the other direction. However for some reason, if I am going in the reverse direction it crashes at that spot.
I am going to try an uninstall then reinstall, but has anyone else encountered this?