DayZ 0.63 Blue Screen [Crash Cause now Know]

[Ðëprávèd•Mïšçréånt]

Ok so I finally got the crash today,

Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.
Show DivPrimary Analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff803`9d6a8000 PsLoadedModuleList = 0xfffff803`9da621f0
Debug session time: Sun Jul 8 23:45:51.479 2018 (UTC - 4:00)
System Uptime: 2 days 14:05:20.293
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8039dba1c37, The address that the exception occurred at
Arg3: ffffef8f388f5668, Exception Record Address
Arg4: ffffef8f388f4eb0, Context Record Address

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!ObpCreateHandle+387
fffff803`9dba1c37 410fb6402c movzx eax,byte ptr [r8+2Ch]

EXCEPTION_RECORD: ffffef8f388f5668 -- (.exr 0xffffef8f388f5668)
ExceptionAddress: fffff8039dba1c37 (nt!ObpCreateHandle+0x0000000000000387)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000000002c
Attempt to read from address 000000000000002c

CONTEXT: ffffef8f388f4eb0 -- (.cxr 0xffffef8f388f4eb0)
rax=ffffda83c5cc5700 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffef8f388f5b60 rsi=0000000000000000 rdi=00000000001f01ff
rip=fffff8039dba1c37 rsp=ffffef8f388f58a0 rbp=ffffef8f388f59c0
r8=0000000000000000 r9=0000000000000000 r10=7ffffffffffffffc
r11=ffffef8f388f5880 r12=ffffda83ce3d5240 r13=da83ce3d52400001
r14=ffffef8f388f5b60 r15=0000000000000010
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210246
nt!ObpCreateHandle+0x387:
fffff803`9dba1c37 410fb6402c movzx eax,byte ptr [r8+2Ch] ds:002b:00000000`0000002c=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000000000000002c

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
000000000000002c

FOLLOWUP_IP:
BEDaisy+255bfe
fffff807`2eb75bfe 68b577f7e5 push 0FFFFFFFFE5F777B5h

BUGCHECK_STR: AV

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

EXCEPTION_STR: 0x0

LAST_CONTROL_TRANSFER: from fffff8039dbb1b13 to fffff8039dba1c37

STACK_TEXT:
ffffef8f`388f58a0 fffff803`9dbb1b13 : 00000000`00000000 00000000`00000000 ffffda83`ce3d5270 ffffef8f`001f01ff : nt!ObpCreateHandle+0x387
ffffef8f`388f5ae0 fffff807`2eb75bfe : ffffef8f`388f5e40 00000000`00000000 ffffda83`00000000 fffff807`2e92ea88 : nt!ObOpenObjectByPointer+0xc3
ffffef8f`388f5d40 ffffef8f`388f5e40 : 00000000`00000000 ffffda83`00000000 fffff807`2e92ea88 ffffda83`c3d9edc0 : BEDaisy+0x255bfe
ffffef8f`388f5d48 00000000`00000000 : ffffda83`00000000 fffff807`2e92ea88 ffffda83`c3d9edc0 00000000`00000001 : 0xffffef8f`388f5e40


SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: BEDaisy+255bfe

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: BEDaisy

IMAGE_NAME: BEDaisy.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5b39d590

STACK_COMMAND: .cxr 0xffffef8f388f4eb0 ; kb

FAILURE_BUCKET_ID: X64_AV_BEDaisy+255bfe

BUCKET_ID: X64_AV_BEDaisy+255bfe

Followup: MachineOwner
---------


This free analysis is provi

The process csrss.exe is crashing

What Is Client Server Runtime Process?
The csrss.exe process is an important part of the Windows operating system. Before Windows NT 4.0, which was released in 1996, csrss.exe was responsible for the entire graphical subsystem, including managing windows, drawing things on the screen, and other related operating system functions.

With Windows NT 4.0, many of these functions were moved from the Client Server Runtime Process, which runs as a normal process, to the Windows kernel. However, the csrss.exe process is still responsible for console windows and the shutdown process, which are critical functions in Windows.

RELATED: What Is conhost.exe and Why Is It Running?

Prior to Windows 7, the CSRSS process drew console (Command Prompt) windows itself. On Windows 7 and later, the Console Host (conhost.exe) process draws console windows. However, csrss.exe is still responsible for launching the conhost.exe process when necessary.

In other words, this process is responsible for a few critical system functions in the background. That’s just how Windows does things.

When the module MODULE_NAME: BEDaisy
Battle eye, interacts with the Client Server Runtime Process.

I am not a coder and I cannot offer a fix however this is the cause.

I hope the dev's have this already and am sure they are testing fixes.
Likely this is something battle eye has to address.

So until a patch is made there is no solution.

I have not reinstalled battle eye and this is the only battle eye game I have tested so far.
Sorry for the lack of other testing but I will post them as I get them.

This might help people realise that the issue is not computers OS or hardware and actually a BOS caused by the interaction of the Battle Eye Module and the Client Server Runtime Process.

This also happened when I just tried to immediately run DayZ which would have also initiated the command to run battle eye causing the crash.

This is a list of technical diagnosis as well as Q/A relating to the above minidump log, personal opinions about the product please withhold.

Thank You

[Deaths]

Cheers

[Punisher]

Originally posted by Deus_Drone:

snip

+1

Originally posted by BattlEye $able:

Could you guys please contact support[at]battleye.com so we can determine what the issue is for you?

[[BattlEye] $able]

Can you confirm that this crash only happens after running Windows for a few hours? Not right after booting up?

[Alpha]

Originally posted by BattlEye $able:

Can you confirm that this crash only happens after running Windows for a few hours? Not right after booting up?

Yes, I can confirm this, if your system crashes or you reboot then launch the game it starts without a crash.

[Alpha]

It has to be RIGHT after the reboot/crash though.

[Ðëprávèd•Mïšçréånt]

Originally posted by BattlEye $able:

Can you confirm that this crash only happens after running Windows for a few hours? Not right after booting up?

i'll get back to you.

Due to the fault being a blue screen I am hesitent to do continual testing however in the morning I will do a reboot and see if it runs after a reboot.

Then during the day tomorrow after the reboot test I will do one where windows has been running for several hours.

[[BattlEye] $able]

Originally posted by Deus_Drone:

Originally posted by BattlEye $able:

Can you confirm that this crash only happens after running Windows for a few hours? Not right after booting up?

i'll get back to you.

Due to the fault being a blue screen I am hesitent to do continual testing however in the morning I will do a reboot and see if it runs after a reboot.

Then during the day tomorrow after the reboot test I will do one where windows has been running for several hours.

Could you already send us your crash dump (Memory.dmp - upload to a file host) to support[at]battleye.com? We would appreciate that.