Hi, I consistently keep crashing to desktop after anywhere from 5min to an hour-ish of gameplay. I have repaired the game and run windows file system checks which were all successful. No error messages are displayed when its happening. Just hoping someone can take a look at the crash logs and provide some insight as I am unsure how to use Windbg to analyze the logs. Thanks in advance
it happens to many players. nothing wrong with your PC it's the game faults.
happen to me at least once a day - every day. if not this - the DX error.
shameless bump, looking for some insight into the logs. ty in advance
DICE TeamHey, @Demion03 can you try a clean boot to see if any programs are messing with Battlefield 2042 and turn off any overlay programs, such as Discord or Nvidia experience.
Can you add a Dxdiag so we can see what hardware and drivers you have?
Let me know if this works or not for you. 🙂
/Atic
Same thing is happening to me, but the game would just freeze/crash to desktop with no error; anywhere from 5 minutes to 1 hour. I can alt tab, ctrl alt delete, and end the bf2042 process. I will then have to re-open the game.
ASUS rog stix z690 gaming-A DDR4
ddr4 3600 cas14
3080ti evga ftw3
12900k
EVERYTHING is running stock and nothing is oced.
I turned off "future frame rendering" and I thought it fixed it, but then it did it again after like 45 minutes of playing.
Reinstalling the game and deleting the folder in documents = does nothing to fix this issue. I am on windows 11 fyi. Every other game works fine.
Yep I get it after an hour or two then it just go straight to desktop, my temps are good and it’s in a bare new install…..I got a feeling its a memory leak
I would like to add that Battlefield 1 does not do this, not a single crash. Neither does Diablo 2 Resurrected. I just played them both today for a long time each (to test). Clearly this seems like an issue on battlefield 2042 and NOT my system.
My specs:
12900k
Asus rog strix gaming A z690
DDR4 3600 cas14, gear 1 mode, 1T
EVGA 3080ti FTW3
Turns out this is the same "ERROR" everyone has been getting. I just saw the error (actually saw it a few times before, but a few CTD's gave no error to so that's weird) for the first time after a CTD
DirextX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG
