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
Hope somebody has ideas on a fix. Kinda nice to see that im not the only one experiencing this..
* Would like to include in notes that I am in SEA.. This update came a day or two ago so its fairly new. Thought maybe players from Middle East had experienced the same when it launched and has a fix for this
Or u can try to play on virtual machine...
That's good to know.. I thought I was the only one since all my friends at steam have been playing dust 2 as well as public lobbies spamming the dust2 map. Having bootcamped windows also made me think that the new map was not compatible with my current setup..
im running a i9-7920X with GTX 1080 TI and get "WHEA_UNCORRECTABLE_ERROR" bluescreen while loading dust2 or max. 5 seconds in the game. All other games and csgo maps work.
Nice specs dude! I assume you run 64 bit windows? Some are saying its because of the 32bit OS that Im running..
pls help
When I play solo queue new DE_DUST2 working fine,but when I play with my friends in lobby MatchMaking it crashes upper mid from T Spawn, LONG Doors,and all tunnels ( lower,upper,outside).
Any fix please?
PS: I'm using Windows 10 x86.
Not sure how to fix this, but id say verify your game files, if not.. Maybe its the same issue I was having and we just need to wait for patch. (I formatted my pc making it x64 and now the new dust 2 works fine). Its probably because you run 32 bit.. Try upgrading to 64?
Yes it worked after i installed a 64 bit system ~