Jump to content

Forums Announcement

Read-Only Mode for Announcements & Changelogs

Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.

For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.

Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!

Stay safe out there,
Your DayZ Team

Sign in to follow this  
Bogenfuckyouwhoevertookmyname

DayZ crashing very often, mostly with a BSOD (PAGE_FAULT_IN_NONPAGED_AREA)

Recommended Posts

Hey, this begin to happen after the last DayZ patch  ( 1.12 )

Its mostly crashing with errors from Graphics drivers. I have reinstalled the game multiple times, done fresh win10 install, ive tried multiple versions of my GPU drivers, no matter overclocked or not. It crashes with a variety of BSOD errors almost all of them refers to GPU drivers more or less. under i have the report from one of them that is mentioned in the title. Please send help!

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except.

Typically the address is just plain bad or it is pointing at freed memory.

Arguments:

Arg1: ffffb0024c3f3050, memory referenced.

Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

Arg3: fffff80743a0af4b, If non-zero, the instruction address which referenced the bad memory address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec Value: 2156

Key : Analysis.DebugAnalysisManager Value: Create

Key : Analysis.Elapsed.mSec Value: 7054

Key : Analysis.Init.CPU.mSec Value: 405

Key : Analysis.Init.Elapsed.mSec Value: 5430 Key

: Analysis.Memory.CommitPeak.Mb Value: 75 Key

: WER.OS.Branch Value: vb_release Key

: WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key

: WER.OS.Version Value: 10.0.19041.1

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffb0024c3f3050

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80743a0af4b

BUGCHECK_P4: 2

READ_ADDRESS: ffffb0024c3f3050

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

TRAP_FRAME: ffffed032b23ea50 -- (.trap 0xffffed032b23ea50)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffffb08a4b1ef080 rbx=0000000000000000 rcx=ffffb0024c3f3050 rdx=000000006e457350 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80743a0af4b rsp=ffffed032b23ebe0 rbp=ffffed032b23f670 r8=ffffed032b23ec20 r9=7fffb08a4bc216f8 r10=7ffffffffffffffc r11=000000000000036a r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy nt!ObReferenceObjectSafeWithTag+0xb: fffff807`43a0af4b 488b01 mov rax,qword ptr [rcx] ds:ffffb002`4c3f3050=???????????????? Resetting default scope STACK_TEXT: ffffed03`2b23e7a8 fffff807`43c8dd7d : 00000000`00000050 ffffb002`4c3f3050 00000000`00000000 ffffed03`2b23ea50 : nt!KeBugCheckEx ffffed03`2b23e7b0 fffff807`43b28210 : 00000000`00000000 00000000`00000000 ffffed03`2b23ead0 00000000`00000000 : nt!MiSystemFault+0x147cbd ffffed03`2b23e8b0 fffff807`43c04d5e : 00000000`00000200 ffffb08a`2da02340 00000000`000000c0 00000000`00000000 : nt!MmAccessFault+0x400 ffffed03`2b23ea50 fffff807`43a0af4b : ffffb08a`4bc218a0 ffffb08a`4bc212c0 00000000`0005f408 00000000`00000000 : nt!KiPageFault+0x35e ffffed03`2b23ebe0 fffff807`43df51b7 : ffffb08a`4b1ef568 ffffb08a`00000000 ffffb08a`00000000 00000000`00000000 : nt!ObReferenceObjectSafeWithTag+0xb ffffed03`2b23ec10 fffff807`43efcbf7 : 00000000`00000000 00000000`00000000 00000000`000000ff 00000000`00000000 : nt!ExpGetProcessInformation+0xee7 ffffed03`2b23f270 fffff807`43efbda7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpQuerySystemInformation+0xd07 ffffed03`2b23f5b0 fffff807`43c085b5 : 00000000`00000000 00000000`00040297 ffffed03`2b23f610 00000001`401e7bf8 : nt!NtQuerySystemInformation+0x37 ffffed03`2b23f5f0 fffff807`43bfaa80 : fffff807`5e65c93a ffffed03`2b23f9e0 fffff807`5e334c01 00000000`00000004 : nt!KiSystemServiceCopyEnd+0x25 ffffed03`2b23f788 fffff807`5e65c93a : ffffed03`2b23f9e0 fffff807`5e334c01 00000000`00000004 00000000`0000000a : nt!KiServiceLinkage ffffed03`2b23f790 fffff807`5e65fff1 : 00000000`0000000a fffff807`5e334c01 00000000`00000004 00000000`00000004 : BEDaisy+0x32c93a ffffed03`2b23f8e0 fffff807`43af53b5 : ffffb08a`4c91e040 fffff807`5e334cb0 00000000`00000000 000fa4ef`bd9bbfff : BEDaisy+0x32fff1 ffffed03`2b23fb10 fffff807`43bfe278 : fffff807`4123f180 ffffb08a`4c91e040 fffff807`43af5360 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffffed03`2b23fb60 00000000`00000000 : ffffed03`2b240000 ffffed03`2b239000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: BEDaisy+32c93a

MODULE_NAME: BEDaisy

IMAGE_NAME: BEDaisy.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 32c93a

FAILURE_BUCKET_ID: AV_R_INVALID_BEDaisy!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {87fe11a0-6d87-e4e2-4753-299ea15a8beb}

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

Share this post


Link to post
Share on other sites
Sign in to follow this  

×