User Details
- User Since
- Mar 6 2013, 1:31 PM (610 w, 3 d)
May 11 2016
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.
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>
The best way to beat a script, is to monitor the forums where the scripts are created. Most scriptwriters will not share their work. Some people will monetize, as this site does.
One can not go after the website, however, it is well within the security teams purview to monitor, join and participate in said forums and to also purchase and download the hacks themselves, those that are available, to reverse engineer and examine where the coding loopholes are and plug them as they are revealed.
Security is a top level priority for the Development Team and they are always looking for ways to improve their code.
@heirfuher: Anonymous is NYPA '-)