The game crashes after running for a while #571

Closed

opened 2026-11-08 11:58:05 +00:00 by gbyoung666 · 3 comments

gbyoung666 commented

2026-11-08 11:58:05 +00:00

(Migrated from github.com)

The idea

The game crashes after running for a while

I am using the latest released build: low-vram: GitHub-outage-proof setup, 4 GB cards, Intel freeze, build workers

ryzen 5 4600g, rx 6600

windows 11 26h2: 26300.9818

The AMD driver is likely crashing as well

AMD driver: 26.10.1

Anything else

hookshot_log.txt
hookshot_log.1.txt

### The idea The game crashes after running for a while I am using the latest released build: low-vram: GitHub-outage-proof setup, 4 GB cards, Intel freeze, build workers ryzen 5 4600g, rx 6600 windows 11 26h2: 26300.9818 The AMD driver is likely crashing as well AMD driver: 26.10.1 ### Anything else [hookshot_log.txt](https://github.com/user-attachments/files/34542602/hookshot_log.txt) [hookshot_log.1.txt](https://github.com/user-attachments/files/34542603/hookshot_log.1.txt)

NotRexed commented

2026-11-08 12:43:54 +00:00

(Migrated from github.com)

Release https://github.com/NotRexed/Hookshot/releases/tag/fast-updates no longer gives back memory the GPU used, on Windows (it was meant for a Linux AMD driver; fuxau traced the Arc device lost to it in #17, and the AMD logs show device lost right after it). If you had device lost, could you try this release and tell us? On Linux/Steam Deck the old behaviour stays; there, please try RX_VK_KEEP_RETIRED=1 and say whether the device lost goes away.

Release https://github.com/NotRexed/Hookshot/releases/tag/fast-updates no longer gives back memory the GPU used, on Windows (it was meant for a Linux AMD driver; fuxau traced the Arc device lost to it in #17, and the AMD logs show device lost right after it). If you had device lost, could you try this release and tell us? On Linux/Steam Deck the old behaviour stays; there, please try `RX_VK_KEEP_RETIRED=1` and say whether the device lost goes away.

👍 1

gbyoung666 commented

2026-11-08 14:16:43 +00:00

(Migrated from github.com)

without RX_VK_KEEP_RETIRED=1 - The textures even show up

now using RX_VK_KEEP_RETIRED=1

I tried it with the RX_VK_KEEP_RETIRED=1 variant and it stopped crashing, but the grass and tree textures keep flickering, and there’s an intense light

version=fast-updates

hookshot_log.txt
hookshot_log.1.txt
hookshot_log.2.txt
hookshot_log.3.txt
hookshot_log.4.txt

without RX_VK_KEEP_RETIRED=1 - The textures even show up <img width="1917" height="1015" alt="Image" src="https://github.com/user-attachments/assets/2b5ea319-1404-4223-b8e6-975c6f097981" /> now using RX_VK_KEEP_RETIRED=1 <img width="1917" height="1018" alt="Image" src="https://github.com/user-attachments/assets/d864da4d-66ba-42b3-8e91-1b8791689966" /> I tried it with the `RX_VK_KEEP_RETIRED=1` variant and it stopped crashing, but the grass and tree textures keep flickering, and there’s an intense light version=fast-updates [hookshot_log.txt](https://github.com/user-attachments/files/34544971/hookshot_log.txt) [hookshot_log.1.txt](https://github.com/user-attachments/files/34544975/hookshot_log.1.txt) [hookshot_log.2.txt](https://github.com/user-attachments/files/34544974/hookshot_log.2.txt) [hookshot_log.3.txt](https://github.com/user-attachments/files/34544970/hookshot_log.3.txt) [hookshot_log.4.txt](https://github.com/user-attachments/files/34544973/hookshot_log.4.txt)

NotRexed commented

2026-11-09 05:49:41 +00:00

(Migrated from github.com)

Tracked in #996, follow there. That issue collects every report of AMD driver crashes, device lost and freezes on Windows, and this one is linked from it with its GPU, version and log details. If it still happens on v2.0.6 (https://github.com/NotRexed/Hookshot/releases/tag/v2.0.6; Update next to Play in the launcher), please add a comment there with your hookshot_log.txt.

Commenting is not possible because the repository is archived.