Page MenuHomeFeedback Tracker

Crash on "Exit" Only
Closed, ResolvedPublic

Description

Occasionally, after an undetermined amount of time, once the game is "exited" to return to the launch screen, the game will close to desktop, with a windows error. This error and crash only occurs once the game has been opened for a while. Further testing is required to either elliviate the issue or reproduce more consistently.

Typically, after playing more than hour, this error will occur when exiting the server to go to the launch screen.

Details

Legacy ID
867118177
Severity
None
Resolution
Duplicate
Reproducibility
Sometimes
Category
Game Crash
Steps To Reproduce

I have tried to reproduce this. This crash only occurs after playing for a little while AND upon exiting a server. I have not crashed while connected to a server. The game will not go to the Character/Server select screen, it just dumps to the desktop.

The game will start up fine again, without any issues.

I have tried launching the game, joining a server and exiting the server right away to reproduce the result, but the game will exit to the lobby just fine, without error. This crash only occurs after playing for a while and deciding to manually exit the server normally.

It's just your standard Windows Popup error "This application has unexpectedly closed", name of application, click ok, etc.

Additional Information

I have command line arguments added to the launcher. I will test with the command line args removed after filling this report and update if necessary. These launch options, within Steam, have had no ill-effect on the game to date.

The command running at launch are as follows:

-noSplash -cpuCount=4 -exThread=7 -noPause -world=ChernarusPlus

The Game .exe is also running in WinXp compatibility mode. Again, I will revert to normal, retest and report if there is a noticeable change.

Additionally, here is a crashdump with the exception code, exception offset and faulting proc id.

Log Name: Application
Source: Application Error
Date: 04-Dec-2014 4:00:49 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Galileo
Description:
Faulting application name: DayZ.exe, version: 0.51.125.720, time stamp: 0x547603d9
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000005
Fault offset: 0x00038c9f
Faulting process id: 0x3c4c
Faulting application start time: 0x01d01015de82e4b3
Faulting application path: D:\Games\Steam\steamapps\common\DayZ\DayZ.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: c48ea74f-7c11-11e4-8a7c-485b3975fe29
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2014-12-05T00:00:49.000000000Z" />
  <EventRecordID>32224811</EventRecordID>
  <Channel>Application</Channel>
  <Computer>Galileo</Computer>
  <Security />
</System>
<EventData>
  <Data>DayZ.exe</Data>
  <Data>0.51.125.720</Data>
  <Data>547603d9</Data>
  <Data>ntdll.dll</Data>
  <Data>6.1.7601.17725</Data>
  <Data>4ec49b8f</Data>
  <Data>c0000005</Data>
  <Data>00038c9f</Data>
  <Data>3c4c</Data>
  <Data>01d01015de82e4b3</Data>
  <Data>D:\Games\Steam\steamapps\common\DayZ\DayZ.exe</Data>
  <Data>C:\Windows\SysWOW64\ntdll.dll</Data>
  <Data>c48ea74f-7c11-11e4-8a7c-485b3975fe29</Data>
</EventData>

</Event>

Event Timeline

PaX edited Steps To Reproduce. (Show Details)Dec 5 2014, 1:43 AM
PaX edited Additional Information. (Show Details)
PaX set Category to Game Crash.
PaX set Reproducibility to Sometimes.
PaX set Severity to None.
PaX set Resolution to Duplicate.
PaX set Legacy ID to 867118177.May 8 2016, 8:50 PM

i get this problem also

PaX added a subscriber: PaX.May 8 2016, 8:50 PM
PaX added a comment.Dec 5 2014, 2:22 AM

Although this is most likely a DayZ.exe faulting module, executable/memory dump problem, I have included as much information possible related to the Video card and other components for reference purposes. These screenshots and information will most likely not be needed, however, they are available if needed.

PaX added a comment.Dec 5 2014, 10:27 AM

Aditional Crash, this time it was not Dayz.exe or the nt.dll, which has been common as well.

I have had several of these crashes on game closing, and there is only one entry that raises suspicion; BEClient.dll

It appears as though the BattlEye client is faulting on close. Several other people have reported BE issues, so the .dll might be worth investigating.

Here's the Summary of the event ID.

Log Name: Application
Source: Application Error
Date: 04-Dec-2014 8:34:34 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Galileo
Description:
Faulting application name: DayZ.exe, version: 0.51.125.720, time stamp: 0x547603d9
Faulting module name: BEClient.dll_unloaded, version: 0.0.0.0, time stamp: 0x541d077d
Exception code: 0xc0000005
Fault offset: 0x4e30b5d7
Faulting process id: 0x32d4
Faulting application start time: 0x01d00fcb247514f0
Faulting application path: D:\Games\Steam\steamapps\common\DayZ\DayZ.exe
Faulting module path: BEClient.dll
Report Id: 6dd95cd9-7bd3-11e4-8a7c-485b3975fe29
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2014-12-04T16:34:34.000000000Z" />
  <EventRecordID>32224809</EventRecordID>
  <Channel>Application</Channel>
  <Computer>Galileo</Computer>
  <Security />
</System>
<EventData>
  <Data>DayZ.exe</Data>
  <Data>0.51.125.720</Data>
  <Data>547603d9</Data>
  <Data>BEClient.dll_unloaded</Data>
  <Data>0.0.0.0</Data>
  <Data>541d077d</Data>
  <Data>c0000005</Data>
  <Data>4e30b5d7</Data>
  <Data>32d4</Data>
  <Data>01d00fcb247514f0</Data>
  <Data>D:\Games\Steam\steamapps\common\DayZ\DayZ.exe</Data>
  <Data>BEClient.dll</Data>
  <Data>6dd95cd9-7bd3-11e4-8a7c-485b3975fe29</Data>
</EventData>

</Event>

Same prob here. What info should i upload?

andy added a comment.Dec 8 2014, 12:41 PM

Hi PAX and thank you a lot for the information! Appreciated!
We are currently investigating this (#19480). Please be patient.
Regards,
Andy