MagicBeanDev/Hookshot

Archived

Watch

Fork 0

AMD 6800XT VK_ERROR_DEVICE_LOST #2176

Closed

opened 2026-11-11 06:08:47 +00:00 by l326108519-lab · 7 comments

l326108519-lab commented

2026-11-11 06:08:47 +00:00

(Migrated from github.com)

Hookshot version

v2.1.0

What kind of problem

Crash, freeze or black screen

What happened

Bug Report: VK_ERROR_DEVICE_LOST - Game crashes at several locations

Summary

Hookshot v2.0.11-v2.1.0
The game crashes in the following scenarios. Every crash results in a black screen, followed by an AMD GPU driver error. After that, the window either closes or stays white with background music continuing to play.

Sacred Forest Meadow: Crash at the long straight corridor in the final section of the dungeon.
Zora's River: Crash immediately after finishing dialogue with the owl on first entry.
Hyrule Field: Crash after fighting enemies for an extended period.
Room to the right of Hyrule Castle Town Gate (pot room): Crash after breaking pots, when many pot shards spawn and the scene geometry becomes complex.
This issue triggers immediately when the resolution is set to 2K or higher. If using fully default settings, the crash only occurs after roughly 15–20 minutes of gameplay (e.g., moving around or fighting enemies on Hyrule Field).

hookshot_log: vk: FATAL: the GPU device was lost (VK_ERROR_DEVICE_LOST): the driver stopped or reset the GPU, and nothing sent to it runs any more (on Linux, dmesg or journalctl -k around this time names the reset)

Where in the game

Sacred Forest Meadow, Zora's River, Hyrule Field, pot room of Hyrule Castle Town Gate

How often

Every time

Graphics card and driver version

RX 6800XT Adrenalin Edition 26.10.1

CPU, RAM and operating system

i7-11700K 16GB Windows11 26H2

Changes from the defaults

Render resolution set to 2K or higher (triggers crash instantly). Default settings take ~15-20 minutes to crash.

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

Sacred Forest Meadow
hookshot_log.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.1.0 ### What kind of problem Crash, freeze or black screen ### What happened # Bug Report: VK_ERROR_DEVICE_LOST - Game crashes at several locations ## Summary Hookshot v2.0.11-v2.1.0 The game crashes in the following scenarios. Every crash results in a black screen, followed by an AMD GPU driver error. After that, the window either closes or stays white with background music continuing to play. 1. Sacred Forest Meadow: Crash at the long straight corridor in the final section of the dungeon. 2. Zora's River: Crash immediately after finishing dialogue with the owl on first entry. 3. Hyrule Field: Crash after fighting enemies for an extended period. 4. Room to the right of Hyrule Castle Town Gate (pot room): Crash after breaking pots, when many pot shards spawn and the scene geometry becomes complex. 5. This issue triggers immediately when the resolution is set to 2K or higher. If using fully default settings, the crash only occurs after roughly 15–20 minutes of gameplay (e.g., moving around or fighting enemies on Hyrule Field). hookshot_log: vk: FATAL: the GPU device was lost (VK_ERROR_DEVICE_LOST): the driver stopped or reset the GPU, and nothing sent to it runs any more (on Linux, dmesg or journalctl -k around this time names the reset) ### Where in the game Sacred Forest Meadow, Zora's River, Hyrule Field, pot room of Hyrule Castle Town Gate ### How often Every time ### Graphics card and driver version RX 6800XT Adrenalin Edition 26.10.1 ### CPU, RAM and operating system i7-11700K 16GB Windows11 26H2 ### Changes from the defaults Render resolution set to 2K or higher (triggers crash instantly). Default settings take ~15-20 minutes to crash. ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt Sacred Forest Meadow [hookshot_log.txt](https://github.com/user-attachments/files/34672160/hookshot_log.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.

👍 1

Danrarbc commented

2026-11-11 06:45:33 +00:00

(Migrated from github.com)

It kinda feels like the device lost errors are getting worse on RX 6000 GPUs. The RX_VK_SKIP_CODE fixes don't seem to reliably work around it anymore either.

hookshot_log.txt

Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: Dumping IP State
Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: Dumping IP State Completed
Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: [drm] AMDGPU device coredump file has been created
Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.2.0 timeout, signaled seq=216037, emitted seq=216038
Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0:  Process hookshot pid 186239 thread mkw_vk order pid 186318
Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: Starting comp_1.2.0 ring reset
Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: Ring comp_1.2.0 reset failed
Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: GPU reset begin!. Source:  1
Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: MODE1 reset
Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: GPU mode1 reset
Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: GPU smu mode1 reset
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: GPU reset succeeded, trying to resume
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: [drm] PCIE GART of 512M enabled (table at 0x00000081FEB00000).
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: VRAM is lost due to GPU reset!
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: PSP is resuming...
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: reserve 0xa00000 from 0x81fd000000 for PSP TMR
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: RAS: optional ras ta ucode is not available
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: SECUREDISPLAY: optional securedisplay ta ucode is not available
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: SMU is resuming...
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: use vbios provided pptable
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: SMU is resumed successfully!
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: kiq ring mec 2 pipe 1 q 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: [drm] DMUB hardware initialized: version=0x02020023
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring sdma0 uses VM inv eng 13 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring sdma1 uses VM inv eng 14 on hub 0
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring jpeg_dec uses VM inv eng 5 on hub 8
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: GPU reset(7) succeeded!
Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: [drm] device wedged, but no recovery needed

It kinda feels like the device lost errors are getting worse on RX 6000 GPUs. The RX_VK_SKIP_CODE fixes don't seem to reliably work around it anymore either. [hookshot_log.txt](https://github.com/user-attachments/files/34674206/hookshot_log.txt) ``` Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: Dumping IP State Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: Dumping IP State Completed Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: [drm] AMDGPU device coredump file has been created Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: [drm] Check your /sys/class/drm/card1/device/devcoredump/data Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.2.0 timeout, signaled seq=216037, emitted seq=216038 Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: Process hookshot pid 186239 thread mkw_vk order pid 186318 Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: Starting comp_1.2.0 ring reset Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: Ring comp_1.2.0 reset failed Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: GPU reset begin!. Source: 1 Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: MODE1 reset Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: GPU mode1 reset Nov 11 00:50:08 cachyos-x8664 kernel: amdgpu 0000:08:00.0: GPU smu mode1 reset Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: GPU reset succeeded, trying to resume Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: [drm] PCIE GART of 512M enabled (table at 0x00000081FEB00000). Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: VRAM is lost due to GPU reset! Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: PSP is resuming... Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: reserve 0xa00000 from 0x81fd000000 for PSP TMR Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: RAS: optional ras ta ucode is not available Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: SECUREDISPLAY: optional securedisplay ta ucode is not available Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: SMU is resuming... Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: use vbios provided pptable Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: SMU is resumed successfully! Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: kiq ring mec 2 pipe 1 q 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: [drm] DMUB hardware initialized: version=0x02020023 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring gfx_0.1.0 uses VM inv eng 1 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.0.0 uses VM inv eng 4 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.1.0 uses VM inv eng 5 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.2.0 uses VM inv eng 6 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.3.0 uses VM inv eng 7 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.0.1 uses VM inv eng 8 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.1.1 uses VM inv eng 9 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.2.1 uses VM inv eng 10 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring comp_1.3.1 uses VM inv eng 11 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring sdma0 uses VM inv eng 13 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring sdma1 uses VM inv eng 14 on hub 0 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring vcn_dec_0 uses VM inv eng 0 on hub 8 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: ring jpeg_dec uses VM inv eng 5 on hub 8 Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: GPU reset(7) succeeded! Nov 11 00:50:09 cachyos-x8664 kernel: amdgpu 0000:08:00.0: [drm] device wedged, but no recovery needed ```

alvaroum02-rgb commented

2026-11-11 11:10:32 +00:00

(Migrated from github.com)

It still happens even on an RX 6700XT

Layfuboxu007 commented

2026-11-11 12:28:37 +00:00

(Migrated from github.com)

Happens on RX 6600 XT, Just 1 question for people with AMD, What GPU drivers are you on?

alvaroum02-rgb commented

2026-11-11 12:58:38 +00:00

(Migrated from github.com)

Mesa 26.2.6-arch3.1

l326108519-lab commented

2026-11-11 14:15:34 +00:00

(Migrated from github.com)

I found that disabling frame pacing may prevent this crash.
With frame pacing disabled, I have played for nearly an hour without triggering the AMD driver timeout popup.
The popup message reads: AMD software detected that a driver timeout has occurred on your system.

I found that disabling frame pacing may prevent this crash. With frame pacing disabled, I have played for nearly an hour without triggering the AMD driver timeout popup. The popup message reads: `AMD software detected that a driver timeout has occurred on your system.`

NotRexed commented

2026-11-11 21:26:03 +00:00

(Migrated from github.com)

Thanks for the report. Reports of the same problem are now collected in #996, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #996 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.