Random Number GodsRNG · Enemy Territory · Battlefield · D&D
Friday BF64 + Sunday D&D

Check the calendar. ET pubs running the new Frostbite rotation all week.

Game crash big error msg, how to fix it ?

Permalink Preview Print BF6
lolikovski
Rifleman
Members
21 posts 22 Oct 2021 joined
28 Jul 2026 at 08:29 #1

Dired function "Hang Detected in waitforFrameFences Timed out after 9000 ms. Waiting for Signallo: 127976. Last Signaled Fence Value: 127977. Unsignaled Fences:
[Graphics" stopped at 1279751, "Taled with DG_ERROR_DEVICE_HUNG The GPU will not respond to more commands] GPU "NVIDIA GeForce RIX S090", Driver
61074.
Dride/InT Code PackagesiRenderCore2RenderCore2.devs
ource platform Dx12 SubmissionManagerDx12 opThu error is usually caused by the graphics driver crashing; try installing the latest drivers.

lolikovski - Map votes
Frostbite supremacy.

nothingeverhppens
Rifleman
Members
14 posts 9 May 2025 joined
29 Jul 2026 at 16:40 #2

Dired function "Hang Detected in waitforFrameFences Timed out after 9000 ms. Waiting for Signallo: 127976. Last Signaled Fence Value: 127977. Unsignaled Fences:
[Graphics" stopped at 1279751, "Taled with DG_ERROR_DEVICE_HUNG The GPU will not respond to more commands] GPU "NVIDIA GeForce RIX S090", Driver
61074.
Dride/InT Code PackagesiRenderCore2RenderCore2.devs
ource platform Dx12 SubmissionManagerDx12 opThu error is usually caused by the graphics driver crashing; try installing the latest drivers.
Hey there,
Sorry to hear you're running into this.
The error message indicates a GPU hang (DXGI_ERROR_DEVICE_HUNG), which is commonly related to the graphics driver, GPU stability, or software interfering with DirectX 12.
A few things that would be helpful to know:
When did this start? Was it after the latest game update or a recent NVIDIA driver update?
Does the crash happen consistently, or only in certain maps or game modes?
Are you running any GPU overclock or undervolt?
In the meantime, you can also try:
Performing a clean installation of the latest NVIDIA driver (or rolling back to a previous driver version if the issue started after updating).
Verifying the game's files through Steam.
Disabling overlays (NVIDIA App, Steam, Discord, MSI Afterburner/RivaTuner, etc.) to see if the issue persists.
Performing a
Clean Boot
[support.microsoft.com]
to rule out software conflicts.

nothingeverhppens - Lurker
I read more than I post.

Sign in to reply.