Forum Discussion
Hi there. Thanks for the DxDiag. It looks like you just updated your Nvidia driver. Try using DDU in Safe Mode to remove it and then install an older driver. Let me know how it goes.
I updated my NVIDIA Driver this morning. The first freezes happened yesterday before the driver update.
- EA_Aljo27 days ago
Community Manager
Thanks for letting me know. You may want to try rolling back your GPU driver to a previous version. Here are some other suggestions as well.
- Disable any GPU overclocking/undervolting. If you use MSI Afterburner or ASUS GPU Tweak, reset them to stock
- Check your temps while playing. Your GPU should say about or under 80°C and 85°C for the CPU
- Test your RAM by running MemTest64 or OCCT. If it's unstable, disable EXPO/XMP in the BIOS temporarily and test again
- Delete the Battlefield shader cache folder and repair the game in the EA App/Steam
- Disable Hardware Accelerated GPU Scheduling as a test. Go to Windows Settings > Graphics and turn this off. Then, reboot.
- MrSpicy199627 days agoRising Rookie
Thanks for trying.
I didn't change anything on my system yesterday. So there is no need to roll back for any driver.
The freeze happened before any driver updates and persists after the updates.
On Reddit and Steam there're a lot of ppl with the exact same problem and everyone of them has their build with a AMD cpu (and probably all on an X3D cpu).
If I had one guess, I'd say it's the anti-cheat again. The kernel anti-cheat was many times the culprit for my problems with crashes, but this time it is a whole system freeze.
Edit: Just starting the game froze my system....
Edit2: Also happens on BFV, it has to be the latest anti cheat update. - herod0t23 days agoNew Rookie
please just stop , read the topic , see people did do more than you suggest , acknowledge is not our fault and some of us we know what hardware we have . This is the only games who hard freeze the pc . No other games on the market no matter how bad they are will not hard lock the computer.
There are no crash dumps given the nature of the hard lock
Windows event view has no information due to the nature of this hard lock