MagicBeanDev/Hookshot

Archived

Watch

Fork 0

[AMD RX 6600 / v2.1.0] Repeated VK_ERROR_DEVICE_LOST across different scenes and quick inventory — AMD checkpoints available #2870

Open

opened 2026-11-12 19:00:49 +00:00 by github-sync · 0 comments

github-sync commented

2026-11-12 19:00:49 +00:00

Owner

@notreallyfreddie76-arch opened on GitHub · 2026-11-12 18:02 UTC · original

Hookshot version

v2.1.0

What kind of problem

Crash, freeze or black screen

What happened

<html>

Summary

Hookshot v2.1.0 shows noticeable improvements in general stability and performance on my AMD Radeon RX 6600 compared with previous versions.

However, I encountered three separate VK_ERROR_DEVICE_LOST crashes on November 12, 2026, during normal gameplay and while opening the quick item-selection inventory.

All three crashes occurred without a noticeable prolonged freeze or progressive performance degradation. The game was running normally before the application abruptly terminated.

RX_VK_CHECKPOINTS was enabled in all three sessions, and each crash produced usable AMD GPU execution markers.

One of the crashes also occurred with the GPU maximum clock deliberately reduced to 2044 MHz, well below the manufacturer's advertised 2491 MHz boost clock.

System specifications

Common observations

All three sessions end in a confirmed VK_ERROR_DEVICE_LOST.
The crashes are intermittent, with no single reliably reproducible location.
The game appears to run normally until the abrupt termination.
Each failure includes AMD buffer-marker information.
GPU memory allocation repeatedly reaches the Vulkan-reported budget.
The logs report substantial memory allocation and resource-management activity.
Synchronization waits or write-back-related operations appear close to the device-loss events.
Lowering the GPU maximum frequency to 2044 MHz did not prevent Crash #3.

The VRAM statistics also show some available space within previously allocated blocks. Therefore, reaching the reported allocation budget does not by itself demonstrate that the GPU ran out of usable physical memory.

Likewise, the AMD markers identify commands around the point where GPU progress stopped, but do not conclusively identify the root cause.

Possible investigation areas

Based on these observations, potential areas worth investigating include:

Vulkan submission synchronization and GPU write-back handling.
Resource lifetime management and render-target reuse.
Memory pressure and allocation behavior on 8 GB AMD GPUs.
AMD driver interaction with the renderer's command scheduling.
Draw/pipeline resource dependencies around the reported AMD checkpoints.

I am not claiming that any of these is the confirmed cause.

The fact that the same failure occurs at multiple resolutions, in different scenes, and with a substantially reduced GPU clock makes a simple high-frequency instability or excessive-resolution explanation less convincing.

Previous reports

This follows my earlier AMD RX 6600 / RX 7600 comparison in #1123.

The previous RX 6600 menu freezes may also be related to the existing AMD freeze tracker #996.

However, the present issue specifically documents three confirmed Vulkan device losses on v2.1.0, with AMD checkpoints available for each occurrence.

Attached logs

hookshot_log.3.txt — Crash #1, higher-resolution session.
hookshot_log(20261112-162655).txt — Crash #2, 1080p normal gameplay.
hookshot_log(20261112-174324).txt — Crash #3, quick item-selection inventory, GPU capped at 2044 MHz.

The full logs contain the associated memory statistics, Vulkan submissions, execution markers, and GPU synchronization reports.

The crashes are not reliably reproducible on demand, but the repeated VK_ERROR_DEVICE_LOST signatures suggest a persistent issue despite the stability improvements introduced in v2.1.0.

</html>

hookshot_log(20261112-162655).txt
hookshot_log(20261112-174324).txt
hookshot_log.3.txt

Where in the game

Lonlon Ranch, Cocorico Village

How often

Every time

Graphics card and driver version

RX7600 v26.8.1

CPU, RAM and operating system

Ryzen 5 3600 32GB RAM Win11

Changes from the defaults

No response

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

[hos Presentation Thread] vk: bound in guest memory, by pool (the GPU reads these over PCIe; binds and the bytes of their ranges over these 600 submits, 517.4 MB in all, a range counted once a submit): 0x7fd7000000 (96 MB, state 3): 4159 binds, 339 MB; 0x7fbd000000 (96 MB, state 3): 3728 binds, 159 MB; 0x7fde000000 (48 MB, state 3): 529 binds, 19 MB; 0x1144000000 (48 MB, state 3): 132 binds, 0 MB; 0x1052000000 (16 MB, state 3): 47 binds, 0 MB; 0x113f000000 (48 MB, state 3): 17 binds, 0 MB;
[hos Presentation Thread] vk: replay reads of guest memory as submitted: 70880000 (41463114 pages from the captures)
[hos ModuleSystemWorker5] nvn: 14450000 recordings made, 109097 live copies (29.5 MB), 93831 texture copies; 6 command buffers' segments (4.3 MB)
[hos Presentation Thread] nvn: QueueSubmitCommands #740000: queue 000010100C290020 (its #123297), 1 handles (lr 0x805282f4)
[hos Presentation Thread] vk: replay reads of guest memory as submitted: 70900000 (41474425 pages from the captures)
[hos Presentation Thread] vk: 3 textures retired (2608 left, 2862 MB)
[hos Presentation Thread] vk: mirror syncs (600 submits): 408 dirty pages from their submits' captures, 53056 from earlier ones', 0 from guest memory as it was at the replay; 25 captures kept; 0 pages the GPU wrote copied over (0 live); 0 kept for the GPU (RX_VK_PROTECT_BARE)
[hos Presentation Thread] vk: read live, by pool:
[hos Presentation Thread] vk: bound in guest memory, by pool (the GPU reads these over PCIe; binds and the bytes of their ranges over these 600 submits, 476.1 MB in all, a range counted once a submit): 0x7fbd000000 (96 MB, state 3): 3666 binds, 164 MB; 0x7fd7000000 (96 MB, state 3): 3024 binds, 296 MB; 0x7fde000000 (48 MB, state 3): 458 binds, 16 MB; 0x1144000000 (48 MB, state 3): 155 binds, 0 MB; 0x1052000000 (16 MB, state 3): 45 binds, 0 MB; 0x113f000000 (48 MB, state 3): 17 binds, 0 MB;
[hos Presentation Thread] vk: imports: 103 live (4048 MB), 32 retired still imported (1856 MB), 0 retired given back (0 MB)
[hos Presentation Thread] vk: program picks: 92907576 kept (40213184 by the last picks' textures, a uniform buffer bound since), 56826 new, 47435597 with other textures (of 140400000)
[hos Presentation Thread] vk: 12 textures retired (2604 left, 2861 MB)
[hos Presentation Thread] vk: replay reads of guest memory as submitted: 70920000 (41485602 pages from the captures)
[hos ModuleSystemWorker1] vk: readbacks of GPU results: 1087 of 3000 waited for their write-back, 0.03 ms each
[hos ModuleSystemWorker5] nvn: CommandBufferSignalEvent #2135000: event 0x100c318034 mode 0 value 2134999 (lr 0x806616b0)
[hos Presentation Thread] vk: readback pages refreshed from guest memory: 47513986 pages so far (0 held: may be written ahead in their submission)
[hos Presentation Thread] vk: capture: a submit 0.65 ms (lock 0.02, scan 0.11 over 763 ranges, 6179 MB), 1344 pages written, 1344 copied (5.3 MB)
[hos Presentation Thread] vk: a capture taken (ms): all 1.373; GPU wait for late pages 1.287 (85 of 600 takes), pools lock 0.000, retires and stamps 0.066, bytes copied 0.000; 25 kept (815 MB), 5 spare buffers, 9246 texture pages copied (36 MB)
[hos Presentation Thread] vk: replay reads of guest memory as submitted: 70940000 (41495887 pages from the captures)
[hos Presentation Thread] vk: mirror syncs (600 submits): 170 dirty pages from their submits' captures, 55180 from earlier ones', 507 from guest memory as it was at the replay; 25 captures kept; 0 pages the GPU wrote copied over (0 live); 0 kept for the GPU (RX_VK_PROTECT_BARE)
[hos Presentation Thread] vk: read live, by pool: 0x1064000000 (16 MB, captured, state 2): 161; 0x1055000000 (16 MB, captured, state 2): 111; 0x104b000000 (64 MB, captured, state 2): 74; 0x1050000000 (16 MB, captured, state 2): 72; 0x102d000000 (32 MB, captured, state 2): 42; 0x108a000000 (240 MB, captured, state 2): 34; 0x1036000000 (32 MB, captured, state 2): 4; 0x1158000000 (64 MB, captured, state 2): 2;
[hos Presentation Thread] vk: bound in guest memory, by pool (the GPU reads these over PCIe; binds and the bytes of their ranges over these 600 submits, 471.9 MB in all, a range counted once a submit): 0x7fbd000000 (96 MB, state 3): 3743 binds, 153 MB; 0x7fd7000000 (96 MB, state 3): 3056 binds, 302 MB; 0x7fde000000 (48 MB, state 3): 442 binds, 16 MB; 0x1144000000 (48 MB, state 3): 159 binds, 0 MB; 0x1052000000 (16 MB, state 3): 51 binds, 0 MB; 0x113f000000 (48 MB, state 3): 18 binds, 0 MB;
[hos Presentation Thread] vk: 2 textures retired (2615 left, 2864 MB)
[hos nn.npln.Callback] vcores: 105568 takes, 19314 waits (mean 63 us, longest 36.5 ms), 9131 kicks, 8973 yields, 0 escapes in 5 s
[hos rmbl::VibrationThread] hid: 610304 vibration values, strongest 0.00 since the last count
[hos sead::MainThread] nvn: GPU waits in 5 s: 1 sync waits (5633 ms), 0 polls timed out (0 ms), 5 queue finishes (1 ms)
[hos host] vk: texture 0x10001be6200 1600x1600x1 x3 levels 1 NVN 0x32 (15600 KB of storage) re-uploaded (its memory was written; flags 0x8): a GPU write into its storage, 15600 KB of it, over what the GPU wrote (finalized since)
[hos host] vk: submit 863683 failed (-4)
[hos host] vk: device lost: reading the buffer markers
[hos host] vk: device lost: 153300919 markers set, 61209 reached; the last whose earlier work all finished: 153296587
[hos host] vk: finished before: marker 153296581 (draw of program e63d9ab36296c03d, frame 123350)
[hos host] vk: finished before: marker 153296582 (draw of program 418065c6876a3d13, frame 123350)
[hos host] vk: finished before: marker 153296583 (draw of program 1115bf68c8fccb16, frame 123350)
[hos host] vk: finished before: marker 153296584 (draw of program 136d9555efa9a389, frame 123350)
[hos host] vk: finished before: marker 153296585 (write-back of pool 000000102c000000, frame 123350)
[hos host] vk: finished before: marker 153296586 (write-back of pool 000000113a000000, frame 123350)
[hos host] vk: RUNNING after: marker 153296587 (draw of program 136d9555efa9a389, frame 123350)
[hos host] vk: running: marker 153296588 (draw of program 136d9555efa9a389, frame 123350)
[hos host] vk: reached, earlier work unfinished: marker 153296588 (draw of program 136d9555efa9a389, frame 123350)
[hos host] vk: reached, earlier work unfinished: marker 153296589 (draw of program 136d9555efa9a389, frame 123350)
[hos host] vk: reached, earlier work unfinished: marker 153296590 (draw of program 136d9555efa9a389, frame 123350)
[hos host] vk: reached, earlier work unfinished: marker 153296591 (draw of program 136d9555efa9a389, frame 123350)
[hos host] vk: reached, earlier work unfinished: marker 153296592 (draw of program a6fd6a636241d42e, frame 123350)
[hos host] 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)
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)

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.

