-I have done research on this problem and I have a theory on what is occurring. I have looked at multiple recent postings in the last few days. There are many similarities between users, but these are the main ones to keep in mind: 50 series gpus, dlss, frame caps, overclocking, v sync, DX12, and errors occuring in the main game menu.
-When using DirectX12, it utilizes the cpu as the main frame pacing system. The cpu tells the gpu when and how much to send. In Battlefield 2042, the cpu usage is higher than most games. When DX12 sends a message, it already has to pass through an extra system, the cpu, to reach the gpu. The extra cpu stress causes more delay and sudden bursts of commands.
-The 50 series gpus are beefy and have a high base clock with low voltage margins. Using overclock settings makes this even higher and margins even lower. Being high end cards, the usage is typically very low. Things like frame capping, dlss frame generation, OC, DX12 utilizing the cpu, and game menu states make the gpu usage even lower. When gpu usage is low the clocks, voltage, and vram are slowed and relaxed. A spike in demand causes the gpu to rapidly ramp up all systems throughput. This transition can introduce delay and instability, especially under overclocked conditions.
-The combination of delay between the cpu and gpu causes frames to arrive late. Systems that synchronize frames, like v sync, amplify the timing error. DX12 interprets this delay as a gpu non-response, triggering a DEVICE_HUNG error.
-In summary, systems that lower general gpu usage, increase cpu usage, and create stricter frame pacing can cause delay in the frames sent during high spikes. DX12 reads these delays as unresponsive behavior and causes the shutdown error.
-It is possible that this is an issue with the current graphics driver, 581.08. While I have not tested any other drivers, I have tested differences in settings using frame caps, dlss, and overclocking. All of these seem to increase the probability of the error occurring. It is important to note, the error does not happen every time. Opening the game and landing in the menu causes the highest occurrence, but it can also happen when sitting on the menu and landing on the menu post-game.
