Crashes with AMD Radeon graphics [MERGED] [SOLVED]

I am not naive, have a really old PC and a Nvidia 1650 and HAD NEVER crash - in the last 3 years. This is not believe or not believe, it is fact.

The links are reporting crashes - not only Zwift.
And when downgrading driver helps, does it for me look like an AMD issue.

Did you try to contact AMD?
I would do it.

Not downgrading helps. Certain driver version seem to work, others not. That does not at all show that AMD is guilty here. Can be also incompatibility on Zwift side. In any case Zwift should have an interest to solve the issue for their customer and contact AMD or test themselves. No feedback over almost 1y is not acceptable for such a big company.
But however: The main issue is the usage of OpenGL which is not at all state of the art anymore. Zwift should have an own interest to keep the renderer on a recent development level. Vulcan is fully supported by any system.

Frequent freezing at certain spots in watopia, making zwift virtually unusable for me. About to cancel and move on.

MSI/Ryzen 7 5800H/AMD Radeon RX6700M/Windows 11

Had this set up for 5 months everything was fine until maybe a month ago. Crash/freeze just about every time I start a ride. Sometimes 2 mins, sometimes 30 mins, sometimes 1 hour. Data is also not collected either. I’ve tried every driver since mid 2021 and none work. Terrible that zwift can’t work with mid/high level amd gpu’s.

Why is this neglected?

If Zwift the company can’t ensure the game runs in a stable way on AMD GPUs they should hold their hands up and make it clear that they are not supported.

Then again, the same goes for 10th and 11th gen Intel iGPUs, and they’ve never addressed that either aside from Support telling people to use a different device(!) to run the game.

They’ve moved Apple platforms off OpenGL and onto Metal. This may mean they finally drop OpenGL on Windows and move to DirectX or Vulkan, which would provide a big raw performance boost for those AMD GPUs just by not being OpenGL. But performance isn’t the issue here, it’s basic stability. It’s worked fine for years on AMD, so I don’t buy the argument that it’s an AMD problem. Likewise that the iGPU stuff is an Intel problem.

Alternatively if changes have been made by those companies which mean Zwift doesn’t work any more, they need to be honest with the user base so nobody buys something that isn’t reliable/can’t be used properly.

1 Like

Agree, Zwift needs to own up and not mislead people that it is even remotely stable with AMD GPU’s. I’ve read things that say AMD are not optimal, but what I am experiencing is beyond not optimal. My experience is CAN’T use Zwift at all.

@Lauren

How about a real response?

I’ve been spectating all day and it is pretty clear that zwift freezes at certain repeatable points in watopia. Mostly in the desert, on the way to ADZ on the first dirt section, and quite often downtown headed towards the volcano. I’ve spectated with every AMD driver released in the last 1 year and can repeat the same results. Interestingly enough for me at least everything has been fine up until last month or so. Coincidence with new AMD drivers and the new zwift updates? IDK but pretty sure this is 100% zwift problem. I haven’t been able to complete a ride in weeks and no crash reports, no data saved either. About to stop donating my hard earned money to zwift here pretty soon.

I’m going to add my voice to this issue: I cannot run Tempus Fugit or any other routes that start in the same area for more than 6-10 seconds before the game freezes as the assets finish loading. I’ve tried rolling my drivers back to older versions, the latest version, compatibility mode and all points in between.

Weirdly, other routes/worlds seem to load in fine?

1 Like

If you are freezing there you are going to run into multiple freezing points in watopia on other routes that do load. There are spots around watopia that will freeze repeatedly. I’ve sent all the necessary data to zwift and got the response that it is the “new AMD drivers” and I should be using some lower grade device like an ipad to be in zwift. I though that was a crappy response from zwift.

If indeed zwift has an amd problem since Oct 2021 then can we expect a fix anytime soon? No. Why have to pay for something that doesn’t work.

Is this just a Watopia problem then? That’s even more of a reason to think that it’s a Zwift problem, not an AMD problem. I’ve cancelled my subscription already but I might use my remaining time to try and do some riding in other worlds, if it doesn’t crash and it’s just watopia that’s broken then it’s not as big of a problem for me. Still, a crappy response (or lack thereof) from Zwift.

I believe it is watopia only problem. I’ve been testing London and Makuri and have not had a freeze, but I am in the early stages of testing. I’ve identified 4 spots in watopia that freeze all the time since the mid April zwift 1.24.2 update.

lots of good information everyone, thanks for your input! Please lets try to summarize what we know to get Zwift as much useful information as possible. I know this is frustrating alot of us AMD users and i know its something we should not have to do, but perhaps Zwift needs better info to get this resolved. Lets do our part to work together and get a summary going!:slight_smile:

