Forum Discussion

Re: Constant c0000005 (Access violation) errors causing crashes

I did extensive tests on my RAM (16GB) in the past 2 days including WIndows Memory Diagnostic and MemTest86 and all have resulted in zero errors which means my RAM isnt the issue. For some reason since Update #3, I have been getting non-stop crashing due to this memory access violation error and I have no clue how to fix it. I tried to disable Data Execution Protection in Windows Defender but that only prolonged the persistent crashing by about 5-10 minutes then its an immediate crash. If anyone can help me fix this, I will appreciate it greatly.

5 Replies

  • EA_Atic's avatar
    EA_Atic
    Icon for DICE Team rankDICE Team
    4 years ago
    Could you try another windows account with admin rights and see if the same issue happens.@SilentReaprr

    /Atic
  • SilentReaprr's avatar
    SilentReaprr
    New Traveler
    4 years ago

    Sure i'll give that a try sometime this weekend and will report back

  • SilentReaprr's avatar
    SilentReaprr
    New Traveler
    4 years ago

    @EA_Atic I created a brand new local account with administrator privileges and same result. It crashed after 10 minutes of gameplay and a c0000005 error code after checking the crash dump file. Next i'll order new RAM tomorrow to see if that'll fix the issue. I'll also get my current kit replaced by G. Skill just in case its faulty.

  • SilentReaprr's avatar
    SilentReaprr
    New Traveler
    4 years ago

    @EA_Aticbrand new ram kit and same issue. It seems my ram isnt the issue here unfortunately. This is the result from my latest crashdump from today

    COMMENT: Frostbite MiniDump. Address: 140ecb8be (In Windbg type: .ecxr)
    [EOF]

    NTGLOBALFLAG: 0

    PROCESS_BAM_CURRENT_THROTTLED: 0

    PROCESS_BAM_PREVIOUS_THROTTLED: 0

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !BF2042
    140ecb83e-140ecb93a 253 bytes - BF2042!isGlimpseEnabled+b8386e
    [ 33 95 c9 3a 02 e8 00 d6:59 48 54 f3 0f 58 08 74 ]
    140ecb93c-140ecb93d 2 bytes - BF2042!isGlimpseEnabled+b8396c (+0xfe)
    [ 3e 1e:5b c3 ]
    142be89ba-142be8a0b 82 bytes - BF2042!isGlimpseEnabled+28a09ea (+0x1d1d07e)
    [ 57 60 a4 b3 36 59 2c 0f:04 6b 41 8b d0 41 8b c8 ]
    142be8a0d-142be8ab9 173 bytes - BF2042!isGlimpseEnabled+28a0a3d (+0x53)
    [ 37 36 a8 77 9f 5f f9 01:48 b8 07 e7 63 70 3e 06 ]
    510 errors : !BF2042 (140ecb83e-142be8ab9)

    CONTEXT: (.ecxr)
    rax=ffffffffe3646d10 rbx=000000004f56f500 rcx=000000004f56f500
    rdx=000000013de5dc15 rsi=00000001e3af9d20 rdi=000000001fd2c228
    rip=0000000140ecb8be rsp=000000004f56f1a0 rbp=000000004f56f390
    r8=00000001e3646d20 r9=000000004f56f5c0 r10=00000001e3646d10
    r11=000000004f56f2e0 r12=0000000000000000 r13=00000001c5348060
    r14=00000001e3646aa0 r15=00000001e2fbd510
    iopl=0 nv up ei pl zr na po nc
    cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
    BF2042!isGlimpseEnabled+0xb838ee:
    00000001`40ecb8be 80790800 cmp byte ptr [rcx+8],0 ds:00000000`4f56f508=00
    Resetting default scope

    EXCEPTION_RECORD: (.exr -1)
    ExceptionAddress: 0000000140ecb8be (BF2042!isGlimpseEnabled+0x0000000000b838ee)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 00000000ce7e6f25
    Attempt to read from address 00000000ce7e6f25

    PROCESS_NAME: BF2042.exe

    READ_ADDRESS: 00000000ce7e6f25

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

    EXCEPTION_CODE_STR: c0000005

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: 00000000ce7e6f25

    ADDITIONAL_DEBUG_TEXT: Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

    STACK_TEXT:
    00000000`00000000 00000000`00000000 memory_corruption!BF2042.exe+0x0


    STACK_COMMAND: ** Pseudo Context ** ManagedPseudo ** Value: ffffffff ** ; kb

    SYMBOL_NAME: memory_corruption!BF2042.exe

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE_c0000005_memory_corruption!BF2042.exe

    IMAGE_NAME: memory_corruption

    MODULE_NAME: memory_corruption

    OS_VERSION: 10.0.19044.1415

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

  • SilentReaprr's avatar
    SilentReaprr
    New Traveler
    4 years ago

    @EA_Aticgood news. After further investigation and troubleshooting, the issue turned out to be an unstable CPU overclock. I turned it down 100 Mhz and now it stopped crashing. My RAM kit wasnt the issue after all.

About Battlefield 2042 Technical Issues & Bugs

Having issues with Battlefield 2042? Join here to report bugs, and find help with, crashes, connectivity and more.12,993 PostsLatest Activity: 2 hours ago