So I'm one of the folks whose game has been crashing nearly daily since TU12.1 (increased to daily and during the character selection screen after the first Uplay update that they fixed).
The following is not a crashproof fix, but I've been able to play for hours at a time and a crash every 2-3 days followed by more game time.
I also can't say it'll work for everyone, but if you've noticed oddities when modifying settings in the game (long freezes before the game does NOT apply the settings and the *.cfg files often show nothing changed even after game says settings were applied), this might work for you.
After Windows KB5001330 was re-introduced (it might've not been called that originally, but the basic cause affecting PC gaming existed in a prior Windows Update too), I uninstalled it. Someone posted that you need a restore point to do it, but that is incorrect. I used this method: https://www.windowscentral.com/how-u...ues-windows-10 .
After uninstalling it, I deleted the contents of the shadercache in the game folder and deleted all of the settings files in \Documents\my games\Tom Clancy's The Division 2:
*graphic settings.cfg
*loading tips.cfg
*persistent settings.cfg
*settings.cfg
*state.cfg
*ui config.cfg
(if you don't want to delete them permanently, you can rename each one to *.xxx (instead of *.cfg)
Finally, I verified game files; no problems found.
After those steps, I started the game. Note: do not use any game / video optimisation tools. So, don't use Nvidia, AMD or any other video / game settings optimisation tools.
Once I got to character selection screen, I kept the default settings for Audio, Video, and Graphics. I did remap all of my keys to what I wanted again.
Note that the game used DX11 as the default in my case; I don't know if this is standard or if it's DX12 for other folks; whatever it is, don't adjust it from the "default" setting.
Then I started into the gameworld.
No crash; was able to play for four hours then I quit because I wanted to do (not crashed).
The next day, no problems again.
Fourth day, the game froze but when I checked Task Manager, it was showing "not responding" so I killed the game then immediately started the game again. The game acted as if I had been disconnected and I did not reappear at the closest safehouse, but instead on top of a storage container where I had been doing an air drop open-world mission. Previously when the game would crash (silent crash, freeze or crash with report to Ubisoft), I would spawn at the closest safehouse.
After that crash, I've had one crash every 2-3 days, but the next time, no crash and able to play for several hours (six hours has been the longest, and I logged out after that... not because game crashed).
Best regards.
PS: For Massive, the biggest change I've found is that the game's shadercache size is tiny. Prior to trying this method, it contained as much as 58,000KB. With this method, it only contains 8,000KB. Also, the game's two percentage "metres" each take 10-15 seconds at longest, not hanging on 9% for ten seconds, and in-game world loading doesn't hang or stutter the game much or frequently.
1 people found this helpful