Game is crashing my entire system
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...
Forum Discussion
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
Featured Places
