mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-25 07:46:01 +03:00
[GH-ISSUE #2399] [GAME BUG]: Bloodborne Crashing - Not HTTP Related but unsure why #810
Labels
No labels
Bloodborne
bug
contributor wanted
documentation
enhancement
frontend
good first issue
help wanted
linux
pull-request
question
release
verification progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shadPS4#810
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FreshVegetables-Please on GitHub (Feb 10, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2399
Checklist (we expect you to perform these steps before opening the issue)
Describe the Bug
The crash seems random and not caused by any one thing.
I am unsure exactly why my game is crashing, I tried searching some of these different lines and nothing has appeared to be common for me.
I have already disabled the HTTP Requests which I thought were the cause of the random crashes.
The only thing I've changed since then was I added the vortex explosion mod fix which doesn't seem to be an issue for anyone else, and it did seem to fix my vortex explosions.
Anyone got any ideas?
Reproduction Steps
Not sure how to reproduce, the crashes happen at random intervals.
Specify OS Version
Windows 11
CPU
AMD Ryzen 7 7700X 8-Core Processor, 16 CPUS, ~4.5GHz
GPU
AMD Radeon RX 7900 XT
Amount of RAM in GB
36GB
Amount of VRAM in GB
20GB
Log File
shad_log.txt
@FreshVegetables-Please commented on GitHub (Feb 11, 2025):
It seems like now all of a sudden my character starts walking sometimes instead of running. My controller works fine on other games and it just started happening after turning on/off Vsync, trying to fix the screen tearing (which is also still happening)
@polybiusproxy commented on GitHub (Feb 12, 2025):
Closing due to lack of system modules. One of the required items in the checklist is: