HOOKSHOT GITHUB

The program closes

Hookshot keeps crashing

There is no single crash code. The useful sort is the issue number plus the place in the game, then a driver update before anything else.

In-game frame from a Hookshot comparison
Ocarina of Time scene frame from a Hookshot location video

Desktop reports

Issue 317 is a crash in Hyrule Castle Town, tagged as a bug, without a single vendor attached in the summary I read. Issue 648 is an RX 9070 XT that crashes in Hyrule Field on a repeatable path. The log line quoted there is a write to guest address 0 after flags of no memory pool, on the OptimizeChangeBanc thread. Issue 708 is an RX 6600 on v2.0.2 that loses the Vulkan device inside the Deku Tree, and issue 614 is the matching Deku Tree crash title. The readme's general line is to update the driver and to attach hookshot_log.txt plus the four older copies.

Handheld AMD

Issue 997 gathers about 19 people across 11 reports. A Legion Go with the Z1 Extreme goes black and the audio stalls for two or three minutes in the Deku Tree and Navi scenes. An ROG Ally with the same chip, on a 6 GB or Auto frame buffer, lost the device and rebooted the machine with LiveKernelEvent 141. Setting the UMA frame buffer to 8 GB stopped that reboot for the reporter. A 780M on an older driver hit device lost on code 0x80014b in four of five tries. I do not turn the 8 GB frame-buffer change into a universal fix. It is one reporter's result on one Ally.

A crash is not the same report as a black screen that still has audio. If the window stays open and only the picture is dark, use the black-screen page. If the process exits or the GPU resets, stay here and quote the issue that matches the card.

Questions

Is the Deku Tree crash fixed?

Issues 708 and 614 were open as bug reports when they were read on 11 Nov 2026. I do not mark them fixed without a closing note.

What should a comment include?

The readme asks for the GPU, the driver, the place in the game, and hookshot_log.txt.

Sources

Public references and check dates
SourceEvidence statusChecked
Issue 708 1 reference · shared publishers and mirrors count together 2026-11-11
Issue 648 1 reference · shared publishers and mirrors count together 2026-11-11
Issue 997 1 reference · shared publishers and mirrors count together 2026-11-11
Readme 1 reference · shared publishers and mirrors count together 2026-11-11

How we check pages

Related