Forum Discussion

EA_Blueberry's avatar
EA_Blueberry
Icon for Community Manager rankCommunity Manager
4 years ago

Re: BF2042 Crashes to Desktop

@o_OTrip wrote:

Any overlay app will cause this crash to desktop without an error like Discord overlay, MSI Afterburner + rivatuner, Origin overlay ,NZXTCAM overlay, and many others.

Try to disable any overlay draw and you should be able to play without any issues.

Hope this helps someone.

Programs CAN conflict with games at times. One thing we recommend doing is performing a clean boot and then immediately launch the game as administrator before you launch anything. This way if the game runs normally, it's possible one or a combination of overlays or other software running in the background can help lead up to the crash. Opening up one at a time is a good way to potentially find out the culprit, however this might not ultimately be the primary root cause of the crashes everyone is experience. Great callout though!


How to Clean Boot your PC

https://help.ea.com/en-us/help/faq/how-to-clean-boot-your-pc/

If you're still crashing after a clean boot, please provide us a DxDiag so we can gather this information for the Battlefield team.

It is also helpful to know any error messages you get when it crashes and describe what you're doing right before it crashes.

How to gather DxDiag information

https://help.ea.com/en-us/help/pc/how-to-gather-dxdiag-information/

5 Replies

  • o_OTrip's avatar
    o_OTrip
    4 years ago
    @EA_Blueberry my crashing to desktop was caused by Discord overlay, not sure why. Once the overlay is disabled the game runs normally without any issues or crashes.
  • junkPost's avatar
    junkPost
    4 years ago

    Hi,

    same problem here: Playing for half an hour or so and that in the game - crash to desktop.

    Win 10 Pro

    CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz 4.00 GHz

    RAM: 16 GB

    Graphics:  NVIDIA GeForce GTX 970 , driver version 496.76

    Here is one of the CrashDumps:

    Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\xxx\Documents\Battlefield 2042\CrashDumps\CrashDump_2021.11.21_00.06.13.915.mdmp]
