starred/shadPS4

Fork 0

mirror of https://github.com/shadps4-emu/shadPS4.git synced 2026-04-24 23:36:00 +03:00

[GH-ISSUE #3220] [GAME BUG]: Bloodborne crashes on Intel CPUs (12th gen and up) only on Windows #996

New issue

Open

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

kerem commented

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

Owner

Originally created by @Missake212 on GitHub (Jul 9, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3220

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

This is a known issue and it has already been reported but I'm making a new one, with more details and no misinformation (like the previous one). Using a 12th+ gen CPU in Bloodborne will make you crash, this happens because of different sfx (special effects, not sound effects) being displayed (hence why renaming the sfx folder in your game files allows you to not crash) and only on Windows for some reason, Linux works fine. These crashes are silent as they seem to occur in game code, only way to find more info about this is to run the game in a debugger to get the address.

I've tested a few of these crashes in a debugger to get the address on each one, I've also conducted each of these three times to make sure the address doesn't change. Here are the results:

Getting hit by the first wolf

Swinging your weapon

Shooting with a gun

Falling from a height which causes fall damage

Using D-pad up to get Blood bullets

The good news is that the address stay the same for the same crash, the bad news is that some of these have different address than the others, also something I haven't tested is stuff like swinging different weapons, shooting different guns, falling from different heights, getting hit by different enemies or even attacks etc. This will be a pain to debug but I hope whoever is willing to do it now has enough information to do it, if you need someone to test your potential fixes feel free to ask me directly (missake212 on Discord). That's about all I can do, at least for now.

Reproduction Steps

Easiest way to reproduce this is to launch the game on a system with an Intel CPU 12th gen and up, walk towards the first werewolf and get hit. You can also reproduce this by swinging a weapon (you can swing with your bare hands without crashing), falling from a height that will make you take damage, using D-pad up to gain blood bullets, shooting your gun and numerous other ways. You can use this save file to test it out if you got the hardware for it, I placed myself in front of a ladder to conduct my tests, with it you can directly reproduce everything but getting hit, for that you can just create a new save file and run to the first wolf.

SPRJ0005.zip

Specify OS Version

Windows 11

CPU

Intel Core I9 13900K

GPU

Nvidia RTX 4090

Amount of RAM in GB

32 GB

Amount of VRAM in GB

24 GB

Log File

CUSA03173.log

Originally created by @Missake212 on GitHub (Jul 9, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3220 ### 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/wiki/I.-Quick-start-%5BUsers%5D#4-adding-modules) installed. ### Describe the Bug This is a known issue and it has already been reported but I'm making a new one, with more details and no misinformation (like the previous one). Using a 12th+ gen CPU in Bloodborne will make you crash, this happens because of different sfx (special effects, not sound effects) being displayed (hence why renaming the sfx folder in your game files allows you to not crash) and only on Windows for some reason, Linux works fine. These crashes are silent as they seem to occur in game code, only way to find more info about this is to run the game in a debugger to get the address. I've tested a few of these crashes in a debugger to get the address on each one, I've also conducted each of these three times to make sure the address doesn't change. Here are the results: Getting hit by the first wolf <img width="274" height="402" alt="Image" src="https://github.com/user-attachments/assets/42d7af49-2a68-41ad-a670-b8c915fc5494" /> <img width="296" height="402" alt="Image" src="https://github.com/user-attachments/assets/a1c723b1-3636-40d7-b2d4-af3f0b7330e8" /> <img width="275" height="397" alt="Image" src="https://github.com/user-attachments/assets/5ef68067-e893-40a8-9690-4e47fe31d8f9" /> Swinging your weapon <img width="317" height="573" alt="Image" src="https://github.com/user-attachments/assets/0b509dea-e41a-4ddb-9aed-8f777ae50aa3" /> <img width="287" height="571" alt="Image" src="https://github.com/user-attachments/assets/98f0075e-9abd-4aaf-a6ed-13a903d95801" /> <img width="292" height="572" alt="Image" src="https://github.com/user-attachments/assets/00ecf738-83dc-4ac6-b675-8508abc34c13" /> Shooting with a gun <img width="322" height="393" alt="Image" src="https://github.com/user-attachments/assets/7fe1570b-7e67-4c02-a7d3-6512793a66a6" /> <img width="280" height="400" alt="Image" src="https://github.com/user-attachments/assets/f61c45c2-743e-4be3-af28-6dda88341373" /> <img width="281" height="373" alt="Image" src="https://github.com/user-attachments/assets/b00182c1-834c-4763-bc87-58aa76f43efb" /> Falling from a height which causes fall damage <img width="276" height="383" alt="Image" src="https://github.com/user-attachments/assets/9ad2ccf3-b5ca-49e6-9880-b7742e603d94" /> <img width="286" height="394" alt="Image" src="https://github.com/user-attachments/assets/3c0ee723-93ef-4f3e-8472-6902c9233ef9" /> <img width="275" height="388" alt="Image" src="https://github.com/user-attachments/assets/3e3a1fae-7d3e-4757-abde-588d5438d1d7" /> Using D-pad up to get Blood bullets <img width="274" height="395" alt="Image" src="https://github.com/user-attachments/assets/21b1afde-f4da-49ba-af84-68e0bef0ff75" /> <img width="298" height="414" alt="Image" src="https://github.com/user-attachments/assets/b83392d1-c2f7-4bcf-b1b9-e274e2986629" /> <img width="279" height="387" alt="Image" src="https://github.com/user-attachments/assets/d49d8809-8351-4265-8f3e-84828034a27a" /> The good news is that the address stay the same for the same crash, the bad news is that some of these have different address than the others, also something I haven't tested is stuff like swinging different weapons, shooting different guns, falling from different heights, getting hit by different enemies or even attacks etc. This will be a pain to debug but I hope whoever is willing to do it now has enough information to do it, if you need someone to test your potential fixes feel free to ask me directly (missake212 on Discord). That's about all I can do, at least for now. ### Reproduction Steps Easiest way to reproduce this is to launch the game on a system with an Intel CPU 12th gen and up, walk towards the first werewolf and get hit. You can also reproduce this by swinging a weapon (you can swing with your bare hands without crashing), falling from a height that will make you take damage, using D-pad up to gain blood bullets, shooting your gun and numerous other ways. You can use this save file to test it out if you got the hardware for it, I placed myself in front of a ladder to conduct my tests, with it you can directly reproduce everything but getting hit, for that you can just create a new save file and run to the first wolf. [SPRJ0005.zip](https://github.com/user-attachments/files/21148658/SPRJ0005.zip) ### Specify OS Version Windows 11 ### CPU Intel Core I9 13900K ### GPU Nvidia RTX 4090 ### Amount of RAM in GB 32 GB ### Amount of VRAM in GB 24 GB ### Log File [CUSA03173.log](https://github.com/user-attachments/files/21148648/CUSA03173.log)

kerem added the

Bloodborne

label

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

kerem commented

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

Author

Owner

@StevenMiller123 commented on GitHub (Aug 2, 2025):

Unlocked as requested in #1641

@StevenMiller123 commented on GitHub (Aug 2, 2025): Unlocked as requested in #1641

kerem commented

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

Author

Owner

@shinobuoshin0 commented on GitHub (Aug 3, 2025):

https://www.nexusmods.com/bloodborne/mods/70?tab=files might help to fix

@shinobuoshin0 commented on GitHub (Aug 3, 2025): https://www.nexusmods.com/bloodborne/mods/70?tab=files might help to fix

kerem commented

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

Author

Owner

@Missake212 commented on GitHub (Aug 3, 2025):

@shinobuoshin0 Mods are not fixes, please don't send mods links here that's not the point of this issue.

@Missake212 commented on GitHub (Aug 3, 2025): @shinobuoshin0 Mods are not fixes, please don't send mods links here that's not the point of this issue.

kerem commented

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

Author

Owner

@bigol83 commented on GitHub (Aug 3, 2025):

@shinobuoshin0 Mods are not fixes, please don't send mods links here that's not the point of this issue.

it also says it has issues

@bigol83 commented on GitHub (Aug 3, 2025): > [@shinobuoshin0](https://github.com/shinobuoshin0) Mods are not fixes, please don't send mods links here that's not the point of this issue. it also says it has issues

kerem commented

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

Author

Owner

@carrrrrrrrot commented on GitHub (Nov 28, 2025):

I can replicate the same issue on my old haswell-e CPUs. Here are the logs after being hit by the first wolf, I've tested on two different systems:

shad_log_1660v3.txt
shad_log_5820k.txt

For the record the 1660v3 is on an ASUS motherboard, 5820k on an MSI one

@carrrrrrrrot commented on GitHub (Nov 28, 2025): I can replicate the same issue on my old haswell-e CPUs. Here are the logs after being hit by the first wolf, I've tested on two different systems: [shad_log_1660v3.txt](https://github.com/user-attachments/files/23828954/shad_log_1660v3.txt) [shad_log_5820k.txt](https://github.com/user-attachments/files/23828955/shad_log_5820k.txt) For the record the 1660v3 is on an ASUS motherboard, 5820k on an MSI one

kerem referenced this issue

2026-02-27 21:14:16 +03:00

[PR #996] [MERGED] ci: Refresh CMake cache on build. #1871