Possible issues could stem from insufficient RAM causing crashes.
Possible issues could stem from insufficient RAM causing crashes.
The projects you mentioned work with Unity - Rust and Cities Skylines 2. I've only experienced Rust crashes a few times, but CS2 has had occasional CTD issues since its release, though they seem to be becoming less common lately. The dump files consistently show the message "ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s." It doesn’t appear any crash handlers are triggered afterward. Your system specs are solid: Windows 10 home, 5800X3D processor, 32GB DDR4-3200 RAM (XMP enabled), RTX 4070 with 12GB VRAM, Rog Strix B550-A, and you’re running a 2TB Samsung 970 EVO plus a new purchase from four months ago.
It might stem from a RAM problem or a Windows issue. The message indicates the program is attempting to use restricted memory areas. To check if your RAM speeds are too fast or the timing is problematic, you could manually lower it to slower options such as DDR4-3133 or DDR4-3000. Is this 32GB of memory all from one package, or does it come from two or more separate kits?
Adjusted the clock speed to 3000MHz and refreshed the display drivers. Attached translated dump files for each game as a potential aid.
There are several factors contributing to the issue you're experiencing. It appears to be a general memory-related problem, though it may not always be the exact cause. Record the time you begin playing and when the crashes occur. Determine whether the problem happens instantly or gradually. Below are some troubleshooting actions you can follow one by one:
Hardware Check: Verify that your memory and other components are properly installed. This is likely not the main issue, but it's worth confirming.
Software & Drivers: Make sure Windows is up to date. Updates can resolve compatibility problems. Also, check if graphics drivers need reinstalling after an update.
Overclocking: Confirm your system isn't running beyond stable limits. If overclocked, reset the CPU and GPU to their default speeds.
GPU Temperatures: Use monitoring tools such as MSI Afterburner or GPU-Z to track GPU temperatures during gameplay. High temps can trigger crashes. Ensure your GPU has sufficient cooling.
BIOS & Firmware: Visit your motherboard manufacturer's site for any BIOS or firmware updates. Keeping your system updated can fix compatibility issues.
RAM Considerations: If the problem persists, consider downclocking your RAM speed from 3200MHz to a lower setting. Disable XMP settings to see if it resolves the issue. Gradually increase speed until stability returns, then decrease again if needed.
Memory Stability: Run a memory test using tools like Memtest86 if downclocking didn't help. Persistent errors may point to faulty RAM.
System Logs & Security: Open Event Viewer in Windows to review crash details. Look for error codes or events that could clarify the problem.
Take your time through these steps. Rushing can lead to permanent damage. Good luck!
Check RAM performance, run OCCT and MemTest86, observe any failures.
EOSSDK-Win64-Shipping.dll is included in the Epic Online Services SDK. I checked both games you're experiencing problems with—they’re both from Epic Games. Do non-Epic titles also crash? Check your app logs for similar errors and verify if the same module is causing issues across both games. It seems event ID 1000 might be the culprit. Right-click on "Application" and use the filter option to sort by that event ID. If other events in the logs point to the same faulting module, consider reinstalling Epic and the affected games as a troubleshooting step.