ROG Ally Z1 Extreme: Windows BSOD VIDEO_SCHEDULER_INTERNAL_ERROR when loading a save (v2.1.0-rc.3-256-g51da0464) #2891

Open

opened 2026-11-12 19:01:04 +00:00 by github-sync · 1 comment

github-sync commented

2026-11-12 19:01:04 +00:00

Owner

@mokmeuh opened on GitHub · 2026-11-12 18:33 UTC · original

Hookshot version

v2.1.0-rc.3-256-g51da0464

What kind of problem

Crash, freeze or black screen

What happened

Loading a save from the save selection screen right after launch crashes the whole device with the Windows bugcheck VIDEO_SCHEDULER_INTERNAL_ERROR (a BSOD). Expected: the save loads and the game runs.

It happens every time.
It happens with several different save files, so it is not one bad save.
It worked yesterday on the same setup.
Same result with the main build and with the dev build.
Same result with the newest AMD driver and with the older one (I went back to 32.0.23027.3001).
Same result with and without OptiScaler.

The end of the latest hookshot_log.txt shows VK_ERROR_DEVICE_LOST (see the log field). This looks like the AMD handheld device-lost family in #997.

Where in the game

Save selection screen at launch, right after choosing a save to load

How often

Every time

Graphics card and driver version

AMD Radeon Graphics (ROG Ally Z1 Extreme iGPU, 6 GB UMA), driver 32.0.23027.3001 (2026-02-25)

CPU, RAM and operating system

AMD Ryzen Z1 Extreme, about 18 GB RAM visible to Windows (6 GB UMA frame buffer), Windows 11 Home 10.0.26200

Changes from the defaults

Settings in hookshot_options.ini: quality_preset=0, handheld_profile=1, output_res=1920x1080, resolution=3, upscaling=1, amd_anti-lag_2=1, fullscreen=1, vram_budget=4. frame_generation=2 and mesh_shaders=1 originally; I have also tried both off.
OptiScaler is installed in the game folder; I tested with and without it.
I did not have a hookshot_env.txt when the crashes happened.

Other software hooked into the game

Yes (named under "Changes from the defaults")

hookshot_log.txt

End of the latest hookshot_log.txt (paths removed). I can attach the full file if needed.

[hos host] hookshot v2.1.0-rc.3-256-g51da0464 (source 18ed87b5)
[hos host] boot: 18129 MB of memory, 24144 MB of swap
[hos sead::MainThread] vk: a capture's wait for write-back 18985 timed out (done 18981)
[hos sead::MainThread] vk: slow submit: 264.7 ms: memory sync 264.1
[hos Presentation Thread] vk: submit 18993 failed (-4)
[hos Presentation Thread] vk: device lost: reading the fault info (RX_VK_CHECKPOINTS=1 for markers)
[hos Presentation Thread] vk: FATAL: the GPU device was lost (VK_ERROR_DEVICE_LOST)

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.

> [@mokmeuh](https://github.com/mokmeuh) opened on GitHub · 2026-11-12 18:33 UTC · [original](https://github.com/NotRexed/Hookshot/issues/2891) ### Hookshot version v2.1.0-rc.3-256-g51da0464 ### What kind of problem Crash, freeze or black screen ### What happened Loading a save from the save selection screen right after launch crashes the whole device with the Windows bugcheck `VIDEO_SCHEDULER_INTERNAL_ERROR` (a BSOD). Expected: the save loads and the game runs. - It happens every time. - It happens with several different save files, so it is not one bad save. - It worked yesterday on the same setup. - Same result with the main build and with the dev build. - Same result with the newest AMD driver and with the older one (I went back to 32.0.23027.3001). - Same result with and without OptiScaler. The end of the latest hookshot_log.txt shows `VK_ERROR_DEVICE_LOST` (see the log field). This looks like the AMD handheld device-lost family in #997. ### Where in the game Save selection screen at launch, right after choosing a save to load ### How often Every time ### Graphics card and driver version AMD Radeon Graphics (ROG Ally Z1 Extreme iGPU, 6 GB UMA), driver 32.0.23027.3001 (2026-02-25) ### CPU, RAM and operating system AMD Ryzen Z1 Extreme, about 18 GB RAM visible to Windows (6 GB UMA frame buffer), Windows 11 Home 10.0.26200 ### Changes from the defaults Settings in hookshot_options.ini: quality_preset=0, handheld_profile=1, output_res=1920x1080, resolution=3, upscaling=1, amd_anti-lag_2=1, fullscreen=1, vram_budget=4. frame_generation=2 and mesh_shaders=1 originally; I have also tried both off. OptiScaler is installed in the game folder; I tested with and without it. I did not have a hookshot_env.txt when the crashes happened. ### Other software hooked into the game Yes (named under "Changes from the defaults") ### hookshot_log.txt End of the latest hookshot_log.txt (paths removed). I can attach the full file if needed. ``` [hos host] hookshot v2.1.0-rc.3-256-g51da0464 (source 18ed87b5) [hos host] boot: 18129 MB of memory, 24144 MB of swap [hos sead::MainThread] vk: a capture's wait for write-back 18985 timed out (done 18981) [hos sead::MainThread] vk: slow submit: 264.7 ms: memory sync 264.1 [hos Presentation Thread] vk: submit 18993 failed (-4) [hos Presentation Thread] vk: device lost: reading the fault info (RX_VK_CHECKPOINTS=1 for markers) [hos Presentation Thread] vk: FATAL: the GPU device was lost (VK_ERROR_DEVICE_LOST) ``` ### 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:01:04 +00:00

github-sync commented

2026-11-12 19:03:31 +00:00

Author

Owner

@mokmeuh commented on GitHub · 2026-11-12 18:51 UTC · original

Update: it no longer crashes. With VRAM at 4.8 the save loads and the game runs. This may be solved, but I changed several things together, so I can't say which one fixed it:

updated to the latest nightly, v2.1.0-rc.3-267-g1c0cd980 (the report above was on v2.1.0-rc.3-256-g51da0464)
VRAM set to 4.8
vram_budget=3 (was 4)
mesh_shaders=0 (was 1)
frame_generation=0 (was 2)
new hookshot_env.txt with RX_VK_PER_QUEUE_FENCES=0 and RX_VK_FORCE_MESH_FALLBACK=1 (from the workaround in #997); the log now says no mesh shaders: task and mesh programs run as compute shaders

Same device and same driver (32.0.23027.3001) as in the report above. I'm leaving the issue open in case someone wants to narrow down which change matters.

> [@mokmeuh](https://github.com/mokmeuh) commented on GitHub · 2026-11-12 18:51 UTC · [original](https://github.com/NotRexed/Hookshot/issues/2891#issuecomment-6832887601) Update: it no longer crashes. With VRAM at 4.8 the save loads and the game runs. This may be solved, but I changed several things together, so I can't say which one fixed it: - updated to the latest nightly, `v2.1.0-rc.3-267-g1c0cd980` (the report above was on `v2.1.0-rc.3-256-g51da0464`) - VRAM set to 4.8 - `vram_budget=3` (was 4) - `mesh_shaders=0` (was 1) - `frame_generation=0` (was 2) - new `hookshot_env.txt` with `RX_VK_PER_QUEUE_FENCES=0` and `RX_VK_FORCE_MESH_FALLBACK=1` (from the workaround in #997); the log now says `no mesh shaders: task and mesh programs run as compute shaders` Same device and same driver (32.0.23027.3001) as in the report above. I'm leaving the issue open in case someone wants to narrow down which change matters.

Commenting is not possible because the repository is archived.