Constant Game Crashes

[R_H_PvMDream]

Hi all, pulling my hair out with this one.
I have constant game crashes, mainly in games that run EAC (Easy anti cheat) haven’t played much games lately without it so can’t confirm how bad it is otherwise.

There are days I can play a couple hours with no crashes, and days that I crash 10x in 30 min.
Sometimes if I crash very fast one after another, I got a BSOD aswell, I have those dump files saved. No error messages from the games crashing, it just closes.

I have tried about everything that I can think of, Clean windows install, clean driver installs, different power modes, clean game installs, adding files, removing files, verifying files, running all the tests (RAM/GPU bench/CPU Bench/m2 tests). The event log also looks “useless” to me (I am not that good in tech, so it looks useless to me atleast)

Here are some of the specs:

Corsair RM1000x 80 Plus gold 1000 watt
ASUS ROG Strix Z690-F Gaming WiFi mobo
MSI GeForce RTX 3080 Ti Ventus 3X 12G OC GPU
Intel Core i9-12900KF 12th gen CPU
Corsair VENGEANCE RGB DDR5 32GB (2x16GB) 5600MHz

Speccy link of my stuff that ive seen in other threads:

http://speccy.piriform.com/results/ufrDIBlwbvkd5q8CdI3oXiR

[phillpower2]

Thread moved to the appropriate forum.
Operating System
Windows 11 Home 64-bit
Computer type: Desktop
[COLOR=rgb(184, 49, 47)]Installation Date: 10/28/2022 7:01:51 PM

There is a problem with the system drivers, see explanation below;

Once Windows has been clean installed you must then install first the MBs chipset drivers, then the storage/SATA drivers and third the graphics drivers, the drivers can either come from a disk provided by the motherboard manufacturer or downloaded from their site and saved to a flash drive etc, this is a must and Windows should not be allowed to check for updates before it has been done as more often than not Windows installs the wrong drivers or in the incorrect order and this can cause all sorts of problems.

Intel Core i9-12900KF 12th gen CPU
Corsair VENGEANCE RGB DDR5 32GB (2x16GB) [COLOR=rgb(184, 49, 47)]5600MHz
[/COLOR]

[COLOR=rgb(184, 49, 47)]
That is the wrong RAM for your CPU, Intel state here up to 4800MHz and if you have XMP enabled the RAM will get auto OCd past what the CPU can handle and the PC fall over.

1. Copy any dmp files from C:\Windows\Minidump onto the desktop.
2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.
3. Upload the zip folder using the Attach button, bottom left of the dialogue input box

[/color][/COLOR]

[R_H_PvMDream]

Thanks for the quick reply.

Weird, you’d assume the newest chipsets would also “accept” the newest RAM, ill go in BIOS and disable XMP and set the RAM to 4800MHz

I tried to attach the last 4 dump files, but the file was too large, I have attached the last 2 dump files instead. Really appreciate you looking into this, thank you.

[phillpower2]

It is nothing to do with the chipset but all to do with the CPU.

CPUs have to be compatible with a MB whereas the RAM has to be compatible with both the CPU & MB, your RAM is ok with the board but not the CPU.

Will get back to about the crash dmps after work.

[phillpower2]

Post separate so that you get notification;

Your crash dmps point towards memory issues, see attachment below which is from the last crash dmp;

[R_H_PvMDream]

Thanks for checking, both of them do?

The last one did show a memory issue on the BSOD so I did a 3rd mem check and came out fine. The other one had a different error IIRC, something like Werfault, and another one said usbccgp

Little update, however - Haven’t crashed in the past 24h ish since I went to 4800MHz which is a big improvement in and of itself already

[phillpower2]

Testing RAM needs to be done properly and testing two sticks using Memtest can take 24hrs+ coupled with the fact that Memtest checks for faulty RAM and not RAM that is paired with an inappropriate CPU running any type of memory test would not give reliable results.

The crash dmp pointing towards the RAM as being the cause does not mean that the RAM is faulty but that as was previously explained the RAM was being OCd past what the CPU can handle, no further BSOD since you knocked off the OC supports this.

You are welcome btw ???