Homepage › Forums › Technical Support › ARMA III – Status Access Violation Error
- This topic has 11 replies, 4 voices, and was last updated Feb 24, 2017 12:27am by BLAs68.
-
AuthorPosts
-
Jan 28, 2017 at 11:52pm #125430BLAs68Participant
0xC0000005 – STATUS_ACCESS_VIOLATION
Any solution found yet for this problem that results because of VorpX and ARMA?
The game worked fine through the first mission, then crashes within 15 minutes the rest of the time. The time before crashing is prolonged but not fixed by running VorpX as admin.
I tried deleting ARMA’s DLLs in its DLL folder which used for the proprietary memory usage software, that some said would fix this error. However. it will not allow ARMA game to even be started.
I am using Freetrack for Oculus Rift to control character head movement.
Jan 31, 2017 at 8:04pm #125613jungleboy123ParticipantHello BLAs68,
Yes i indeed had this same problem when i tried it with vorpx i believ it was 0.9 about a year ago.
I dont think that we can get this resolved soon as far as i am aware.
There remains the issue with battleye compatibility with freetrack, vorpx and other addon software needed to run VR.
I have to say that the 15 minutes i spent playing arma 3 was actually one of the best VR titles with vorpx.
I am sure that a fix will come eventually, but i think this issue is only limited to us because as far as i am aware the guy who made the arma 3 vorpx tutorial on youtube did not experience this issue.
Sorry i couldnt be of more help.
The status access violation error continued to plague me after using VR, so i had to reinstall the entire game (removing mods etc) for it to work.
You could try to disable all mods and try the 64 bit dev build and let me know outcome?
Feb 2, 2017 at 4:22am #125646BLAs68ParticipantThanks for posting. Before I tried to use Arma III in VR, I did a clean install of the game. Clean vanilla for the most part. VorpX wasn’t hooking when I tried first and figured it was BattleEye so I disabled to run the game in VR I’ll try the 64bit dev build when I can and post the results, thanks for letting me know.
It has something to do with their proprietary memory software.
Feb 2, 2017 at 8:35pm #125669jungleboy123ParticipantHello,
I tried setting up VR today with vorpx and can confirm that this issue is still there. It has crashed twice on me since trying, approx 15 mins into the game.
I definately suspect a memory leak/memory issue between vorpx and arma 3. Unfortunately i dont think it will be fixed anytime soon.
I may try to lower my ingame settings to see if that will have an effect.
Feb 5, 2017 at 11:00am #125760nich10soloParticipantI am also getting this error whenever I exit a map, which includes the ‘briefing screen’ at the beginning of most missions. Any ideas?
Feb 5, 2017 at 11:27am #125762RalfKeymasterNo promises, but I’ll look into it. Never heard of this before, maybe there was a recent Arma III update that causes this.
Feb 5, 2017 at 10:29pm #125806jungleboy123ParticipantI believe it seems to work using the 64 bit dev build of arma 3. You might want to try this. I have tried it briefly and it seems to run okay.
The framerate is also higher and less chances of stuttering or screen tear.
Feb 7, 2017 at 11:20pm #125857nich10soloParticipantHey thanks for the replies. I haven’t tried the 64 bit version yet, I’ll look into that.
This is what crashes, from the rpt:
Version 1.66.139586
Fault time: 2017/02/05 04:48:49
Fault address: 60F93671 01:006A2671 C:\Windows\System32\DriverStore\FileRepository\nvami.inf_amd64_01b64dec419235d3\nvwgf2um.dll
file: AliveFeb2017clean (__CUR_MP)
world: Altis
Prev. code bytes: 8B EC 51 53 8B 5A 0C 33 D2 56 57 8B 7D 08 8B C7
Fault code bytes: 0F B7 73 22 F7 F6 8B 43 18 89 4D FC 6A 00 8D 0CIt seems to be a dll related to nvida drivers. This only happens when running vorpx. It doesn’t happen with just running arma 3 normally. It also happens when I don’t have any mods running.
Feb 10, 2017 at 5:53pm #125962jungleboy123ParticipantHey thanks for the replies. I haven’t tried the 64 bit version yet, I’ll look into that.
This is what crashes, from the rpt:
Version 1.66.139586
Fault time: 2017/02/05 04:48:49
Fault address: 60F93671 01:006A2671 C:\Windows\System32\DriverStore\FileRepository\nvami.inf_amd64_01b64dec419235d3\nvwgf2um.dll
file: AliveFeb2017clean (__CUR_MP)
world: Altis
Prev. code bytes: 8B EC 51 53 8B 5A 0C 33 D2 56 57 8B 7D 08 8B C7
Fault code bytes: 0F B7 73 22 F7 F6 8B 43 18 89 4D FC 6A 00 8D 0CIt seems to be a dll related to nvida drivers. This only happens when running vorpx. It doesn’t happen with just running arma 3 normally. It also happens when I don’t have any mods running.
Do you have an AMD card you can test to see if it runs ok?
Feb 21, 2017 at 12:01pm #126247BLAs68ParticipantDid you get a chance to have a run at this issue Ralf?
Feb 23, 2017 at 6:51pm #126274RalfKeymasterI recently made a change to the Z3D renderer that *might*, but really just might, be related to this issue. In Arma III (and some other DX10/11games) there was a chance that under certain circumstances the Z3D renderer potentially could run into problems after some time.
I can’t really say whether that actually is related to your issue though since I couldn’t replicate it.
Feb 24, 2017 at 12:27am #126279BLAs68ParticipantThanks for getting back to us on that. I’ll run ARMA III when I have a chance and post back the results.
-
AuthorPosts
- You must be logged in to reply to this topic.