MagicBeanDev/Hookshot

Archived

Watch

Fork 0

Game Crash with Green Flickering and Window Flickering #342

Closed

opened 2026-11-07 21:47:01 +00:00 by Kuro-cyber-code · 6 comments

Kuro-cyber-code commented

2026-11-07 21:47:01 +00:00

(Migrated from github.com)

Builder version

latest

How you built

Hookshot Builder app (Windows)

Game files given to it

romfs and exefs folders

The error


1. Main crash

[swscaler @ 000002902F6C2E00] bad dst image pointers
[swscaler @ 000002902F6C2E00] bad dst image pointers

[hos ムービー入力読込] CRASH: exception 0xc0000005 (read 0, guest 0xfffff00000000000) at hookshot.exe+0x1a4fa2dd

[hos ムービー入力読込] CRASH: host backtrace: hookshot.exe+0x1a4fa2dd hookshot.exe+0x190fec72 hookshot.exe+0x1096f091 hookshot.exe+0x1096d4c8 hookshot.exe+0x10970d03 hookshot.exe+0x10647b77 hookshot.exe+0x1064544a hookshot.exe+0x190d6ab2 hookshot.exe+0x190d6ab2 hookshot.exe+0x190d66eb hookshot.exe+0x1a4fb2df hookshot.exe+0x13ee hookshot.exe+0x190dd6d5 KERNEL32.DLL+0x2dda7 ntdll.dll+0x7ee4c

[hos ムービー入力読込] CRASH: thread ムービー入力読込

2. Vulkan / frame timing

[hos Presentation Thread] vk: slow submit: 18.4 ms: draw 18.0 descriptors 17.7 texture lookups 17.6

[hos Presentation Thread] vk: 1320 presents, 48.0 fps; a frame: 6 draws (12 skipped), 2 dispatches, 3 passes, 15 barriers, 6 submits, 0.4 uploads (0.1 MB), 1 ub updates (1 overlays); 79 pipelines (46 ms), 0 programs (10 failed), 56 textures (94 MB)

[hos Presentation Thread] vk: skips a frame by vk_draw.cpp line: 4744: 12.0

3. CPU/thread scheduling

[hos ModuleSystemWorker5] vcores: ModuleSystemWorker5 (priority 16) ran without a core after 250.7 ms: core 5: ムービー入力読込 (17) asked;

[hos ARes Loading 2] vcores: ARes Loading 2 (priority 18) ran without a core after 250.9 ms: core 5: ムービー入力読込 (17) asked;

[hos ARes Loading 0] vcores: ARes Loading 0 (priority 19) ran without a core after 251.4 ms: core 5: ムービー入力読込 (17) asked;

[hos BaseProcExecutor5] vcores: BaseProcExecutor5 (priority 16) ran without a core after 250.5 ms: core 5: ムービー入力読込 (17) asked;

[hos ParallelDecompThread] vcores: ParallelDecompThread (priority 19) ran without a core after 3538.2 ms: core 5: ムービー入力読込 (17) asked;

[hos ParallelDecompThread] vcores: 26606 takes, 2902 waits (mean 2068 us, longest 3538.3 ms), 1039 kicks, 1071 yields, 6 escapes in 6 s

4. AMD telemetry

File:
R-gpu-0-g10-c9-2026-11-7-17-49-59-739.log

GPU: AMD Radeon RX 6600
Driver: 32.0.21045.16010
Driver package: 25.10.45.16-261009a-205305C
Executable referenced: hookshot.exe

5. System configuration

CPU: AMD Ryzen 5 5600
GPU: AMD Radeon RX 6600 8 GB
RAM: 32 GB DDR4
Vulkan: 1.4.315
Vulkan driver: 2.0.353
Windows build: 26200

Visual Studio or Build Tools version, and Windows SDK version

2026

Operating system and free space on the output drive

windows 11 25h2 223 GB free

Before you send it

I'm on the newest release, or it still fails on it.
I searched the open issues for this error.
I'm not attaching game files or anything built from them.

