When I face the Dodongo king, it freezes and everything on the PC shuts down #2081

Closed

opened 2026-11-11 01:56:32 +00:00 by titissg · 3 comments

titissg commented

2026-11-11 01:56:32 +00:00

(Migrated from github.com)

Hookshot version

2.0.14

What kind of problem

Crash, freeze or black screen

What happened

When I face the boss, it freezes for about 3 seconds, the whole screen goes black, and it closes everything I have open.

Where in the game

dodongo´s cavern

How often

Every time

Graphics card and driver version

Rx 6650XT 32.0.21045.2006

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

Screenshots or video

https://1024terabox.com/s/1rrlkZQJ582ryRAcqlj4CGw

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.0.14 ### What kind of problem Crash, freeze or black screen ### What happened When I face the boss, it freezes for about 3 seconds, the whole screen goes black, and it closes everything I have open. ### Where in the game dodongo´s cavern ### How often Every time ### Graphics card and driver version Rx 6650XT 32.0.21045.2006 ### 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.txt](https://github.com/user-attachments/files/34666026/hookshot_log.txt) ### Screenshots or video https://1024terabox.com/s/1rrlkZQJ582ryRAcqlj4CGw ### 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.

Arkex-ai commented

2026-11-11 02:03:15 +00:00

(Migrated from github.com)

The attached log records an access violation in amdvlk64.dll+0x319b63 on the Presentation Thread, reading address 0x38. That identifies where this run faulted, but it does not yet tell us whether the trigger is a renderer command, resource state or a driver defect.

Do you also see this on v2.1.0-rc.2, and does it happen with frame generation off? If you have a new failing run, please add RX_VK_CHECKPOINTS=1 to hookshot_env.txt beside the game and attach the resulting log. AMD buffer markers are enabled when supported. Please also say whether Windows recovered the display by itself or the PC needed a restart.

The attached log records an access violation in `amdvlk64.dll+0x319b63` on the Presentation Thread, reading address `0x38`. That identifies where this run faulted, but it does not yet tell us whether the trigger is a renderer command, resource state or a driver defect. Do you also see this on v2.1.0-rc.2, and does it happen with frame generation off? If you have a new failing run, please add `RX_VK_CHECKPOINTS=1` to `hookshot_env.txt` beside the game and attach the resulting log. AMD buffer markers are enabled when supported. Please also say whether Windows recovered the display by itself or the PC needed a restart.

titissg commented

2026-11-11 04:04:17 +00:00

(Migrated from github.com)

Now the game runs worse, like 50% less performance, it has FPS drops and the textures don't load properly
the screen comes back

hookshot_log.txt

Now the game runs worse, like 50% less performance, it has FPS drops and the textures don't load properly the screen comes back [hookshot_log.txt](https://github.com/user-attachments/files/34669508/hookshot_log.txt)

NotRexed commented

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