![]() ![]() I'm posting this just in case anyone still looking for the possible solution or even just clues. If Nvidia’s monster vms have the issue too then there’s little we can do and that sucks. I could try running it in GeForceNow and seeing if that crashes in the same way. ![]() Other systems may have different results and I realize my story is a bit anecdotal. Since my PC is completely rebuilt and doesn’t have lots of leftover c distributables or lots of stuff running, it is handily above the system requirements, and has the issue with either renderer, we can’t conclude that DX12 is the culprit. I think I got two hours of buttery smooth Division deliciousness before it randomly froze in melee range of the last enemy at a control point. Worked well, and then I tried running DX12. The other night I disabled all integrations like cross play and voip and tried adjusting graphics a bit. Had multiple freezes with DX11 while answering another agent’s backup request. I have a completely new install with nothing but a selection of games and all the latest and greatest drivers, with a 1070 card. If nothing helps revert to an older Nvidia driver (466.xx). Or instead of that - some players have also said that enabling DX12 resolves the issue but keep in mind that the game can crash randomly with DX12 enabled so if you start getting crashes disable DX12 and revert the driver instead. īefore reverting to older driver you can try this: \_artifacting\_on\_nvidia/hc5b6ja?utm\_source=share
0 Comments
Leave a Reply. |