Unhandled Exception Nearly Every Game

[DaN00b]

Hi there,

I've been playing FAF without any problems, but recently I started to have an error that looks like this:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at address 0x0068292c
attempted to write memory at 0x2e926000

Note: I've attached the game logs.

The error occurs on practically every game in the middle of the game (maybe 20-30 mins in) and is extremely frustrating. I've tried uninstalling Supreme Commander as well as FAF, deleting all related files, then re-installing but no luck, same error. I read that this could be a mod error, but I've been playing the same maps and everything for a while now before this started happening, so I'm not sure what changed?

Any ideas?
Thanks

[DaN00b]

Today the error happened right at the start of a game as well (first time that has happened so far), and then later on in another game.

[pshd21]

Not much of an help what you posted, because that address points to some memory copy operation which shouldn't be a trouble spot.

Some options:
1) Post your system specs and the full exception message plus more logs and more scenarios.
2) If possible, also inspect the executable after the crash happened with process hacker or process explorer:
- How much resources were being used (RAM, very high GPU I/O or CPU)
- Stacktrace of the thread on which the exception was thrown
- modules (which dlls and from where are these being loaded, i.e. d3d9.dll)
3) Remember/Check what has been changed that now causes this memory exception on your system.
4) Check if other games run without problems (perferably d3d9 games before 2010)
5) Update every driver and if you use windows, make sure to use windows 10 latest version - eventually reinstall it.
6) Windows' eventviewer might have details for such problems
7) Anti-virus software or other kernel mode drivers can cause abnormal behavior on user mode software. Uninstall or deactivate applications / background drivers.
8) Lower your video settings in supcom, use fullscreen
9) Upgrade your pc components, better no amd
10) See if there any signs that happen right before the exception occurs
11) Clear all mods, maps, cache, settings, game files - redownload if needed

What I can read from the log, is:
warning: c:\work\rts\main\code\src\libs\gpggal\DeviceD3D9.cpp(866) Device lost
Right after you minimized the application.

The function at the posted address is somewhat connected with loading textures, so there might be a problem with d3d9 for you (I guess losing the d3d9 device, which is the interface to your graphics drivers, is something that might not be handled well in supcom, because it just shouldn't happen).
And
DeviceD3D9.cpp(779) Not available
probably says that the interface instance couldn't be reinitialized.

This is just an assumption. You could also google something like "directx 9 device lost".

[Uveso]

@DaN00b:

your game.log shows that the game lost connection to your GFX card.

I am not sure why this happened.

In some cases in can be the pyton FAF client in full screen mode.
Try to reduce the windows size.

You could also try Downlords java FAF client:
https://faforever.github.io/downlords-faf-client/



@pshd21:

First of all, thanks for your help!

Not much of an help what you posted, because that address points to some memory copy operation which shouldn't be a trouble spot.

He posted game and client log. We normaly don't need more (See red text)

Also there is no memory copy operation. It's an access operation.
This operation failed, because the programmcode at 0x0068292c (SupCom memory offset) tries to write memory to address HEX 0x2e926000.
This is 781,344,768 in decimal. Unless there are not more then 780 GigaByte RAM installed, this IS a trouble spot.

warning: c:\work\rts\main\code\src\libs\gpggal\DeviceD3D9.cpp(866) Device lost

That is the error. "Directx 9c" has lost the connection to the GFX card.

All texture errors and everything that is following is only because the GFX card is not present.
This means that there are no problems with textures.

If you are interested in bughunting, visit my long term bugtracing place at GitHub:
https://github.com/FAForever/fa/issues/2045

[DaN00b]

So I found out what the problem was. Somehow the Windows User Push Notification Service was taking up tons of RAM and was crashing the game. It was a Windows update problem, not FAF or sup comm. I did a system reset and now the problem's gone.

[pshd21]

Also there is no memory copy operation. It's an access operation.
This operation failed, because the programmcode at 0x0068292c (SupCom memory offset) tries to write memory to address HEX 0x2e926000.
This is 781,344,768 in decimal. Unless there are not more then 780 GigaByte RAM installed, this IS a trouble spot.

All texture errors and everything that is following is only because the GFX card is not present.
This means that there are no problems with textures.

You serious?
The function at the address clearly performs copy operations with qmemcpy and standard mov's, as I have analyzed it with IDA. Not sure what you are talking about.
I expressively mentioned the log and the exception output wasn't enough, since it can be triggered by anything (No stacktrace i.e.).

There were clearly log informations about problems with textures after the device was lost. I have also debugged the address and there are informations
about albedo textures near the addresses which are hold in the handover registers which are, in turn, thought for copy and paste operations.

The default registers on x86 are 32 bit and since it's a virtual address space, it has not much to do with your RAM. You seem to have no idea
how to translate a virtual address to a physical address and how complex that is on windows.
Understanding the heap isn't easy, and allocations can happen nearly on any free unprotected and unreserved address space up to 0x7FFFFFFF (2.147.483.648 for you), rest is for windows itself.
For example at address 0x7FFE0000, you have something allocated on every process.
Also 0x2e926000 sounds like an ordinary heap block for x86 to me, no idea what you are talking about.

So I found out what the problem was. Somehow the Windows User Push Notification Service was taking up tons of RAM and was crashing the game. It was a Windows update problem, not FAF or sup comm. I did a system reset and now the problem's gone.

So it was an out of memory issue, which I have mentioned to look for (Option 2).
See you next time ig.

[Uveso]

Well, i know that

But you where writing "shouldn't be a trouble spot".
But we have an error message thats is exactly saying this.

Also the texture problems is only because there was no GFX card present at this point.
Mostly all errors after the first are aftereffects from the first error.
Like here. First the GFX card is gone, after this we can't load textures.

But as i said before, any help is welcome.
If you like, you can debug the following addresses:

0x0213d267
0x023fde58
0x0047a820
0x00598eec
0x005f39f7
0x0067aa5f
0x008b94f0
0x00938ac8
0x0095854f
0x009d7b75

https://github.com/FAForever/fa/issues/2045

[Rowey]

Question are you using headphones with Dolby 7.1 surround sound ? as this can cause issues as I've just experience it my self.