Forum Discussion
So here's my latest update:
I uninstalled my entire game, and video drivers using Revo uninstaller for the game and Display driver uninstalled for the GPU - Both via Safe mode.
Reinstalled them both. After that, the game seemed to be a lot more stable. Two days of blissful crash free gaming (2 - 3 hrs per evening that is).
I thought, I've cracked it..... and literally as if it sensed what I'd said, Immediate crash to desktop.
Restarted the PC and game. A bit more crash free gaming. I thought, it must have just been an anomaly. This evening however, I spent TWO full hours literally being either unable to load the game entirely, if I did get in, I couldn't load into a round as it would CTD. I did get in a couple of rounds but did not get more than 5 mins into it before being booted. So, tonight, no one single full round of BF2042.
I noticed a cumulative update was required for Windows 11 so I ran that update. Restarted and my game ran stable for 3 rounds.... then it just crashed out. I've not gone back in because it's 2:25am and I'm absolutely f'king raging. :D
EA - ABSOLUTELY NO OTHER GAME DOES THIS!!!!! BF2042 is an outright mess.
I've reinstalled the game multiple times
Repaired it multiple times
Reinstalled Video drivers multiple times (even tried the Pro.24 Q4 AMD driver)
Scanned the system for Malware / Viruses.
Run System File Check within Windows
Closed EVERY SINGLE unnecessary process/service down that I do not feel needs to run.
Tried playing via a secondary user account on my PC
Opened and closed ports on my router
Tried via a VPN
Tried directly tethering to my cell phone using a 5G connection
Reset my BIOS to optimised defaults (thus disabling OC profiles)
Under-clocked my RAM speeds
Switched to the secondary BIOS on my Radeon Sapphire Nitro+ 7900 XTX which is by factory settings an under-clocked version.
Come back to the default full power BIOS on the GPU.
Tried with my secondary monitor powered off and disconnected.
I've Enabled DX12 in the config, Disabled it, Re-enabled it.
I've run the executable as an administrator
Tried Windows, Borderless, Full screen.
Disabled full screen optmisations
Run the game in full minimal graphics settings.
Run MemTest which completed with No Errors.
Prayed to Covfefe, Offered my Soul to Covfefe
The only things I haven't done is to reinstall Windows, try a different Power Supply but I have a high quality 1000w PSU. I could try installing the game on a different disk drive. That would mean moving it off my M.2 drive on to a regular platter drive. Heck, if that worked, I could handle the longer load times. It's not as if the loading process is quick anyway with the forced loading screens.
I use this machine to edit 4K 100,000 Bitrate video footage and it chews through that kind of work absolutely solidly.
It's not any specific map or game mode. All suffer the same random out of the blue for no good reason Crash to Desktop.
Interrogating the Crashdump reveals the following line: "ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s."
I've taken this from ANOTHER discussion here on the Forums for someone having the exact same issues TWO YEARS ago!
"C0000005 is a Windows system error code that indicates an access violation. This typically occurs when a program attempts to read or write to a memory location that it does not have permission to access. Some key things to know about the c0000005 error:
- It is a software issue, not a hardware one. The error occurs because of a bug or flaw in a program's code, not because of a physical problem with the hardware.
- It often happens when a program attempts to access an invalid memory address, tries to read from a write-only location, or writes to a read-only location.
- The specific program that triggered the error will be indicated in the error details. The error generally occurs within that program's code.
- It can sometimes be caused by a corrupt registry, drivers, or system files. Reinstalling or updating these can potentially resolve the issue.
- Hardware issues like bad RAM or a failing hard drive can lead to c0000005 errors, but only because they cause system file corruption that the software then struggles to deal with.
So in summary, c0000005 indicates an access violation bug within software code. Troubleshooting should focus on identifying the faulty software and then either updating/reinstalling it or correcting the specific coding error causing the problem. Hardware issues are rarely the root cause."
Because MEMTEST doesn't come back with any errors, I can only assume this is software related (and very much BF2042).
I will probably give in and reinstall Windows (or at least install via a Dual Boot) but I do not hold out ANY hope with this.