Kakariko → Death Mountain Trail transition: freeze / device lost every time (RX 6700 XT, v2.0.5 and v2.0.6) #1015

Closed

opened 2026-11-09 05:57:47 +00:00 by wheezypulls-hue · 2 comments

wheezypulls-hue commented

2026-11-09 05:57:47 +00:00

(Migrated from github.com)

Hookshot version

v2.0.6

What kind of problem

Crash, freeze or black screen

What happened

Walking from Kakariko Village up the path to Death Mountain Trail freezes the
game every time (2 freezes, 1 device lost + crash). 3 logs attached.

Narrowed down:

Debug teleport to Death Mountain Trail: loads fine
Walking Death Mountain Trail -> Kakariko: fine
Walking Kakariko -> Death Mountain Trail: freeze / crash, every time
So it's the transition itself, not either scene.

Same texture fails each time (1600x1600x1 x3, NVN 0x32, GPU-rendered):

"a capture's wait for write-back ... timed out" (x4)
"texture 0x10002da1800 1600x1600 NVN 0x32: the GPU wrote its storage:
uploaded again" / "re-uploaded (flags 0x8): a GPU write into its storage,
15600 KB of it, over what the GPU wrote (finalized since)"
"nvn: GPU waits in 5 s: 1 sync waits (~4400 ms)"
latest run: "vk: submit 38605 failed (-4)", "device lost", then
"CRASH: exception 0xc0000005 (read 0x38) at amdvlk64.dll+0x319b63"
(backtrace through hookshot_vk.dll+0x1ad60b)

Where in the game

Path to Death Mountain

How often

Every time

Graphics card and driver version

AMD Radeon RX 6700 XT, Vulkan 1.4, driver 0x800161, Windows

CPU, RAM and operating system

Ryzen 5 7500F, Windows 11 Home

Changes from the defaults

No response

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

2_freeze_v2.0.6.txt
3_crash_v2.0.6.txt
1_freeze_v2.0.5.txt

Screenshots or video

No response

Before you send it

I'm on the newest release, or the problem is still there on it.
I searched the open issues for this problem.
I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.

### Hookshot version v2.0.6 ### What kind of problem Crash, freeze or black screen ### What happened Walking from Kakariko Village up the path to Death Mountain Trail freezes the game every time (2 freezes, 1 device lost + crash). 3 logs attached. Narrowed down: - Debug teleport to Death Mountain Trail: loads fine - Walking Death Mountain Trail -> Kakariko: fine - Walking Kakariko -> Death Mountain Trail: freeze / crash, every time So it's the transition itself, not either scene. Same texture fails each time (1600x1600x1 x3, NVN 0x32, GPU-rendered): - "a capture's wait for write-back ... timed out" (x4) - "texture 0x10002da1800 1600x1600 NVN 0x32: the GPU wrote its storage: uploaded again" / "re-uploaded (flags 0x8): a GPU write into its storage, 15600 KB of it, over what the GPU wrote (finalized since)" - "nvn: GPU waits in 5 s: 1 sync waits (~4400 ms)" - latest run: "vk: submit 38605 failed (-4)", "device lost", then "CRASH: exception 0xc0000005 (read 0x38) at amdvlk64.dll+0x319b63" (backtrace through hookshot_vk.dll+0x1ad60b) ### Where in the game Path to Death Mountain ### How often Every time ### Graphics card and driver version AMD Radeon RX 6700 XT, Vulkan 1.4, driver 0x800161, Windows ### CPU, RAM and operating system Ryzen 5 7500F, Windows 11 Home ### Changes from the defaults _No response_ ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [2_freeze_v2.0.6.txt](https://github.com/user-attachments/files/34565535/2_freeze_v2.0.6.txt) [3_crash_v2.0.6.txt](https://github.com/user-attachments/files/34565536/3_crash_v2.0.6.txt) [1_freeze_v2.0.5.txt](https://github.com/user-attachments/files/34565537/1_freeze_v2.0.5.txt) ### Screenshots or video _No response_ ### Before you send it - [x] I'm on the newest release, or the problem is still there on it. - [x] I searched the open issues for this problem. - [x] I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.

