Game unexpectedly terminating.
Game unexpectedly terminating.
PC specifications: Intel Core i7-13700KF at 3.4 GHz, 16-core processor, CPU cooler from Cooler Master, MasterLiquid ML280 mirror liquid cooler, MSI MAG B660 ATX motherboard, TOMAHAWK Wi-Fi DDR4 ATX LGA1700 board, TEAMGROUP T-Force Vulcan Z with 32 GB DDR4-3200 CL16 RAM, Seagate Barracuda 8 TB 3.5" drive, Western Digital Blue SA510 1 TB M.2-2280 SSD, Zotac GAMING AMP GeForce RTX 4080 graphics card, Lian Li O11 dynamic mini ATX case with 750W power supply, Power Supply Thermaltake SFX 850W (Platinum certified), operating system Microsoft Windows 10 Pro OEM DVD. For approximately five months I've encountered frequent crashes in games. I've replaced RAM, PSU, storage, and returned two graphics cards to a working unit. Ran RAMtest64 and various benchmarks to assess GPU performance, reinstalled Windows, cleaned game installations, and reinstalled graphics drivers using ddu. I'm at my worst. When different titles crash, they don't generate .dmp logs or crash reports, or at least I can't locate any in the Windows directory for Em or via AppCrashView v1.35. I don't grasp why these games are unstable. The titles include Rust, Dota2, Magic the Gathering, Heretics fork, Overwatch 2, and Marvel Rivals. I would greatly appreciate assistance or suggestions to diagnose what's causing these issues. I'm open to a reward if anyone can help.
Have you upgraded the BIOS to address Intel instability problems? Were you experiencing instability, such as video memory crashes, previously?
You swapped all components except the CPU, which is expected to wear out. Check the latest BIOS updates—likely won’t help much. Then explore the extended RMA options for Intel 13/14 generation CPUs.
It's the CPU. There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any damage is permanent - The Verge You'll need to RMA it. Even if updating the UEFI (BIOS) stopped the crashing, I would still RMA it because it's permanently damaged and it's life is shortened. Update your UEFI (BIOS) when you get the new CPU so that this doesn't happen to it.
I've updated the information once more when I installed the PC about a year prior. My approach was to use process elimination, as CPU problems usually don't cause general instability but rather crashes from demanding games. I also considered that only one game reported an issue, pointing toward a graphical-heavy application. The crash log showed a specific fault module and error code, which helped narrow down the problem.
The crash report was processed using CHATGPT, which I use when trying to decipher crash details. The summary states: "This crash report shows that the application RotMG Exalt.exe (part of Realm of the Mad God) stopped because of a UnityPlayer.dll problem. Let's clarify: Main Points from the Report: Application Details – Name: RotMG Exalt.exe Version: 2022.3.10.14226 (the client version in use) Timestamp: 65010ee0 (date the app was built) Fault Module: UnityPlayer.dll Version: 2022.3.10.14226 (the Unity version used by the game) Fault Module Time: 65011305 This is important. The failure is linked to UnityPlayer.dll, a vital part of the Unity engine that manages rendering and game logic."
Exception information:
- Exception Code: c0000005 (access violation)
- Offset: 000000000074cc3e
- Possible reasons: outdated or damaged game files, Unity engine bug, insufficient system resources, hardware or driver problems.
Loaded components: UnityPlayer.dll, GameAssembly.dll, Steam-related DLLs.
System info: Running on Windows 10 version 10.0.19045 with 65,391 MB RAM; NVIDIA GPU detected.
Possible causes:
- Bug in Unity engine (2022.3.10) affecting compatibility.
- Memory access error due to corrupted files or outdated drivers.
- Hardware issues such as failing RAM or graphics card.
- Steam overlay or mods like steam_api64.dll causing instability.
Solutions:
- Confirm game file integrity, especially if using Steam.
- Update graphics drivers and ensure GPU drivers are current.
- Disable Steam overlay or remove mods temporarily.
- Run the game as administrator to check permissions.
- Reinstall the application if corruption is suspected.
If the problem continues, reaching out to RotMG’s support team for further help would be advisable.
Extensive knowledge of their failures and the fact that all will fail if the UEFI wasn't updated with the latest release from... two months ago. If you've been using the PC for a year, you're 100% likely to have a faulty CPU by now. Since Intel couldn't resolve it until October/November 2024 (when the motherboard manufacturers issued updates), there was nothing you could do. Don't stress—just update your UEFI to the newest version and it should work for the replacement CPU. You can try updating again; I've seen a few unstable fixes, but the harm is already done. That's why I advise replacing it regardless. Also, be careful: updating with your current defective CPU might make the PC unusable because new microcode restricts voltages, and your chip—already damaged—could need even higher power to function.