Question Completely random crashes (dll related?)

[ShanxOW]

As of about three days ago every single game that I play crashes. The interval for the crashes ranges between Two and about Twenty minutes. When I open up the system events viewer and look around more often than not it is the same issue. As of last night, I did a complete wipe and reinstall of Windows with no improvements on the issue. The Exception Code that I get when a specific application crashes is "Exception code: 0xc0000005". But I did get a more recent Exception Code "Exception code: 0xc0000374". Before this, I had no issues with my PC whatsoever. I don't know what to do or where to go, as this issue only happens with games, but I can otherwise use my desktop normally and without issue.

From what I have found and researched it has something to do with the "Faulting module name: ntdll.dll". But I have no idea where to or where to start with solving this issue.

 

[Lutfij]

Welcome to the forums, newcomer!

Please pass on the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

Followed by the .dmp files for us to see what might be triggering your issue.

 

[ubuysa]

Both of those exception codes indicate failures when accessing memory. 0xC000005 is an invalid memory access and 0xC0000374 is a heap corruption (heaps are memory allocation units). I would suggest you test your RAM...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.