I updated to latest driver (23/12/2020 if memory serves) following a request from Zwift to try that first. Same result. Same error messages.
I have been having similar crashing, probably about once per hour of riding. 11th gen i5 with Iris Xe integrated graphics. Same windows hardware error for a graphics pagefault when Zwift crashes.
My assessment is that there is either a bug in Zwift or there is a problem in the Intel graphics driver and Zwift doesnât have a workaround (and the december update triggers this issue more often).
I typically get about 70fps average and about 50fps minimum, with about 70% GPU load, so on the basic setting, this does not appear to be a performance issue.
Has anyone gotten a response from support as to whether they have recreated this on their end, or have even tried to?
Josh
Same story: error 4101 âDisplay driver igfxn stopped responding and has successfully recovered.â, followed by Zwift not responding.
Maybe (just maybe) Zwift was better in handling display driver recovery before last update, so the issue was always there, but wasnât so visible.
Same here.
Here is the frustrating part.
After the crash on my 4 month old I5 laption with Intel UHD, I used my wifeâs 2 year old laptop with a driver from 2018 for an hour and a half. No lag, no crashes.
Out of curiosity and frustration I checker her PC display settings and driversâŚ1366X768 resolution on an Intel 620 GPU. Driver date was 11/10/2018. Driver version was 24.20.100.6344.
I hope the above helps someone. I got rid of the i5 and went with a gaming laptop with a powerful dedicated Nvidia GPU. No more intergrated GPUs for gaming or virtual software.
If you do change something based on the above, post it up. I would love to see if it makes a difference to someone else.
Hi everyone. Yesterday I did some simple things like reset the router, restart the computer, uninstall and reinstall Zwift. The not so simple (for me) thing I did was uninstall and reinstall graphics drivers (I donât even know what that means). I believe I have a built in graphics card.
This seems to have been successful. Last night I opened Zwift and just cycled a couple hundred metres and left my Avatar there. Over 3 hours later, Zwift was still running.
Today I cycled on Zwift for over 2 hours with no crashing and my ride was saved in Zwift, and appears in Garmin and Strava. So far so good for me, but I really feel for those of you who canât fix the crashing, it is so frustrating, especially if like me you arenât IT knowledgeable.
Hi all,
So Iâm glad I came across this thread as this has been frustrating me for the last 2weeks especially as I specifically bought a new Windows Surface Laptop Go with plenty of beans to run the Zwift App (or so I hope). In fear that I received a dodgy new laptop I had Windows Support run a health check, update the drivers and perform a clean boot of which all seemed present and correct. Iâve done a uninstall and reinstall of Zwift on 3 occasions too but still 4 out of 10 rides have crashed with the app not responding.
Therefore may I kindly ask that some take a look at my âZwiftalizedâ log from todays crashed ride to help point me in the direction of the issue. I am new to the indoor trainer world, plus I have a new internet provider/router so I would be extremely grateful if you can help me get an understanding of where the problem lies. Is it trainer hardware (Wahoo Kickr), laptop/graphics, internet network, Bluetooth connection or just an issue with Zwift itself which I guess would put me at ease with my current investment in hardware, but still not get me on the road to Zwifting!
Thanks in advance, Luke
Log errors from NotePad:
[17:58:09] NETCLIENT:[INFO] World clock offset updated from +1638410999ms to +1638410998ms (-1ms)
[17:58:12] BLE : Crank power 3sec timeout
[17:58:13] BLE : Crank power 3sec timeout
[17:58:14] BLE : Crank power 3sec timeout
[17:58:15] BLE : Crank power 3sec timeout
[17:58:16] BLE : Crank power 3sec timeout
[17:58:17] BLE : Crank power 3sec timeout
[17:58:18] BLE : Crank power 3sec timeout
[17:58:24] NETCLIENT:[WARN] UDP connection timeout (1 so far), reconnection attempt 1
[17:58:24] NETCLIENT:[INFO] Connecting to UDP serverâŚ
[17:58:34] NETCLIENT:[WARN] UDP connection timeout (2 so far), reconnection attempt 2
[17:58:34] NETCLIENT:[INFO] Connecting to UDP serverâŚ
[17:58:44] NETCLIENT:[WARN] UDP connection timeout (3 so far), reconnection attempt 3
[17:58:44] NETCLIENT:[INFO] Connecting to UDP serverâŚ
Please see Zwiftalizer screenshots too.
Zwift logs are most likely a red herring: app stopped responding, thus all those timeouts. The correct and slightly more involved way to look at what happened is described in the article called âSending Crash Logs to Supportâ (stupid forum doesnât let me insert any link, even to the Zwiftâs own pages.
The âConnecting to UDP serverâ is a repeating theme. It looks to me like Zwift seems to be susceptible to GPU resets during this process. It would help if you looked at your Windows event log* and show us what was reported prior to the crash. Could you also please indicate the GPU your laptop has (I suspect it is Intel Iris, but can you please confirm).
*Use you favorite search engine to find âZwift send crash logâ
Great point - and super helpful. Iâve been chasing down BLE potential causes cause every time I get the Crank Power Timeout errorâŚdidnât think about that being a consequence rather than a cause.
So maybe Iâm now back in the graphics drivers boat like the others.
Itâs just so weird how that happens. Like how can I ride for two hours fine and then all of a sudden freeze. What technically with respect to a hardware driver is happening to cause the freeze after so much time?
Iâm afraid to uninstall the graphics driver for fear it wonât be there when I reboot - and thus no screenâŚ
Hello,
So I was using zwift with a brand new Asus vivobook with an integrated intel GPU. Zwift stopped responding each time I used it.
I took a 15 year old hand me down Lenovo thinkpad laptop and installed zwift. I started a central park ride over two hours ago and zwift is still running. One caveat: Iâm not actually riding but my avatar is on the side of the road (rest day today).
Thomas, thanks for posting this, it supports my theory that this is not about GPU processing power but rather a specific issue between a set of Intel GPUs and Zwift.
Hi Zack, fear not when uninstalling / reinstalling windows has a built in gpu to navigate through windows etc. It is safe to uninstall/reinstall without risking no monitor. Use the manufacturers software to ensure a smooth transition. Hopefully this solves your issue.
Agree with Erwin on this. Got your log for it or error code?
A few options: Notwithstanding some issues Apple TV sounds quite good as are iPads. Both not very hi detail. If you are prepared to tinker a bit a used PC with a fast single thread performance CPU ( anything from 3rd gen I3 onwards) available on eBay in the UK from < ÂŁ100 plus a used, half decent GPU (I got a GTX750Ti for ÂŁ65). Ideally SSD (ÂŁ16) and 8GB (ÂŁ35) in the PC though I think youâd get away with 4GB. I got OK ish FPS with a very old i7-870 and the card above (8GB) and Zwift selected High profile. I was able to improve FPS by adjusting the config file. But beware, going down this route can lead to much googling and endless upgrades (I spotted a cheap nearly new GTX 1050 Ti and now use that
As little as 2GB RAM maintains Zwift performance, but you need 6GB or greater to avoid the game providing low quality textures automatically. They look awful.
Thank you for the response Erwin, the GPU is âIntel(R) UHD Graphicsâ (I hope Iâm looking at the correct thing).
The text on the Error Event is as follows;
The description for Event ID 1002 from source Application Hang cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
*The following information was included with the event: *
ZwiftApp.exe
0.0.0.0
2db8
01d6e5e1d5e3aa40
7
C:\Program Files (x86)\Zwift\ZwiftApp.exe
5f46485e-95cb-497a-bb95-6116a83d4f1d
Unknown
Element not found
The text on the Display Warning Prior is;
The description for Event ID 4101 from source Display cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
*The following information was included with the event: *
igfxn
Element not found
Hi all. Unfortunately Zwift crashed on me today. Had been fine, completed TDZ stage 2, then went to Watopia for a warm down, 5k in and it crashed. The ride on Zwift shows it was 4k long, and when I click, it wonât open. Ride doesnât show in Garmin or Strava, when I try to upload it to those it says on Strava: âThe upload appears to be malformed and we are unable to process it.â, and on Garmin: âWe donât support the file type you tried to import.â.
Could someone please tell me how to find Windows crash log and Iâll see if I can post it here?
Hit the Windows key and type event viewer.
Hi
I think I found this:
âDisplay driver igfxn stopped responding and has successfully recovered.â
and this:
âThe application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-3KJ48PO\clurr SID (S-1-5-21-3291581635-2615439880-3479457894-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.â
|||- Provider
[ Name ] Microsoft-Windows-DistributedCOM
[ Guid ] {1B562E86-B7AA-4131-BADC-B6F3A001407E}
[ EventSourceName ] DCOM|
| â | â |
|||- EventID 10016
[ Qualifiers ] 0|
| â | â |
Version 0
Level 3
Task 0
Opcode 0
Keywords 0x8080000000000000
|||- TimeCreated
[ SystemTime ] 2021-01-09T11:11:35.617216500Z|
| â | â |
EventRecordID 38095
|||- Correlation
[ ActivityID ] {358dcadc-5e1d-46db-a0f5-48f52c154646}|
| â | â |
|||- Execution
[ ProcessID ] 1196
[ ThreadID ] 10440|
| â | â |
Channel System
Computer DESKTOP-3KJ48PO
|||- Security
[ UserID ] S-1-5-21-3291581635-2615439880-3479457894-1001|
| â | â |
- EventData
param1 application-specific
param2 Local
param3 Activation
param4 {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
param5 {15C20B67-12E7-4BB6-92BB-7AFF07997402}
param6 DESKTOP-3KJ48PO
param7 clurr
param8 S-1-5-21-3291581635-2615439880-3479457894-1001
param9 LocalHost (Using LRPC)
param10 Unavailable
param11 Unavailable
Makes no sense to me!
Alan you can use fitfiletools to fix corrupted fitfiles. Download from Zwif (using the gear icon when viewing your activity and uplaoad to fitfiletools. You can the manually import into Strava.