[GH-ISSUE #3011] [GAME BUG]: CUSA03173 Bloodborne Crashes on startup ROG ALLY Z1E #957

New issue

Closed

opened 2026-02-27 21:09:09 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 21:09:09 +03:00

Owner

Originally created by @Antagram on GitHub (May 29, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3011

Checklist (we expect you to perform these steps before opening the issue)

I have searched for a similar issue in this repository and did not find one.
I am using an official build obtained from releases or updated one of those builds using its in-app updater.
I have re-dumped the game and performed a clean install without mods and the issue is still present.
I have disabled all patches and cheats and the issue is still present.
I have all the required system modules installed.

Describe the Bug

On my ROG Ally Z1E, with all vcreddist installed an VRAM set on Auto, trying to lunch Bloodborne end up on a crash. I only managed to boot it once. Here is the log:

shad_log.txt

I already tried a clean base shadps4 version, updated and with no patches. Also tried diegolix29 version. Tried the usual patches lowering the res to 484, and mods like vertex fix.

Didn't tried changing VRAM to a fixed value, but this will make all the other games and general system behavior unplayable.

Any idea what could I do?

Reproduction Steps

Install ShadPS4 on ROG Ally Z1E, and update it.
Install Bloodborne and update it.
Launch Bloodborne.

Expected behavior: Launch.
Real behavior: Crash to desktop.

Specify OS Version

Windows 10 Iot Enterprise LTSC 21H2

CPU

AMD Ryzen Z1 Extreme

GPU

AMD Radeon Graphics

Amount of RAM in GB

Amount of VRAM in GB

Auto

Log File

shad_log.txt

Originally created by @Antagram on GitHub (May 29, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3011 ### Checklist (we expect you to perform these steps before opening the issue) - [x] I have searched for a similar issue in this repository and did not find one. - [x] I am using an official build obtained from [releases](https://github.com/shadps4-emu/shadPS4/releases) or updated one of those builds using its in-app updater. - [x] I have re-dumped the game and performed a clean install without mods and the issue is still present. - [x] I have disabled all patches and cheats and the issue is still present. - [x] I have all the required [system modules](https://github.com/shadps4-emu/shadps4-game-compatibility?tab=readme-ov-file#informations) installed. ### Describe the Bug On my ROG Ally Z1E, with all vcreddist installed an VRAM set on Auto, trying to lunch Bloodborne end up on a crash. I only managed to boot it once. Here is the log: [shad_log.txt](https://github.com/user-attachments/files/20511943/shad_log.txt) I already tried a clean base shadps4 version, updated and with no patches. Also tried diegolix29 version. Tried the usual patches lowering the res to 484, and mods like vertex fix. Didn't tried changing VRAM to a fixed value, but this will make all the other games and general system behavior unplayable. Any idea what could I do? ### Reproduction Steps 1. Install ShadPS4 on ROG Ally Z1E, and update it. 2. Install Bloodborne and update it. 3. Launch Bloodborne. Expected behavior: Launch. Real behavior: Crash to desktop. ### Specify OS Version Windows 10 Iot Enterprise LTSC 21H2 ### CPU AMD Ryzen Z1 Extreme ### GPU AMD Radeon Graphics ### Amount of RAM in GB 16 ### Amount of VRAM in GB Auto ### Log File [shad_log.txt](https://github.com/user-attachments/files/20511990/shad_log.txt)

kerem closed this issue

2026-02-27 21:09:09 +03:00

kerem commented

2026-02-27 21:09:10 +03:00

Author

Owner

@StevenMiller123 commented on GitHub (May 29, 2025):

The logs you've provided are from forks, your game dump appears to be modified, and you've got several patches enabled. Please, read those checkboxes you clicked before reporting bugs.

@StevenMiller123 commented on GitHub (May 29, 2025): The logs you've provided are from forks, your game dump appears to be modified, and you've got several patches enabled. Please, read those checkboxes you clicked before reporting bugs.

kerem commented

2026-02-27 21:09:10 +03:00

Author

Owner

@Antagram commented on GitHub (May 29, 2025):

Sorry, I'll open a new one with the right log

@Antagram commented on GitHub (May 29, 2025): Sorry, I'll open a new one with the right log