Information:
OS: Windows 10 1909 (up to date)
CPU: i7-1065g7
RAM: 16gb
GPU: Integrated Iris Plus Graphics (Driver: 27.20.100.8476, also tried several older versions)
Network: Tried WiFi, Ethernet and tethered to 4g mobile. (all still causes freezes)
Zwift version: 1.0.54377(also crashed on july version, but not prior to june)
I have tried going Bluetooth only, Ant+ only and a combination of both.
In all cases zwift companion is running.
Message from event viewer:
" Display Driver Igfx Has Stopped Responding and Has Successfully Recovered"
message from zwift log (all looks the same):
'[17:56:43] NETCLIENT:[WARN] UDP connection timeout (1 so far), reconnection attempt â and so on.
I donât believe the network is the issue since the Event viewer message always appears about 10-15 seconds before not being able to re-establishing connection to the udp server. I have put it through zwiftalizer[dot]com and the only warnings/errors it picks up is the udp error and failing to nslookup on âapi[dot]segment[dot]ioâ as Iâm running pi-hole (this should not be the cause of the issue as iâve got it to freeze while tethered to 4g running 1.1.1.1 dns server as well)
Sometimes it crashes after over an hour sometimes it crashes within 10 minutes. it has crashed on NY Map, Watopia, Yorkshire maps. It has happened within a workout and during freeride.
Chuck your log file into zwiftalizer.com and show the results (when it crashes). Network issues normally have other symptoms but the analysis may highlight some anomalies that the guruâs here can assist with diagnosing.
Thanks for that Dean, the network errors would be:
[19:09:18] NETCLIENT:[ERROR] Curl error: [6] âCouldnât resolve host nameâ for: POST h t t p s://api[dot]segment[dot]io/v1/track
[19:09:18] NETCLIENT:[ERROR] Failed to send telemetry
One thing you could try if you havent done so yet is to disable pi-hole for a bit (and anything else you may have running). Also your Win10 version could be bumped up to 2004 or whatever it is thats been out for a bit but thats just an fyi. Unlikely to make a difference.
Hard to know what the root cause as I certainly expected to see a flood of errors pointing to network, ANT or BT. UDP packet errors arent usually a big deal, and they are designed to be connectionless to tolerate failures plus the volume seems the volume seems low, and could well be your pi-hole.
And based on the Eventviewer timing, I would tend to agree with you that its not network. But what the root cause of the crashes is I really dont know.
And I dont want to tell you how to suck eggs as you seem fairly informed on these things but I did a search of interweb for that error and a lot of those issues are resolved by drivers - the one common fix was deleting the current driver, rebooting and allowing windows to use its default one before loading up the current. Apologies if this is a bit of an insult!
Might have to see if any of the pc guruâs out there can jump on this and help.
No insult taken at all! youâve been super helpful with all this.
I am unable to update to the Windows 10 update 2004 as Microsoft still has issues that they are resolving that affects my device (ht tps://aka .ms/wrh-2004).
I have tried almost every driver from sep/2019 up to the beta version that was released on 27/08/2020 for my iGPU.
I have also tried all the different resolutions and fullscreen vs windowed to no avail. I have another device I could try, but itâll require some setting up as it is running on linux at the moment.
I have a similar issue with same symptoms and Windows 10 x64 i5 with latest drivers and Iris Plus GPU also. It happens, or it doesnât, sometimes 10 minutes, sometimes 1 hour. The event viewer shows this every time right before it happens:
âDisplay driver igfxn stopped responding and has successfully recovered.â
but Zwift canât recover. Currently have a ticket open. Found a post on answers. microsoft. com (wonât let me post the link) as well where 2 people have the same issue (no solution).
Could you explain more Paolo? I donât understand if youâre saying todayâs update resolved it or not.
As for gpu power / drivers comment from Milan: yes I manually updated to the latest version. Itâs integrated graphics card in laptop so I donât think adding an external card is an option for me. Windows says it recovered (it didnât hang) but zwift does not. I have it on the basic settings. Sometimes it doesnât happen at all so your lack of power argument doesnât seem correct.
The error message "âDisplay driver igfxn stopped responding and has successfully recovered.â can be a software (driver) problem, for sure. But when reading the postings it looks like Zwift need more GPU power. I am not an expert for gaming, no idea how Intel handles Open GL (that is why Nvidia cards are better for Zwifting).
Does Intel say the GPU âcan easily run Zwiftâ?
Of course they will not blame their own product⌠I read the article, looked once more the benchmarks - I do not believe it is Zwift problem.
