Over the last week I've encountered countless game freezes, the exact behaviour can be seen in the video below.
https://www.youtube.com/watch?v=oT953F5jJ6g
(Credit to Denis Schumacher for capturing this)
The freeze can happen at any point anywhere from 10-30 minutes of gameplay, before the 22nd of March this was about 1-2 hours.
After troubleshooting the issue I was able to reproduce the problem on a fresh Windows 10 build with the latest windows updates, latest Nvidia drivers and only The Division 2.
Checking the application event logs after the freeze I see the following.
1. 10-15 minutes before the freeze there is a windows error report created for "thedivision2.exe" - I believe the event name signifies that the process is consuming a lot of memory.
Fault bucket 1418575334245378234, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0
Problem signature:
P1: TheDivision2.exe
2. 10-15 minutes later when the freeze occurs a windows error report is created signifying a hardware failure, I suspect this is related to the GPU due to what I found in point 3.
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1: 141
3. At the same time in the system event logs we see a corresponding event which shows the nvidia display driver stop responding and then recover. I think this is related to Windows timeout detection and recovery, see - http://developer.download.nvidia.com...n_Recovery.htm
Log Name: System
Source: Display
Event ID: 4101
Display driver nvlddmkm stopped responding and has successfully recovered.
Based on this evidence I believe there is a memory leak occurring which leads to the nvidia driver to stop responding resulting in the freeze. I would be interested to know whether other people who have experience this have the same events raised.
I tried using Nvidia Nsight to gather more logging information however the process doesn't like being injected into by 3rd party software and refuses to launch, presumably in relation to Anticheat.
I'm trying my best to figure this one out, I'm more than happy to help assist in anyway possible.
UPDATE:
Basing my theory that this is a memory issue I spent several more hours testing. Below are my findings.
TEST 1:
I set my resolution in windows to 1920x1080 (my native is 3440x1440)
Disabled Full Screen Optimisations for "thedivision2.exe"
Launched the Division 2 and set the following.
Video:
Windowed Mode (Fullscreen)
Enabled Reduced Lag Latency - Yes
Enable Direct X12 Render - No
Graphics:
Resolution Scale - 75%
Then basically put every setting which consumes VRAM to as low as possible, most notable the following.
Particle Detail - Low
Antisotroping Filtering - x1
Ambient Occlusion - Low
Object Detail - 0
Extra Streaming Distance - 0
Projected Texture Resolution - 128
High Resolution Sky Textures - Off
Texture Quality - Low
RESULT:
After making these changes I have been able to play the game for over an hour without any problems, completing a mission and some side stuff, usually the game will freeze part way into a mission.
TEST 2:
I set my resolution in windows back to native 3440x1440
Launched the Division 2 and set the following.
Video:
Windowed Mode (Fullscreen)
Enabled Reduced Lag Latency - Yes
Enable Direct X12 Render - No
Graphics:
Used the Ultra pre-set of settings.
RESULT:
After making these changes I was still able to play the game for over an hour, completing missions etc... with no freeze.
CONCLUSION:
The only thing which I hadn't changed from my normal setup when the problem occurred to these tests was "Full Screen Optimisations". I disabled this and re-ran TEST 2, after 20 minutes the game froze with the same errors in the event logs.
I still need to test this for longer periods of time however "Full Screen Optimisations" might be causing problems on larger resolutions. I'd be interested to know if disabling this has a positive effect for anyone else. To disable "Full Screen Optimisations" simply go to the location of The Division 2 executable, right click it and go to properties, then compatibility, click the option to disable full screen optimisations.
EDIT:
Further testing showed disabling "Full Screen Optimisations" made no difference.
No problem. If you need any more information let me know, I'm happy to help anyway I can.Originally Posted by UbiSailorScout Go to original post
Unfortunately the page file change doesn't work for me, in my case I don't think physical memory is the issue, but more so the video memory on my GPU, which isn't affected by the page file. They only way I can get the freezing to stop is by dropping my resolution to 1080p thus reducing the load on the GPU, it also affects me less on DX11 as the GPU utilization is not as good, DX12 is far more GPU intensive. I find when the GPU is under load it may become unresponsive, when this happens the windows timeout detection and recovery (TDR) feature detects this and resets the GPU leading to the freeze. By default the GPU only has to be unresponsive for 2 seconds and the TDR feature will kick in and reset the GPU, I've increased this timeout to 20 seconds and will test shortly.