4 years ago
BF2042 Still crashing
The game is still intermittantly crashing. Especially when I alt+tab the game sometimes. It does it when theres a lot going on in screen as well like a big firefight, or fire from the rocket explos...
I have an email that @EA_Atic replied but seems the comment is gone.
If it was more info...
- I've updated again to the latest Nvidia driver 512.77
- I've updated my BIOS to the latest AGESA ComboV2PI 1207
- My EVGA RTX3080 Ti FTW3 is underclocked to the stock 1775Mhz boost clock
- I have no Overclock / Precision Boost Overdrive / Curve Optimiser on my CPU
- My memory is not running in XMP, and is at the stock 2666Mhz
- Windows 11 is the very latest build and updates
Still crashed twice so far today, one of them was right after the rocket exploded on Orbital
OMMENT: Frostbite MiniDump. Address: 1431abd73 (In Windbg type: .ecxr) [EOF] NTGLOBALFLAG: 0 PROCESS_BAM_CURRENT_THROTTLED: 0 PROCESS_BAM_PREVIOUS_THROTTLED: 0 CHKIMG_EXTENSION: !chkimg -lo 50 -db !BF2042 256 errors : !BF2042 (1431abcf3-1431abdf2) 1431abcf0 12 10 4c *21 *00 *b4 *e9 *16 *a7 *19 *01 *2e *20 *99 *6b *4d ..L!........ .kM 1431abd00 *e9 *a0 *16 *77 *00 *0f *8a *35 *64 *ff *01 *e9 *db *82 *c4 *01 ...w...5d....... 1431abd10 *ad *e9 *a1 *d5 *0d *03 *cc *47 *cc *f3 *1e *c9 *0f *83 *5c *42 .......G......\B 1431abd20 *13 *03 *e9 *b1 *ef *1e *02 *aa *57 *e3 *7a *9f *78 *4c *40 *d3 ........W.z.xL@. 1431abd30 *48 *89 *5c *24 *10 *48 *89 *74 *24 *18 *57 *48 *83 *ec *20 *b8 H.\$.H.t$.WH.. . 1431abd40 *00 *08 *00 *00 *49 *8b *f8 *66 *09 *41 *14 *48 *8b *d9 *0f *b7 ....I..f.A.H.... 1431abd50 *71 *14 *40 *84 *f6 *79 *17 *48 *8b *41 *08 *48 *8d *54 *24 *30 q.@..y.H.A.H.T$0 1431abd60 *48 *89 *44 *24 *30 *4c *8b *00 *41 *ff *50 *60 *eb *08 *48 *8b H.D$0L..A.P`..H. 1431abd70 *01 *33 *d2 *ff *50 *08 *66 *0f *ba *e6 *0d *72 *28 *66 *0f *ba .3..P.f....r(f.. 1431abd80 *e6 *08 *73 *04 *48 *83 *c3 *f0 *48 *85 *ff *75 *0d *b2 *01 *48 ..s.H...H..u...H 1431abd90 *8b *cb *e8 *89 *5e *75 *fd *48 *8b *f8 *48 *8b *d3 *48 *8b *cf ....^u.H..H..H.. 1431abda0 *e8 *1b *5f *75 *fd *48 *8b *5c *24 *38 *48 *8b *74 *24 *40 *48 .._u.H.\$8H.t$@H 1431abdb0 *83 *c4 *20 *5f *c3 *cc *cc *cc *cc *cc *cc *cc *cc *cc *cc *cc .. _............ 1431abdc0 *48 *89 *5c *24 *08 *48 *89 *74 *24 *10 *57 *48 *83 *ec *20 *48 H.\$.H.t$.WH.. H 1431abdd0 *8b *f1 *41 *8b *f8 *48 *8b *49 *20 *48 *8b *da *48 *3b *ce *74 ..A..H.I H..H;.t 1431abde0 *09 *e8 *da *ff *ff *ff *84 *c0 *75 *49 *48 *8b *06 *45 *33 *c0 ........uIH..E3. 1431abdf0 *41 *8b *d0 0f cc c7 a5 a6 8a 17 71 18 bf 30 92 bc A.........q..0.. CONTEXT: (.ecxr)rax=0000000300000032 rbx=000000002038d050 rcx=000000002038d050 rdx=0000000000000000 rsi=0000000000000800 rdi=0000000000000000 rip=00000001431abd73 rsp=0000000052ebf390 rbp=00000001c6f59b00 r8=0000000000000000 r9=000000028d773a60 r10=00000000000000ca r11=0000000052ebedc4 r12=000000005c3eaa78 r13=00000001c6f59b00 r14=000000000d52b2e0 r15=0000000000000011 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!GetDenuvoTimeTicketRequest+0xbb293: 00000001`431abd73 ff5008 call qword ptr [rax+8] ds:00000003`0000003a=???????????????? Resetting default scope EXCEPTION_RECORD: (.exr -1)ExceptionAddress: 00000001431abd73 (BF2042!GetDenuvoTimeTicketRequest+0x00000000000bb293) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 000000030000003a Attempt to read from address 000000030000003a PROCESS_NAME: BF2042.exe READ_ADDRESS: 000000030000003a 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: 000000030000003a 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_256_c0000005_memory_corruption!BF2042.exe IMAGE_NAME: memory_corruption MODULE_NAME: memory_corruption OS_VERSION: 10.0.22000.1 BUILDLAB_STR: co_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {39839b07-45dd-00df-7031-f8e9ce57ef35}
MEMORY_CORRUPTION_LARGE_256_c0000005_memory_corruption!BF2042.exe
That was on crash dump file today. This happened to me 5 times today. I suppose this will never be fixed.
maybe check windows it self for any issues.
run this command in 64bit shell or open elevated command prompt (admin rights)
sfc /scannow
It's not a consistency issue in windows.
This is the 3rd fresh install on a fresh nvme since the game launched last year. Its the second completely new build, ALL new hardware.
The issue is exhasterbated when the system is overclocked even though Windows is stable and no other games crash. I currently have memory below XMP, cpu at base clock and gpu is underclocked which reduces the frequency of issues but still does it.
@EA_Atic Nothing is overclocked. It started acting up again since last night. I played for a couple of hours and then it crashed. It continued to crash to desktop 3 times before I called it quits. Today, I booted up the game and played for about 15 min before it crashed again. Restarted the game, it crashed again while attempting to join a server. Same error.
MEMORY_CORRUPTION_LARGE_256_c0000005_memory_corruption!BF2042.exe
I get this same issue with the latest version of BF2042. Just drops my straight to my Windows 11 desktop(mid game) with no errors or warnings!.. Really REALLY annoying. I am using the EA App. I think it's a bug in the game personally or the EA App, maybe in a recent patch?.. because it only recently started doing it in the past few months. None of my hardware has changed, still using the same PC that I have been using for the past 3 years!
You are right!
I also find-out that it related to the XMP, specifically XMP 2.0, try to set it on XMP 1 or Auto.
I notice this after my mobo had a bios update, all the valus deleted and reconfigure one by one later (Turn on the XMP2) the random crash began.
So changing it for Auto manage to fix it so far.
Hope EA will fix it, we are goddam in the 2023!