Crash to desktop starwars battlefront 2 midgame
I keep getting crashes to desktop midgame, no error message pops up. The game freezes for 3 seconds and then closes and im back at my desktop (like it just alt+f4'd me out the game) I ran the memory dump crash file through winDbg, this is its contents:
KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 73061 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on SAM Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 319849 Key : Analysis.Memory.CommitPeak.Mb Value: 4722 Key : Analysis.System Value: CreateObject Key : Timeline.OS.Boot.DeltaSec Value: 10223 Key : Timeline.Process.Start.DeltaSec Value: 1284 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 Key : WER.Process.Version Value: 1.0.117.50617 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 COMMENT: Frostbite MiniDump. Address: 00007FF8E113D759 (In Windbg type: .ecxr) [EOF] NTGLOBALFLAG: 0 PROCESS_BAM_CURRENT_THROTTLED: 0 PROCESS_BAM_PREVIOUS_THROTTLED: 0 CONTEXT: (.ecxr)rax=bf00474e55485f45 rbx=0000000000000001 rcx=bf2b6af7bf2b6af7 rdx=bf2b6af7bf2b6af7 rsi=000000004a301120 rdi=000000004a301120 rip=00007ff8e113d759 rsp=00000000450f57b0 rbp=00000000450f5990 r8=00007ff8e33fa9f0 r9=bf0c238dbf0c238d r10=bf0c238dbf0c238d r11=bf198dc7bf198dc7 r12=000000004a30c378 r13=00000000887a0006 r14=0000000000000aa8 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206 KERNELBASE!RaiseException+0x69: 00007ff8`e113d759 0f1f440000 nop dword ptr [rax+rax] Resetting default scope EXCEPTION_RECORD: (.exr -1)ExceptionAddress: 00007ff8e113d759 (KERNELBASE!RaiseException+0x0000000000000069) ExceptionCode: 887a0006 ExceptionFlags: 00000000 NumberParameters: 0 PROCESS_NAME: starwarsbattlefrontii.exe ERROR_CODE: (NTSTATUS) 0x887a0006 - The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application. EXCEPTION_CODE_STR: 887a0006 STACK_TEXT: 00000000`450f57b0 00000001`415c33b9 : 00000000`00000aa8 00000000`00000001 00000000`00000001 00000000`4a301120 : KERNELBASE!RaiseException+0x69 00000000`450f5890 00000001`415c5986 : 00000000`0002a90b 00000000`450feb70 00000000`00000000 00000000`0002a90b : starwarsbattlefrontii!isGlimpseEnabled+0x1439e09 00000000`450fea70 00000001`414f7bdc : 00000000`4e799150 00000000`4a34cde0 00000000`31f7d400 00000000`4e799150 : starwarsbattlefrontii!isGlimpseEnabled+0x143c3d6 00000000`450ff850 00000001`411f0326 : 00000000`31fb4180 00000000`31fb421c 00000000`31f7d400 00000001`43fe05c0 : starwarsbattlefrontii!isGlimpseEnabled+0x136e62c 00000000`450ff900 00000001`411ee42a : 00000000`31fb4180 00000000`00000000 00000000`31f7d310 00000000`00000000 : starwarsbattlefrontii!isGlimpseEnabled+0x1066d76 00000000`450ff940 00000001`411f433c : 00000000`00000000 00000000`31fafe80 00000000`00000000 00000000`00000000 : starwarsbattlefrontii!isGlimpseEnabled+0x1064e7a 00000000`450ff9e0 00000001`4776dc7c : 00000001`43fe05c0 00000000`450ffca0 00000001`43fe0401 00000001`43d05e80 : starwarsbattlefrontii!isGlimpseEnabled+0x106ad8c 00000000`450ffb90 00000001`4776d78a : 00000000`2c362038 00000001`43fe04e0 00000000`00000000 00000001`43dafb50 : starwarsbattlefrontii!AmdPowerXpressRequestHighPerformance+0x3cc2d88 00000000`450ffc70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : starwarsbattlefrontii!AmdPowerXpressRequestHighPerformance+0x3cc2896 SYMBOL_NAME: starwarsbattlefrontii!isGlimpseEnabled+1439e09 MODULE_NAME: starwarsbattlefrontii IMAGE_NAME: starwarsbattlefrontii.exe STACK_COMMAND: ~17s ; .ecxr ; kb FAILURE_BUCKET_ID: APPLICATION_FAULT_887a0006_starwarsbattlefrontii.exe!isGlimpseEnabled OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 1.0.117.50617 FAILURE_ID_HASH: {600659f4-1e1f-0dec-7da1-e7db20efe344} Followup: MachineOwner ---------
"0x887a0006" which has popped up in the past with other EA games appears present.
@EA_AticHey Atic. I've been dealing with this same crash for a while now and I may have something new for you to suggest to others.
There are 2 errors I've been seeing consistently in Battlefront 2's crash logs that coincide with the game closing / crashing to desktop without warning at random times (e.g, while loading a multiplayer map, during any MP game mode match at random, as soon as a loading screen transitions to in-game, even during single-player campaign and arcade mode occasionally).
These are the two errors:
Error 1 (0xc0000005 - d3d11.dll):
This is a Memory Access Violation error (0xc0000005) in module d3d11.dll (yes I tried reinstalling VC++ runtime libraries and direct-x) and it is the error I see most often when I get this crash to desktop.
Error 2 (887a006):
APPLICATION_FAULT_887a0006_starwarsbattlefrontii.exe!isGlimpseEnabled. This was seen less frequently (using windbg to open the .dump SWBF2 crash log files) but the symptoms are identical to error 1 (running perfectly fine locked 60 fps max settings and suddenly it closes without warning)
I have tried all of the routine troubleshooting strategies EA support are copy/pasting around.
-updating hardware drivers (chipset, GPU, BIOS - - all using DDU or other clean install methods) and Windows itself
-reinstalling origin/game
-disabling in-game overlays
-disabling ansel
-disabling xbox game bar / game mode
-uninstalling front-end OC software like MSI afterburner (and reverting any applicable OCs to stock)
-uninstalling GFE
-repairing the game
-clearing OS/Origin/game cache/temp files/my documents user files for SWBF2
-disabling DX12
-toggling other in-game settings on and off and checking the .cfg files for conflicting boot settings
-scanning and repairing system files (sfc scannow)
-running DISM repair
-running windows memory diagnostics/memtest86
-installing both Origin and Battlefront 2 on the same SSD (a new one too, purchased while ruling out my old HDD as the problem)
-adjusting page file / virtual memory for my drives (while troubleshooting the memory access violation error specifically)
-running Origin client (just the main application exe alone, AND all 23 .exe files scattered throughout the Origin program files subdirectories) in administrator mode
-running the game exe in administrator mode
None of that worked for me and I've read dozens of threads where other people tried all of the above and still had the crashes (just like me).
Yesterday I was reading up on memory access violation errors and what causes them for other people and I thought it might be worth disabling my RAM overclock in the BIOS. My RAM is on the QVL for my motherboard, I did my research. It runs fine and again, never had an issue with any other game crashing.
Now, I've never had to do this for any game and I have not received 1 blue screen or system crash since building this PC a year and a half ago. I'm an advanced user and I keep my system in very good working order inside and out.
Knowing the frostbite engine is picky I thought hey, why not try setting my RAM timings manually instead of using XMP profile which can result in unstable voltages and clock speeds due to everything defaulting to "auto" in DRAM overclock menus.
I took pictures of all my RAM timings in the BIOS which were automatically set my XMP and then disabled XMP and manually keyed in all of the same values essentially changing nothing, just removing the "auto" variable from the equation.
Then I rebooted and noticed my RAM was running at 2666mhz instead of 3200mhz which they are rated at and were running at under XMP profile 1 for a year and a half without issue. I decided to turn XMP back on since my manual settings were not applying right and this is where something unexpected happened. I double-checked and all of the XMP / DRAM overclock settings are back to "auto" as they were before the change, yet the game no longer crashes.
RAM overclocking is a grey zone for some people. When someone suggests "reverting overclocks" most people think CPU/GPU. RAM is supposed to run at x speed but runs at y speed out of the box so I think some people don't consider XMP RAM OC to fall under the same category as GPU/CPU overclocking.
Hence why I didn't try this until now. Maybe you could suggest restoring BIOS settings to default to people who have tried all the usual stuff and still get the crash like I did. It appears to have fixed it for me.
