Riding a structured workout normally for 20-30 minutes normally, then screen starts freezing in 2-second intervals for remainder of ride. The intervals appear to record normally, only the real-time screen is affected. This has happened on every ride after installing latest update on 5/27/26 - never before.
I’m seeing this too. I have an 8th Gen i7 with 48GB RAM, and a RTX 3060Ti in Ultra. After ~30 minutes I go from a smooth 60fps to 0.5 fps. All data continues to record well, bluetooth music from my PC keeps going smooth and the task manager says everything is low load and my thermals on the CPU and GPU are fine.
Do you have an ANT+ dongle in the system? If so, pull it out and test again.
It’s difficult to see CPU bottlenecks in task manager since Zwift is going to mostly use a single core, so even if you are hammering that core to death you will see the CPU is mostly unused (because it is mostly unused).
I’ve still been seeing this, not only in ERG Workouts. I have unplugged my ANT+ Dongle as I am 100% Bluetooth now. I have had multiple driver updates for my RTX 3060Ti to no resolve, and my CPU / GPU Aren’t overloaded for %Usage, or Temp. When the problem hits they both drop in utilization drastically. All data keeps flowing for my ride, and I get feedback for actions performed with my Zwift Play controllers, but the video drops to 0.5 fps (one frame every other second perfectly timed). I’ve had it after as little as 3minutes into a ride, but typically about 35~45 minutes in. Please help as I would like to resume using my Windows PC instead of my AppleTV as indoor race season approaches.
I did a full uninstall, cleanup of zwift then a windows repair install, and fresh zwift install today and it still happened. To test I did just watch another rider in watopia.
I’ve nothing massively useful to add, aside from occasionally having the same issue (sonetimes if I run zwift twice without shutting the PC down , and then only when going past specific places - just past the rock tunnels on Tempus going towards the desert turnaround / titans junction will be where it happens, it ''f it does happen)
Oddly whilst the visible frame rate drops to a something like 0.5 fps, any video screens work sorta ok (though almost like they’ve been slightly sped up).
I’ve never really spotted any obvious triggers or system issues unfortunately (aside from the above, but I’m not sure it’s any more than coincidence) - the trainer DX analysis of my logs from affected rides didn’t really yield anything useful for me.
Edit, should mention that I only started having these issues after doing an in place upgrade from Win10 to 11.
Hello all. I was experiencing intermittent frame issues with display responding slowly, etc. I have a pc gaming rig way more than adequate for zwift. Well, after months of troubleshooting and many smart people going ‘huh’? it turns out it was the monitor. Double check your monitor settings. It was simple and all issues have completely disappeared. I hope this helps someone… ride on
Somewhere on the list of troubleshooting steps should be a clean Windows install and no installation of updated Nvidia drivers beyond what comes with Windows.
Wesley already has video screenshots disabled so that does not appear to be a factor.
Hi Paul, it was a setting on the monitor. It’s a 4k high res 120hz blah blah and the built in hisense software felt the need to be involved.
Yes I should have clarified I am talking about the two people above who are still working through it. One did an in-place upgrade and the other did a repair. They should look into your suggestion as well.
Update from today, it lasted 107 minutes before I got off with no issue.
Note: Since the issue started I have not been running Discord or OBS.
Today I disabled “Scroll Inactive Windows”, closed Chrome, and what I likely attribute the big change to is set Zwift to Full-Screen and closed Borderless Gaming.
I typically run Zwift in Windowed mode for better OBS Streaming with Borderless Gaming setting it to Borderless full-screen. Google Gemini suggested this was causing blocking with DWM and going to native full-screen may help.
My next ride I will try to keep Chrome open.