Page MenuHomeFeedback Tracker

After 1.46 update: Crash when connecting to multiplayer server, "The instruction at 0x.. referenced memory at 0x.."
Closed, ResolvedPublic

Description

My game has started crashing while connecting to a multiplayer server. It always crashes at the same spot on the loading bar after choosing your unit to spawn in to on the server. The error started to occur for me after the 1.46 patch was applied.

More specifically it appears when I have established a connection to the server, chosen my unit to spawn into, and pressed "continue" to join the game. I will attach a screenshot of what it looks like when the error occurs.

The error reads: "The instruction at 0x0bb9854f referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program.".

After this it is common to see an error message pop up from the toolbar saying that the display driver has stopped working and recovered, how ever it is not always seen.

After the error has terminated ArmA, most other programs (for example Paint, Task manager, Arma 3 launcher) I try to start gets the windows error "Application X has stopped working".

The only time this error isn't appearing (and the only way for me to play Arma 3 anymore) is for me to restart my computer and, as unlikely as it sounds, quickly start the game and log into a server without doing anything before it. This generally works, but if I try alt-tabbing for more than a minute or so the game crashes, and sometimes it crashes spontaneously after playing a few minutes on the server as well. {F26527}

Details

Legacy ID
1451869952
Severity
None
Resolution
Open
Reproducibility
Always
Category
Game Crash
Steps To Reproduce
  1. Start ArmA 3
  2. Connect to a multiplayer server
  3. Choose your position to spawn in as
  4. Wait for the game to crash while Arma 3 is loading
Additional Information

I have tried resolving the issue by:

*Removing Arma 3 launch options
*Verifying integrity of Arma 3 through Steam
*Uninstalling and reinstalling Arma 3
*Removing all forms of overclocking to my hardware
*Running SFC to scan for bad windows files
*Running Windows Memory Diagnostic to ensure my RAM is okay
*Uninstalling antivirus software
*Removing background applications
*Updating BIOS, graphics drivers, DirectX drivers, etc
*Performing clean install of graphics driver

My computer specifications are as follows:
CPU: Intel i7 5930k
Motherboard: Asus X99-Deluxe
Graphics card: NVidia GTX 980
RAM: 4x4GB DDR4-2133
1000W PSU
Running the game with G-Sync and in the resolution 2560x1440.

Event Timeline

Aquila21 edited Steps To Reproduce. (Show Details)Jun 29 2015, 6:27 PM
Aquila21 edited Additional Information. (Show Details)
Aquila21 set Category to Game Crash.
Aquila21 set Reproducibility to Always.
Aquila21 set Severity to None.
Aquila21 set Resolution to Open.
Aquila21 set Legacy ID to 1451869952.May 8 2016, 12:17 PM
Adam added a comment.Jun 30 2015, 7:57 AM

Hello,
Thank you for reporting the issue.
We need crash dump files from this folder to analyze your problem.
C:\Users\<Name>\AppData\Local\Arma 3\
Can you upload somewhere in winrar package, please?
Archive smaller than 5000 KB can be attached directly to the ticket. For bigger archives, please use some free sharing service and post link here.

How to find correct crashdump file:
Try to make the crash happen
Look into crashdump folder
Upload crashdump with latest date in name (crashdump is rpt + bidmp + mdmp file with same name). Please try to provide as many crashdumps as possible, it helps us investigating the problem in a big way.

Thank you.

http://feedback.arma3.com/how-to-user.html

Hi!

I attached 10 .rpt files in a winrar package together with my dxdiag info and screenshot of crash (where the application always freezes & error message). Those were all the files from the arma 3 folder, no .bidmp or .mdmp files were present.

I've found one .mdmp and a bunch of .rpt files in the arma 3 launcher folder, are those relevant?

Is there something I need to do to make it save the .bidmp and .mdmp files when it crashes?

Thanks,
Johan

Edit: Is the Arma 3 Launcher responsible for saving those extra logs? Because it always crashes just after arma 3 has crashed.

Adam added a comment.Jun 30 2015, 11:28 AM

Could you please attach the newest .RPT file right after your game crashes? Thanks.

Absolutely, the new .RPT is uploaded, "arma3_2015-06-30_12-29-51.rpt".

Thanks

Edit: Not sure if it's helpful but the arma 3 launcher .rpt says this at the time of the game crashing:

2015-06-30 12:31:47,265 [DEBUG] 4: ArmaExecutor [Launcher.ArmaExecutor+<>cDisplayClass4+<<MonitorBattlEyeProcess>b3>d__6.MoveNext:0] BattlEye output code read: 0xFFFFFFFF

2015-06-30 12:31:47,266 [ INFO] 3: ArmaExecutor [Launcher.ArmaExecutor.armaProc_Exited:0] Arma exited (ExitCode: -1073741819)

Adam added a comment.Jun 30 2015, 1:36 PM

Try some of the solutions that are posted here:
https://community.bistudio.com/wiki?title=Arma_3_Unusual_process_exit&redirect=no#0xC0000005_-_ACCESS_VIOLATION

If that does not work please get back to me. Thanks!

I have now tried the solutions with out any result.

The only oddity I encountered was the SFC /scannow-solution which said it had found some corrupted files but was unable to repair them. The same thing happened when I tried to run it in safe mode.

Edit: I also ran Memtest86 to ensure my RAM was indeed good condition.

Regarding the SFC scan showing corrupted files; There is a Windows update KB3022345 (KB3068708) that will make SFC fail when there is nothing wrong. CBS.log shows utc.app.json and telemetry.ASM-WindowsDefault.json as corrupt but they are known false positives. Removing the update can fix the SFC issue, but it doesn't affect the error with the game.

rogerx added a comment.Jul 6 2015, 6:41 AM

I can reproduce this bug pretty redundantly by logging into the 69th Infantry Division (http://sixnine.enjin.com/) and using the "FSG Gunner" profile. Setup a mortar bipod/tripod using the ammo truck in the parking lot, assembling the mortar next to the ammo truck. Lob some flares/HE rounds and after awhile, the game crashes. Not sure if a "FSG UAV operator" spotting enemy is also required to reproduce the crashes.

Sometimes I can go for awhile without seeing a crash, but the bug is pretty imminent in that it will eventually appear regardless.

Adam added a comment.Jul 27 2015, 2:20 PM

Could you please attach your Dxdiag? Thank you.

I, myself, have reinstalled "MS C++ x86 redistributable" and haven't seen a crash so far, although I've also upgraded from RC to 1.48.

So it's completely unknown if 1.48 or the redistributable solved the problem for me. I think I have seen one sporadic crash since, but I didn't bother spending time trying to forcefully extract details using this operating system.

If this were Linux/Unix based, I'd have the log files copied and compressed within several seconds.

Guess we'll wait and see if the original author is still experiencing this bug.

dedmen closed this task as Resolved.May 18 2020, 11:08 AM