Page MenuHomeFeedback Tracker

Game does not start under Windows 8.1 x64 (Steam)
Closed, ResolvedPublic

Description

Arma3 stopped working on my PC a few days ago.

Current content BuildID according to Steam->Arma3->Properties->Local files: 283304

When starting the Game via Steam. the 3 intro panes are displayed

  1. Bohemia Interactive presents
  2. Arma3 logo
  3. BI logo, Arma3 logo, PhysX logo, some text

After displaying the third pane the screen turns black and the "Arma3 (32 Bit)" process is marked as inactive by the Windows task manager.

CPU usage is at 0.4% tops. RAM usage is 402.6MB (Fullscreen) and 383.9MB (Windowed) values are +-0.1MB

DayZ Standalone does not work aswell, if that is relevant.

Tried some other things with no noticable change:

  1. Uninstalled Arma3 & DayZ and deleted Profiles in "User Documents"
  2. Tried developer version of Arma3
  3. Deactivated Zeus DLC
  4. Closed other programs such as Opera browser, Geforce Experience, Origin
  5. Installed Geforce driver 337.50 & 337.88

As previously stated, DayZ and Arma3 worked before. Several other games work as expected, such as BF3, BF4, Counterstrike: Global Offensive {F24058} {F24059}

Details

Legacy ID
2756765061
Severity
None
Resolution
Unable To Duplicate
Reproducibility
Always
Category
Game Freezes
Steps To Reproduce
  1. Start game via Steam
  2. Select Fullscreen or Windowed mode
  3. Wait for 3 intro panes to pass
  4. Exit game via Alt+Tab
Additional Information

System specification:

CPU: Intel i5 2500k
Graphics card: MSI V298-012R GTX 780Ti (Twin Frozr)
PSU: Corsair HX850 (Single 12V Rail, 70A)
MB: GA-Z77X-UD3H (1.1) (Bios F20d)
RAM: Corsair Venegance DDR3 2x4GB
SSD: Samsung 830

Event Timeline

tbsn edited Steps To Reproduce. (Show Details)Jun 8 2014, 10:19 AM
tbsn edited Additional Information. (Show Details)
tbsn set Category to Game Freezes.
tbsn set Reproducibility to Always.
tbsn set Severity to None.
tbsn set Resolution to Unable To Duplicate.
tbsn set Legacy ID to 2756765061.May 7 2016, 6:43 PM
tbsn edited a custom field.
tbsn added a subscriber: tbsn.
tbsn added a comment.Jun 8 2014, 1:36 PM

I did some more research and found out that my joystick seems to cause the problem.

The game does start when the joystick is not plugged in. I attached 2 logfiles for each testcase.

Whilst looking at the log I noticed something. See the log extract below for clarification:

<log>
Error: JoystickDevices - CoInitilizeEx return 80010106
Detected Joystick: SideWinder Force Feedback 2 Joystick

0 ... X-Achse [1,30]
1 ... Y-Achse [1,31]
5 ... Z-Rotation [1,35]
6 ... Schieberegler [1,36]

</log>

The log file lists all control elements of my joystick in my Windows locale (German). The list of control elements is not complete, yet. The elements are listed in the Windows 8 Gamecontroller-Settings tool aswell. As next element I would expect 8 digitial buttons, which are grouped as "Schaltflächen" in my locale. Note the German Umlaut 'ä' in "Schaltflächen".

My wild guess now is, that your parser checks each field for validity and does not like said Umlaut.

Iceman added a comment.Jun 9 2014, 2:56 PM

Hello,
would it be possible to plug a joystick again and try to find crashdump in the same folder as the rpt? (crashdump is rpt + bidmp + mdmp file with same name)
Thank you.

tbsn added a comment.Jun 9 2014, 3:52 PM

Hi,

the game does not generate the bidmp or mdmp files, because it is only freezing not crashing. The process can't be killed via the taskbar or Alt+F4.

I created a process image with the task manager and killed the task with the task manager subsequently.

After killing the process, no bidmp + mdmp files were created.

I uploaded two sets of the process image (.dmp) and .rpt file to: http://bnkr.no-ip.biz:10080/ARMA3/

Regards
Tobias

Hello,

it seems that you Arma is not actually crashing but shutting down in emergency mod. It is most likely caused by Windows or third-party software. Would it be possible to try other USB devices? Also, have you tried updating all possible drivers (ie. motherboard, BIOS)?

tbsn added a comment.Jun 16 2014, 11:06 PM

Hi,

I reinstalled Windows 8.1 x64 from scratch, today. I applied all Windows updates. Installed are the following programs:

  • Steam
  • Origin
  • Teamspeak
  • Nvidia Experience
  • Opera Browser
  • PuTTY
  • Xming

The issue is still 100% reproducable. I.e. Arma crashes, when my joystick is attached to the USB port it was *always* plugged into. I will call this port USB_A2 in the following. As previously stated, the joystick works fine in USB_A2 with Windows Gamecontroller Widget, BF3, BF4, etc. Arma 3 worked like a charm until approximately one month ago.

I did some more research with with the joystick and arma3 and discovered some interesting things.

When the joystick is disconnected from the USB_A2, when the game is frozen after the 3 splash screens, Arma 3 loads successfully into the main menu.

I plugged the joystick back into USB_A2 and the game froze, as i entered the configuration menu.

Unplugged the joystick again and Arma came back to life.

Now the interesting part: I plugged the joystick into another USB port (USB_B1) and all described problems are gone.

I believe this is a regression in Arma 3.

MadDogX added a subscriber: MadDogX.May 7 2016, 6:43 PM

Mass closing tickets marked as resolved more than 1 month ago.

If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.