rpcs3
rpcs3 copied to clipboard
Metal gear solid 4 error: Access violation writing location 0x68 (unmapped memory)
Quick summary
I am getting the following error sometimes when I play the game. It can be in 10 minutes playing or 1 hour:
F {PPU[0x1000001] Thread (MGS4 MAIN) [0x0013f204]} VM: Access violation writing location 0x68 (unmapped memory)
The game crashes.
Details
No response
Attach a log file
Attach capture files for visual issues
No response
System configuration
No response
Other details
No response
Bad settings and no canary patches, go to wiki for optimal settings and the required patches for the game.
Like @ItsALH said, enable the "Crash fix" canary patch.
That being said, this issue should probably be left open so it can be properly fixed.
@ItsALH and @cipherxof , thank you. I applied the canary patch (only the fix for 0x68 crash checkbox), I will test it for a while and see if it works. This is my first time using the canary patch. For those that don't know how to apply:
I followed this step on Reddit post: https://www.reddit.com/r/rpcs3/comments/mixu2q/finally_got_mgs4_to_run_on_rpcs3_using_canary/
I will post in some weeks if it works, to help anyone else too.
Hello Brothers, thanks a lot for sharing the fixes, just wanted to share that my Canary fix was already on but the game continued to crash
FIX : I initially had shadows disabled (via Patches), but enabling the shadows back on seems to have fixed it for me. The Canary fix is awesome, but remember to leave shadows on if someone faces this issue
Note : No performance impact with shadows turned on
I have the same issue with crash fix on, Ryzen 5 5600X, GTX1060, Windows 10 22H2
Hello, I Have the same issue on the Rog Ally. I have the canary patches crash fix and CellSpurs 4.91 on (i'm on firmware 4.91) and wiki settings. Crash happen especially when quitting start menu or codec.
Your log has an entirely different crash.
{RSX [0x00210e4]} VM: Access violation reading location 0x68272a00 (unmapped memory)
Thank you for your answer My mistake, i will create a new issue