starred/shadPS4

Fork 0

mirror of https://github.com/shadps4-emu/shadPS4.git synced 2026-04-26 16:25:58 +03:00

[GH-ISSUE #2891] [APP BUG]: Game had trouble detecting VRAM unless launched from a shortcut #930

New issue

Closed

opened 2026-02-27 21:08:57 +03:00 by kerem · 3 comments

kerem commented

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

Owner

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

Checklist

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.

Describe the Bug

Bloodborne had issues starting one day due to it thinking i had too little VRAM, no issues the day before i ran it smoothly at 60 fps with no problems and then suddenly i can't even start it

[Loader] emulator.cpp:124 Run: Starting shadps4 emulator v0.8.1 WIP
[Loader] emulator.cpp:125 Run: Revision 15da121174273d543ef919e9b6465143f7152a8c
[Loader] emulator.cpp:126 Run: Branch Full-Souls
[Loader] emulator.cpp:127 Run: Description 15da121
[Loader] emulator.cpp:128 Run: Remote ttps://github.com/diegolix29/shadPS4
[Config] emulator.cpp:130 Run: General LogType: sync
[Config] emulator.cpp:131 Run: General isNeo: false
[Config] emulator.cpp:132 Run: GPU isNullGpu: false
[Config] emulator.cpp:133 Run: GPU shouldDumpShaders: false
[Config] emulator.cpp:134 Run: GPU vblankDivider: 1
[Config] emulator.cpp:135 Run: Vulkan gpuId: 0
[Config] emulator.cpp:136 Run: Vulkan vkValidation: false
[Config] emulator.cpp:137 Run: Vulkan vkValidationSync: false
[Config] emulator.cpp:138 Run: Vulkan vkValidationGpu: false
[Config] emulator.cpp:139 Run: Vulkan crashDiagnostics: false
[Config] emulator.cpp:140 Run: Vulkan hostMarkers: false
[Config] emulator.cpp:141 Run: Vulkan guestMarkers: false
[Config] emulator.cpp:142 Run: Vulkan rdocEnable: false
[Loader] emulator.cpp:145 Run: Game id: CUSA03173 Title: Bloodborne™
[Loader] emulator.cpp:146 Run: Fw: 0x4000000 App Version: 01.09
[Debug] address_space.cpp:82 operator(): Assertion Failed!
Unable to reserve virtual address space: Not enough memory resources are available to process this command.

[process exited with code 2147483651 (0x80000003)]

This is the error that i got and i started troubleshooting on the discord, we tried
Same, spent like 4 hours with the good samaritans on the shadps4 discord trying to fix it but we couldn't get it to work. We tried

Disabling Memory integrity and Control flow
Disable one drive
Change the pagefile size on all my drives
Change do Diegolix version of shadps4
Change to then nightly version
Downgrade to 0.7 or even 0.6
Update bios on my B-650E
Close down programs to free up Vram and RAM
Turn off windows defender
Change the file to my desktop or the drive my windows is installed on
Install Visual C++
Apply the 360p patch
Try to start the game with NULL Gpu
Change Vblank Divider from 1 to 4

But nothing worked, then i saw a post on the reddit about several other people that had the exact same issue, it worked on the 7th and stopped working on the 8th and someone suggested creating a desktop shortcut and launching the game from that which worked. So I'm wondering if launching it through the emulator causes some issue with recognizing the VRAM?

My specs are:
2x16gb 6000mhz ram sticks
Ryzen 7 9800x3d
RTX 3070 8gb vram
ASUS TUF 650E Wifi motherboard

Reproduction Steps

Launching it from the shortcut is the only way to fix it

Expected Behavior

I expected the game to launch from the emulator menu but it does not, only the shortcut works

Specify OS Version

Windows 11

CPU

Ryzen 9800x3d

GPU

RTX 3070 8gb

Amount of RAM in GB

32GB 6000mhz

Originally created by @pontarn00 on GitHub (May 9, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2891 ### Checklist - [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. ### Describe the Bug Bloodborne had issues starting one day due to it thinking i had too little VRAM, no issues the day before i ran it smoothly at 60 fps with no problems and then suddenly i can't even start it [Loader] <Info> emulator.cpp:124 Run: Starting shadps4 emulator v0.8.1 WIP [Loader] <Info> emulator.cpp:125 Run: Revision 15da121174273d543ef919e9b6465143f7152a8c [Loader] <Info> emulator.cpp:126 Run: Branch Full-Souls [Loader] <Info> emulator.cpp:127 Run: Description 15da121 [Loader] <Info> emulator.cpp:128 Run: Remote ttps://github.com/diegolix29/shadPS4 [Config] <Info> emulator.cpp:130 Run: General LogType: sync [Config] <Info> emulator.cpp:131 Run: General isNeo: false [Config] <Info> emulator.cpp:132 Run: GPU isNullGpu: false [Config] <Info> emulator.cpp:133 Run: GPU shouldDumpShaders: false [Config] <Info> emulator.cpp:134 Run: GPU vblankDivider: 1 [Config] <Info> emulator.cpp:135 Run: Vulkan gpuId: 0 [Config] <Info> emulator.cpp:136 Run: Vulkan vkValidation: false [Config] <Info> emulator.cpp:137 Run: Vulkan vkValidationSync: false [Config] <Info> emulator.cpp:138 Run: Vulkan vkValidationGpu: false [Config] <Info> emulator.cpp:139 Run: Vulkan crashDiagnostics: false [Config] <Info> emulator.cpp:140 Run: Vulkan hostMarkers: false [Config] <Info> emulator.cpp:141 Run: Vulkan guestMarkers: false [Config] <Info> emulator.cpp:142 Run: Vulkan rdocEnable: false [Loader] <Info> emulator.cpp:145 Run: Game id: CUSA03173 Title: Bloodborne™ [Loader] <Info> emulator.cpp:146 Run: Fw: 0x4000000 App Version: 01.09 [Debug] <Critical> address_space.cpp:82 operator(): Assertion Failed! Unable to reserve virtual address space: Not enough memory resources are available to process this command. [process exited with code 2147483651 (0x80000003)] This is the error that i got and i started troubleshooting on the discord, we tried Same, spent like 4 hours with the good samaritans on the shadps4 discord trying to fix it but we couldn't get it to work. We tried Disabling Memory integrity and Control flow Disable one drive Change the pagefile size on all my drives Change do Diegolix version of shadps4 Change to then nightly version Downgrade to 0.7 or even 0.6 Update bios on my B-650E Close down programs to free up Vram and RAM Turn off windows defender Change the file to my desktop or the drive my windows is installed on Install Visual C++ Apply the 360p patch Try to start the game with NULL Gpu Change Vblank Divider from 1 to 4 But nothing worked, then i saw a post on the reddit about several other people that had the exact same issue, it worked on the 7th and stopped working on the 8th and someone suggested creating a desktop shortcut and launching the game from that which worked. So I'm wondering if launching it through the emulator causes some issue with recognizing the VRAM? My specs are: 2x16gb 6000mhz ram sticks Ryzen 7 9800x3d RTX 3070 8gb vram ASUS TUF 650E Wifi motherboard ### Reproduction Steps Launching it from the shortcut is the only way to fix it ### Expected Behavior I expected the game to launch from the emulator menu but it does not, only the shortcut works ### Specify OS Version Windows 11 ### CPU Ryzen 9800x3d ### GPU RTX 3070 8gb ### Amount of RAM in GB 32GB 6000mhz

kerem closed this issue

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

kerem commented

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

Author

Owner

@TakimuraRen commented on GitHub (May 9, 2025):

We are the same, bro. I also have 32GB of memory, and I have experienced the same situation as you, but it was normal a few days ago.

@TakimuraRen commented on GitHub (May 9, 2025): We are the same, bro. I also have 32GB of memory, and I have experienced the same situation as you, but it was normal a few days ago.

kerem commented

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

Author

Owner

@MajorP93 commented on GitHub (May 9, 2025):

@pontarn00 your log shows that you are using a fork (“Branch Full-Souls”).
You should use use an official build, otherwise there will most probably be no support.

@MajorP93 commented on GitHub (May 9, 2025): @pontarn00 your log shows that you are using a fork (“Branch Full-Souls”). You should use use an official build, otherwise there will most probably be no support.

kerem commented

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

Author

Owner

@StevenMiller123 commented on GitHub (May 9, 2025):

[Debug] address_space.cpp:82 operator(): Assertion Failed!
Unable to reserve virtual address space: Not enough memory resources are available to process this command.

This is a known bug which is being mass-reported at the moment. It also has nothing to do with your device's VRAM or RAM.
It's related to some issue with how Windows works, and will probably get handled at some point.

Your report is invalid due to the use of a fork. If you can reproduce this behavior on the current official main builds, please open a new report.

@StevenMiller123 commented on GitHub (May 9, 2025): ``` [Debug] address_space.cpp:82 operator(): Assertion Failed! Unable to reserve virtual address space: Not enough memory resources are available to process this command. ``` This is a known bug which is being mass-reported at the moment. It also has nothing to do with your device's VRAM or RAM. It's related to some issue with how Windows works, and will probably get handled at some point. Your report is invalid due to the use of a fork. If you can reproduce this behavior on the current official main builds, please open a new report.

kerem referenced this issue

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

[PR #930] [CLOSED] Sort opcodes by their indices. Group them too when applicable #1835