Page MenuHomeFeedback Tracker

d3d9.dll Game Crash on Startup SWEETFX and DirectX Conflict
Assigned, WishlistPublic


When I start the game without the ArmA 3 Launcher (using the -nolauncher parameter or with a third party launcher like PlayWithSix or ArmA3Sync), the game will repeatedly crash on startup.

It looks like some kind of conflict with DirectX and SweetFX, but I can't be certain. It says 'Loading Addons' then it says ArmA 3 has stopped working. When I click Show more Information, the error message is as follows:

Problem signature:

  Problem Event Name:	APPCRASH
  Application Name:	arma3.exe
  Application Version:
  Application Timestamp:	54f47474
  Fault Module Name:	d3d9.dll
  Fault Module Version:
  Fault Module Timestamp:	4ee53333
  Exception Code:	c0000005
  Exception Offset:	00004fe7
  OS Version:	6.1.7601.
  Locale ID:	2057
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:


When I remove d3d9.dll from the ArmA 3 directory, I can launch with the -nolauncher parameter, but third party launchers do not work. The game appears as a running process but is not in a visible window.

SweetFX has worked in the past, so I don't see any reason to stop using it all of a sudden. I have tried reinstalling DirectX and verifying the game files with Steam to no avail.

Strangely, the only time the game will launch properly, is when I use the ArmA 3 launcher. The launcher removes alot of functionality for me since I already have mod collections and update repositories on third party launchers (Like PWS and ArmA3Sync).

I've also attached the DXDiag log file too, where it reads:

DX Setup Parameters: Not found

{F25893} {F25894}


Legacy ID
Game Crash
Steps To Reproduce

Use SweetFX and ArmA 3 since the last update which defaults the launcher as the only startup option, and the game will crash during the loading screen.

DirectX and SweetFX problem, removing d3d9.dll from directory is a temporary workaround.

Additional Information

This is obviously quite a serious issue for me, since I cannot even play the game anymore.

I'm happy to send more details over if you need them and try and troubleshooting methods you might have.

Event Timeline

TOMMEH edited Steps To Reproduce. (Show Details)Mar 30 2015, 6:55 PM
TOMMEH edited Additional Information. (Show Details)
TOMMEH set Category to Game Crash.
TOMMEH set Reproducibility to Always.
TOMMEH set Severity to None.
TOMMEH set Resolution to Open.
TOMMEH set Legacy ID to 1372813933.May 8 2016, 11:47 AM
Adam added a comment.Mar 31 2015, 9:10 AM

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 without using mods or custom memory allocators
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.

TOMMEH added a subscriber: TOMMEH.May 8 2016, 11:47 AM
TOMMEH added a comment.Apr 3 2015, 1:32 AM

OK Adam, thank you for the quick reply! The 'ArmA 3 has stopped working' message has actually changed to a KERNELBASE.dll fault module, here is the full log:

Problem signature:

  Problem Event Name:	APPCRASH
  Application Name:	arma3.exe
  Application Version:
  Application Timestamp:	54f9d119
  Fault Module Name:	KERNELBASE.dll     <<< instead of D3D9.dll
  Fault Module Version:	6.1.7601.18409
  Fault Module Timestamp:	53159a86
  Exception Code:	406d1388
  Exception Offset:	0000c42d
  OS Version:	6.1.7601.
  Locale ID:	2057
  Additional Information 1:	375d
  Additional Information 2:	375d7f8896349689eeae94fb5d0c01e8
  Additional Information 3:	fa10
  Additional Information 4:	fa10336a709103d7521c4ab63830c01f

Here's what's interesting, I turned off my -nologs parameter to get the crash dump files for you, and the game starts up. Once the game is started up once, it will continue to start up normally. These fault module problems always happen when Windows starts up.

On a second bootup, the same KERNEL.dll error came up. So I verified the game cache (no files were missing), yet now the game starts up normally. I have to repeat this process every single time I boot up Windows.

A recent hard drive problem has arisen on my system. When I tried launching with the -nolauncher parameter, I'd repeatedly get this error:

'Arma 3 disk write error while updating. Please see Steam support for more information'

Below I have attached screenshots of this bizzare texture lag (my hard drive works fine in all other games I have, even ARMA 2 and DayZ:

The crash dump files have also been uploaded in a WINRAR package ---> to this file sharing link:!ttYEALJK!w5SV90kxdJAjHGA-LYMYfEgoFR_NVwVZBqAWE9Uc_gg

I have no .mdmp files because it's an issue which prevents the game from booting, so only .rpt and .bidmp files seem to be written.

Hope this helps!

Adam added a comment.Apr 3 2015, 11:13 AM

Unfortunately we need the .mdmp files to investigate your issue. Try reproducing the crash without any parameters. Thank you in advance.

TOMMEH added a comment.Apr 3 2015, 2:56 PM

I found this on the Steam forums:

"the dump files are only created if the game crashes due to an issue in the game. if the game crashes due to a driver issue or Windows crash, they won't be written"

So because the game isn't starting, the .rpt and .bidmp files are the only crash dump files I have. .mdmp files are only written when the game is running.
This is out of my control unfortunately.

TOMMEH added a comment.Apr 7 2015, 1:02 AM

Any updates on the issue?

Adam added a comment.Apr 7 2015, 12:40 PM

As i stated above there is not much that we can do without .mdmp files. The issue seems to be with your Windows. Try logging in as different user on your PC and launch ARMA There and see if it works.

I've uploaded '' which contains the .mdmp files related to ArmA 3. I'll also be reformatting my computer soon to sovle the Windows issues.

One question I have, is that I have 90GB of mods in my ArmA 3 folder. Is there an easy way to transfer them to another disk instead of reinstalling them?

Thanks for the assistance.

Adam added a comment.Apr 9 2015, 9:00 AM does not contain any .mdmp files only dmp files which are not helpful. Please attach the correct files. Thank you.

TOMMEH added a comment.Apr 9 2015, 6:08 PM

Very sorry about this, I've now uploaded the correct files to 'All My ARMA 3 Crash'

Thanks again for your time looking into this crash.

Adam added a comment.Apr 10 2015, 12:09 PM

Please try reproducing crashes without running any custom launch parameters. Thank you.

Ok, I've been away for a while due to finals this summer. I've had another look at the problem and it seems to be specific to my Windows build.

I deleted the d3d9.dll from the ArmA 3 directory which is used by SweetFX, but luckily SweetFX is still functioning without it. This solved the first instances of the arma3.exe startup issue.


To solve the 'ArmA 3 has stopped working' due to a kernelbase.dll fault module error, Open regedit (Windows key+R) type regedit and then click OK

Now just browse HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\arma3.exe

If you have UseLargePages REG_DWORD there and it's data is 0x0000001 (1) then that's the cause of your problem

Simply right click the registry value and then Modify... and change the value data to 0 and click OK

Now it should show 0x00000000 (0) in the data and your Arma 3 should now work.
I hope this helps anyone else with a similar problem.

Credit of original fix to St.Jimmy on the BIS forums...