[PC] Crash on Launch - bf6.exe Access Violation (ffxFsr2ResourceIsNull)

Subject: [PC] Critical Crash on Launch - bf6.exe Access Violation (ffxFsr2ResourceIsNull) - RTX 4060

Body: Game: Battlefield 6 Platform: PC (Windows 11 - Latest Build) GPU: Nvidia RTX 4060 (Drivers updated) CPU: Intel Core i9-9900KF RAM: 64 GB DDR4

Issue Description: The game consistently crashes to desktop (CTD) immediately upon launch or during the initial loading phase. No error message is displayed via UI.

Deep Technical Analysis: I performed a debugging session on the generated Crash Dump (.mdmp) using WinDbg. The environment was clean (NTGLOBALFLAG: 0, no Driver Verifier active).

The crash is a consistent ACCESS_VIOLATION (Exception Code: c0000005) attempting to read address 0000000000000000 (Null Pointer). Faulting Module: bf6.exe Faulting Function: bf6!ffxFsr2ResourceIsNull

The stack trace indicates the engine is attempting to access FSR2 resources that have not been initialized.

Reproduction & Trigger: The crash occurs when the PROFSAVE_profile settings are configured for Exclusive Fullscreen: GstRender.FullscreenMode 1 GstRender.FullscreenEnabled 1

Crucially, this crash happens even if FSR is explicitly DISABLED in the config: GstRender.FsrEnabled 0 GstRender.Fsr2Quality 0

It appears the render pipeline attempts to validate FSR resources during the Fullscreen initialization sequence regardless of user settings, resulting in a null pointer exception on RTX 40-series cards.

Current Workaround (Unstable): Manually editing PROFSAVE_profile to force Windowed/Borderless mode: GstRender.FullscreenMode 0 GstRender.FullscreenEnabled 0

NOTE: This workaround is NOT 100% consistent. While it allows the game to launch most of the time, the game remains fragile and prone to crashing if other parameters (such as GstRender.FutureFrameRendering) are toggled. A proper code fix for the FSR initialization logic is required.

Please escalate to the dev team.