I have spent the last 4 hours trying to fix my game. I have updated my bios, updated my drivers, done a complete reinstall, turned on and off features and still cannot fix the issue. No other game on my has over done this and its at the point where my game is unplayable.
Up until recently, I had zero issues. I am not sure what happened but I am close to requesting a refund from steam. I have tested my hardware and there is zero indication that there is anything wrong with it.
Has anyone else experienced anything like this? The game went from working to being unplayable.
I've had the same over the past few weeks. I had no issues up until then with 200 hrs played. It happens randomly, sometimes i can run a few games but last night i just had to turn it off it was happening that constantly even in the menus.
The game screen would go black however could still talk to and hear friends on discord then 5 to 10 seconds later the pc would reboot. Sometimes it didnt even do that and just instantly reboot.
I did a stress test on my gpu and cpu with no issues, downloaded another game (hogawarts) thinking ill try another game to see what happens, no issues.
Event viewer isnt showing me anything that could be the problem. The only thing that showed originally was a critical TPM error which looks to have gone since i updated my bios as i thought that was the cause but not seeing that error anymore.
I've had a look online, hence finding this recent post and theres so many views however im putting it down to the game, this is the only game it happens too and i havent found any component issues, will have a go at uninstalling and re installing and see if that helps but thats probably as far as ill go.
MiniMuffinz did you get an error on rebboting the game that the save file was corrupt and it makes you watch the full intro and the settings are reset?
Sounds like javelin isn't happy after it updated its signatures in Jan. Turned out my Corsair software (iCue) needed an update then it was happy again.
I have the same since 4 weeks, the mid januar update. No error logs or crashdumps available. The crash is within 10 Minutes of starting the game. No matter what I do ingame, it will crash (menu / firerang / play mp).
YOU are dealing with a kernel 41 EVENT ID in here, I had had the same problem from mounths
In cases where Kernel-Power Event ID 41 appears in the system logs—typically indicating an unexpected shutdown or instability (often CPU or memory related)—one possible cause may be overly aggressive RAM timings.
Disabling XMP or EXPO is not necessarily required. Instead, a more precise solution is to slightly relax the primary memory timings. For example, if your memory is running at 3733MT/s CL15-15-15-15 (as mine did), adjusting it to CL16-16-16-16 while keeping the same frequency can significantly improve system stability.
In this case, the memory kit that I am using is G.Skill 3200C14D-32GTZ (Samsung B-die). Samsung B-die modules are well known for their strong overclocking potential, but they can also be sensitive to tight timings, especially under heavy load.
The issue tends to appear in demanding applications and games that utilize the Frostbite engine, as this engine heavily stresses the CPU and memory subsystem. Under such workloads, stable communication between the CPU, the Integrated Memory Controller (IMC), and the Infinity Fabric (FCLK) becomes critical.
When timings are pushed to the edge of stability, high CPU load can trigger WHEA errors or Kernel 41 restarts. Slightly increasing the latency values provides additional stability margin, allowing the FCLK to communicate more reliably with the CPU and preventing sudden shutdowns.
It may pass stability tests such as y-cruncher, TestMem5 (Anta777 Extreme or Absolute profiles), yet still encounter issues in real-world scenarios.
Open-world games like Battlefield 6 can place a different and often heavier type of load on the system, stressing the CPU, memory controller, Infinity Fabric, and GPU simultaneously. This mixed workload can expose marginal instability that synthetic memory tests do not always detect.
Here's a screenshot with my timmings also bare in mind that twr tcwl needs to have the same values as the TCL (CL) with all that I hope this helps you.
Last but not least I didn't try to return in my previeus values yet but I am gonna try and test it
Please try what I suggested from my comment above, lower your timings by one value each tcl, trcdwr, trcdrd, trp make sure that twr and tcwl have the same value as with those which I mentioned also don't forget that trtp must be half the value of twr for example my twr is at 16 so I will put my trtp to 8. Try this and let me know how it went.
Having issues with Battlefield 6? Join here to find help with connectivity, performance issues, crashes and more.Latest Activity: 15 minutes ago6,859 Posts
