Page MenuHomeFeedback Tracker

"0xC000041D - STATUS_FATAL_USER_CALLBACK_EXCEPTION" when loading savegame of scenario Old Man
New, NormalPublic

Description

Hi,
I had been playing the Old Man scenario (which is great BTW) for many hours, when the game suddenly crashed. After restarting the game and loading the scenario again, the game keeps crashing:
"0xC000041D - STATUS_FATAL_USER_CALLBACK_EXCEPTION"

I have tried renaming the latest "autosave *.Arma3Save" to "continue *.Arma3Save" (I read somewhere that the crash may have caused the continue-file to be corrupt), but to no avail.
I am attaching the dump files to this ticket.

BTW: I have already updated my graphics drivers and restarted the game and system.

Thanks in advance.

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
10.0.18362 Build 18362
Category
Savegame/Loadgame
Steps To Reproduce

Resume Old Man scenario. The load screen with map op Tanoa appears, with a progress bar at the top. The bar loads up fully, but then after some 10 seconds, crash...

Additional Information

Event Timeline

Kaveman_nl updated the task description. (Show Details)
Wulf added a subscriber: Wulf.Wed, Jan 8, 3:37 PM

Hello.

Thank you for the report. There are multiple reasons for this error, for example 3rd party programs interfering with the game and failing, crashing the game in the process. or something very similar to when the game throws ERROR_MOD_NOT_FOUND. I will list the possible solutions here please try those that you didn't already and let us know, if anything changed.

Possible solutions:

  • Close all unnecessary applications.
  • Un-install 3rd party applications that could interfere with the game (performance boosters, streaming apps, FPS indicators, overlays, graphics enhancers) or disable them.

or

  • 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 the Windows System File Check tool to repair corrupted system files.

Dependency Walker might give an insight, but unfortunately this issue mostly happens for libraries that are loaded dynamically, so they are not visible in Dependency Walker.

Nevrose added a subscriber: Nevrose.Wed, Jan 8, 8:20 PM

I encountered the same error while clicking on a bed ingame, near Losi, after stealing diver gears from gendarmes for a mission. The game crashed instantly when I clicked on the bed (or maybe the watch screen appeared and I clicked the "confirmed" button, I do not remember). Now, I am getting the exact same message.

My game used the following mods : CBA _A3, Enhanced Soundscape. VCOM AI Driving V1.03

Hi Wulf,

Thank you for the investigation and reply.

I am not running any boosters, streaming apps, FPS indicators or graphics enhancers. I did uncheck the Steam overlay option.

I have verified the Steam files; all is OK.
I am running W10 x64, so as far as I understood from articles I googled, I can only update DirectX versions up untill 11. Dx 12 should be managed via Windows updates. Or am I mistaken? If so, do you have a link to a useful article?
The Visual C++ Redist packages I re-installed.
I did an "sfc /scannow" and some errors were fixed, according to the report.

Unfortunately, that didn't help. In fact, I am now even getting errors when initially loading the game.

After clicking OK, the game continues to load. When finished, a message appears:
"No entry 'bin\config.bin/CfgMagazines/IEDUrbanSmall_Remote_Mag.scope'."
All I can do there is close the message.

Then once I load the Old Man scenario, I quite quickly get this message:
"You cannot play/edit this mission; it is dependent on downloadable content that has been deleted.a3_data_f_mod_loadorder"
And then I'm back in the Scenario view.

As far as I know, I did not delete or unload any mods. Googling makes me think that last message is connected to the CBA_A3 mod. I tried unsubscribing and subscribing again, but that makes no difference.

So in short: the good news is the game itself doesn't crash anymore. The bad news is there are other issues now... :-\
Any ideas?