+- RPCS3 Forums (https://forums.rpcs3.net)
+-- Forum: Support & Issues (https://forums.rpcs3.net/forumdisplay.php?fid=17)
+--- Forum: Support (https://forums.rpcs3.net/forumdisplay.php?fid=18)
+--- Thread: E {PPU[1] Thread (CPUThread)[0x006ba418]} Exception: Access violation: addr = 0x18d00 (/showthread.php?tid=163368)
RE: E {PPU[1] Thread (CPUThread)[0x006ba418]} Exception: Access violation: addr = 0x18d00 - Cyrax_X(Ru4slan has banned) - 07-11-2014
This error stopped emulation game(Asura Wrath, Hard Corps Uprising, Dead Rising).
Build:3642b26
RE: E {PPU[1] Thread (CPUThread)[0x006ba418]} Exception: Access violation: addr = 0x18d00 - ssshadow - 07-11-2014
And these games worked (better) before this revision?
RE: E {PPU[1] Thread (CPUThread)[0x006ba418]} Exception: Access violation: addr = 0x18d00 - Cyrax_X(Ru4slan has banned) - 07-11-2014
(07-11-2014, 04:47 PM)ssshadow Wrote: And these games worked (better) before this revision?
Yes.Maybe, this games again worked in revision 14050c7(not downloable build)-Not.This problem show again
Very small commit to take care of one thing missing in #409.
Reasons for that change:
<Nekoteki>AlexAltea: it's fatal error that shouldn't be ignored
<Nekoteki>AlexAltea: the second reason, ps3 can handle page faults by
itself
(07-11-2014, 04:47 PM)ssshadow Wrote: And these games worked (better) before this revision?
0x006ba418-this address not always same.
RE: E {PPU[1] Thread (CPUThread)[0x006ba418]} Exception: Access violation: addr = 0x18d00 - ssshadow - 07-11-2014
I think the changes in this build and the last are actually the problem. You could ignore segmentation faults/access violations/read/write to null block before, now you can't, so these games get stuck... Well, it's not that big of a deal anyway, those games would never get further than maybe intro with those errors anyway.
RE: E {PPU[1] Thread (CPUThread)[0x006ba418]} Exception: Access violation: addr = 0x18d00 - Cyrax_X(Ru4slan has banned) - 07-11-2014
(07-11-2014, 04:56 PM)ssshadow Wrote: I think the changes in this build and the last are actually the problem. You could ignore segmentation faults/access violations/read/write to null block before, now you can't, so these games get stuck... Well, it's not that big of a deal anyway, those games would never get further than maybe intro with those errors anyway.
This problem maybe fixed in next time?
RE: E {PPU[1] Thread (CPUThread)[0x006ba418]} Exception: Access violation: addr = 0x18d00 - ssshadow - 07-11-2014
(07-11-2014, 05:00 PM)Cyrax_X(Ru4slan has banned) Wrote:(07-11-2014, 04:56 PM)ssshadow Wrote: I think the changes in this build and the last are actually the problem. You could ignore segmentation faults/access violations/read/write to null block before, now you can't, so these games get stuck... Well, it's not that big of a deal anyway, those games would never get further than maybe intro with those errors anyway.
This problem maybe fixed in next time?
Probably in a longer time frame. The error "Exception: Access violation: addr = 0x18d00" could happen for several different reasons, for example maybe missing cellSpurs. But again, even if you ignored this error the game would still not run without Spurs.
(I hope I am right here in this thread and didn't say anything stupid...)
RE: E {PPU[1] Thread (CPUThread)[0x006ba418]} Exception: Access violation: addr = 0x18d00 - Cyrax_X(Ru4slan has banned) - 07-11-2014
(07-11-2014, 05:03 PM)ssshadow Wrote:I understand.(07-11-2014, 05:00 PM)Cyrax_X(Ru4slan has banned) Wrote:(07-11-2014, 04:56 PM)ssshadow Wrote: I think the changes in this build and the last are actually the problem. You could ignore segmentation faults/access violations/read/write to null block before, now you can't, so these games get stuck... Well, it's not that big of a deal anyway, those games would never get further than maybe intro with those errors anyway.
This problem maybe fixed in next time?
Probably in a longer time frame. The error "Exception: Access violation: addr = 0x18d00" could happen for several different reasons, for example maybe missing cellSpurs. But again, even if you ignored this error the game would still not run without Spurs.
(I hope I am right here in this thread and didn't say anything stupid...)
(07-11-2014, 05:03 PM)ssshadow Wrote:In CoD:Black Ops [BLES01031](07-11-2014, 05:00 PM)Cyrax_X(Ru4slan has banned) Wrote:(07-11-2014, 04:56 PM)ssshadow Wrote: I think the changes in this build and the last are actually the problem. You could ignore segmentation faults/access violations/read/write to null block before, now you can't, so these games get stuck... Well, it's not that big of a deal anyway, those games would never get further than maybe intro with those errors anyway.
This problem maybe fixed in next time?
Probably in a longer time frame. The error "Exception: Access violation: addr = 0x18d00" could happen for several different reasons, for example maybe missing cellSpurs. But again, even if you ignored this error the game would still not run without Spurs.
(I hope I am right here in this thread and didn't say anything stupid...)
RE: E {PPU[1] Thread (CPUThread)[0x006ba418]} Exception: Access violation: addr = 0x18d00 - Nekotekina - 07-11-2014
Option "Ignore read/write errors" has been deleted. I doubt it will appear again (of course, there always is some 0.01% chance).
From my point of view, this option doesn't make any sense. "Access violation" is nothing but this kind of error.
You may think it's regression, but what makes you think so?
RE: E {PPU[1] Thread (CPUThread)[0x006ba418]} Exception: Access violation: addr = 0x18d00 - Cyrax_X(Ru4slan has banned) - 07-11-2014
(07-11-2014, 06:39 PM)NekotekinaHito Wrote: Option "Ignore read/write errors" has been deleted. I doubt it will appear again (of course, there always is some 0.01% chance).
From my point of view, this option doesn't make any sense. "Access violation" is nothing but this kind of error.
You may think it's regression, but what makes you think so?
I do not know
RE: E {PPU[1] Thread (CPUThread)[0x006ba418]} Exception: Access violation: addr = 0x18d00 - ps0ne - 07-12-2014
(07-11-2014, 06:39 PM)NekotekinaHito Wrote: Option "Ignore read/write errors" has been deleted. I doubt it will appear again (of course, there always is some 0.01% chance).Some games do not continue after error and after pressing resume button, while previously were going. Maybe Access violation error in these games are more fatal that in others which actually go on after resume. I believe devs know what are they doing. The culprit is that there will be less reports right now of intro games after the commit than previously with ignore option, until emulation become more completed i think
From my point of view, this option doesn't make any sense. "Access violation" is nothing but this kind of error.
You may think it's regression, but what makes you think so?
