Game: GPU hang (no submission finishes for 30 s) right after the game window loses focus, RX 9070 XT, Windows #316

New issue

Open

opened 2026-11-13 22:15:21 +00:00 by eazyves · 0 comments

eazyves commented

2026-11-13 22:15:21 +00:00

Longshot version

v3.0.0-rc.3 (source cb01b5a3)

Channel

Release candidate

What kind of problem

Crash, freeze or black screen

What happened

Three times in one evening the game froze and then closed with vk: FATAL: the GPU hung: no submission finished in 30 s, and the driver never reported the device lost. Every time it happened a few seconds after I switched from the game (fullscreen) to a browser window. Before that the game ran normally at 60 fps.

All three hangs show the same sequence in the log:

hid: game window not in front (foreground window: ... "MozillaWindowClass" / "Chrome_WidgetWin_1")
vk: slow present: ~200 ms (second hang)
vk: a capture's wait for write-back ... timed out
vk: slow submit: ~251 ms: memory sync ~251 [... capture ~251 ...]
vk: the GPU has finished nothing for 10 s → 30 s → GPU hang → device fault: (empty) → FATAL

Second hang (20:42 local, log attached):

hid: game window not in front (foreground window: process 18648, class "MozillaWindowClass")
vk: slow present: 200.8 ms:
vi: 151188 frames presented (57.7 fps over the last 5.1 s, interval 1)
vk: a capture's wait for write-back 1058570 timed out (done 1058564)
vk: slow submit: 251.6 ms: memory sync 251.5 [memory sync: maps 0.0 (lock waits 0.0), capture 251.4, collect 0.1]
vk: the GPU has finished nothing for 10 s: the timeline at 1058564, 1058577 sent (RX_VK_GPU_HANG_SEC=30)
vk: the GPU has finished nothing for 30 s: the timeline at 1058564, 1058577 sent (RX_VK_GPU_HANG_SEC=30)
vk: GPU hang: the timeline at 1058564, 1058577 sent
vk: device lost: reading the fault info (RX_VK_CHECKPOINTS=1 for markers)
vk: device fault:
vk: FATAL: the GPU hung: no submission finished in 30 s, and the driver never reported the device lost

First hang (19:31 local; that log has since been rotated away, these lines were copied from it before):

hid: game window not in front (foreground window: process 12552, class "Chrome_WidgetWin_1")
vk: a capture's wait for write-back 303775 timed out (done 303769)
vk: slow submit: 251.2 ms: memory sync 251.2 [memory sync: maps 0.0 (lock waits 0.0), capture 250.6, collect 0.6]
vk: the GPU has finished nothing for 10 s: the timeline at 303769, 303782 sent (RX_VK_GPU_HANG_SEC=30)
vk: the GPU has finished nothing for 30 s: the timeline at 303769, 303782 sent (RX_VK_GPU_HANG_SEC=30)
vk: GPU hang: the timeline at 303769, 303782 sent
vk: device fault:
vk: FATAL: the GPU hung: no submission finished in 30 s, and the driver never reported the device lost

Third hang (about 21:08 local, log attached; the controller was lying still on the table, so the motion-debug lines show a pad at rest):

hid: game window not in front (foreground window: process 18316, class "Chrome_WidgetWin_1")
vk: a capture's wait for write-back 594433 timed out (done 594427)
vk: slow submit: 250.0 ms: memory sync 250.0 [memory sync: maps 0.0 (lock waits 0.0), capture 249.9, collect 0.1]
vk: the GPU has finished nothing for 10 s: the timeline at 594427, 594440 sent (RX_VK_GPU_HANG_SEC=30)
vk: the GPU has finished nothing for 30 s: the timeline at 594427, 594440 sent (RX_VK_GPU_HANG_SEC=30)
vk: GPU hang: the timeline at 594427, 594440 sent
vk: device fault:
vk: FATAL: the GPU hung: no submission finished in 30 s, and the driver never reported the device lost

Earlier focus switches in the same sessions did not hang (in the third session 3 switches were fine, the 4th hung), so it doesn't happen on every switch. Windows logged no display driver reset (no TDR event). Note: during the first hang the CPU had an unstable undervolt (Windows logged corrected WHEA cache errors). I reverted it to stock before the second hang, and no WHEA errors were logged after that, so the second hang happened on a stable system.

