Crash to desktop starwars battlefront 2 midgame

@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.