[GH-ISSUE #2408] [GAME BUG]: Bloodborne game screen is frozen and the background sound is still playing. #808

New issue

Closed

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

kerem commented

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

Owner

Originally created by @lmutig on GitHub (Feb 12, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2408

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

It was probably after mid-December that the emulator had this problem, but it was only now that I couldn't stand it anymore that I brought it up.
The last time it happened was in this emulator: Build and Release #3977,shadps4-win64-qt-main-02-10-b51c767
There is no mod installed in the game. I wear a helmet that can completely cover the face of the character.
I didn't disable the patch because 30 frames was unbearable. But this is really problematic, because I started playing Bloodborne in September, and this has never happened before. This problem didn't appear when using patches during this period of time.
I also asked some of my friends who also like Bloodborne. One of my friends with a 1650 graphics card also has this problem.
It's just that my situation is more serious. Every time a bug happens, I can't do any other actions about the window, otherwise my computer will get stuck, and I have to manually press the restart button of the computer to recover.

Reproduction Steps

I don't know how to reproduce it. It appears randomly. Sometimes it appears after playing for five minutes, and sometimes it takes half an hour to an hour.

Specify OS Version

Windows10 22H2

CPU

Intel core i5 10400

GPU

nVidia 2060 (Desktop)

Amount of RAM in GB

32GB

Amount of VRAM in GB

6GB

Log File

I don't know why the log file can't be uploaded, but
Every time this bug happens, the last line of the log file will display the following red content:
[Lib.Kernel] time.cpp:114 sceKernelClockGettime: unsupported = 16 using CLOCK_REALTIME

Originally created by @lmutig on GitHub (Feb 12, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2408 ### 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. - [] 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 It was probably after mid-December that the emulator had this problem, but it was only now that I couldn't stand it anymore that I brought it up. The last time it happened was in this emulator: Build and Release #3977,shadps4-win64-qt-main-02-10-b51c767 There is no mod installed in the game. I wear a helmet that can completely cover the face of the character. I didn't disable the patch because 30 frames was unbearable. But this is really problematic, because I started playing Bloodborne in September, and this has never happened before. This problem didn't appear when using patches during this period of time. I also asked some of my friends who also like Bloodborne. One of my friends with a 1650 graphics card also has this problem. It's just that my situation is more serious. Every time a bug happens, I can't do any other actions about the window, otherwise my computer will get stuck, and I have to manually press the restart button of the computer to recover. ### Reproduction Steps I don't know how to reproduce it. It appears randomly. Sometimes it appears after playing for five minutes, and sometimes it takes half an hour to an hour. ### Specify OS Version Windows10 22H2 ### CPU Intel core i5 10400 ### GPU nVidia 2060 (Desktop) ### Amount of RAM in GB 32GB ### Amount of VRAM in GB 6GB ### Log File I don't know why the log file can't be uploaded, but Every time this bug happens, the last line of the log file will display the following red content: [Lib.Kernel] <Error> time.cpp:114 sceKernelClockGettime: unsupported = 16 using CLOCK_REALTIME

kerem closed this issue

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

kerem commented

2026-02-27 21:08:17 +03:00

Author

Owner

@roamic commented on GitHub (Feb 12, 2025):

The checklist is not optional for a reason. Patches are not officially supported and provided only as a courtesy to the community. Mods are not supported either and can cause more issues than they solve. This is why we need testers to test as clean of a game as it can possibly be. If you are not a tester and just looking for the support I encourage you to close this issue and ask people on the discord to help.

@roamic commented on GitHub (Feb 12, 2025): The checklist is not optional for a reason. Patches are not officially supported and provided only as a courtesy to the community. Mods are not supported either and can cause more issues than they solve. This is why we need testers to test as clean of a game as it can possibly be. If you are not a tester and just looking for the support I encourage you to close this issue and ask people on the discord to help.

kerem commented

2026-02-27 21:08:17 +03:00

Author

Owner

@polybiusproxy commented on GitHub (Feb 12, 2025):

Closing as invalid due to lack of log file and use of patches. If you're unable to upload a log due to size limitations, you can compress it.

@polybiusproxy commented on GitHub (Feb 12, 2025): Closing as invalid due to lack of log file and use of patches. If you're unable to upload a log due to size limitations, you can compress it.

kerem referenced this issue

2026-02-27 21:13:56 +03:00

[PR #808] [CLOSED] Inv godess #1783