> [@notreallyfreddie76-arch](https://github.com/notreallyfreddie76-arch) opened on GitHub · 2026-11-12 18:02 UTC · [original](https://github.com/NotRexed/Hookshot/issues/2870) ### Hookshot version v2.1.0 ### What kind of problem Crash, freeze or black screen ### What happened <html> <body> <h2>Summary</h2>Hookshot v2.1.0 shows noticeable improvements in general stability and performance on my AMD Radeon RX 6600 compared with previous versions.However, I encountered three separate <code>VK_ERROR_DEVICE_LOST</code> crashes on November 12, 2026, during normal gameplay and while opening the quick item-selection inventory.All three crashes occurred without a noticeable prolonged freeze or progressive performance degradation. The game was running normally before the application abruptly terminated.<code>RX_VK_CHECKPOINTS</code> was enabled in all three sessions, and each crash produced usable AMD GPU execution markers.One of the crashes also occurred with the GPU maximum clock deliberately reduced to 2044 MHz, well below the manufacturer's advertised 2491 MHz boost clock.<h2>System specifications</h2> Component | Specification -- | -- GPU | Sapphire Pulse Radeon RX 6600 8 GB CPU | AMD Ryzen 5 3600 RAM | 32 GB OS | Windows 11, build 26200 AMD Adrenalin | 26.8.1 Vulkan | 1.4 Vulkan driver ID | 0x800161 Hookshot | v2.1.0, source 633eb435 Renderer | Vulkan (hookshot_vk.dll) AMD checkpoints | VK_AMD_buffer_marker enabled VRAM clock | 1750 MHz (stock) <h3>Common observations</h3><ol start="1"><li>All three sessions end in a confirmed <code>VK_ERROR_DEVICE_LOST</code>.</li><li>The crashes are intermittent, with no single reliably reproducible location.</li><li>The game appears to run normally until the abrupt termination.</li><li>Each failure includes AMD buffer-marker information.</li><li>GPU memory allocation repeatedly reaches the Vulkan-reported budget.</li><li>The logs report substantial memory allocation and resource-management activity.</li><li>Synchronization waits or write-back-related operations appear close to the device-loss events.</li><li>Lowering the GPU maximum frequency to 2044 MHz did not prevent Crash #3.</li></ol>The VRAM statistics also show some available space within previously allocated blocks. Therefore, reaching the reported allocation budget does not by itself demonstrate that the GPU ran out of usable physical memory.Likewise, the AMD markers identify commands around the point where GPU progress stopped, but do not conclusively identify the root cause.<h2>Possible investigation areas</h2>Based on these observations, potential areas worth investigating include:<ul><li>Vulkan submission synchronization and GPU write-back handling.</li><li>Resource lifetime management and render-target reuse.</li><li>Memory pressure and allocation behavior on 8 GB AMD GPUs.</li><li>AMD driver interaction with the renderer's command scheduling.</li><li>Draw/pipeline resource dependencies around the reported AMD checkpoints.</li></ul>I am not claiming that any of these is the confirmed cause.The fact that the same failure occurs at multiple resolutions, in different scenes, and with a substantially reduced GPU clock makes a simple high-frequency instability or excessive-resolution explanation less convincing.<h2>Previous reports</h2>This follows my earlier AMD RX 6600 / RX 7600 comparison in #1123.The previous RX 6600 menu freezes may also be related to the existing AMD freeze tracker #996.However, the present issue specifically documents three confirmed Vulkan device losses on v2.1.0, with AMD checkpoints available for each occurrence.<h2>Attached logs</h2><ul><li><code>hookshot_log.3.txt</code> — Crash #1, higher-resolution session.</li><li><code>hookshot_log(20261112-162655).txt</code> — Crash #2, 1080p normal gameplay.</li><li><code>hookshot_log(20261112-174324).txt</code> — Crash #3, quick item-selection inventory, GPU capped at 2044 MHz.</li></ul>The full logs contain the associated memory statistics, Vulkan submissions, execution markers, and GPU synchronization reports.The crashes are not reliably reproducible on demand, but the repeated <code>VK_ERROR_DEVICE_LOST</code> signatures suggest a persistent issue despite the stability improvements introduced in v2.1.0. </body> </html> [hookshot_log(20261112-162655).txt](https://github.com/user-attachments/files/34762433/hookshot_log.20261112-162655.txt) [hookshot_log(20261112-174324).txt](https://github.com/user-attachments/files/34762435/hookshot_log.20261112-174324.txt) [hookshot_log.3.txt](https://github.com/user-attachments/files/34762434/hookshot_log.3.txt) ### Where in the game Lonlon Ranch, Cocorico Village ### How often Every time ### Graphics card and driver version RX7600 v26.8.1 ### CPU, RAM and operating system Ryzen 5 3600 32GB RAM Win11 ### Changes from the defaults _No response_ ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hos Presentation Thread] vk: bound in guest memory, by pool (the GPU reads these over PCIe; binds and the bytes of their ranges over these 600 submits, 517.4 MB in all, a range counted once a submit): 0x7fd7000000 (96 MB, state 3): 4159 binds, 339 MB; 0x7fbd000000 (96 MB, state 3): 3728 binds, 159 MB; 0x7fde000000 (48 MB, state 3): 529 binds, 19 MB; 0x1144000000 (48 MB, state 3): 132 binds, 0 MB; 0x1052000000 (16 MB, state 3): 47 binds, 0 MB; 0x113f000000 (48 MB, state 3): 17 binds, 0 MB; [hos Presentation Thread] vk: replay reads of guest memory as submitted: 70880000 (41463114 pages from the captures) [hos ModuleSystemWorker5] nvn: 14450000 recordings made, 109097 live copies (29.5 MB), 93831 texture copies; 6 command buffers' segments (4.3 MB) [hos Presentation Thread] nvn: QueueSubmitCommands #740000: queue 000010100C290020 (its #123297), 1 handles (lr 0x805282f4) [hos Presentation Thread] vk: replay reads of guest memory as submitted: 70900000 (41474425 pages from the captures) [hos Presentation Thread] vk: 3 textures retired (2608 left, 2862 MB) [hos Presentation Thread] vk: mirror syncs (600 submits): 408 dirty pages from their submits' captures, 53056 from earlier ones', 0 from guest memory as it was at the replay; 25 captures kept; 0 pages the GPU wrote copied over (0 live); 0 kept for the GPU (RX_VK_PROTECT_BARE) [hos Presentation Thread] vk: read live, by pool: [hos Presentation Thread] vk: bound in guest memory, by pool (the GPU reads these over PCIe; binds and the bytes of their ranges over these 600 submits, 476.1 MB in all, a range counted once a submit): 0x7fbd000000 (96 MB, state 3): 3666 binds, 164 MB; 0x7fd7000000 (96 MB, state 3): 3024 binds, 296 MB; 0x7fde000000 (48 MB, state 3): 458 binds, 16 MB; 0x1144000000 (48 MB, state 3): 155 binds, 0 MB; 0x1052000000 (16 MB, state 3): 45 binds, 0 MB; 0x113f000000 (48 MB, state 3): 17 binds, 0 MB; [hos Presentation Thread] vk: imports: 103 live (4048 MB), 32 retired still imported (1856 MB), 0 retired given back (0 MB) [hos Presentation Thread] vk: program picks: 92907576 kept (40213184 by the last picks' textures, a uniform buffer bound since), 56826 new, 47435597 with other textures (of 140400000) [hos Presentation Thread] vk: 12 textures retired (2604 left, 2861 MB) [hos Presentation Thread] vk: replay reads of guest memory as submitted: 70920000 (41485602 pages from the captures) [hos ModuleSystemWorker1] vk: readbacks of GPU results: 1087 of 3000 waited for their write-back, 0.03 ms each [hos ModuleSystemWorker5] nvn: CommandBufferSignalEvent #2135000: event 0x100c318034 mode 0 value 2134999 (lr 0x806616b0) [hos Presentation Thread] vk: readback pages refreshed from guest memory: 47513986 pages so far (0 held: may be written ahead in their submission) [hos Presentation Thread] vk: capture: a submit 0.65 ms (lock 0.02, scan 0.11 over 763 ranges, 6179 MB), 1344 pages written, 1344 copied (5.3 MB) [hos Presentation Thread] vk: a capture taken (ms): all 1.373; GPU wait for late pages 1.287 (85 of 600 takes), pools lock 0.000, retires and stamps 0.066, bytes copied 0.000; 25 kept (815 MB), 5 spare buffers, 9246 texture pages copied (36 MB) [hos Presentation Thread] vk: replay reads of guest memory as submitted: 70940000 (41495887 pages from the captures) [hos Presentation Thread] vk: mirror syncs (600 submits): 170 dirty pages from their submits' captures, 55180 from earlier ones', 507 from guest memory as it was at the replay; 25 captures kept; 0 pages the GPU wrote copied over (0 live); 0 kept for the GPU (RX_VK_PROTECT_BARE) [hos Presentation Thread] vk: read live, by pool: 0x1064000000 (16 MB, captured, state 2): 161; 0x1055000000 (16 MB, captured, state 2): 111; 0x104b000000 (64 MB, captured, state 2): 74; 0x1050000000 (16 MB, captured, state 2): 72; 0x102d000000 (32 MB, captured, state 2): 42; 0x108a000000 (240 MB, captured, state 2): 34; 0x1036000000 (32 MB, captured, state 2): 4; 0x1158000000 (64 MB, captured, state 2): 2; [hos Presentation Thread] vk: bound in guest memory, by pool (the GPU reads these over PCIe; binds and the bytes of their ranges over these 600 submits, 471.9 MB in all, a range counted once a submit): 0x7fbd000000 (96 MB, state 3): 3743 binds, 153 MB; 0x7fd7000000 (96 MB, state 3): 3056 binds, 302 MB; 0x7fde000000 (48 MB, state 3): 442 binds, 16 MB; 0x1144000000 (48 MB, state 3): 159 binds, 0 MB; 0x1052000000 (16 MB, state 3): 51 binds, 0 MB; 0x113f000000 (48 MB, state 3): 18 binds, 0 MB; [hos Presentation Thread] vk: 2 textures retired (2615 left, 2864 MB) [hos nn.npln.Callback] vcores: 105568 takes, 19314 waits (mean 63 us, longest 36.5 ms), 9131 kicks, 8973 yields, 0 escapes in 5 s [hos rmbl::VibrationThread] hid: 610304 vibration values, strongest 0.00 since the last count [hos sead::MainThread] nvn: GPU waits in 5 s: 1 sync waits (5633 ms), 0 polls timed out (0 ms), 5 queue finishes (1 ms) [hos host] vk: texture 0x10001be6200 1600x1600x1 x3 levels 1 NVN 0x32 (15600 KB of storage) re-uploaded (its memory was written; flags 0x8): a GPU write into its storage, 15600 KB of it, over what the GPU wrote (finalized since) [hos host] vk: submit 863683 failed (-4) [hos host] vk: device lost: reading the buffer markers [hos host] vk: device lost: 153300919 markers set, 61209 reached; the last whose earlier work all finished: 153296587 [hos host] vk: finished before: marker 153296581 (draw of program e63d9ab36296c03d, frame 123350) [hos host] vk: finished before: marker 153296582 (draw of program 418065c6876a3d13, frame 123350) [hos host] vk: finished before: marker 153296583 (draw of program 1115bf68c8fccb16, frame 123350) [hos host] vk: finished before: marker 153296584 (draw of program 136d9555efa9a389, frame 123350) [hos host] vk: finished before: marker 153296585 (write-back of pool 000000102c000000, frame 123350) [hos host] vk: finished before: marker 153296586 (write-back of pool 000000113a000000, frame 123350) [hos host] vk: RUNNING after: marker 153296587 (draw of program 136d9555efa9a389, frame 123350) [hos host] vk: running: marker 153296588 (draw of program 136d9555efa9a389, frame 123350) [hos host] vk: reached, earlier work unfinished: marker 153296588 (draw of program 136d9555efa9a389, frame 123350) [hos host] vk: reached, earlier work unfinished: marker 153296589 (draw of program 136d9555efa9a389, frame 123350) [hos host] vk: reached, earlier work unfinished: marker 153296590 (draw of program 136d9555efa9a389, frame 123350) [hos host] vk: reached, earlier work unfinished: marker 153296591 (draw of program 136d9555efa9a389, frame 123350) [hos host] vk: reached, earlier work unfinished: marker 153296592 (draw of program a6fd6a636241d42e, frame 123350) [hos host] 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) 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) ### 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.

github-sync added the

bug

label

2026-11-12 19:00:49 +00:00

Commenting is not possible because the repository is archived.