Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It's not hugely annoying but I hope it gets fixed.
The game has not crashed during gameplay in 12 hours.
Hope to see it fixed.
Driver issue ?
I have done the usual troubleshooting steps including clean-installing drivers which I always do with DDU.
I have run DISM and SFC already ,my windows install is healthy and so is my hardware.
I am already running the latest chipset drivers and GPU drivers.
I appreciate your answer but I know how to maintain a clean and lean system.
I have looked into the crash logs and the same NVIDIA module always comes up : nvwgf2um.
This would indicate a driver issue, I have reached out to Ballistic Moon support just in case. I have received no answer from them.
Have you contacted NVIDIA about this issue ?
The form takes a few minutes to fill. https://docs.google.com/forms/d/e/1FAIpQLSewHJk1xP-C5elLBRCDLTLpNQZ9eiefrdZmUGP9hMCN6gKssA/viewform
That's the only way to get this fixed.
Why NVIDIA ? Because in my case (and I suspect yours) the faulty module is nvwgf2umx.
Locate the crash log and look it up with WinDBG.
I have the 566.14 installed.
I'm just a detail oriented person.
To anyone who wants a workaround fix for this issue:
The problem within the drivers that is corrupting internal modules is the use of AMD / Nvidia exclusive technologies such as DLSS, Radeon Super Resolution, Radeon Chill or Boost.
It is recommended to run most graphics settings at stock and turn off any overclocking as well as power management features, Zero RPM if you use AMD.
It's also a good idea to turn off PCI-e link state power management in windows if you haven't already done so.
Universal settings like antialiasing, anisotropic filtering, vsync and triple buffering are safe to use until the issue is fixed.
I promise this workaround will work to stop the issue until such a time you can reuse advanced graphics settings and overclock again.
The error remains.