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 possible, I had the update too. But I doubt it causing issues with dx12 other than in Monster Hunter World. I can see this issue and error shows from time to time and so far couldn't find any solution to this, I hope steam community will help but if not I'll give up.
Didn't have any issues with Elden Ring, Valorant or Cyberpunk, I played few indie games but they were short, but didn't trigger any issue with dx12 or anything graphic related. Those are only few games that I played for more than 2-3 hours in single session and didn't trigger anything so it's clearly specific to Monster Hunter
This will assure that old drivers residue that most likely caused this error in this one game (some people suggested changing gpu which was insane, and some did it which was even more crazy to me)
To those who stumbled on that old thread here on steam with weird people just know your gpu is not in any way defective if it's has issue in only one specific game and no issues outside that.
Hope this solves your problem as it most likely solved mine (I've played for 6-10 hrs yesterday and had 0 crashes and errors which is something but will test few more days to 100% confirm that)