@EA_Alijo Requested report: PC hard freezes since Season 3, returned in Season 4
Hello @EA_Alijo
As requested, I am opening a new thread and attaching my current DxDiag report together with the only crash dump (.dmp) that I was able to obtain during the original investigation.
Because this issue has now persisted across multiple seasonal updates despite extensive troubleshooting, I wanted to provide a complete chronological history instead of reporting only the latest symptoms. I believe the timeline itself may contain important clues that could help identify the underlying cause.
I have been playing Battlefield 6 since December. Throughout Season 1 and Season 2, the game ran flawlessly. I never experienced a single freeze, crash, or system instability, and my PC has remained completely stable in every other game and application.
Everything changed with the release of Season 3.
Shortly after the Season 3 update, Battlefield 6 began randomly freezing my entire computer after several minutes of gameplay. Sometimes it happened before joining a battle, or in the menu, or maybe after five minutes, sometimes after fifteen or twenty, but eventually the result was always the same: the image froze completely, Windows became entirely unresponsive, and the only way to recover the system was by performing a hard reset.
Since this behavior was exclusive to Battlefield 6, I began an extensive troubleshooting process over the following weeks.
Among many other tests, I performed multiple clean AMD driver installations using DDU in Safe Mode, tested several different Radeon driver versions, updated my motherboard BIOS, installed the latest AMD chipset drivers, verified the integrity of the game files, completely reinstalled Battlefield 6, reinstalled EA Anti-Cheat, repaired Windows using both SFC and DISM, reviewed Windows Event Viewer, analyzed the generated crash dump using WinDbg, restored all Radeon settings to their defaults, and tested different graphics configurations and frame rate limits.
The attached crash dump corresponds to the only BSOD generated during the entire investigation. WinDbg identified it as a DPC_WATCHDOG_VIOLATION (0x133). The analysis consistently pointed to ntkrnlmp.exe (KeAccumulateTicks), but it never identified any specific third-party driver, hardware device, or software component as the direct cause of the failure.
Apart from that single watchdog crash, the vast majority of failures resulted in complete system freezes that produced no usable crash dump at all, making the issue particularly difficult to diagnose.
One of the most significant improvements came after rolling back to AMD Adrenalin 25.9.1 WHQL, which proved noticeably more stable than the newer driver versions I had tested.
Another important observation came after completely reinstalling Battlefield 6 and later clearing the EA App cache using App Recovery. After those steps, the behavior of the game changed dramatically. Battlefield became completely stable again, allowing me to play for several weeks, including many long gaming sessions, without a single freeze or crash. At that point I genuinely believed the issue had finally been resolved.
Unfortunately, everything changed again with the release of Season 4.
Immediately after updating to Season 4, Battlefield began freezing my entire computer again with symptoms that are virtually identical to those experienced during the beginning of Season 3.
Another detail that caught my attention is that Battlefield once again started recompiling shaders every time the game launches. This is exactly the same behavior I observed when the issue originally appeared during Season 3. During the weeks when the game remained completely stable, shader compilation behaved normally, but after the Season 4 update it returned to recompiling shaders at every launch.
Naturally, I repeated the exact same troubleshooting steps that had previously restored stability. I cleared the EA App cache again because that had coincided with a major improvement during Season 3. Unfortunately, this time it made absolutely no difference. I also continued testing different AMD driver versions, including Adrenalin 25.9.1 WHQL, which had previously provided the best results. Under Season 4, however, even that driver is no longer sufficient to restore stability.
One detail that I believe may be relevant is that between the period when the game was completely stable and the moment the issue returned with Season 4, there were no hardware changes, BIOS changes, Windows reinstallation, CPU changes, GPU changes, RAM changes, storage changes, or significant software changes on my system. The only meaningful change before the freezes returned was the Season 4 update itself.
This repeatable sequence—stable throughout Season 1 and Season 2, unstable after Season 3, stable again for several weeks after troubleshooting, and unstable again immediately after the Season 4 update—appears to form a consistent pattern rather than isolated random failures.
During the original investigation, I was directed by a Community Manager to the main technical megathread dedicated to these freezing issues, where many affected players were gathering information and comparing troubleshooting results.
For reference, my original report and follow-up posts can be found here:
That discussion documents the complete troubleshooting process, every major test that was performed, the temporary recovery achieved during Season 3, and all the observations collected while trying to isolate the problem.
At this point, my impression is that Season 4 has brought the issue back to almost exactly the same state in which it originally appeared during Season 3. The symptoms are practically identical, while the workaround that previously restored stability is no longer effective.
The fact that the game remained completely stable for several weeks before the Season 4 update strongly suggests that the underlying trigger may be influenced by changes introduced between seasonal updates rather than by a permanent hardware or operating system issue.
For completeness, I am attaching both my current DxDiag report and the original WinDbg crash dump in the hope that they may provide additional information for the investigation.
If there are any additional logs, ETW traces, memory dumps, experimental builds, or diagnostic tools that could help narrow down the root cause, I would be more than happy to provide them and continue testing.
If this report can help correlate similar cases reported by other players or assist the development team in identifying a common pattern, I will gladly continue providing any additional information or performing any further diagnostic tests that may be useful.
Thank you again for your time, @EA_Alijo, and for continuing to investigate this issue. I genuinely appreciate your efforts
