mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-26 00:05:58 +03:00
[GH-ISSUE #3742] [APP BUG]: Shadps4 crashes (possibly) related to nvidia card driver #1111
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#1111
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 @DangHuy4 on GitHub (Oct 18, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3742
Checklist
Describe the Bug
Hi I was trying to play bloodborne on pc and shadps4 keep crashing out as not responding whenever i try open the game or open the setting. When i go and update the nvidia driver in the nvidia app, I suddenly can open the setting menu. A fascinating fact is when I do, the graphic card selection only shown the AMD card (my cpu) and no NVIDA (GTX 1650). Since my driver was still installing so i didnt try to open the game, however, I think like the setting menu, it could infact openable at that time. After the driver installing is finished, i reopen the emulation and the crashes came back. I thinking it may have some problem with nvidia
Reproduction Steps
Expected Behavior
No response
Specify OS Version
window 10
CPU
AMD R5 5600H
GPU
NVIDIA GTX 1650
Amount of RAM in GB
16 GB
@DangHuy4 commented on GitHub (Oct 18, 2025):
ah shit forgot to mention: I've tried it with 0.4 0.8 and the newest 0.11 version, all came back not responding. The version i used during the driver installation is 0.11
@Missake212 commented on GitHub (Oct 18, 2025):
The 1650 should support everything the emulator needs, it might be an issue with your iGPU here, make sure it's also up to date.
@DangHuy4 commented on GitHub (Oct 18, 2025):
Updating the AMD driver seem to fix it. Thanks man!