Rpcs3: Access violation reading 0x10010010 on specific stage places and missions [BLES02057]

Created on 5 May 2018  ·  32Comments  ·  Source: RPCS3/rpcs3

CPU: Intel i7-7500u
GPU: Intel HD Graphics 620
RAM: 16GB
SSD
RPCS3 v0.0.5-6694-25ec899cf Alpha
PPU: LLVM Recompiler
SPU: ASMJIT
Renderer: Vulkan

Dynasty Warriors Gundam Reborns (BLES02057)
I get this error every time i get to a part of the stage. I can get to other stages and make it trough the end and not get the error at all. I have tried changing the PPU , SPU and renderer

F {PPU[0x100002f] Thread (CStageSceneBuilder) [0x0021dfc4]} MEM: Access violation reading location 0x10010010

Most helpful comment

Made a patch that lets you get ingame, it probably breaks stuff but at least it's something while you wait for a proper fix.
put in patch.yml

PPU-da76bae72f6d8fef4865e63c4e75e91d8b7204ac: #Dynasty Warriors Gundam Reborn BLES02057 hack
  - [be32, 0x212494, 0x63e30000]

PPU-d526f54bfa95c26ecb612318f58a49c62ea53915: #Dynasty Warriors Gundam Reborn NPUB31531 hack
  - [be32, 0x212464, 0x63e30000]

image

All 32 comments

Mem access violation doesn't mean anything by itself, needs more information, a log is the least.

Tested with build 0.0.5 7006: core i7 8700K, Nvidia 1080ti error still persists
BLES02057 LLVM.zip

@Tom-Neverwinter does this happen to you also #4632 I also notice this happens with Gundam Crossbone.

I do not currently have access to Gundam Crossbone

and Wing Zero Endless Waltz? I have another thread about the broken graphics i get while using him. Wanted to know if its just me.

Tested with #5082 and i still get the F {PPU[0x100002f] Thread (CStageSceneBuilder) [0x0021dfc4]} MEM: Access violation reading location 0x10010010 when starting certain missions or going to certain places in some stages. Just updating the issue.

·W 0:04:16.348216 {PPU[0x1000000] Thread (main_thread) [0x00bfdd60]} sys_ppu_thread: _sys_ppu_thread_create(thread_id=*0xd001ffc0, param=*0xd001ff00, arg=0x21d364a0, unk=0x0, prio=1011, stacksize=0x2000, flags=0x1, threadname=“CStageSceneBuilder”)
·F 0:15:40.441481 {PPU[0x100002f] Thread (CStageSceneBuilder) [0x0021dfc4]} MEM: Access violation reading location 0x10010010

Relevant part

So @AniLeo any word on when will this get worked
RPCS3.log.gz

Not possible to say, games are usually not randomly investigated to find issues with the emulator unless the developer is looking into a specific issue that requires it, this can be fixed by:

  • Continuous updates to the emulator that will eventually fix whatever is causing this issue (most likely)

  • Someone wanting to specifically investigate and debug this game and find out what is happening (less likely)

Who know? maybe in this year or next. Year to year emulator fix many more issues so i belive its been fix but when?.

if no developer pays attention i doubt of a fix we waited for more than a year since game is boot-able .
Still thanks to devs for what we have so far but again my doubts on fix coming if with general fixes.

Almost all issues are fixed with general fixes, and a year is really not much in this kind of development timelines, I waited more than a year for a small vdec bugfix to go Ingame on S;G0 a couple of years ago and it eventually came

Made a patch that lets you get ingame, it probably breaks stuff but at least it's something while you wait for a proper fix.
put in patch.yml

PPU-da76bae72f6d8fef4865e63c4e75e91d8b7204ac: #Dynasty Warriors Gundam Reborn BLES02057 hack
  - [be32, 0x212494, 0x63e30000]

PPU-d526f54bfa95c26ecb612318f58a49c62ea53915: #Dynasty Warriors Gundam Reborn NPUB31531 hack
  - [be32, 0x212464, 0x63e30000]

image

THANK YOU SO MUCH FOR THE PATCH I SALUTE YOU ! YOU FIXED A GREAT thing., NOW I CAN FINALLY MOD THIS GAME AND MAKE AI Moves usable by player!
GOD BLESS YOU!

Ani:
i am sure it will come eventually. Still as I said we are grateful for what so far has been achieved and i admit PS2 and PS3 age games ...they were the last good games generation after that its complete UNFUN and Money grinding generation made not for FUN factor but for micros.

God bless all developers and all who work and help and contribute!

Sorry for the pushup I am glad it WORKED!

yeah thx. patch works fine.

Will it be merged into master?

https://youtu.be/0s2f7JyNWrI
here is the mod i develop for the game.
Now thanks to isJuhn this is possible

@isJuhn This pacth can work in BLES02057 and NPUB31531, but it can not fix the same error in BLAS50682. And they are the same game. So if you can solve it easily, please help us . If not, just let it go.

RPCS3.zip

I need a log from crash with ppu interpreter to translate the patch to another serial

Here,thanks
RPCS3.log.gz

you didn't use PPU interpreter and you didn't crash, I can't do anything with that log

but when I crashed, it disappeared

ok, I got one , it is useful? and sorry about it @isJuhn
RPCS3.log

you're still using ppu llvm instead of interpreter but I tried anyway

PPU-3cea7a3a766105e781d7cd3379c569baf7a565e8: #Dynasty Warriors Gundam Reborn BLAS50682 hack
  - [be32, 0x214D14, 0x63e30000]

!!!! thanks too much !!!!!!

ok , I know what your mean now, but it is useless. and I take it again by PPU interpreter. Sorry about I wasted your time. @isJuhn
RPCS3.log

try this

PPU-3cea7a3a766105e781d7cd3379c569baf7a565e8: #Dynasty Warriors Gundam Reborn BLAS50682 hack
  - [be32, 0x214C08, 0x63e30000]

...useless and other PPU interpreter ( precise ) , thanks again. @isJuhn
RPCS3.log

@isJuhn Is there a patch that works with BLJM61140?
I really want to play...
RPCS3.log

Just dropped by to check if there's anything new involving the crashes. Sadly nothing new here for slightly over a year...

CPU: AMD Ryzen 5 3600x
GPU: AMD Radeon RX 570
RAM: 16GB
SSD
RPCS3 v0.0.13-11304-3f028fbb Alpha
PPU: LLVM Recompiler
SPU: LLVM Recompiler
Renderer: OpenGL

Shin Gundam Musou (BLJM61140)
I'm aware that the patches was provided above, but not for BLJM61140.
Still, it also provides the exact same error of this

F {PPU[0x1000036] Thread (CStageSceneBuilder) [0x00202354]} VM: Access violation reading location 0x10010010 (unmapped memory) [type=u0]
Recompiler (LLVM) log: RPCS3.log.gz
Interpreter (precise) log: RPCS3.log.gz RPCS3.log.gz

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Luffykun007 picture Luffykun007  ·  3Comments

kurosh10000 picture kurosh10000  ·  3Comments

Nezarn picture Nezarn  ·  3Comments

elad335 picture elad335  ·  3Comments

JohnGodgames picture JohnGodgames  ·  3Comments