CTD games running smoothly with no warnings.
CTD games running smoothly with no warnings.
I've faced numerous problems lately, beginning with updating my BIOS on the Asus H610M-A D4 board. It caused major issues across my system—windows would freeze, games would crash or fail to load textures, and I ended up replacing the motherboard and swapping RAM. Once I got a new B760M-P motherboard and DDR5 RAM, most problems disappeared. After installing Palworld, it briefly crashed until I adjusted memory slots. Overwatch also stopped working after about 30-40 minutes without any error alerts. Elden Ring showed a DLL error in the event viewer, but after a clean driver reset with DDU, those crashes ceased. Now it randomly fails, usually pointing to the Elden Ring executable.
I’ve tried reinstalling drivers, using MSI Kombustor and Prime95 side by side without issues, and even ran both at once safely. No BSODs appear. The only parts I haven’t swapped are my graphics card, power supply, and CPU. I removed two older SSD drives to run the newer M2 drive, which is fairly recent. The graphics card itself hasn’t had problems beyond occasional crashes in Overwatch 2 when memory ran low—usually just a few renders before it stops.
I was advised to enable XMP profiles in BIOS, but that didn’t help. My CPU specs are Intel i7 13700K, running stock without overclocking. I’ve tested MSI B760M-P with Gigabyte GeForce RTX 4070TI and 12GB DDR5 memory, all stable. PC specs are solid—no crashes during gaming sessions. The only hiccups were in Overwatch 2 with video memory limits or rendering issues, but nothing persistent.
your processor speed is 6000mhz, which means you're overclocking. turn off XMP and test again. game performance usually shows signs of damaged files, but since you reinstalled them, inspect the storage first. checking file integrity remains a solid method too.
I would reset your memory to its default settings. It seems there might be a software issue or driver corruption. Are you using any RGB tools or driver hooking software such as afterburner or MSI motherboard utilities? Has the system received the updated firmware?
I was playing without XMP, but I decided to try XMP profile 2 because a friend suggested it on the GeForce forums for Elden Ring.
I use NZXT Cam, My Cooler, and case fans connected to the NZXT fan/RGB controller. The only MSI software I have is MSI Center with a hardware monitor installed; no other plugins are available. CPU-Z shows MSI without firmware installed—can install it now but haven’t yet. After a clean DDU install, I ran OW2 and played for about 40 minutes without any crashes. Update note: Samsung Magician reports firmware version 5B2QGXA7; unsure if the update was applied with Magician or was already present. Event viewer didn’t log any errors after Overwatch crashed at around 70 minutes.
Inspect both sites for any dump files. If they have them, retrieve the full folder. Avoid compressing the directory directly at those spots—it can irritate Windows. Move the contents to another place, such as your desktop or the Downloads folder, which remains secure regardless of sync issues. Once you have the copy, zip it and attach it to a post. If it's too big, consider using a file host. The first folder is C:\Windows\LiveKernelEvents. The second is in Appdata—press Windows + R, type "%localappdata%", select it, and confirm. Also, please share the date you adjusted the RAM settings so I can match the files accordingly.
Here you are – the file is available. I didn’t find the LiveKernelEvents folder; instead, I only saw LiveKernelReports with an empty WATCHDOG folder. I don’t recall when the module swap happened, but it might have been around the third week.
It seems you're referring to a folder where memory errors are occurring. The files are mostly showing "Reference by Pointer" issues, meaning pointers are pointing to incorrect memory locations. This often indicates memory problems or corruption. Previous crashes might have contributed to the issue. Nvidia DLL files were part of several cases, but they consistently triggered the same error. Have you performed a clean installation of the operating system with the new board? If not, consider doing so.