### Builder version latest ### How you built Hookshot Builder app (Windows) ### Game files given to it romfs and exefs folders ### The error ```text 1. Main crash [swscaler @ 000002902F6C2E00] bad dst image pointers [swscaler @ 000002902F6C2E00] bad dst image pointers [hos ムービー入力読込] CRASH: exception 0xc0000005 (read 0, guest 0xfffff00000000000) at hookshot.exe+0x1a4fa2dd [hos ムービー入力読込] CRASH: host backtrace: hookshot.exe+0x1a4fa2dd hookshot.exe+0x190fec72 hookshot.exe+0x1096f091 hookshot.exe+0x1096d4c8 hookshot.exe+0x10970d03 hookshot.exe+0x10647b77 hookshot.exe+0x1064544a hookshot.exe+0x190d6ab2 hookshot.exe+0x190d6ab2 hookshot.exe+0x190d66eb hookshot.exe+0x1a4fb2df hookshot.exe+0x13ee hookshot.exe+0x190dd6d5 KERNEL32.DLL+0x2dda7 ntdll.dll+0x7ee4c [hos ムービー入力読込] CRASH: thread ムービー入力読込 2. Vulkan / frame timing [hos Presentation Thread] vk: slow submit: 18.4 ms: draw 18.0 descriptors 17.7 texture lookups 17.6 [hos Presentation Thread] vk: 1320 presents, 48.0 fps; a frame: 6 draws (12 skipped), 2 dispatches, 3 passes, 15 barriers, 6 submits, 0.4 uploads (0.1 MB), 1 ub updates (1 overlays); 79 pipelines (46 ms), 0 programs (10 failed), 56 textures (94 MB) [hos Presentation Thread] vk: skips a frame by vk_draw.cpp line: 4744: 12.0 3. CPU/thread scheduling [hos ModuleSystemWorker5] vcores: ModuleSystemWorker5 (priority 16) ran without a core after 250.7 ms: core 5: ムービー入力読込 (17) asked; [hos ARes Loading 2] vcores: ARes Loading 2 (priority 18) ran without a core after 250.9 ms: core 5: ムービー入力読込 (17) asked; [hos ARes Loading 0] vcores: ARes Loading 0 (priority 19) ran without a core after 251.4 ms: core 5: ムービー入力読込 (17) asked; [hos BaseProcExecutor5] vcores: BaseProcExecutor5 (priority 16) ran without a core after 250.5 ms: core 5: ムービー入力読込 (17) asked; [hos ParallelDecompThread] vcores: ParallelDecompThread (priority 19) ran without a core after 3538.2 ms: core 5: ムービー入力読込 (17) asked; [hos ParallelDecompThread] vcores: 26606 takes, 2902 waits (mean 2068 us, longest 3538.3 ms), 1039 kicks, 1071 yields, 6 escapes in 6 s 4. AMD telemetry File: R-gpu-0-g10-c9-2026-11-7-17-49-59-739.log GPU: AMD Radeon RX 6600 Driver: 32.0.21045.16010 Driver package: 25.10.45.16-261009a-205305C Executable referenced: hookshot.exe 5. System configuration CPU: AMD Ryzen 5 5600 GPU: AMD Radeon RX 6600 8 GB RAM: 32 GB DDR4 Vulkan: 1.4.315 Vulkan driver: 2.0.353 Windows build: 26200 ``` ### Visual Studio or Build Tools version, and Windows SDK version 2026 ### Operating system and free space on the output drive windows 11 25h2 223 GB free ### Before you send it - [x] I'm on the newest release, or it still fails on it. - [x] I searched the open issues for this error. - [x] I'm not attaching game files or anything built from them.

Kuro-cyber-code commented

2026-11-07 21:59:00 +00:00

(Migrated from github.com)

I’m testing the game port on an AMD Radeon RX 6600 and encountered a crash during gameplay.

The crash appears to happen in the video/movie input thread. Right before the crash, the log reports bad dst image pointers, followed by an access violation (0xc0000005) inside hookshot.exe.

There were also Vulkan performance issues around the same time, including slow submits and skipped frames. A CPU thread also waited for a core for several seconds.

I’m providing the relevant logs below so they can be compared with the port’s behavior on AMD.

I’m testing the game port on an AMD Radeon RX 6600 and encountered a crash during gameplay. The crash appears to happen in the video/movie input thread. Right before the crash, the log reports bad dst image pointers, followed by an access violation (0xc0000005) inside hookshot.exe. There were also Vulkan performance issues around the same time, including slow submits and skipped frames. A CPU thread also waited for a core for several seconds. I’m providing the relevant logs below so they can be compared with the port’s behavior on AMD.

NotRexed commented

2026-11-07 22:20:04 +00:00

(Migrated from github.com)

Thanks for the detailed excerpt. The crash is in the movie playback thread (swscaler ... bad dst image pointers, then an access violation reading address 0), which is a different bug from the flicker. Could you attach the whole hookshot_log.txt from that run (next to hookshot.exe), and say at which point it crashed (opening movie, or a cutscene later on) and whether it happens every time?

Thanks for the detailed excerpt. The crash is in the movie playback thread (`swscaler ... bad dst image pointers`, then an access violation reading address 0), which is a different bug from the flicker. Could you attach the whole `hookshot_log.txt` from that run (next to `hookshot.exe`), and say at which point it crashed (opening movie, or a cutscene later on) and whether it happens every time?

Kuro-cyber-code commented

2026-11-07 22:38:38 +00:00

(Migrated from github.com)

The first crash happened while I was on the way to the Deku Tree. Shortly afterward, I tried to enter the Deku Tree, and the game crashed again.

The crash happens consistently when I try to enter the Deku Tree.

After the crash, I receive an AMD driver error/timeout message, and I have to restart the PC to reset the AMD driver before I can launch the game again. If I try to enter the Deku Tree again, the crash happens at the same point.

So far, the crash appears to be reproducible both on the way to the Deku Tree and when entering the Deku Tree, with the latter happening consistently.

hookshot_log.txt

<img width="359" height="204" alt="Image" src="https://github.com/user-attachments/assets/c78346a2-f116-46b3-b8bc-3dfb91bc528e" /> The first crash happened while I was on the way to the Deku Tree. Shortly afterward, I tried to enter the Deku Tree, and the game crashed again. The crash happens consistently when I try to enter the Deku Tree. After the crash, I receive an AMD driver error/timeout message, and I have to restart the PC to reset the AMD driver before I can launch the game again. If I try to enter the Deku Tree again, the crash happens at the same point. So far, the crash appears to be reproducible both on the way to the Deku Tree and when entering the Deku Tree, with the latter happening consistently. [hookshot_log.txt](https://github.com/user-attachments/files/34529971/hookshot_log.txt)

NotRexed commented

2026-11-08 00:07:45 +00:00

(Migrated from github.com)

Thanks for the log excerpt. '[swscaler] bad dst image pointers' followed by the read of address 0 means a movie picture's memory could not be allocated (the PC was short on memory at that moment) and the movie code went on with no picture. It now checks that, and drops that one frame instead of crashing (024b2a7). That's in the next release; if it still crashes there, please attach the whole hookshot_log.txt.

Thanks for the log excerpt. '[swscaler] bad dst image pointers' followed by the read of address 0 means a movie picture's memory could not be allocated (the PC was short on memory at that moment) and the movie code went on with no picture. It now checks that, and drops that one frame instead of crashing (024b2a7). That's in the next release; if it still crashes there, please attach the whole hookshot_log.txt.

NotRexed commented

2026-11-08 01:02:03 +00:00

(Migrated from github.com)

Fixed in the new release: https://github.com/NotRexed/Hookshot/releases/tag/no-visual-studio (rebuild your game folder with its HookshotBuilder.zip; it no longer needs Visual Studio). If it still happens with it, please reopen with your hookshot_log.txt.

Kuro-cyber-code commented

2026-11-09 15:53:43 +00:00

(Migrated from github.com)

https://youtu.be/wNsl0Di54M0

The AMD driver crash is still occurring. I was recording when the game crashed again, but this time I managed to enter the Deku Tree. It’s less frequent now, but it still happens. I’m using the latest version, 2.0.8. https://youtu.be/wNsl0Di54M0 <img width="356" height="215" alt="Image" src="https://github.com/user-attachments/assets/75cba3f9-1943-43db-8f82-dea62666172b" />

Commenting is not possible because the repository is archived.