I can run again with RX_VK_CHECKPOINTS=1 if markers would help.

Where in the game

Dodongo's Cavern (the second dungeon), playing normally. The hangs don't seem tied to a spot: each came right after I switched from the game to the browser.

How often

Sometimes (3 hangs in about 2 hours of play, all right after switching to another window)

Graphics card and driver version

AMD Radeon RX 9070 XT, AMD Software 26.20.15.07 (driver 32.0.32015.7029; Vulkan reports driver 0x8001a0)

CPU, RAM and operating system

Ryzen 7 5800X3D (stock), 32 GB, Windows 11 Pro 25H2 (build 26200)

Changes from the defaults

Upscaler AMD FSR 4, Render resolution Native (FSR 4 Native AA) for the second hang; FSR 4 at Render resolution Auto (2580x1080 → 3440x1440) for the first
Output resolution 2560x1440 with Aspect ratio Monitor's shape (picture 3440x1440)
Frame generation Auto (144 Hz monitor: "a frame for each of the display's refreshes, up to 4 a game frame")
Fullscreen on, V-Sync Auto (swapchain immediate)
Quality preset Custom, Ultrawide menus off, FPS counter on, mouse sensitivity 60, motion sensitivity 300/200
Three monitors: the game on a 3440x1440 144 Hz monitor; the primary display is a 4K 60 Hz TV; a third one is 1080p
Started from Steam as a non-Steam game (Steam overlay possible); Steam Input on for the first hang, off for the second
No longshot_env.txt for the first two hangs; HOS_MOTION_DEBUG=1 for the third (only extra logging); no ReShade or other injector

longshot_log.txt

longshot_log_hang_2042.zip (second hang) and longshot_log_hang_3.zip (third hang); the Windows user name in one path is replaced with USER

Before you send it

