Constant c0000005 (Access violation) errors causing crashes
COMMENT: Frostbite MiniDump. Address: 140ecb8c7 (In Windbg type: .ecxr)
[EOF]
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
CHKIMG_EXTENSION: !chkimg -lo 50 -d !BF2042
140ecb847-140ecb93a 244 bytes - BF2042!isGlimpseEnabled+b83877
[ b8 ac e7 29 ea 06 f0 14:0f 2f c3 77 05 0f 2f d1 ]
140ecb93c-140ecb943 8 bytes - BF2042!isGlimpseEnabled+b8396c (+0xf5)
[ 3e 1e 1f 28 ba aa 42 c7:5b c3 cc cc 48 89 5c 24 ]
140ecb945-140ecb946 2 bytes - BF2042!isGlimpseEnabled+b83975 (+0x09)
[ ba 5e:57 48 ]
14364151d-1436415f3 215 bytes - BF2042!GetDenuvoTimeTicketRequest+67a81d (+0x2775bd8)
[ 30 d6 4c 11 99 25 fc 2e:b9 18 00 00 00 48 c7 44 ]
1436415f5-143641630 60 bytes - BF2042!GetDenuvoTimeTicketRequest+67a8f5 (+0xd8)
[ e7 ae 95 fb 34 93 0f 0d:d2 41 0f b7 46 02 41 8b ]
143641632-143641636 5 bytes - BF2042!GetDenuvoTimeTicketRequest+67a932 (+0x3d)
[ 77 5c 4d aa 51:0f 59 c1 f3 41 ]
534 errors : !BF2042 (140ecb847-143641636)
CONTEXT: (.ecxr)
rax=0000000032429200 rbx=000000004f2cf500 rcx=000000004f2cf500
rdx=000000013de5dbf9 rsi=00000001ec695c80 rdi=00000001de023528
rip=0000000140ecb8c7 rsp=000000004f2cf1a0 rbp=000000004f2cf390
r8=0000000232429210 r9=000000004f2cf5c0 r10=0000000232429200
r11=000000004f2cf2e0 r12=0000000000000000 r13=00000000568a6010
r14=0000000232428f90 r15=00000001f3e28f98
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+0xb838f7:
00000001`40ecb8c7 0000 add byte ptr [rax],al ds:00000000`32429200=??
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000140ecb8c7 (BF2042!isGlimpseEnabled+0x0000000000b838f7)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000209f702c9
Attempt to read from address 0000000209f702c9
PROCESS_NAME: BF2042.exe
READ_ADDRESS: 0000000209f702c9
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: 0000000209f702c9
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
FAILURE_ID_HASH: {2871c057-a757-f9e2-6f5b-b9a68f67761f}
@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.