Comment: 'Frostbite MiniDump. Address: 14033b4fe (In Windbg type: .ecxr)
[EOF]'
User Mini Dump File: Only registers, stack and portions of memory are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Version 19042 MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS
19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Debug session time: Sun Nov 21 00:06:14.000 2021 (UTC + 1:00)
System Uptime: not available
Process Uptime: 0 days 0:33:10.000
................................................................
................................................................
..........................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(4d0.5314): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ffb`e17ceba4 c3              ret
0:026> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Fault
    Value: Write

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on PC-MIKE

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 18

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : Timeline.Process.Start.DeltaSec
    Value: 1990


COMMENT:  Frostbite MiniDump. Address: 14033b4fe (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 (14033b47e-14033b57d)
14033b470  30  3f  d6  61  fb  0d  d9  13  10  ef  e1  06  41  e5 *6d *04 0?.a........A.m.
14033b480 *48 *81 *c1 *08 *01 *00 *00 *e8 *94 *ae *06 *01 *48 *8b *83 *e8 H...........H...
14033b490 *00 *00 *00 *48 *85 *c0 *74 *1a *48 *83 *b8 *a0 *00 *00 *00 *00 ...H..t.H.......
14033b4a0 *75 *10 *80 *bb *20 *01 *00 *00 *00 *74 *07 *c6 *83 *20 *01 *00 u... ....t... ..
14033b4b0 *00 *00 *48 *83 *c4 *20 *5b *c3 *cc *cc *cc *cc *cc *cc *cc *cc ..H.. [.........
14033b4c0 *48 *83 *ec *28 *b8 *01 *00 *00 *00 *87 *05 *b9 *90 *73 *05 *85 H..(.........s..
14033b4d0 *c0 *74 *0c *b9 *e8 *03 *00 *00 *e8 *f3 *3d *5b *00 *eb *f4 *83 .t........=[....
14033b4e0 *f9 *01 *75 *1a *e8 *37 *26 *07 *01 *41 *b8 *01 *00 *00 *00 *48 ..u..7&..A.....H
14033b4f0 *8d *15 *aa *56 *6d *04 *48 *8b *c8 *e8 *02 *0c *07 *01 *c7 *04 ...Vm.H.........
14033b500 *25 *00 *00 *00 *00 *01 *00 *00 *00 *48 *83 *c4 *28 *c3 *cc *cc %........H..(...
14033b510 *c6 *81 *20 *01 *00 *00 *01 *e9 *14 *57 *ce *02 *cc *cc *cc *cc .. ......W......
14033b520 *48 *8b *41 *f8 *c6 *81 *3d *01 *00 *00 *00 *48 *83 *c1 *f8 *48 H.A...=....H...H
14033b530 *ff *60 *38 *cc *cc *cc *cc *cc *cc *cc *cc *cc *cc *cc *cc *cc .`8.............
14033b540 *8b *42 *0c *3d *d7 *fe *31 *f7 *74 *19 *3d *22 *3f *85 *43 *75 .B.=..1.t.="?.*
14033b550 *1e *48 *8b *41 *e0 *48 *83 *c1 *e0 *8b *52 *58 *48 *ff *a0 *b0 .H.A.H....RXH...
14033b560 *00 *00 *00 *48 *8b *41 *e0 *48 *83 *c1 *e0 *48 *ff *60 *50 *c3 ...H.A.H...H.`P.
14033b570 *e9 *9b *b7 *c6 *07 *9a *27 *6b *8e *25 *e9 *fa *2d *b3  84  df ......'k.%..-...

CONTEXT:  (.ecxr)
rax=0000000000000000 rbx=0000000145822038 rcx=00000000ffffffff
rdx=0000000037c02df0 rsi=0000000000000001 rdi=0000000145822048
rip=000000014033b4fe rsp=000000004f57eda0 rbp=000000045f910000
 r8=000000000000004f  r9=0000000037c60070 r10=0000000037c4472c
r11=0000000144a10bac r12=0000000000000001 r13=1ffffffffffffffc
r14=0000000144bc55b0 r15=0000000000010000
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
BF2042!isGlimpseEnabled+0x1ae:
00000001`4033b4fe c704250000000001000000 mov dword ptr [0],1 ds:00000000`00000000=????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 000000014033b4fe (BF2042!isGlimpseEnabled+0x00000000000001ae)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

PROCESS_NAME:  BF2042.exe

WRITE_ADDRESS:  0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000000

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+0x0


SYMBOL_NAME:  memory_corruption!BF2042

STACK_COMMAND:  ** Pseudo Context ** ManagedPseudo ** Value: 1f97db27160 ** ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_256_c0000005_memory_corruption!BF2042

IMAGE_NAME:  memory_corruption

MODULE_NAME: memory_corruption

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {dd859c97-ba9b-49ae-e123-2ae5f24dcf95}

Followup:     MachineOwner
---------
  • Kuiriel's avatar
    Kuiriel
    4 years ago
    @EA_Blueberry Game was working well enough until yesterday - there were bugs but no crashes. Yesterday crashes for both my wife's pc and my own. No driver updates, no recent Windows updates that we could see in the list, no game updates that we know of. Was there an update server side? No discord overlay, even turned off flow control for bf2042, no virus protection or firewalls running, no controller plugged in.

    Just joystick, and playing on steam so can't turn off the origin in game overlay, and I think I need the steam overlay for my joystick to work, I forget.
  • EA_Blueberry's avatar
    EA_Blueberry
    Icon for Community Manager rankCommunity Manager
    4 years ago

    @Kuiriel 

    Can you try disabling Origin Overlay under Settings and see if it still crashes on you? As others have mentioned, Discord overlay was causing it for them and I've seen their overlay also cause mouse issues in the past. 

    Does it crash on you if you don't have the joystick plugged in and also steam's overlay turned off/on? That way we can determine if it could be the root cause?

  • Kuiriel's avatar
    Kuiriel
    4 years ago
    @EA_Blueberry Steam overlay is off. Discord overlay is off. Origin overlay in game is forced on and grayed out under settings, even though it's off in overall origin settings, because it's a Steam purchase and apparently I don't have a choice there then?

    I'll test without the joystick next time, today. It seemed to work fine as long as I turned off windows anti virus real time protection. Given that this was a new bug for me that only just happened, I do wonder if it was somehow triggered by Windows defender.

    I have no mouse issues after clearing keybindings for controller soldier and setting those controller schemes to custom.

About Battlefield 2042 Technical Issues & Bugs

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