What's new
By:
Filters
Roleplay UK

Join the UK's biggest roleplay community on FiveM and experience endless new roleplay opportunities!

Arma crash

Keven Stewart

Keven Stewart

Well-known member
Unlinked
Location
Bournemouth
Now I ve been having this type of crash since a bit... It happens on all servers, after some minutes of playing.... And also whenever i shoot someone my game crashes it says some  "weird numbers" could not be read.

 bug.PNG

 
Keven Stewart said:
Now I ve been having this type of crash since a bit... It happens on all servers, after some minutes of playing.... And also whenever i shoot someone my game crashes it says some  "weird numbers" could not be read.

 View attachment 5577
Click to expand...
Common problem - happens all the time and can be anything from an arma problem, to memory problem, to driver problem. Here's some reccomendations from BI themselves:

0xC0000005 - ACCESS_VIOLATION

This error is very generic. It may be caused by many issues, such as a hardware malfunction, a virus in the computer, but also an error in the game itself. Possible solutions:

  • Try joining another server, then rejoin the previous one.
  • Update the graphics card drivers to a newer version.
  • Rollback the graphics card drivers to an older version.
  • Check the temperature of your GPUs and CPUs.
  • Verify the integrity of the game cache using Steam.
  • Re-install DirectX.
  • Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again (do not use the Repair function).
  • Run a Windows System File Check tool to repair corrupted system files. (open command prompt and type "sfc /scannow")
 
As it is tied often to audio queues, it would be well worth looking at checking your drivers for your SC/Headset either rolling back or trying other audio settings.

 
To add on to this - for a while Razer peripherals and the software that controls them was causing this kind of issue. It's literally as generic as an error can get.

Also those 'weird numbers' are memory addresses. so I'd focus on driver and memory problems to start with.

lionel said:
As it is tied often to audio queues, it would be well worth looking at checking your drivers for your SC/Headset either rolling back or trying other audio settings.
Click to expand...
Especially if a razer headset.

 
@Zeito here you can have a better look about the second thing i was talking about. Sorry for it being in French

It says: The instruction 0x000.... uses the memory adress 0x0000...... The state of the memory cannot be read.

fu.PNG

 
Last edited by a moderator:
Keven Stewart said:
Nope, but strangely the crash fixed itself..... wtf
Click to expand...
Could simply be a game update / .net update / Windows update / graphics update / headset update ....... This is why we tend to ensure people are on the latest of each item as there you are likely to find everything to be compatible (not always !!) as they all should be adhering to set standards.

 
You must log in or register to reply here.
Back
Top