zwift team you guys are a failure, plenty of emails and zero done from you in 8 months
canceled as of today
@Jon Correct me if I’m wrong but I think you’re the lead dev now?
Perhaps you could spare some resources and look into this? It would definitely be good for PR and would sure make a lot of people happy!
I’m sure everyone would help out with details of their setups, logs etc. It sucks having to ride only two words that are on rotation at the moment, there isn’t always a lot of choice.
1 Like
Still broken for me…
Progress?
Newest AMD drivers on 5700xt (22.5.1), latest Zwift 1.25.1; no crash on loading Tempus Fugit…
I didn’t have time to ride (I did Makuri instead as I only had 45 mins for lunch and didn’t want to spend it troubleshooting), but an initial test seems better? Interested to hear if any improvement for others…
It’s odd, perhaps they snuck something in quietly?
I remember checking on AMD driver 22.5.1 and ‘Triple Flat Loops’ was definitely crashing as soon as I opened it, it’s not anymore.
Not sure if I’m going to have a chance to ride today but the fact that it’s not crashing anymore despite the GPU driver not changing would suggest that the issue is with Zwift and whatever has changed fixed at least some of it.
Hi all,
For me (consistent crash at entrance to Tempus Fugit from Downtown just before the fork to the springs) manually uninstalling the AMD chipset software through Windows Apps, end then installing the latest version fixed the issue!
So for me at least it seamed not to be the graphics driver but AMD chipset drivers.
This won’t help off course on Intel processor bases systems.
For me (consistent crash at entrance to Tempus Fugit from Downtown just before the fork to the springs) manually uninstalling the AMD chipset software through Windows Apps, end then installing the latest version fixed the issue!
So for me at least it seamed not to be the graphics driver but AMD chipset drivers.
This won’t help off course on Intel processor bases systems.
Could you share what chipset driver version you’re on right now? And do you remember what was the version before? I’m curious because my chipset driver seems to be pretty old but still, Zwift seems to have sorted itself out,
I’m now on the 25km free trial until this is fixed, I was going to renew my subscription because I opened Triple Flat Loops a couple of times and it hasn’t crashed, I’ve ridden two rides within the 25 km limit and they haven’t crashed either.
I was gonna pay for the subscription today but I wanted to check Triple Flat Loops again and it has just crashed today. I’m still on the same GPU driver version. I’ve updated the chipset driver as @Karsten_Neus_TEAM_NL suggested, but no luck with that either.
I’m gonna carry on with my free 25km and will keep checking the progress on this, but I won’t start paying a subscription again until it’s fixed, the lack of response from Zwift is ridiculous as well.
AMD 3600x / 5700xt
I’ve been riding on this PC for 3 years with 99% zero issues. I tried reinstalling windows and the issue is still there from time to time. I did a 3hr ride on Sunday with no issues then today and Monday I can’t ride for more than 15mins without a crash. Any insight on this would be super helpful.
I find it odd that windows doesn’t show the app version in this report. I’m pretty dumb with computers but i’m trying here.
Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files (x86)\Zwift\ZwiftApp.exe
Problem signature
Problem Event Name: AppHangB1
Application Name: ZwiftApp.exe
Application Version: 0.0.0.0
Application Timestamp: 623124ed
Hang Signature: 7553
Hang Type: 134217728
OS Version: 10.0.19044.2.0.0.768.101
Locale ID: 1033
Additional Hang Signature 1: 755356579d6431abb19c5ef3638cf3ba
Additional Hang Signature 2: 41bd
Additional Hang Signature 3: 41bd85fdb86ebbf086af90383796f532
Additional Hang Signature 4: 7553
Additional Hang Signature 5: 755356579d6431abb19c5ef3638cf3ba
Additional Hang Signature 6: 41bd
Additional Hang Signature 7: 41bd85fdb86ebbf086af90383796f532
Extra information about the problem
Bucket ID: 709d175dc82d64add2812338d87254e4 (1333385691734889700)
Have you updated your graphics drivers recently? There seem to be a fair few AMD-related problems going on at the moment.
Crashing randomly on Nvidia too.
Welcome to the Forums!
In my experience, there’s not much we can tell from the “Application Hang” error itself in the Windows Event Viewer (EVTX) crash log… other than perhaps confirming the fact that Zwift crashed.
In virtually all cases, our tech support team is looking at the surrounding events in the log to see what’s happening leading up to the app crash. As I understand, it’s oftentimes the surrounding happenings before (or perhaps immediately after) the Zwift app crashes that provides us with the most useful information.
That being said, if you’d like our tech support team to take a look and let you know what we find, please send us a support request and provide the following information:
- All of your log files as explained in the PC section of this article.
- Your full computer specs as explained in this article.
- Your 7-day Windows Event Viewer (EVTX) crash logs, as explained in the Issue Occurred within the Past Week section of this article.
You can contact us here.
I’m getting a freeze within <10 seconds when attempting to ride Tempus Fugit. At first I thought it was because I was joining C. Cadence with too many other riders, but I can recreate the issue when starting Tempus Fugit solo. Everything else I ride is running fine to my knowledge (Road to Sky, Volcano, D. Diesel, large group rides, etc.). I have completed Tempus Fugit in the past and just noticed this issue earlier in the week.
Specs:
Windows 10
Ryzen 9 5900X
32GB PC3200 ram
AMD RX 5600 XT (tried multiple drivers and no luck)
Kickr Snap (BT)
I’ve tried reinstalling Zwift and Companion app, checking all drivers, opening firewall settings, running on lowest settings, windowed/full screen, modifying ultra config to match lowest settings, etc. It just seems to hang (freeze), and I have to force close. Everything looks good to go on the AMD Adrenalin logger and process lasso - no excessive GPU/CPU temp or memory use prior to freezing. As mentioned, other routes work fine.
Here’s an example log (hung within about 2-3 seconds, and I forced close about 20 seconds later):
[0:25:27] Setting Route: Tempus Fugit
[0:25:27] Calculating route stats for 168 CPs
[0:25:27] Printing Regular Route. Decisions Count 6. Infinite loop start at: -1 Finite loop start at: -1, end at: -1 for -1 loops
[0:25:27] Marker Id: 810002, Turn: LEFT, Direction: FORWARD
[0:25:27] Marker Id: 820000, Turn: STRAIGHT, Direction: REVERSE
[0:25:27] Marker Id: 780001, Turn: RIGHT, Direction: REVERSE
[0:25:27] Marker Id: 780000, Turn: STRAIGHT, Direction: REVERSE
[0:25:27] Marker Id: 810004, Turn: STRAIGHT, Direction: REVERSE
[0:25:27] Marker Id: 950000, Turn: STRAIGHT, Direction: FORWARD
[0:25:27] Route stats: 1723130.125000cm long with 246968.937500cm leadin, 2560.000000cm ascent
[0:25:27] Route Decision: Staying on same road
[0:25:27] Loading WAD file ‘assets/Humans/Jerseys/Originals/originals_01.wad’ with file.
[0:25:27] Loading WAD file ‘assets/Humans/Jerseys/Originals/originals_02.wad’ with file.
[0:25:27] NETWORK:Joining world 1
[0:25:27] NETWORK:Got the list of worlds
[0:25:27] [NOESIS/W] Type ‘Zwift.ViewModels.NavigationBarViewModel’ does not contain a property named ‘NotificationCount’
[0:25:27] [NOESIS/E] Binding failed: Path=NotificationCount, Source=Zwift.ViewModels.NavigationBarViewModel(‘’), Target=TextBlock(‘NotificationText’), TargetProperty=TextBlock.Text
[0:25:27] SaveActivityService::OnNewActivityId {activityId: 1062807306078519296, internalId: 0}
[0:25:27] NETCLIENT:[INFO] Auxiliary Controller attempting to connect to phone at: 192.168.1.133:21587
[0:25:27] NETWORK:error (8) sending player state
[0:25:27] m_bCullInaudibleEntityAudio: ON (‘game_1_25_0_gmplay_2246_cull_inaudible_entity_audio’ state retrieved from sedrver)
[0:25:27] NETCLIENT:[INFO] Changed to world-map [1,6]
[0:25:27] NETCLIENT:[INFO] UDP host 34.219.246.42:3022
[0:25:27] NETCLIENT:[INFO] Connecting to UDP server…
[0:25:27] NETCLIENT:[INFO] TCP disconnected
[0:25:27] NETCLIENT:[INFO] TCP host 54.244.130.233:3023
[0:25:27] NETCLIENT:[INFO] Connecting to TCP server…
[0:25:27] FPS 87.98, 60189, 10655, -50684
[0:25:27] Giant dt in app. dt = 5.36
[0:25:27] Profile: shutdown
[0:25:27] Profile bike distance: 1861881
[0:25:27] INFO LEVEL: Queuing high volume analytics event: hs_perf
[0:25:27] NETWORK:error (8) sending player state
[0:25:27] NETWORK:error (8) sending player state
[0:25:27] NETWORK:error (8) sending player state
[0:25:27] NETWORK:error (8) sending player state
[0:25:27] NETCLIENT:[INFO] Saying hello to TCP server (largest wa is 0)
[0:25:28] NETCLIENT:[INFO] UDP host 18.237.214.72:3022
[0:25:28] NETCLIENT:[INFO] Connecting to UDP server…
[0:25:28] NETCLIENT:[INFO] UDP host 34.219.246.42:3022
[0:25:28] NETCLIENT:[INFO] Connecting to UDP server…
[0:25:30] NETCLIENT:[INFO] Auxiliary Controller failed to connect to socket: ‘No connection could be made because the target machine actively refused it.’ (10061)
[0:25:31] NETCLIENT:[INFO] World clock offset updated from -362900887ms to -362900887ms (+0ms)
[0:25:31] NETCLIENT:[INFO] Auxiliary Controller attempting to connect to phone at: 192.168.1.133:21587
[0:25:32] NETCLIENT:[INFO] World clock offset updated from -362900887ms to -362900887ms (+0ms)
[0:25:34] NETCLIENT:[INFO] Auxiliary Controller failed to connect to socket: ‘No connection could be made because the target machine actively refused it.’ (10061)
[0:25:35] NETCLIENT:[INFO] World clock offset updated from -362900887ms to -362900887ms (+0ms)
[0:25:40] NETCLIENT:[INFO] World clock offset updated from -362900887ms to -362900888ms (-1ms)
[0:25:50] NETCLIENT:[INFO] World clock offset updated from -362900888ms to -362900888ms (+0ms)
Okay, an additional data point with more testing. If I drop in on C. Cadence at the right spot in Tempus Fugit like near the waterfall or in the mining town and let all the assets load, I don’t freeze. I can then end the ride and select Tempus Fugit and load solo with no issues (assets are already loaded it appears). The freeze happens while assets are loading, so usually a few seconds in.
Small update, I’m still getting freezing issues loading in Tempus. I also freeze when loading Sand and Sequoias and don’t even get past the loading screen for Dust in the Wind. However, I loaded with D. Diesel then peeled off and manually rode to Tempus and joined C. Cadence. I was able to ride with her group for a good while with no frame drops or freezes. Something is hanging during loading when trying to enter the desert from home screen.
Other info, I’m on a wired connection and just got the latest update (1.24.2).
Okay, working now. Rolled waaay back to 20.7.2 driver for 5600 xt. Now no freesync… Anyone have a list of more recent AMD drivers that work?
Moving slowly through drivers. Up to 20.8.2 with no issues. Just lacking some of the features of more recent drivers.
Here’s what I’ve tested:
20.7.2 - works
20.8.1 - works
20.8.2 - works
20.9.1 - works
21.6.1 - works
21.9.1 - works (maybe more flickering?)
I’m going to stop here for now because the AMD driver thread noted problems with 21.10++. I hope someone in the future finds this helpful.
2 Likes
Good work. It’s ridiculous that the userbase has to do this, to figure out what’s going on with software we’re paying for.
3 Likes