MagicBeanDev/Hookshot

Archived

Watch

Fork 0

Black screen and crashing #2370

Closed

opened 2026-11-11 16:18:36 +00:00 by crm0820yt · 4 comments

crm0820yt commented

2026-11-11 16:18:36 +00:00

(Migrated from github.com)

Hookshot version

2.1.0

What kind of problem

Crash, freeze or black screen

What happened

When I enter a certain part in dodongo's cavern, the game freezes, crashes and then it makes my screen go black. It's impossible to go further in the game because that part always crashes

Where in the game

Dodongo's Cavern

How often

Every time

Graphics card and driver version

RX6600,

CPU, RAM and operating system

Ryzen 5 5500, 16GB, Windows 11

Changes from the defaults

No response

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

hookshot_log.3.txt

hookshot_log.1.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 2.1.0 ### What kind of problem Crash, freeze or black screen ### What happened When I enter a certain part in dodongo's cavern, the game freezes, crashes and then it makes my screen go black. It's impossible to go further in the game because that part always crashes ### Where in the game Dodongo's Cavern ### How often Every time ### Graphics card and driver version RX6600, ### CPU, RAM and operating system Ryzen 5 5500, 16GB, Windows 11 ### Changes from the defaults _No response_ ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_log.3.txt](https://github.com/user-attachments/files/34696263/hookshot_log.3.txt) [hookshot_log.1.txt](https://github.com/user-attachments/files/34696270/hookshot_log.1.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.

CrafterSama commented

2026-11-11 18:32:40 +00:00

(Migrated from github.com)

Same Error:

Windows 11
CPU: Ryzen 7 5800X
Memory: 32GB
GPU: RX 6800 XT 16GB

Logs in last logs files:

[hos nn.npln.Callback] vcores: 7393 takes, 37 waits (mean 2 us, longest 0.0 ms), 4 kicks, 1 yields, 0 escapes in 5 s
[hos sead::MainThread] nvn: GPU waits in 5 s: 1 sync waits (5863 ms), 0 polls timed out (0 ms), 5 queue finishes (1 ms)
[hos host] vk: submit 355441 failed (-4)
[hos host] vk: device lost: reading the fault info (RX_VK_CHECKPOINTS=1 for markers)
[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)

[hos Presentation Thread] vk: a capture taken (ms): all 0.006; GPU wait for late pages 0.000 (0 of 600 takes), pools lock 0.000, retires and stamps 0.004, bytes copied 0.000; 25 kept (101 MB), 8 spare buffers, 55 texture pages copied (0 MB)
[hos Presentation Thread] vk: a submit's memory work (ms): maps 0.00, capture taken 0.01, writes collected 0.06
[hos Presentation Thread] vk: mirror syncs (600 submits): 315 dirty pages from their submits' captures, 111504 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] vi: 2320 frames presented (58.7 fps over the last 5.0 s, interval 1)
[hos Presentation Thread] vi: present intervals: <15.5 ms 28, 15.5-17.8 240, 17.8-22 25, 22-30 0, 30-40 0, over 40 1
[hos host] display: window closed, exiting

Same Error: Windows 11 CPU: Ryzen 7 5800X Memory: 32GB GPU: RX 6800 XT 16GB Logs in last logs files: ``` [hos nn.npln.Callback] vcores: 7393 takes, 37 waits (mean 2 us, longest 0.0 ms), 4 kicks, 1 yields, 0 escapes in 5 s [hos sead::MainThread] nvn: GPU waits in 5 s: 1 sync waits (5863 ms), 0 polls timed out (0 ms), 5 queue finishes (1 ms) [hos host] vk: submit 355441 failed (-4) [hos host] vk: device lost: reading the fault info (RX_VK_CHECKPOINTS=1 for markers) [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) ``` ``` [hos Presentation Thread] vk: a capture taken (ms): all 0.006; GPU wait for late pages 0.000 (0 of 600 takes), pools lock 0.000, retires and stamps 0.004, bytes copied 0.000; 25 kept (101 MB), 8 spare buffers, 55 texture pages copied (0 MB) [hos Presentation Thread] vk: a submit's memory work (ms): maps 0.00, capture taken 0.01, writes collected 0.06 [hos Presentation Thread] vk: mirror syncs (600 submits): 315 dirty pages from their submits' captures, 111504 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] vi: 2320 frames presented (58.7 fps over the last 5.0 s, interval 1) [hos Presentation Thread] vi: present intervals: <15.5 ms 28, 15.5-17.8 240, 17.8-22 25, 22-30 0, 30-40 0, over 40 1 [hos host] display: window closed, exiting ```

Nachochist742 commented

2026-11-11 19:46:05 +00:00

(Migrated from github.com)

Is it the area with the dodongos that have to light up the torches?

CrafterSama commented

2026-11-11 19:54:45 +00:00

(Migrated from github.com)

Is it the area with the dodongos that have to light up the torches?

Not my case, I am in the Hyrule Field maybe it's the sunset or something like that

> Is it the area with the dodongos that have to light up the torches? Not my case, I am in the Hyrule Field maybe it's the sunset or something like that

NotRexed commented

2026-11-11 21:29:29 +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.

Commenting is not possible because the repository is archived.