Forum Discussion
The latest version hadn’t been released yet when I started experiencing the problem. EA released the update last week, and my game crashed. At first, I thought it was caused by the AMD drivers, so I updated them. I updated my chipsets, BIOS, Visual C++, and all my drivers; I reset my graphics settings config file, ran a file repair, and fixed the Windows Defender exceptions. I reconfigured Windows permissions. I cleared EA’s cache. I ran a file repair, but the problem still persists. I’ve tried every possible method over the past 10 days. When I read the error logs in the “CrashDumps” folder, it’s clear that the crash is entirely caused by faulty graphics engine code in the latest Battlefield 6 update.
DETAILS:
Error Code: The report directly indicates an ACCESS_VIOLATION error. Conflicting Modules: As the game fully launches, the Graphics Engine (Engine.Render.Core2.PlatformPcDx12.retail.dll), AMD’s graphics card driver (amdxc64.dll), and AMD’s Frame Generation library (amd_fidelityfx_framegeneration_dx12.dll) are conflicting with each other.
As a result:
The latest patch EA released for the game attempts to read data from an invalid or non-existent address in the graphics card’s memory (VRAM) during startup. Because of this incorrect command, the game hits a code error and crashes within the first few seconds. I’ve tried various workarounds locally, but there’s no way to fix this broken code from the outside; AMAZING EA absolutely must release a patch (hotfix) to fix this rendering error—otherwise, they’ll lose more than just one player.