If you have AMD and your getting the crashes please post the following

  1. Your AMD graphics card
  2. The driver version your using
  3. Windows Version
  4. Which loops, and more specifically where your getting the issue.
  5. How long have you noticed this?
  6. What are you using in the meantime to Zwift
    I will go first
  7. AMD Radeon RX 5600M GPU
  8. Driver Version 21.40.23.01
    Windows 10
    3.Sand and Sequoia - crashes about 7 seconds after loading into the world
    Triple Flats - crashes about 7 seconds after loading into the world
    Downtown Titans - crashes just before fork in the road to turn right into Titans Grove
    Ocean lavaside cliffs - In Oct 2021, game would crash near the start when you first start going up the road. April 2022 does not appear to be crashing there.
    Tik Tok - Followed Coco cadence in spectator. Crashed in multiple places along the route
    Note: It might be best to just avoid titans grove/desert area altogether if your having this problem at the moment.
  9. Happened in October 2021, appears to have returned as of last week (for me at least).

I am using zwift on an iPad pro in the meanwhile. While not ideal, its getting the job done for now.

Zwift knows about the problem with AMD GPU’s and I’ve cautioned them to change their requirements page before enough AMD folks get upset and rise up via class action. They are ripe for misleading users especially ones who buy/build high end AMD rigs for zwift only to not be able to use them.

  1. AMD Radeon RX 6700M
  2. I’ve tried every driver and all freeze with the April zwift 1.24 update
  3. Win11 (ran with no issues prior to zwift 1.24 update). Reverted back to Win 10 and it doesn’t work with the zwift 1.24 update
  4. Mostly watopia it seems, haven’t ridden other worlds enough. Desert is bad, wooden bridges from downtown towards desert, fareast route, first dirt section on the way to ADZ (road to the sky).
  5. All of my freeze events began on 4.14.22 after the zwift update, not a single freeze/crash before that

Watopia is un-ridable. I jump into pace partners into Makuri and don’t seem to have any freezing there at all. Bad asset loading or something in watopia. Zwift problem for sure, but my communication with them has been pointless. They don’t care. I have the emails to prove it. Probably will allow myself some time to see if the next update fixes anything and if not I am moving on to wahoo.

I’m a returning-with-a-vengeance indoor cyclist. I’ve just fired up Zwift on my PC with a 6800XT and found the same thing - certain places cause a freeze. Some routes for example Tick Tock just lock up about 5 secs after loading up, consistently.

It’s maddening, as I want to use the PC; but I do have an Apple TV so I can use that if I reconfigure the lounge somewhat when I want to work out. I’ll give that a go for a while and if I’m really into Zwift maybe I’ll grab a TV stand, cheap TV and another Apple TV and setup a workout room. That would actually be cheaper than replacing my extremely expensive (and powerful) 6800XT. That would be a nice setup to be honest, I can leave it ready to jump on.

If I switch to another app though none of that will be necessary, so that’s a mark against Zwift. But my hope has been I’ll get into the gamification appeal of Zwift and it will help motivate me. I’m a mountain biker who’s out of shape and road cycling in the real world does not appeal to me more than a cycling game. I just want to get a high (for me) level of fitness and workout what I need to do to maintain it, alongside ride trails.

It’s sad but reading this thread and the other one my hopes of Zwift fixing this are not high. It’s been going on for quite some time and there’s just no update on the issues. It probably affects a small percentage of users and doesn’t have priority, or more likely it’s a huge redesign to fix it and not worth it because it affects relatively few. That’s a tough thing to phrase “right” hence the silence on the issue. They will however make sure a fixed piece of hardware in widespread use like the Apple TV works properly. That’s always been an advantage of the Apple approach. Sitting in my gear, fan on, on the bike, getting kinda frozen, waiting to start and fiddling with the PC - it’s just too frustrating…

Of course, I could just switch to some other training app and watch Youtube or listen to Audible.

It should be said though - it looks crap on an Apple TV versus my 3440x1440p Ultrawide screen. It’s a real shame :frowning:

I’m confused. I’m very done with riding so can’t give it a proper test, but with everything paired up this evening I’m struggling to find something that crashes after loading. Today it was literally everything I tried, about 10 times.

And wow does it look better at 4K on a PC than on the Apple TV…

Even more confused. Now I’m getting it failing every time after loading Tempus Fugit (which wasn’t failing before, worked repeatedly). Fullscreen vs Windowed doesn’t seem to influence results.

1 Like

Zwift needs to get sued for lying to AMD users. They know there is a problem but not according to thier system requirements.

Same here today. Was 30 minutes in to a pace partner ride and it crashed.

Definitely something about Tempus.

AMD 6800xt, 5900 CPU here.

I followed the bouncing ball with support and they’ve come back and said it’s a known issue, the fix is in the pipeline, will be fixed from their end. So there’s hope I think.

For now, I can use Zwift on my kids PC with a 1050Ti, works flawlessly and it’s interesting that’s a pretty low end card but gets 60fps+ at 1440p. It’s a pain logistically but I’ll live with that until they fix AMD cards. I do have an AppleTV 4K but the graphics are too blocky after using it on PC. Looks like a SNES :slight_smile:

I might even build a training room PC for the spare room, upgrade the kids’ card and use his old one for that, leave it all dedicated.

2 Likes

Zwift team - you are an absolute failure.

Your system requirements don’t exclude AMD GPU’s yet so many of us have problems that you know about since 2021. Make us do that dance monkey logging, drivers only to tell us that it is not a priority for you to fix. Absolute failure of a business model.