New computer issue, game crashes at 0xc0000005
New computer issue, game crashes at 0xc0000005
While playing on my new PC, the programs stopped after a while—about an hour seems long. Some crashes show up right away, while others require checking logs in a dump file. Using WinDbg, I examined the dumps and found these entries: My hardware details are listed, including CPU, motherboard, GPU, RAM, SSD, power supply, and BIOS settings. I turned off AMP EXPO but still faced crashes with Counter-Strike. I also ran tests with PRIME95, which revealed performance issues: six workers failed instantly, one finished two tests and then crashed, another lasted through four, and a third kept running until all tests failed. If I run just one or two workers, a BSOD appears. In WinDbg, the logs pointed to a critical failure at 0xEF_svchost.exe. I reinstalled Windows and drivers, tried adjusting the CPU voltage (1.26, 1.27, 1.28), but the advice was that my memory controller might be faulty—raising the voltage could help. This didn’t resolve the problem, and now everything is back to normal. Any thoughts on whether the CPU or RAM is the issue? The file attached is 101024-5500-01.zip.
I adjusted the EXPO configuration from disabled to tweaked and updated 6000 to 5600. TESTMEM5 now runs for 3-6 minutes instead of 10 seconds (max 40 seconds). It crashed after a few minutes, and prime95 appears to be taking longer. No crashes occurred within two minutes. Consider modifying other timing settings if needed.
The files inside the games.zip archive come from various sources such as game folders, LiveKernelReports, or the CrasDumps in appdata. Understanding the crash type is crucial because the details vary greatly depending on the event. The minidump file labeled Critical_Process_Died contains valuable data even when crashes occur rarely. A service crash may not reveal specifics, making debugging from a single dump unreliable. Please share additional dump files if you have them.
Thanks for your feedback. The CS2 file came from the Steam Dump folder, while the other three were from the appdata folder (local/temp for FA). I ran Prime95 for 20 minutes instead of just a short time and then stopped it. It’s time to wind down now. Tomorrow I’ll test it for an hour at 2 PM before starting to play again. If any issues arise, I’ll gather the dump files. Should I consider the TestMem5 test or try another one?
They all share similar characteristics. Applications running on Windows can't inspect memory being used, making them less reliable than tools operating in isolation. I no longer rely on memory testers; they often miss faulty RAM with DDR4 and newer versions. Now I simply run the machine normally, using one stick at a time.
EDIT: The game crashed unexpectedly. Two from Supreme Commander stopped working when a game overlay attempted to access the rendering API (Direct3D) in one case, while the other experienced a memory error. The CS2 crash was also a memory issue in DX11. The last incident I can't identify was a memory problem involving a Radeon GPU running from a DLL file. It seems unrelated to the GPU driver itself, just connected issues. The recurring pattern involves memory and GPU problems within game contexts, which is typical for games. Memory and GPU concerns are usually what players encounter.