I Keep Getting Bsod When I Play Games

I keep getting BSOD whenever I play games. Be it newer games, older games, no matter how heavy or light. What I find strange is that it's not absolutely every time, at least not when I run older games. I could play a match or two of Age of Mythology without a problem, only to have the 3rd one crash. Anything heavier than that, like league of Legends, crashes every time. Sometimes I don't even get the blue screen. Everything stops and I have to hit the reboot button on the case. Other than that, PC runs normally and quietly. The Event Viewer doesn't help me much because I'm really not understanding any of that stuff. And if it's anything about temperatures, I don't know how to measure that when BSOD gets in the way. I just wish to know the exact cause before I replace anything (if such a thing is even needed).

Processor: AMD A6 - 3500 APU with Radeon(tm) HD Graphics 2.10 GHz
Installed RAM: 8,00 GB (7,73 GB usable)
System type 64-bit operating system, x64-based processor
Windows 10 Pro

 

I performed disc checking, ran windows memory diagnostic and did the system scan. None of that helped.

 

See if you've got any *.dmp files in C:\Windows\Minidump. If you do, zip them up (you may need to copy them to your desktop first) then attach the zip file to your next post. I'll see if they reveal the cause.

 

Here it is, made today.

 

If you get any more BSODs, upload the dumps. I'm curious as to whether it's always the same stop code. Make sure if you run anything like CCleaner, that you uncheck cleaning dump files.

That BSOD indicates a CLOCK_WATCHDOG_TIMEOUT which means that one of the processors is hung and explains why everything freezes.
Is this a brand name PC if so what model, otherwise do you know what model the motherboard is?
What windows version are you on? (run winver)

Was there are a time when you could play the more taxing games?
Could you run msinfo32.exe and go to File -> Save, zip the log.nfo and attach?

 

It is an older PC, worked like a charm until recently.
The motherboard model is AsRock A55M-HVS. Windows version 2004 (OS Build 19041.630)
I have another dump file, I'll attach that one and keep an eye on new ones.

 

Did the BSODs coincide with updating to Windows 2004?
Both dumps so far indicate CLOCK_WATCHDOG_TIMEOUT

One of the usual steps for CLOCK_WATCHDOG_TIMEOUT is to remove any overclocking and update BIOS. Given that your BIOS is P1.20 from 2011 and the most recent update is from 2012, I don't see that there's anything to gain stability wise by updating. Also it doesn't appear that you're overclocked.

Try running a Prime95 torture test on the default 3 processors for about 20 minutes and see if you get the freeze or BSOD.

https://www.majorgeeks.com/files/details/prime95.html

 

''Did the BSODs coincide with updating to Windows 2004?'' Hm I can't remember if it did...
I have a dumb question about Prime95 since I never used it: should I run a game while it's testing? Cause gaming is the only time I get BSOD. Or should I just leave it running?

 

Ok nevermind, everything froze after less than 20 minutes of the testing.

 

Could you try booting to safe mode and running Prime95? If it still freezes then that indicates that it's a hardware issue.

 

Ok Prime95 has been running for a while in Safe Mode and no freezing or crashing.

 

OK, I suggest enabling Driver Verifier to flush out any misbehaving driver. Refer to the following link and make sure you understand how to recover if the system won't boot. Upload any DRIVER_VERIFIER_DETECTED_VIOLATION dumps.

https://www.sysnative.com/forums/threads/driver-verifier-bsod-related-windows-10-8-1-8-7-vista.29/

 

I did all that but I cannot find the DRIVER_VERIFIER_DETECTED_VIOLATION dumps.

 

They'll still be *.dmp files and in C:\Windows\Minidump. Just upload any new ones.

 

Oh I got none in that case. I tried to force BSOD by playing a game, but all I get are frozen screens.

 

Try checking temperatures, I see you have HWINFO so use that. Launch HWINFO and select sensors only.
On the window that opens press the Logging Start button and follow the prompts.
Then play a game that causes a freeze.

Afterwards you can open the log in MS Office or any office alternative and check temps or just zip and attach.

 

Ok so I did that and tried playing got BSOD, without any minidumps, which is odd? Anyway, here is the log from HWINFO.

 

Your CPU temperatures exceed the maximum operating temperature for the AMD A6 - 3500. Max temp is 70.9°C and the CPU temp is still rising when things cut out at 77.5°C.
Check that the processor heat sink and fan are free of dust and all case fans are operational.
You may need to remove the processor and replace the thermal place.

 

I was suspecting the same thing, heat or possibly bad caps.