Civ 6 Crashing on game launch, began ~ 4/19/2020

[TripleARay]

Hello all,

New to the forums as a poster, but as the title states since about 3 days ago my Civ has just started crashing. Went to bed one night after a saved Rome game, came back and tried to resume and it just CTD'd. New games or even the benchmark load from the main screen are doing the same thing with a slight tweak; it will launch the game and just hang at the load screen without ever showing the start game button (then crash).

I have reinstalled Civ, reinstalled Steam and Civ, updated my video card driver and nothing seems to be hitting the source of the problem. Log folder and DXDiag attached below. Any help would be appreciated, I need my one more turn fix!

 

[Browd]

Does it only happen with that particular save file? Can you start a new game, save that, and then reload that save?

 

[TripleARay]

Edited my original post - it happens on any game launch, new game, mods, all mods disabled; everything.

 

[Laurana Kanan]

What graphics driver version are you on? I recently had to roll my Nvidia driver back to 445.75 after updating to 445.87 because it was causing a similar issue. You could also try doing a complete uninstall/reinstall of your driver using DDU or similar utility. If that fails you could always try 2K Support.

 

[TripleARay]

I too am on 445.87, using a 2070 super. I will check into rolling it back and seeing how that affects it (although some of these issues did happen before I updated it); can't hurt to try! I will also check with 2k support. Thanks!

 

[Garrulous]

Try running DXSETUP. You can find it here if you're a Steam user: C:\Program Files (x86)\Steam\steamapps\common\Steamworks Shared\_CommonRedist\DirectX\Jun2010

 

[Laurana Kanan]

I'd try running the game in both DX11 & 12 API first to see if either works, before executing DXSETUP. However, since the Nvidia 445.87 driver was just released a few days ago, and according to the OPs dxdiag that is the version that is installed, leads me in that direction as a possible culprit as I had a similar, if not identical problem.