Page MenuHomeFeedback Tracker

The game won't start - 0xc0000135
New, NormalPublic

Description

I just performed a clean installation of the game and after downloading 25+ GB worth of game, I found out it won't start.
This is the error I get every time I try to open it:

---------------------------
arma3_x64.exe - System Error
---------------------------
Exception Processing Message 0xc0000135 Parameters 0x7ff8149f1d28 0x7ff8149f1d28 0x7ff8149f1d28 0x7ff8149f1d28
---------------------------
OK   
---------------------------

The troubleshooting report is attached in the Additional Information section.

I already performed all of the possible solutions suggested here: https://community.bistudio.com/wiki/Arma_3_Unusual_process_exit#0xC0000135_-_STATUS_DLL_NOT_FOUND

- 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.
- To identify the precise DLL that is causing an issue.
- Download a 64-bit version of the Microsoft Dependency Walker and open arma3_x64.exe with it. The libraries with a red icon are the corrupted ones.
- Download a 32-bit version of the Microsoft Dependency Walker and open arma3.exe with it. The libraries with a red icon are the corrupted ones.

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
Pro
Category
Game Crash
Steps To Reproduce
  1. Log into Steam
  2. Open the Arma 3 Launcher
  3. Click on the "Play" or "Play without mods" button

The error occurs then

Additional Information

Launcher version: 1.5.142122
Game version: 1.72.142223
Branch: main / beta branch not specified

Troubleshooting report:

DxDiag log file:

Dependency Walker x64 logs (arma3_x64.exe):

Dependency Walker x86 logs (arma3.exe):

Event Timeline

Creebles_ edited Additional Information. (Show Details)Jul 7 2017, 10:55 AM

I (hopefully) managed to solve the issue by doing copy-paste of all the .dll files of the folders "System32" and "SysWOW64" from another PC (skipping the ones that i already had)