Rpcs3: Final Fantasy X/X-2 HD [BLES01880]: Mem access violation during bossfight

Created on 4 Sep 2018  路  43Comments  路  Source: RPCS3/rpcs3

  • RPCS3 version: latest master (https://github.com/RPCS3/rpcs3/commit/ca5158a03e5ca66623ff39c8bda7185a51a05e9e)
  • System Specs

    • Intel i5 3450

    • AMD R9 270X

    • 8GB DDR3 RAM

Problem:

Final Fantasy X HD remaster can't be played through because of a fatal error during a boss fight. This error always occurs reproducably.

During the second-last boss fight of the game with Yunalesca, once you defeat her first-stage (24,000HP), the game crashes at the place where the transformation sequence into her second form should play.

路F 0:27:13.311372 {PPU[0x1000000] Thread (main_thread) [0x026551a4]} MEM: Access violation reading location 0x300c6d8
路E 0:27:14.315552 {rsx::thread} RSX: nv406e::semaphore_acquire has timed out. semaphore_address=0x40300400
路! 0:27:48.064769 Stopping emulator...

Related messages for that address

路! 0:15:15.387976 {PPU[0x1000011] Thread (fios mediathread 8) [0x026609ac]} LDR: **** MagicScriptLib export: [0x131A6569] at 0x300c6d8
路E 0:15:15.387978 {PPU[0x1000011] Thread (fios mediathread 8) [0x026609ac]} LDR: Already linked function '0x131A6569' in module 'MagicScriptLib'

Settings:

  • PPU: LLVM
  • SPU: ASMJIT
  • Renderer: Vulkan
  • Preffered SPU Threads: 2, lower SPU thread priority
  • resolution to 1920x1080
  • everything else default
  • all caches were previously cleared

This bug must have existed for a long time, because I've started that playthrough at the beginning of the year and that bug already stopped me, and it's still there.

Attached are the RPCS3 logs and the savefile for easy reproduction.

RPCS3.log.gz
BLES01880SAVEDIR--------------1.zip

Bug

Most helpful comment

This issue is been ongoing for what 2 years and the devs I am guessing have not shown any interest in resolving the issue guessing Final Fantasy X/X-2 HD is not worth the fix

If you read the thread, you would see that Eladash looked into it back in March this year, however sadly he wasn't successful.

RPCS3 is open-source, anyone who wants to is free to investigate the issue and fix it. RPCS3 is in Alpha, looking into game specific issues when there is a slew of major general things to work on is going to be a low priority. There is also 554 issues open right now, and a lot more not reported on GitHub. Not to mention when changes are made sometimes there is a regression.

Be patient, and update the issue every 4-6 months to ensure devs know it is actually still broken other wise they might be wary of even looking at it.

All 43 comments

"resolution to 1920x1080" Don't do this. Can cause lower framerate and incompatibility issues. Use 1280x720 (recommended and default) with 150% resolution scaling or higher. There's only a handful of games that require 1920x1080. That being said FFX likely ran at 1080p on a ps3 or at least close to it.

1080p is natively supported by the game, but I'll try with 720p tomorrow, if that fixes a memory access failure at all..

lol

Lots of games will say they support it, but that doesn't mean they render at 1920x1080. Regardless lots of games have issues when using 1920x1080, and its better to just not use it unless required or you have to use strict rendering mode. Likely won't fix the issue though you might want to try interpreters

Upload TTY as well, the log indicates stuff is being written to TTY.log too

Here are the logfiles for a 720p play, crashes at the exact same place.

Address is slightly different 0x302afe0 this time, maybe ASLR?

RPCS3.log.gz
TTY.log

Likely fixed in the past few days. Retest.

@kd-11: Tested with latest master ed8aa774, this was not fixed. Crashes at the exact same place. I have previously cleared all possible caches.

[...]
路! 0:25:05.571516 {PPU[0x1000011] Thread (fios mediathread 8) [0x026609ac]} LDR: **** MagicScriptLib export: [0x131A6569] at 0x3000390
路E 0:25:05.571518 {PPU[0x1000011] Thread (fios mediathread 8) [0x026609ac]} LDR: Already linked function '0x131A6569' in module 'MagicScriptLib'
[...]
路F 0:27:42.610970 {PPU[0x1000000] Thread (main_thread) [0x026551a4]} MEM: Access violation reading location 0x3000390

Log files are attached.

RPCS3.log.gz
TTY.log

Still occuring on latest master.
logs.zip

I signed up to make this report.

Bug and crash still exist in the 7470-43b75ccf build, can be reproduced consistently and without fail. Always occurs at Yunalesca's first transition after losing 24000 HP. Note that I'm using the NA release, BLUS-31211.

System specs are a 2600K Intel CPU, 980ti card, 16gb of ram, Windows 7 64bit. My system is patched and drivers are up to date.

Crash occurs regardless of settings. I have tried a large variety of settings including up what what is arguably the most "safe mode" with precise decoders, 1 SPU and compile thread(s), Vulkan renderer, default res, and no scaling. The error is same as others reported, MEM: Access violation at xxxxxxx, however the exact address is different. I have tried this with a fresh install of RPCS3 so cache should not be a factor, and always restart the program after making any changes to settings or after any crashes.

One quick addition. I went back to an older build, 7022-3d8223fcc, and the same problem exists. The error is the same MEM access violation at the same address.

Edit - Did some more research. Tried about twenty different builds from the latest 7480 today all the way back to a 0.0.3.6 from Oct of 2017 I found on EmuCR. All produce the same crash, but the exact memory address is varies depending on build date. Also realized I should have posted the log files, apologies for that. The log files below are from the 7480-11681f02 build.
rpcs3.zip

Still occuring in 45942c4962c79f6bac0478c4f2d68851734c5d4f.

TTY.log
RPCS3.log

Finally reached this stage in my playthrough of FFX HD [BLUS31211] and I can confirm that the bug still occurs in ad10eb39. The game is otherwise emulated flawlessly, so it would be really nice to get a fix for this issue.

System specs (Mageia 7 x86_64):

CPU: Quad Core Intel Core i7-8705G (-MT MCP-) speed/min/max: 1032/800/4100 MHz Kernel: 5.1.14-desktop-1.mga7 x86_64 
Up: 2d 6h 27m Mem: 2956.8/15792.2 MiB (18.7%) Storage: 953.87 GiB (44.5% used) Procs: 256 Shell: bash 4.4.23 inxi: 3.0.33 

I'd be happy to provide logs and save files, though I believe the ones in OP might still be relevant.

If anyone can advise on how to get more debugging information around the crash, I can do some testing.

I'd be happy to provide logs and save files, though I believe the ones in OP might still be relevant.

Reproduced the issue anyway on b9130dd6 to be thorough. As for others, the crash is due to a memory access violation:

F {PPU[0x1000000] Thread (main_thread) [0x00549f74]} MEM: Access violation reading location 0x328d378

Steps to reproduce:

  • Use the provided game save
  • Proceed forward to the North, wait through the cutscene until the battle starts
  • To crash quickly, switch character to Yuna (L2 by default to change formation), use Summon > Bahamut. Then cast Bahamut's already preloaded Overdrive (Dpad to the left to see Overdrive action), it should be strong enough to kill Yunalesca's first form and trigger the crash when she starts her transformation.

When it crashes, the game is paused in the debugger, and pressing Play will make the same memory access violation happen again. When I tried, pressing Play several times in a row allowed the game's animation to proceed further by a few frames, until it was fully stuck (at least no visual progress anymore after ~300 presses, FPS at 0.06).

Huh, still occurring. @Nekotekina @kd-11 can you make a patreon donation with a specific request, e.g. to investigate this specific bug? At the one year anniversary of this bug I'd be happy to give you money for this to be fixed.

Not directly, you can't post bounty through patreon.

Upload log with latest master.

0.0.6-8368-c7277605
NPUB31247
F {PPU[0x1000000] Thread (main_thread) [0x00549a64]} MEM: Access violation reading location 0x31e8308
RPCS3.log
TTY.log

Sorry for the delay, my laptop was in repair. I think my logs are similar to @jorgensond's, but uploading nevertheless:

0.0.6-8395 1b140c8e
BLUS31211
RPCS3.log
TTY.log

Would it be useful to take a capture at the moment of the access violation issue?

Can you retest with this build? It's a hack but the answer may lead me to a proper fix.

I tried that Windows build through WINE but the initial PPU compilation was taking ages, so in the end I compiled it from source (current master fcc75c8) + the two patches from https://github.com/elad335/rpcs3/commits/sys_prx

It stalls at the same event. There seems to be one instruction more in the call stack.

RPCS3.log
TTY.log

English only, as other people need to understand what you write

sorry

hello good morning how are you
I'm Laurilucio, Brazil
I have the same problem. the game crashes when I finish Yunalesca in the first stage.
Has anyone figured out how to solve?
Is there anything the user can do to solve this problem?

No, no one has figured out a way around it yet and the problem still exists in the latest builds of RPCS3, If you're already at the final boss, I'd suggest just watching the ending on YouTube. No point in waiting for a fix if you've already got this far in the game, it could take awhile before a dev looks into it.

@akien-mga still issue?

Reupload log if it is.

I tried but rpcs3-v0.0.8-9666-6bb083a7_linux64.AppImage doesn't run on my system (while the last version I tried, rpcs3-v0.0.7-9125-0ff5938b_linux64.AppImage, runs fine):

$ ./rpcs3-v0.0.8-9666-6bb083a7_linux64.AppImage 
DEBUG: 2 log messages accumulated. 178 channels registered.

(no window appears)

I tested rpcs3-v0.0.8-9395-ca5bc512_linux64.AppImage which starts fine. I'll try to bisect further to see what introduces the issue, but I'll move this to a dedicated issue as it's unrelated to FFX.

@elad335 Indeed I just played through this section again and it has crashed at the exact same spot. Latest commit 0.0.8-9680-fa3fde7a Alpha on Win64.

S PPU: LLVM: Compiled module v3-tane-EVSAvVGspAjZSprrCpwwLs-000000-znver1.obj
S {PPU[0x1000011] Thread (fios mediathread 8) [0x028609ac]} sys_prx: Loaded module: /dev_bdvd/PS3_GAME/USRDIR/FFX_Data/GameData/PS3Data/magic/magic_0073.sprx
U {PPU[0x1000000] Thread (main_thread) [0x02861038]} sys_prx TODO: _sys_prx_unload_module(id=0x23016e00, flags=0x0, pOpt=*0x0)
F {PPU[0x1000000] Thread (main_thread) [0x00549f74]} VM: Access violation reading location 0x31f4758 (unmapped memory)

Settings on PPU Decoder: LLVM, SPU: ASMJIT.

Logs attached.

new_logs.zip

still facing the same issue is anyone working on fixing this bug

I'm optimistic #7845 can fix this issue, if not then upload log from the PR.

@elad335 I built 1ceb779 + your PR (as of a few hours ago after a few force pushes, but I see now that it's not the latest state since it was force pushed 30 min ago).

The crash is still reproducible, here's the RPCS3.log (trimmed of a lot of spam due to evdev being temporarily broken on my system):
RPCS3.zip

Try using latest build of the PR.

Hi, I was so happy to play when I got stuck during the fight against Yunalesca, the problem is still present. Anyone knows how to break the glitch\bug?
I am not able to provide the log.zip because when the game crashes the log.zip dissapear.. I have only these 2 files. Hope they will fix it
RPCS3.log
TTY.log

@Joynt94 @zafiraa91 If there was a fix, this issue would be closed. If there was a workaround, it would be documented here. So no, there isn't either.

The best workaround is to watch the ending on YouTube as suggested here: https://github.com/RPCS3/rpcs3/issues/5080#issuecomment-555030437

It is possible to transfer your RPCS3 save file to a real PS3 in order to beat this boss and move on (this is far from the end of the game.) Based on my play-through, this fight is the ONLY problem preventing this game from being playable, so the effort isn't a complete waste of time -- there is quite a bit of hassle in transferring saves from PC to console and back.

hi team,

just adding that i'm experiencing this issue as the users above.
FINAL FANTASY X/X-2 HD Remaster [BLUS31211]

on Linux. Memory access issue. Having trouble uploading logs atm

RPCS3 v0.0.11-10707-ebf83221 Alpha | master | Firmware version: 4.82
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz | 8 Threads | 15.57 GiB RAM | TSC: 3.400GHz | AVX

F {PPU[0x1000000] Thread (main_thread) [0x00549f74]} VM: Access violation reading location 0x301c148 (unmapped memory)s

It is possible to transfer your RPCS3 save file to a real PS3 in order to beat this boss and move on (this is far from the end of the game.) Based on my play-through, this fight is the ONLY problem preventing this game from being playable, so the effort isn't a complete waste of time -- there is quite a bit of hassle in transferring saves from PC to console and back.

Hi jorgensond, I'm experiencing the same issue with people here.. I'm interested with this kind of workaround, it seems there are still no issues from dev til now.. if you willing to help, kindly let me know how to transfer save data from PC to console and back ( as far as I know is using encrypt/decrypt software) or if there is any reference / tutorial on doing it, it would be helpful. thanks

@tejakun The software I used is called 'bruteforce save data'. Google that and you should get a download site and some tutorials. Resigning the files is pretty tricky if you don't happen to know anything about encryption (like me) but I was able to do it after a couple tries. KEEP BACKUPS of all the saves you're working with, in case you need to start over. Good luck!

Hi Team,

I also adding the same issue, the system stopped and show an error VM: Access violation reading location ...
BLUS31211SAVEDIR--------------1.zip
RPCS3.log
TTY.log

FINAL FANTASY X/X-2 HD Remaster [BLUS31211] on windows

error :

路F 0:10:20.705144 {PPU[0x1000000] Thread (main_thread) [0x00549f74]} VM: Access violation reading location 0x301c148 (unmapped memory)

just like other people experiencing on this thread, It always happened with my various of system setting.

my version :
RPCS3 Version: 0.0.12-10904-5ac6f090 Alpha
RPCS3 v0.0.12-10904-5ac6f090 Alpha | HEAD | Firmware version: 4.86
AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx | 8 Threads | 5.94 GiB RAM | TSC: 2.096GHz | AVX+ | FMA3

to replicate the issue (SPOILER ALERT!!):

  1. load my save data using BLUS31211
  2. go through the north 2 times and we'll meet cut scene with yunalesca, after that there will be a fight
  3. defeat yunalesca until her HP reached lower than 24000
    the system stopped.

Any fix from the developer will be highly apprreciated.
please find the attached save data, log and TTY.

Thanks in advance.

@tejakun The software I used is called 'bruteforce save data'. Google that and you should get a download site and some tutorials. Resigning the files is pretty tricky if you don't happen to know anything about encryption (like me) but I was able to do it after a couple tries. KEEP BACKUPS of all the saves you're working with, in case you need to start over. Good luck!

@jorgensond Thank you so much.. anyway , do you still have any of the save data after the fight with yunalesca? , it is okay if it is already too far ..
it will be used as my reference when doing encryption & decryption.

@tejakun I do not.

This issue is been ongoing for what 2 years and the devs I am guessing have not shown any interest in resolving the issue guessing Final Fantasy X/X-2 HD is not worth the fix

This issue is been ongoing for what 2 years and the devs I am guessing have not shown any interest in resolving the issue guessing Final Fantasy X/X-2 HD is not worth the fix

If you read the thread, you would see that Eladash looked into it back in March this year, however sadly he wasn't successful.

RPCS3 is open-source, anyone who wants to is free to investigate the issue and fix it. RPCS3 is in Alpha, looking into game specific issues when there is a slew of major general things to work on is going to be a low priority. There is also 554 issues open right now, and a lot more not reported on GitHub. Not to mention when changes are made sometimes there is a regression.

Be patient, and update the issue every 4-6 months to ensure devs know it is actually still broken other wise they might be wary of even looking at it.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Birch-san picture Birch-san  路  3Comments

Nezarn picture Nezarn  路  3Comments

altiereslima picture altiereslima  路  3Comments

LokiGrants picture LokiGrants  路  3Comments

xiangzhai picture xiangzhai  路  3Comments