Many of my games fail with code 0xc0000005 and occasionally trigger BSODs during play.
Many of my games fail with code 0xc0000005 and occasionally trigger BSODs during play.
Hello, I assume you read the title, so here’s a revised version.
I never faced any lag in any game, but most of them would crash roughly every 20 minutes.
This issue isn’t tied to the platform I use—Steam, GOG, Uplay, Epic, etc.—my games generally behave the same way. Only Minecraft and Terraria are exceptions; I also experience BSODs occasionally, though less frequently than crashes to desktop. The error codes vary a bit (like SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL, KMODE_EXCEPTION_OT_HANDLED), but I can’t recall the rest.
To resolve these problems, I’ve tried several solutions:
I updated all my drivers, or at least I believe I did.
I attempted to use only base clocks for CPU, GPU, VRAM, and RAM.
Temperatures for CPU, GPU, and SSD stay normal (40–60°C).
I switched to a different RAM type.
Running memtest86 for hours and Windows memory diagnostics found no issues.
I tested using just one RAM slot at a time.
I removed my video card temporarily and reinserted it.
I updated Windows to the latest version.
Performed a clean boot.
Disconnected all unnecessary USB devices (only kept keyboard and mouse plugged in).
Tried running games as administrator, along with Steam, GOG, Uplay, and Epic Games Launcher.
I reinstalled Windows on the same drive.
Updated my motherboard BIOS to the latest release.
Used one monitor at a time, adjusting the refresh rate between 144 Hz and 60 Hz.
My system specs are:
AMD Ryzen 5 3600
Gigabyte Aorus RTX 2060 Super (rev 1)
Corsair H100i RGB Platinum
Gigabyte X570 Aorus Elite (rev 1)
Samsung 970 Evo Plus (my Windows drive)
Gigabyte Aorus RGB Memory, 2x8 GB, 3600 MHz (GP-AR36C18S8K2HU416RD)
2 Seagate Barracuda drives of 2 TB each (one from a build 5 years prior)
Corsair RM550x (rev 1)
I’m using one monitor at a time.
My PC runs Windows 10 Pro (20H2), and I had similar issues before updating to 20H2.
I don’t have additional power supplies, CPU, motherboard, or video cards.
I could attempt reinstalling Windows on one of my HDDs.
Any advice would be greatly appreciated.
Thanks for reading—I tried to avoid many spelling errors.
The most straightforward step you should avoid is skipping a comprehensive SFC scan, which should be among the first actions when system issues appear. This means ensuring your system image is clean before proceeding. Otherwise, the scan will be ineffective.
Follow these instructions exactly.
https://support.microsoft.com/en-us...nd...d86e0ef4ca
If that doesn't resolve the problem, consider running a drive diagnostic on the affected drives. Many manufacturers provide free testing tools, though you're not required to use those made by them.
The most straightforward step you should avoid is skipping a comprehensive SFC scan, which should be among the first actions when system issues appear. This means ensuring your system image is clean before proceeding. Otherwise, the scan will be ineffective.
Follow these instructions exactly.
https://support.microsoft.com/en-us...nd...d86e0ef4ca
If that doesn't resolve the problem, consider running a drive diagnostic on the affected drives. Many manufacturers provide free testing tools, though you're not required to use those made by them.
Thank you for your response.
I followed the instructions precisely, and it appears there were no mistakes.
I executed SeaTools long test, which lasted several hours without any errors.
The Windows disk diagnosis tool ran quickly, taking only a few seconds and also showed no issues.
Despite this, the same crash code persists; I’m unsure if the BSOD problem has been resolved since I rarely encounter such crashes.
I did that, but when I said "I think so," I might have overlooked some drivers. The ones I'm confident about are the display, audio, and network drivers.
Edit: chipset drivers are also up to date.
If your problems stem from this particular Windows version, I noted in my earlier message that they appeared before the update. I also pointed out that I had fully reinstalled Windows, yet the issues persisted.