{RSX [0x02a6238]} VM: Access violation reading location 0xcf900000 (unmapped memory) (Dynasty Warriors 8 XL)

[Archim119]

The game crashes when entering a stage, always within the first few seconds. I can get through a few minutes of the tutorial before the same happens.

Debug console mode changes the error from: F {RSX [0x0399668]} VM: Access violation reading location 0xcf900000 (unmapped memory)

To: F {PPU[0x1000000] Thread (main_thread) [0x00441ca4]} VM: Access violation writing location 0x0 (unmapped memory)

RPCS3.log

[jy95]

@Archim119 Did you use a RPCS3 patch ? I got a similar message on another game https://github.com/RPCS3/rpcs3/issues/8985

[Archim119]

@jy95 With or without patches enabled, the game still freezes at the same point. Did you manage to get yours to work?

I've tried enabling certain libraries to solve the issue, while it does get rid of the access violation it is then replaced with this: E {PPU[0x1000000] Thread (main_thread) [0x014b8a30]} SYS: 'sys_mutex_create' failed with 0x80010005 : CELL_ESRCH [1]

I've also tried disabling accurate LLVM DFMA, but that didn't work either.

[Darkhost1999]

Last comment is approximately 2 years old. Is this still an issue?

[Jimertons]

@Darkhost1999 yes, sadly still an issue

[KirkixSaturnex]

I've recently come back to emulating PS3 games and after playing most of my favorite games i played Dynasty Warriors 8 and i discovered this crash too. I tested the game for a while and now i discovered the issue and why this happens. It is a problem with the rendering of the level of detail with the soldiers. After a few seconds the game crashes because the game has an issue with loading the low level of details of the soldiers. The RAM has an error that might just be one byte that is unmapped. This error happens on every Dynasty Warriors 8 version, including the japanese and chinese versions, except Dynasty Warriors 8 Empires. I made a screenshot of one of my last tests and this is my conclusion. You can finish the tutorial and you can finish every stage but you need to point the camera at the floor to not load the low level of details and if there are not enough soldiers around you could look up but only in the tutorial. This screenshot is the frame that is crashed on. This is literally 60 frames after the low level of detail of this one soldier was loaded

[ReLyf47]

3 years later and still not fixed

although i got a different access violation code F {RSX [0x004cfbc]} VM: Access violation reading location 0xcf90f7c0 (unmapped memory) which might or might not help the dev figure something out

Game ID is: NPJB00511 (DW8XL JPN Digital version)

[elad335]

Upload updated log and savedata.

[elad335]

I think I figured it out: We assume that the highest vertex index is the frequency divider when modulo op is used because there are vetex indices higher than it. But in reality we should do max_index = max(index % frequency, max_index) for each index. This is of course slower, but it can be optimized to not do it if we have a lot of free memory range left.

[ReLyf47]

RPCS3.log.gz NPJB00510-SAVEDATA.zip

Here is my log and savedata (mind you im not the original poster) and also save data is maybe useless, due to the crash literally happening on any stage that you starts

[elad335]

WIP

[elad335]

Test #14505

[ReLyf47]

sorry for not replying i couldnt test DW8XL since i deleted the game install both from PS3 and RPCS3 and would not rather redownload a 23GB game on my current network situation

BUT i have another DW game that suffer from the same issue and surprise surprise using #14505 build it worked

this was the error code before i used the build 0xcf906420 (nearly identical with DW8XL error code) and here is my log for this other DW game (BLJM61347) RPCS3.log.gz

as pointed out on the comments in #14505 the fallback handler "This sucks" appears also 1x every like 1-2 second

[QJYEAH]

WIP

RPCS3.log the game sometimes still be crashed

[ReLyf47]

Somewhere in the update broke this again RPCS3.log.gz

Last known good build: Honestly idk probably #14505

Old error code: 0xcf906420 New error code: 0xcf905960

seems like its in the same ballpark of issue

[QJYEAH]

RPCS3.log crashed is still exist