I’m being facetious. ![]()
So it’s not the Zwift Launcher. After updating to 1.1.5 I had Zwift crash on me twice in one ride.
A little background on this system, it basically only runs Zwift. I built the computer only for Zwift, so there’s basically nothing else running other than the stuff from the motherboard manufacture (ASUS) and standard Microsoft software.
But, I went a little midevil on this system last night and went through everything that a default Windows 10 install has running. I uninstalled a couple ASUS memory board apps having to do with USB, fans, and BIOS updates that isn’t needed (this motherboard is too old to get BIOS updates anymore). I also removed a few Windows apps and services (like photos, phone, indexing, etc.) which were running but not needed on this system. Not that there was really anything running before, but now it’s about the leanest a Windows 10 system can be. It’s really only running Windows Defender, which will be the next to go if it still doesn’t work.
So I’m doing a ride again tonight and we’ll see what happens.
FWIW I only uninstall OneDrive from a clean install of Win10, and toggle off the Xbox Game Bar. There should be no need to uninstall anything else. I don’t install any drivers (motherboard or otherwise), just let Windows Update deal with everything including the Nvidia driver and control panel app. Literally just set it going and wait. Only one that takes any manual effort whatsoever is the ANT+ driver and even that is only in Optional Updates so it’s like three extra clicks. In my opinion too many people focus on having bang up to date drivers (installed manually) for everything, when I have seen absolutely zero evidence that it makes any difference at all to Zwift. So I don’t bother.
I would suggest trying a clean install. If you have an SSD the entire thing including Zwift is well under an hour if you have half decent internet.
PS: where/when did it crash? World, circumstances etc.
Did you check event viewer (windows logs - applications) after the crash? Might have some useful info.
It’s showing a TDR error. Meaning whatever Zwift is sending to the graphics card is taking more than 2 seconds to render, which is an eternity on my 8GB 1070 video card. Same bug since this thread started, years ago.
No rhyme or reason to the crashes. Will crash 1 mile into a ride, then let me ride 15 miles. Will crash in different worlds, never in the same place. Will crash when I see no bikes on the road, or in a pack of 200 riders. Then, it will allow me to ride in a group ride with 300 people for 2 hours without a glitch. I can find no similarities to when it crashes, other than the graphics card locks up due to something Zwift is sending to the video card that I guess is taking longer than 2 seconds.
I changed the TDR limit to 60 seconds. That may allow me to notice the freeze, exit to Windows and return to Zwift to prevent a crash. But we’ll see on tonight’s ride in an hour.
OneDrive was already uninstalled on this computer and I killed the XBox Game Bar app last night when I when into berserker mode. I also only went down the graphics driver update route when I was already having problems. I have another Zwift trainer system setup right next to the computer having a problem (my wife’s trainer) and that computer has zero issues and has never froze or crashed. It has a lower-spec CPU and a GPU with only 1GB RAM. That power supply is also only a 250 watt while the one that’s crashing is a 80% 750 watt power supply.
Reinstalling Windows will probably be my next step. Although, I don’t have much faith that will fix anything.
I think you may be surprised. I’ve not had a TDR error once, ever. And this is with tons of crap faulty graphics cards that I’ve taken punts on. Since you’re getting it with multiple (presumably known good) cards, that suggests the driver or some other aspect of the OS isn’t right. But if nothing else, a clean install will rule out software.
PS: is your CPU overclocked? Irrespective of how long it’s worked just fine, they’ve messed about with some aspects of how the game tick works in recent months.
I’ve never had a TDR error on any system ever, except with Zwift, even with the same video cards. And nothing would surprise me at this point ![]()
Nothing is overclocked. I’ve also done stress tests of the CPU/RAM/GPU (Prime95 and FurMark) without issue.
Last night’s 1 hour ride was without issue after my rampage of Windows services being removed. I’m doing another ride in a couple hours and we’ll see how that goes.
Another ride tonight without a problem. I’ll keep an eye on it and report back. But at this point it seems there’s something on Windows 10 causing a conflict and Zwift crash. I’ll report back if I experience more issues, but for now it seems killing every service possible in Windows 10 helps.
Having the TDR error as well 4 times over the last week. This on a i7 CPU with NVidia GTX1070 graphics. System is dedicated for Zwift use and has been stable over the last 5-6 years Zwifting. Since one month Zwift crashes randomly exiting me to the Windows 11 desktop.
I think Zwift crashing started once I upgraded(?) to Windows 11. I updated NVidia drivers after tonights Zwift crash and will chage registry TDR value…
I’m also running a 1070 (same problem also happened on a 1060). Looking at other users with this problem, it seems most common on the 1070/1060 GPU.
With that said, I’ve disabled virtually everything running on this PC (as it’s only used for Zwift) and I haven’t had it crash in the last couple weeks. It did hang once, but I was able to do the Windows key/Zwift icon in the task bar trick and it returned to the game.
going through the Windows error logs all 4 crashes were NVidia OpenGL TDR.
Now looking into the other items from the error logs to see if I can find anything related or just try to clean up anything that appears in these logs. So far removed some McAfee True Key remainders (was not aware I ever installed this…).
Will update if measures so far improve Zwifts stability.
Just deleting apps didn’t help for me, I also needed to stop and force a manual start only of several unused Windows services. Also, be sure your video driver is just the driver, not the other crap like PhysicsX or overclocking. And when updating your video driver, be sure to check the clean install option so it totally removes all the old stuff.
thanks for the reply. I will keep trying to stop Zwift from crashing and hope for a result i.e. no more crashes. Will give an update in a few days ![]()
no luck so far. Removed all NVIDIA drivers. Reinstalled NVIDIA driver version 528.02 and reinstalled Zwift.
Thursdays 1hr Zwift ride without problem. Today 2hr in a Zwift ride same “nvlddmkm”, “NVIDIA OpenGLDriver” with “Application Error” from Zwift happened. Application error points at Zwift.exe as the faulty application and nvoglv64.dll as the faulty module…
After constantly struggling with freezes with my Surface Pro 8, I have now downgraded to Windows 10.
But when I try to install the igfx_win10_100.7985 driver, I get “your system does not meet the minimum requirements for this software”.
The Surface has a Intel Iris Xe Graphics chip and runs on i5-1135G7 processors.
Can I really not install the driver after all this effort - or is there some workaround?
You might get better support for this on the ZPCMR group on Facebook
could be. I solved my issue (at least I think so…) by swapping videocards between Zwift PC MSI GeForce GTX 1070 GAMING X 8G and my normal useage PC GTX1080. To me it seems either an issue with Zwift and this specific GTX1070 card or just my videocard being defect. Would prefer Zwift to look into this so sent them my logfiles.
Also signed up for the Facebook group ![]()
Hi,
I’ve managed to resolve the Intel 10th/11th Gen issues on my laptop.
I have a Lenovo V15 IIL laptop and was having the much publicised issues with running Zwift on the integrated Intel GPU, in my case Intel UHD. To be specific, the processor in my laptop is an Intel i5-1035G1. However, I do seem to have managed to resolve the issue.
I was having the game-freezing issue. It was very frustrating and really quite traumatic.
Having tried many of the other proposed solutions with no success, I upgraded to Windows 11, uninstalled the display adaptor driver in Device Manager, and used the Intel Driver and Support Assistant to install:
Intel® 6th-10th Gen Processor Graphics - Windows
Version: 31.0.101.2115
Release date: December 29, 2022
Since then I no longer have the crashes. I can see from other posts that people have followed this route and had no success, but it has worked for me and if just one person can follow in my wake and rid themselves of the heartbreak of having a pride-worthy effort up a steep climb stopped dead in its tracks by a spinning circle of doom then my work here will have been worthwhile.
Note: if you do upgrade to Windows 11 you cannot use the driver roll-back workaround that others have been successful with so I would strongly recommend trying that first.
Ride on,
Gav