Brottuetchen commented

2026-11-09 20:10:43 +00:00

(Migrated from github.com)

Same freeze here on NVIDIA / Linux, so it is not AMD-only, and it happens on several releases.

System: RTX 4080 SUPER, NVIDIA 620.70.06 (Vulkan), Ryzen 9 7900X3D, CachyOS (kernel 7.3.3), KDE Wayland (game window through XWayland), launched from Steam.

What happens: The game freezes completely (no input, Steam overlay unresponsive), GPU at 0 %, while the log shows:

[hos sead::MainThread] vk: a capture's wait for write-back 208232 timed out (done 208228)
[hos Presentation Thread] vk: a capture's wait for write-back 208232 timed out (done 208228)
[hos Presentation Thread] vk: a capture's wait for write-back 208232 timed out (done 208228)

After the timeout a few in play: graphics … lines follow, then the game stalls for good.

Versions and occurrences (all on 2026-11-09, same PC, same save):

v2.0.10: froze on the transition into Hyrule Field (wait for write-back 129406 timed out (done 129402), then nvn: GPU waits in 5 s: … 1 polls timed out (22492 ms)). Just before it: upload over a drawn image … 1600x1600x1 x3 NVN 0x32 … a GPU buffer wrote it / re-uploaded (flags 0x8): a GPU write into its storage. That is the same texture as in the first post. Earlier the same session it also froze right after loading the save (wait for write-back 7057 timed out (done 7053)).
v2.0.11: froze right after loading the save. The OptimizeChangeBanc and mkw_vk threads were at 100 % CPU and the GPU at 0 %.
v2.0.7: ran ~16 min (29,700 frames), then froze with the log above.

With default options (only fullscreen=1 and frame_generation=2), no RX_VK_* switches. Happy to test a build with #1150 or send full logs.

Same freeze here on **NVIDIA / Linux**, so it is not AMD-only, and it happens on several releases. **System:** RTX 4080 SUPER, NVIDIA 620.70.06 (Vulkan), Ryzen 9 7900X3D, CachyOS (kernel 7.3.3), KDE Wayland (game window through XWayland), launched from Steam. **What happens:** The game freezes completely (no input, Steam overlay unresponsive), GPU at 0 %, while the log shows: ``` [hos sead::MainThread] vk: a capture's wait for write-back 208232 timed out (done 208228) [hos Presentation Thread] vk: a capture's wait for write-back 208232 timed out (done 208228) [hos Presentation Thread] vk: a capture's wait for write-back 208232 timed out (done 208228) ``` After the timeout a few `in play: graphics …` lines follow, then the game stalls for good. **Versions and occurrences (all on 2026-11-09, same PC, same save):** - **v2.0.10:** froze on the transition into Hyrule Field (`wait for write-back 129406 timed out (done 129402)`, then `nvn: GPU waits in 5 s: … 1 polls timed out (22492 ms)`). Just before it: `upload over a drawn image … 1600x1600x1 x3 NVN 0x32 … a GPU buffer wrote it` / `re-uploaded (flags 0x8): a GPU write into its storage`. That is the same texture as in the first post. Earlier the same session it also froze right after loading the save (`wait for write-back 7057 timed out (done 7053)`). - **v2.0.11:** froze right after loading the save. The OptimizeChangeBanc and `mkw_vk` threads were at 100 % CPU and the GPU at 0 %. - **v2.0.7:** ran ~16 min (29,700 frames), then froze with the log above. With default options (only `fullscreen=1` and `frame_generation=2`), no `RX_VK_*` switches. Happy to test a build with #1150 or send full logs.

NotRexed commented

2026-11-10 05:07:50 +00:00

(Migrated from github.com)

Thanks for the report. This is part of the AMD-on-Windows device lost / freeze problem (here: every Kakariko to Death Mountain Trail transition on an RX 6700 XT), so it's followed in the tracking issue #996, along with the other reports from the same family of cards. Your exact repro steps are linked from there; please add new logs or results to #996. Closing in favour of the tracker.

Commenting is not possible because the repository is archived.