Game crashing: EXCEPTION_ACCESS_VIOLATION

Raysor

Hi everyone,

I’ve been running into a frustrating issue with FAF, and I’m hoping someone here might have some insights or advice. Here’s the situation:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x0095854f attempted to write memory at 0x02fef000

What’s Happening:

The game keeps crashing, and based on the logs, it looks like it might have something to do with the M28AI mod—specifically the script M28Engineer.lua. From what I can tell, the script could be trying to interact with a "Game object" that’s already been destroyed. That’s just a theory though, and I’m open to any other ideas or suggestions.

Key Things I’ve Noticed:

1. Memory Exception (0xc0000005):
The error EXCEPTION_ACCESS_VIOLATION (0xc0000005) shows up in the logs. As far as I know, this usually means that something tried to access memory it wasn’t supposed to. Maybe the game or mod is referencing something that doesn’t exist anymore?

2. "Game object has been destroyed" Errors:
I keep seeing this in the logs:

warning: Error running lua script: ...er forged alliance\mods\m28ai\lua\ai\m28engineer.lua(14959): Game object has been destroyed
         stack traceback:
         	[C]: in function `?'
         	...er forged alliance\mods\m28ai\lua\ai\m28engineer.lua(14959): in function `ConsiderMinorLandZoneEngineerAssignment'
         	...er forged alliance\mods\m28ai\lua\ai\m28engineer.lua(17246): in function `?'
         	...mander forged alliance\mods\m28ai\lua\ai\m28land.lua(9279): in function <...mander forged alliance\mods\m28ai\lua\ai\m28land.lua:8599>

It seems like the M28AI script is trying to work with an object that’s already been removed (like a dead unit or something).

3. Repeated Errors Before Crash:
These warnings repeat in a loop before the game finally crashes. I’m guessing this is putting too much pressure on the game or causing something to go wrong deeper down. The address (0x0095854f) being listed as an "Unknown symbol" doesn’t help much, but it’s definitely not normal.

Summary:

The crashes seem tied to the M28AI mod interacting with destroyed objects.
The repeated "Game object has been destroyed" errors might be causing the invalid memory access (0xc0000005).

I honestly don’t know for sure what’s causing this. The M28AI mod is the only one that keeps showing up in the logs, which is why I suspect it, but at the same time, I know it’s a very well-maintained and regularly updated mod, so I have my doubts. After countless games of trying to troubleshoot by removing almost every other mod in my list one by one, the crash still happened. The only mod I didn’t disable during all of this was M28AI.

It’s also worth mentioning that the crash always seems to happen in late-game matches with lots of units, especially when there are nukes or Experimental Bombers involved. Disabling other mods helped extend the time I could play before the crash, but it didn’t stop it entirely. At first, I thought this was a RAM issue, but after trying everything I could think of to address that, I’m back to square one and stuck again.

I’ve attached my log file for this game here : game_24026844.log. Any help figuring this out would be super appreciated! Let me know if you need any other info or if there’s something else I should try.

Thanks in advance!

Mod List:

UI:

Advanced Selection Info
Advanced target priorities
BrewLAN: Gameplay mods
Build range Preview
Phillip Crofts Soundtrack
Penguin-s Icon Mod
Redux ACU Icons
SupCom Vanilla Music FAF
SharedMouse
Supreme Economy Next
Supreme Score BoarD

SIM:

BlackOps FAF: ACUs
BlackOps FAF: EXUnits
BlackOps FAF: Unleashed
BrewLAN
BrewLAN: Additional unit mods
Damage Numbers
EXPERIMENTAL UNIT HEALTH X1.5
Kennel Engineering Stations For All
M28AI
Production Buffers Extra
Quantum Resource Generators
Reclaim Turret Aggressive
T2 T3 Storage FAF Rebalanced
Total Mayhem

magge

Finally, someone put ChatGPT to good use.

With those ton of SIM mods, I would suggest trying to reproduce the issue by disabling all mods (even UI), then enabling them one by one to see which causes the issue in the late game. Unless @maudlin27 spots something in the log that blames the AI.

Additionally, with so many mods, the game's memory limits might be causing the issues. Especially, with many players and/or AI.

maudlin27

Nothing obvious from the log relating to M28 error messages that I'd expect to be causing crashes but it's possible it's contributing if the crash was due to lack of memory, I'll make a note on the 2 M28 releated error messages to add a fix for the next release (v172).

If not already I'd suggest enabling the FAF debugger which should give more information on the reasons for a crash:

Agreed with Magge's suggestion of reducing the mods to try and see if you still get such a crash.

Uveso

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x0095854f

This is a memory error. The only solution is to reduce the number of (unit) mods.
https://github.com/FAForever/fa/issues/1445