I will uninstall and go back to the previous drivers. Apart from that I will try a different laptop.
It’s just as many things PC related, it’s so common things simply work, that it’s easy to forget it can be fragile at times.
Thanks for the support!
I have ridden 5 rides without rebooting the computer and have not had another issue, most rides were in Watopia. This was after updating all drivers and bios. then running chkdsk /f /r to check for issues on the drive.
I’m doubtful you are being affected by this bug given the GPU you are using. It’s always a bit confusing when something comes up that causes game crashes, and then everyone else who gets a game crash for some other reason looks at it and wonders if it’s affecting them.
8 gig ram, i crash pretty much every time between 20 -40 mins into ride
I played with the config files to see what increase in graphics quality can be done while still remaining solid 60 fps.
My 2 findings are:
Solved the problem for me: I don’t ride Watopia any more.
I’ve had several crashes/freezes doing workouts in Watopia (as described above), but none in France, Makuri Islands, Richmond, London and Scotland.
I do a lot of long workouts (2-3 hours) theese days.
Looking forward to riding again in Watopia when the bug is fixed…
Same like Oliver for me too. Zwift very reliably crashes in Watopia on the more populated roads. Sometimes I can execute a 3+hour ride on the big ring and/or up and down the epic KOM (the “new” regions in the “south”).
Crashes happen for me on the “old” regions in the “north”. I have had this issue since mid November and none of the “help” and “tips” from Zwift changed anything.
When I ride in other worlds I havent had a crash until now.
Hope they soon get that fixed it is really annoying, at least I have a “workaround”. Hope it also works for others.
I’m glad I found this page, Zwift/AMD crashing has been driving me crazy.
Just like everybody else my PC started misbehaving mid to late November with serious guaranteed crashing starting December. I’ve had to end rides after 50 to 120 minutes, infuriating.
I was running with 16GB ram which would slowly fill until the screen would freeze and seconds later would turn white and refuse to change. I did purchase another 16GB of ram the other day and yesterday I completed over 3 hours of riding.
Not the ideal scenario having to upgrade a PC that was working flawlessly until Nov/Dec.
To achieve this longer ride I did have to change the display setting to low (previously set to ultra with no problems), make sure no other program is running and every 30 minutes check task manager to see the inevitable increase in ram usage. Next step is to increase the display setting to medium.
Good luck everybody.
So in November I was trying to do a memorial ride and after 1:18min it crashed. Then in December I was doing another memorial ride for my Dad that would have been 73 I had to break it up into 3 rides because it was crashing at 1:18min.
I even uninstalled Zwift and reinstalled it again between my first ride and the 2nd ride in December.
I’ve limited my rides to under 1:10 so it doesn’t crash and I loose my weekly streak.
I think I can confirm this. In “France” the shared GPU memory did stay basically “0”. So it must have something to do with the Watopia map.
One “Support” (voodoo) Tip I got from Zwift:
In a log they found that the Google Updater was playing up.
Removed Chrome and all relating stuff with it. Since then it has been quiet here.
But I stil need to do a long ride in the “north” of Watopia.
I dont believe it was the main cause, so I am sure I will soon reporting that it didn´t really help. 
Whatever tier 1 or tier 2 person told you this is just shotgunning ideas. It’s very clear that Zwift itself is the issue with a memory leak. Chrome, OneNote, etc. aren’t going to impact it beyond their usage of shared RAM. The more applications using RAM = less for Zwift = crash sooner. It’s why adding more RAM helps as a bandaid but it doesn’t solve the underlying root cause.
Not sure if it helps move the discussion forward but I have also been having this issue for maybe 3 weeks now. Mine typically crashes at 88-93 minutes about 80% of the time. ~10% at 30-40 minutes and ~10% no crash after 2 hrs. I have Ryzen 7 and 8GB installed RAM. Pretty irritating this time of year when I’m going for routes and rides of 90min+
Latest freeze:
Hi all, a quick update from the Zwift team:
We continue to work on this as a high priority but don’t have any solutions to share just yet. We’re exploring multiple paths in parallel to try to mitigate these freezes/crashes and will share more updates as soon as we have anything.
In the meantime, because this issue is so highly correlated to Windows devices with AMD integrated graphics cards, if you have any other devices available to you (e.g. tablet, phone, Apple TV, non-AMD Windows device, Mac), temporarily switching to one of those devices is one way to avoid the issue. Our goal is to get Windows devices with AMD integrated GPUs working correctly either way, but if you do have any another device available, you may want to try temporarily switching until we have a solution available.
Thanks Evan and team, appreciate your attention to this.
Hi Evan. Will you be providing credit for subscription time for users who are impacted by this and are unable to use the product? This has been ongoing for months now.
well I’ve just had it with Zwift and their total incompetence and failure too test software properly.
I have cancelled my subscription and gone back to TrainerRoad … I just cant have every training session i do ruined for the last 2 months fix it you $$##$__$&!!! Its clearly a memory leak that seems to be happening on every driver release of AMD Drivers I have installed.
I am getting this issue too, the platform is almost unusable at this point. I have tried older drivers and the same issue exists. The memory leak definitely is in Zwift, other apps not affected.
Is there any update please? I am pretty shocked this is taking so long to fix given the impact.
