[GH-ISSUE #835] Crash at loading Bloodborne #223

New issue

Closed

opened 2026-02-27 21:05:14 +03:00 by kerem · 4 comments

kerem commented

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

Owner

Originally created by @Dictavios on GitHub (Sep 7, 2024).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/835

For me, v.1.00 of the game works as I can reach gameplay. Problem is when update to 1.09, since it no longer launch the game anymore. Last thing I can read before it closes is a kernel warning regarding memory, in yellow letters. I'll share the log.
Specs are:
Rx6600
i5 10400f
16gb ram
Tried all emu Winqt builds from yesteday to now on
shad_log.txt

Originally created by @Dictavios on GitHub (Sep 7, 2024). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/835 For me, v.1.00 of the game works as I can reach gameplay. Problem is when update to 1.09, since it no longer launch the game anymore. Last thing I can read before it closes is a kernel warning regarding memory, in yellow letters. I'll share the log. Specs are: Rx6600 i5 10400f 16gb ram Tried all emu Winqt builds from yesteday to now on [shad_log.txt](https://github.com/user-attachments/files/16918815/shad_log.txt)

kerem closed this issue

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

kerem commented

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

Author

Owner

@Dictavios commented on GitHub (Sep 7, 2024):

[Kernel.Vmm] memory_management.cpp:sceKernelGetDirectMemorySize:19: called
[Kernel.Vmm] memory_management.cpp:sceKernelAllocateDirectMemory:51: searchStart = 0x0, searchEnd = 0x120000000, len = 0x7400000, alignment = 0x200000, memoryType = 0x0, physAddrOut = 0x0
[Kernel.Vmm] memory_management.cpp:sceKernelMapDirectMemory:177: called, redirected to sceKernelMapNamedDirectMemory
[Kernel.Vmm] memory_management.cpp:sceKernelMapNamedDirectMemory:150: addr = 0x0, len = 0x7400000, prot = 0x3, flags = 0x0, directMemoryStart = 0x0, alignment = 0x200000

@Dictavios commented on GitHub (Sep 7, 2024): [Kernel.Vmm] <Warning> memory_management.cpp:sceKernelGetDirectMemorySize:19: called [Kernel.Vmm] <Info> memory_management.cpp:sceKernelAllocateDirectMemory:51: searchStart = 0x0, searchEnd = 0x120000000, len = 0x7400000, alignment = 0x200000, memoryType = 0x0, physAddrOut = 0x0 [Kernel.Vmm] <Info> memory_management.cpp:sceKernelMapDirectMemory:177: called, redirected to sceKernelMapNamedDirectMemory [Kernel.Vmm] <Info> memory_management.cpp:sceKernelMapNamedDirectMemory:150: addr = 0x0, len = 0x7400000, prot = 0x3, flags = 0x0, directMemoryStart = 0x0, alignment = 0x200000

kerem commented

2026-02-27 21:05:15 +03:00

Author

Owner

@dogoawesomeness256 commented on GitHub (Sep 7, 2024):

wait for the newest build of bb-hacks and also make sure you downloaded the Bloodborne FPS Boost 1.0 which is apart of the Bloodborne Visual Tweaks mod pack on nexus

@dogoawesomeness256 commented on GitHub (Sep 7, 2024): wait for the newest build of bb-hacks and also make sure you downloaded the Bloodborne FPS Boost 1.0 which is apart of the Bloodborne Visual Tweaks mod pack on nexus

kerem commented

2026-02-27 21:05:15 +03:00

Author

Owner

@dogoawesomeness256 commented on GitHub (Sep 7, 2024):

thank you fromsoftserve for making this mod your one of the most talented people pushing for bloodborne to be playable on pc

@dogoawesomeness256 commented on GitHub (Sep 7, 2024): thank you fromsoftserve for making this mod your one of the most talented people pushing for bloodborne to be playable on pc

kerem commented

2026-02-27 21:05:15 +03:00

Author

Owner

@Hermiten commented on GitHub (Oct 1, 2024):

I suggest you use the latest version and open a new ticket if necessary.

@Hermiten commented on GitHub (Oct 1, 2024): I suggest you use the latest version and open a new ticket if necessary.

kerem referenced this issue

2026-02-27 21:12:25 +03:00

[PR #223] [MERGED] Metadata support #1406