MagicBeanDev/Hookshot

Archived

Watch

Fork 0

ROG Ally Z1 Extreme - Vulkan device lost and full system reboot after opening cutscene #891

Closed

opened 2026-11-09 00:26:34 +00:00 by losmayorvalencia · 2 comments

losmayorvalencia commented

2026-11-09 00:26:34 +00:00

(Migrated from github.com)

Hookshot version

v2.0.5

What kind of problem

Crash, freeze or black screen

What happened

I'm experiencing a reproducible GPU crash with Hookshot v2.0.5 on my ASUS ROG Ally Z1 Extreme.

What happens:

I launch the game and start a new game.
The entire opening cutscene plays normally.
Immediately after the cutscene ends, when the game should transition into gameplay, the entire ROG Ally crashes and automatically reboots.
This has happened multiple times.

Expected behavior:

The game should transition into gameplay without crashing.

My hardware:

Device: ASUS ROG Ally (original model)
CPU/GPU: AMD Ryzen Z1 Extreme / Radeon RDNA 3
RAM: 16 GB
OS: Windows 11
AMD graphics driver: 32.0.31007.6002
Hookshot: v2.0.5 (source cd9cebb6)
Graphics API: Vulkan

Settings tested:

Resolution: 50%
Frame Generation: Off
Upscaling: Off
Frame Pacing: Off
VRAM allocation: Both 6 GB and Auto

The issue persists with all these settings.

Error information:

Windows Reliability Monitor reported a LiveKernelEvent 141.

One of the Hookshot logs contains:

vk: submit 83674 failed (-4)
vk: device lost: reading the fault info

This corresponds to VK_ERROR_DEVICE_LOST.

I have attached the Hookshot logs from multiple attempts.

Is this a known compatibility issue with AMD Ryzen Z1 Extreme integrated graphics? Is there a workaround or a planned fix?

Thank you for your work!

hookshot_log.1.txt
hookshot_log.2.txt
hookshot_log.3.txt
hookshot_log.4.txt
hookshot_log.txt

Where in the game

Immediately after the opening cutscene, during the transition to gameplay in Kokiri Forest.

How often

Every time

Graphics card and driver version

AMD Radeon Graphics (Ryzen Z1 Extreme, RDNA 3), driver 32.0.31007.6002

CPU, RAM and operating system

AMD Ryzen Z1 Extreme, 16 GB LPDDR5 RAM, Windows 11

Changes from the defaults

Quality preset: Custom
Resolution: 50%
Frame Generation: Off
Frame Pacing: Off
Upscaling: Off
Sharpness: 0%
Fullscreen: Off
GPU Device: Auto
Handheld Profile: Off
Robust Buffers: Auto
VRAM allocation in Armoury Crate: tested with 6 GB and Auto
AMD Fluid Motion Frames and Radeon Anti-Lag: Disabled

The system crashes and reboots after the opening cutscene with these settings.

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

hookshot_log.1.txt
hookshot_log.2.txt
hookshot_log.3.txt
hookshot_log.4.txt
hookshot_log.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 v2.0.5 ### What kind of problem Crash, freeze or black screen ### What happened I'm experiencing a reproducible GPU crash with Hookshot v2.0.5 on my ASUS ROG Ally Z1 Extreme. **What happens:** 1. I launch the game and start a new game. 2. The entire opening cutscene plays normally. 3. Immediately after the cutscene ends, when the game should transition into gameplay, the entire ROG Ally crashes and automatically reboots. 4. This has happened multiple times. **Expected behavior:** The game should transition into gameplay without crashing. **My hardware:** - Device: ASUS ROG Ally (original model) - CPU/GPU: AMD Ryzen Z1 Extreme / Radeon RDNA 3 - RAM: 16 GB - OS: Windows 11 - AMD graphics driver: 32.0.31007.6002 - Hookshot: v2.0.5 (source cd9cebb6) - Graphics API: Vulkan **Settings tested:** - Resolution: 50% - Frame Generation: Off - Upscaling: Off - Frame Pacing: Off - VRAM allocation: Both 6 GB and Auto The issue persists with all these settings. **Error information:** Windows Reliability Monitor reported a LiveKernelEvent 141. One of the Hookshot logs contains: ``` vk: submit 83674 failed (-4) vk: device lost: reading the fault info ``` This corresponds to VK_ERROR_DEVICE_LOST. I have attached the Hookshot logs from multiple attempts. Is this a known compatibility issue with AMD Ryzen Z1 Extreme integrated graphics? Is there a workaround or a planned fix? Thank you for your work! [hookshot_log.1.txt](https://github.com/user-attachments/files/34558319/hookshot_log.1.txt) [hookshot_log.2.txt](https://github.com/user-attachments/files/34558318/hookshot_log.2.txt) [hookshot_log.3.txt](https://github.com/user-attachments/files/34558320/hookshot_log.3.txt) [hookshot_log.4.txt](https://github.com/user-attachments/files/34558321/hookshot_log.4.txt) [hookshot_log.txt](https://github.com/user-attachments/files/34558322/hookshot_log.txt) ### Where in the game Immediately after the opening cutscene, during the transition to gameplay in Kokiri Forest. ### How often Every time ### Graphics card and driver version AMD Radeon Graphics (Ryzen Z1 Extreme, RDNA 3), driver 32.0.31007.6002 ### CPU, RAM and operating system AMD Ryzen Z1 Extreme, 16 GB LPDDR5 RAM, Windows 11 ### Changes from the defaults - Quality preset: Custom - Resolution: 50% - Frame Generation: Off - Frame Pacing: Off - Upscaling: Off - Sharpness: 0% - Fullscreen: Off - GPU Device: Auto - Handheld Profile: Off - Robust Buffers: Auto - VRAM allocation in Armoury Crate: tested with 6 GB and Auto - AMD Fluid Motion Frames and Radeon Anti-Lag: Disabled The system crashes and reboots after the opening cutscene with these settings. ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_log.1.txt](https://github.com/user-attachments/files/34558375/hookshot_log.1.txt) [hookshot_log.2.txt](https://github.com/user-attachments/files/34558376/hookshot_log.2.txt) [hookshot_log.3.txt](https://github.com/user-attachments/files/34558374/hookshot_log.3.txt) [hookshot_log.4.txt](https://github.com/user-attachments/files/34558377/hookshot_log.4.txt) [hookshot_log.txt](https://github.com/user-attachments/files/34558378/hookshot_log.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.

🚀 1

kai2143 commented

2026-11-09 00:30:41 +00:00

(Migrated from github.com)

This was happening to me too and i didnt know what the problem was, Windows security thought it was a virus or something so I said to allow the program, also i turned my memory assigned to gpu to 8G instead of auto and it works now without rebooting. the only problem now is listed here #830

NotRexed commented

2026-11-09 06:00:36 +00:00

(Migrated from github.com)

Tracked in #997, follow there. That issue collects every report of AMD handhelds and APUs: black screen, device lost or reboot, and this one is linked from it with its GPU, version and log details. If it still happens on v2.0.6 (https://github.com/NotRexed/Hookshot/releases/tag/v2.0.6; Update next to Play in the launcher), please add a comment there with your hookshot_log.txt.

👍 1

Commenting is not possible because the repository is archived.