Game crashes upon death
Bug Report: Battlefield 2042 Crash on Death Animation So earlier today I started back playing Battlefield 2042 after not playing for about a year due to the new Dead Space collab with the new Outbreak mode. However, I'm having a serious issue where every time I die, right as the death animation starts to play, the game freezes and crashes immediately with no error message. This happens in all modes. I've looked online and seen others with similar issues. Some reported that deleting the cache folder for the game helped, but it was only a temporary fix — the issue returned within 30–45 minutes. Since deleting the folder didn’t help, I decided to reinstall the game, even though it’s large. Unfortunately, the problem got slightly worse: it started freezing even faster, sometimes before the death animation even starts. I then consulted ChatGPT, which recommended analyzing the crash dump file using a program called WinDbg. I did so, and shared the analysis with ChatGPT to interpret the results. ChatGPT Response Summary: Root Cause Summary: The crash was due to an Access Violation (0xC0000005) — specifically a read from a null or invalid pointer (0x0000000000000008). Crash Details: Module: amdxc64.dll (likely part of AMD graphics drivers) Function: Boost Serialization (boost::archive::detail::iserializer::load_object_data) Crash Reason: Attempted to read from RCX + 8, but RCX was NULL (0x0), leading to a crash. Contextual Clues: Crash occurred while BF2042.exe was running. Involves amdxc64.dll — a common AMD GPU driver library. Occurred during Boost serialization and DirectX 12 GPU pipeline operations. Likely Cause: A pointer used by the AMD graphics driver during deserialization or pipeline setup was NULL, causing the game to crash. So at this point, having done nearly every troubleshooting step and even running diagnostics with the help of ChatGPT, this is the closest I’ve gotten to an explanation. Hopefully someone from the developer team can help investigate further. And yes, before anyone asks — I did try switching the game to run in DirectX 11. The same issue persists. System Specs: CPU: AMD Ryzen 7 5800X GPU: AMD Radeon RX 6750 XT RAM: 32 GB DDR4 OS: Windows 11 Home, 64-bit Driver Version: AMD Adrenalin – latest version as of May 2025 Troubleshooting Performed: Verified game files via Steam Reinstalled the game Updated GPU drivers to the latest AMD version Set game to run as administrator Disabled all overlays (Discord, Steam, Radeon) Disabled all background apps No overclocking is done on this system
BF2042 Crash – Access Violation in amdxc64.dll
Battlefield 2042 crashes reproducibly during DirectX12 pipeline initialization. Two minidumps analyzed with WinDbg show an access violation inside amdxc64.dll at offset 0x208080. Exception code is 0xC0000005 – a read from NULL (rcx = 0, [rcx+8]). This happens inside a Boost::serialization function. Stack trace includes D3D12Core and BF2042's DeviceInit. Application Verifier was enabled in one test, confirming the error. amdxc64!boost::archive::detail::iserializer<sc_xml_iarchive, _SC_SI_PS_ATTR_CH_ENTRY>::load_object_data+0x208080 Exception Code: 0xC0000005 – INVALID_POINTER_READ Address: 0x0000000000000008 (rcx was null) The crash occurs while accessing [rcx+8] where rcx = 0, indicating a null pointer read inside the driver module, likely triggered by the game engine (Frostbite) when handling serialized shader or graphics data. Suggested Action: Please investigate how BF2042 passes pipeline/shader data to the AMD driver. A faulty object or driver issue might be the cause. Coordination with AMD may be necessary.Possible unintended NTW damage changes (8.4.1)
Update 8.4.1 states the following: Reduced AP rounds damage relation vs medium armored vehicles. The NTW (front or side hit, using the standard ammo, point blank so no damage drop off) used to deal 16 damage to a RAM and now deals 12. This doesn't seem to be the stated change as: The NTW doesn't have AP ammo (it has Anti-Material and HP Anti-Material). The RAM isn't a medium armor vehicle (it is in the Heavy Armor category). I also suspect that the damage has been reduced against other vehicles too but I can't remember how much it did against any other vehicles. Is this the intended change?
Fix ALL weapon recoil for PC players for mouse, STOP IGNORING!
This problem has LONG BEEN IGNORED by the developers in the game and the recoil is TERRIBLE for all weapons if you play with a MOUSE on a PC even at SMALL DISTANCES, an example in the video, where even turning on the ADDITIONAL RECOIL CONTROL in the weapon did not help. This has not happened in any Battlefield game. Please fix it, because it is IMPOSSIBLE to play normally with a mouse on a PC! But the example is at a short distance, and if you shoot far away, since the maps are VERY large, you get a simply HUGE RECOIL for all weapons, not just assault weapons! I am sure for players with gamepads everything is different.hit registration problem/glitch
I recently created a server in the battlefield portal and have found that whilst shooting at the enemy it's like there is a forcefield around them that can't be shot through i see sparks when bullets impact the target like when you shoot at a chainmail fence and only 2-3 bullets register out of 10-15 bullets and there is, and increased ping compared to other servers this is a massive issue as to try and get player to join the server and it's something I can't fix and this has only happened since the most recent update dice developers need to look into this and fix this fast
Dead bodies making movement sounds
yeah so for like the past month or two, maybe more, in Hazard Zone (i dont play other modes so i dont know if thats an issue outside of it), at the datadrives there are bots protecting them and when the bots are dead their bodies make sound like they are still moving. its a big problem because theres only 8 squads max in hz so every thing u hear is important, and with that bug its just harder to play, for example youre hunting a player and suddenly u hear a footstep, but its a dead bot, the player escapes redeploys etc, please fix this