The problem is still there on the newest release or nightly. (rc.3 is the newest release candidate; nightly-80 crashes on startup, #261)
I searched the open issues for it. (nothing about hangs after a focus change; #130 is a device lost at the VRAM limit, a different case)
I'm not attaching game files, keys, the game's executable, its .bin caches or saves.

Prepared with help from Claude; the facts and logs are from my PC.

### Longshot version v3.0.0-rc.3 (source cb01b5a3) ### Channel Release candidate ### What kind of problem Crash, freeze or black screen ### What happened Three times in one evening the game froze and then closed with `vk: FATAL: the GPU hung: no submission finished in 30 s, and the driver never reported the device lost`. Every time it happened a few seconds after I switched from the game (fullscreen) to a browser window. Before that the game ran normally at 60 fps. All three hangs show the same sequence in the log: 1. `hid: game window not in front (foreground window: ... "MozillaWindowClass" / "Chrome_WidgetWin_1")` 2. `vk: slow present: ~200 ms` (second hang) 3. `vk: a capture's wait for write-back ... timed out` 4. `vk: slow submit: ~251 ms: memory sync ~251 [... capture ~251 ...]` 5. `vk: the GPU has finished nothing for 10 s` → `30 s` → `GPU hang` → `device fault:` (empty) → `FATAL` Second hang (20:42 local, log attached): ``` hid: game window not in front (foreground window: process 18648, class "MozillaWindowClass") vk: slow present: 200.8 ms: vi: 151188 frames presented (57.7 fps over the last 5.1 s, interval 1) vk: a capture's wait for write-back 1058570 timed out (done 1058564) vk: slow submit: 251.6 ms: memory sync 251.5 [memory sync: maps 0.0 (lock waits 0.0), capture 251.4, collect 0.1] vk: the GPU has finished nothing for 10 s: the timeline at 1058564, 1058577 sent (RX_VK_GPU_HANG_SEC=30) vk: the GPU has finished nothing for 30 s: the timeline at 1058564, 1058577 sent (RX_VK_GPU_HANG_SEC=30) vk: GPU hang: the timeline at 1058564, 1058577 sent vk: device lost: reading the fault info (RX_VK_CHECKPOINTS=1 for markers) vk: device fault: vk: FATAL: the GPU hung: no submission finished in 30 s, and the driver never reported the device lost ``` First hang (19:31 local; that log has since been rotated away, these lines were copied from it before): ``` hid: game window not in front (foreground window: process 12552, class "Chrome_WidgetWin_1") vk: a capture's wait for write-back 303775 timed out (done 303769) vk: slow submit: 251.2 ms: memory sync 251.2 [memory sync: maps 0.0 (lock waits 0.0), capture 250.6, collect 0.6] vk: the GPU has finished nothing for 10 s: the timeline at 303769, 303782 sent (RX_VK_GPU_HANG_SEC=30) vk: the GPU has finished nothing for 30 s: the timeline at 303769, 303782 sent (RX_VK_GPU_HANG_SEC=30) vk: GPU hang: the timeline at 303769, 303782 sent vk: device fault: vk: FATAL: the GPU hung: no submission finished in 30 s, and the driver never reported the device lost ``` Third hang (about 21:08 local, log attached; the controller was lying still on the table, so the motion-debug lines show a pad at rest): ``` hid: game window not in front (foreground window: process 18316, class "Chrome_WidgetWin_1") vk: a capture's wait for write-back 594433 timed out (done 594427) vk: slow submit: 250.0 ms: memory sync 250.0 [memory sync: maps 0.0 (lock waits 0.0), capture 249.9, collect 0.1] vk: the GPU has finished nothing for 10 s: the timeline at 594427, 594440 sent (RX_VK_GPU_HANG_SEC=30) vk: the GPU has finished nothing for 30 s: the timeline at 594427, 594440 sent (RX_VK_GPU_HANG_SEC=30) vk: GPU hang: the timeline at 594427, 594440 sent vk: device fault: vk: FATAL: the GPU hung: no submission finished in 30 s, and the driver never reported the device lost ``` Earlier focus switches in the same sessions did not hang (in the third session 3 switches were fine, the 4th hung), so it doesn't happen on every switch. Windows logged no display driver reset (no TDR event). Note: during the first hang the CPU had an unstable undervolt (Windows logged corrected WHEA cache errors). I reverted it to stock before the second hang, and no WHEA errors were logged after that, so the second hang happened on a stable system. I can run again with `RX_VK_CHECKPOINTS=1` if markers would help. ### Where in the game Dodongo's Cavern (the second dungeon), playing normally. The hangs don't seem tied to a spot: each came right after I switched from the game to the browser. ### How often Sometimes (3 hangs in about 2 hours of play, all right after switching to another window) ### Graphics card and driver version AMD Radeon RX 9070 XT, AMD Software 26.20.15.07 (driver 32.0.32015.7029; Vulkan reports driver 0x8001a0) ### CPU, RAM and operating system Ryzen 7 5800X3D (stock), 32 GB, Windows 11 Pro 25H2 (build 26200) ### Changes from the defaults - Upscaler AMD FSR 4, Render resolution Native (FSR 4 Native AA) for the second hang; FSR 4 at Render resolution Auto (2580x1080 → 3440x1440) for the first - Output resolution 2560x1440 with Aspect ratio Monitor's shape (picture 3440x1440) - Frame generation Auto (144 Hz monitor: "a frame for each of the display's refreshes, up to 4 a game frame") - Fullscreen on, V-Sync Auto (swapchain immediate) - Quality preset Custom, Ultrawide menus off, FPS counter on, mouse sensitivity 60, motion sensitivity 300/200 - Three monitors: the game on a 3440x1440 144 Hz monitor; the primary display is a 4K 60 Hz TV; a third one is 1080p - Started from Steam as a non-Steam game (Steam overlay possible); Steam Input on for the first hang, off for the second - No `longshot_env.txt` for the first two hangs; `HOS_MOTION_DEBUG=1` for the third (only extra logging); no ReShade or other injector ### longshot_log.txt `longshot_log_hang_2042.zip` (second hang) and `longshot_log_hang_3.zip` (third hang); the Windows user name in one path is replaced with USER ### Before you send it - [x] The problem is still there on the newest release or nightly. (rc.3 is the newest release candidate; nightly-80 crashes on startup, #261) - [x] I searched the open issues for it. (nothing about hangs after a focus change; #130 is a device lost at the VRAM limit, a different case) - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves. _Prepared with help from Claude; the facts and logs are from my PC._

longshot_log_hang_2042.zip

893 KiB

longshot_log_hang_3.zip

538 KiB