Every game I play crashes for no reason?

[whitty1001]

Hello so as the title suggests my game crashes whenever I play any game for like 2 minutes. Some games don't even start up? When they crash the game freezes and im forced to start task manager and end the process to get back to the desktop my computer does NOT bluescreen. The weird thing is my computer runs like its brand new when not playing games. I can run many livestreams and render videos very quickly its just the games which crash!

(Specs not included in profile) Corsair TX 650w PSU, Arctic cooling freezer for processor.

Here are some of the solutions I have tried so far to get my games to work again:
- Reset to factory settings
- Malware scan
- Virus scan
- Registry clean
- Stress test on hardware
- MEMTEST86
- clean out inside pc
- Validating game cache on steam (Its not just steam games that crash, its all games)
- Defragmented my HDD and SSD
- Removed any overclocks

If anyone has any other ideas please, please get back to me ASAP some people have said to unplug the hardware and plug it back in but I didnt know if this was safe?

Any other ideas are greatly appreciated. If you need more info just ask!

Regards, Luke

 

[Boozad]

What did you have overclocked and how did you remove them?

 

[whitty1001]

What did you have overclocked and how did you remove them?

I had my graphics card OC and removed it via AMD catalyst control center.

 

[Faladu]

Attached is a Video Memory Stress Test program.

I suspect you have busted VRAM now as a result of overclocking, Windows running normal might not push hard enough to reach it, but your demanding games will and so should this utility.

If it was regular RAM or something else, you'd have BSOD or some other symptoms.

Anyhow my theory, vmt attached can prove it wrong.

The next thing to check would be Power Supply, need a PSU tester, $15ish on newegg.com

Other thing would be chipset driver for the motherboard or direct-x, but I would have expected other noticeable things (BSODs included), and dxdiag.exe from search box is a safe thing to run, it's the video diagnostic tool, check the Display Tab(s) for errors.

I have a 7950 you should not have needed to overclock that rig for gaming, at all.

 

[whitty1001]

Attached is a Video Memory Stress Test program.

I suspect you have busted VRAM now as a result of overclocking, Windows running normal might not push hard enough to reach it, but your demanding games will and so should this utility.

If it was regular RAM or something else, you'd have BSOD or some other symptoms.

Anyhow my theory, vmt attached can prove it wrong.

The next thing to check would be Power Supply, need a PSU tester, $15ish on newegg.com

Thank you i will try that VMT later and if that isnt the problem i will buy a psu tester.

 

[whitty1001]

Attached is a Video Memory Stress Test program.

I suspect you have busted VRAM now as a result of overclocking, Windows running normal might not push hard enough to reach it, but your demanding games will and so should this utility.

If it was regular RAM or something else, you'd have BSOD or some other symptoms.

Anyhow my theory, vmt attached can prove it wrong.

The next thing to check would be Power Supply, need a PSU tester, $15ish on newegg.com

Other thing would be chipset driver for the motherboard or direct-x, but I would have expected other noticeable things (BSODs included), and dxdiag.exe from search box is a safe thing to run, it's the video diagnostic tool, check the Display Tab(s) for errors.

I have a 7950 you should not have needed to overclock that rig for gaming, at all.

Also i have updated my chipset driver and direct x before so i can rule that out and the dxdiag came up with this error under display but i dont know what to make of it?

The file aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.

 

[Faladu]

That sounds like you were using a beta version video card driver, was that loaded right before this all started by chance?

WHQL is just verified by M$ drivers via their internal testing as stable, so maybe do a full uninstall of the beta driver and use a stable one, before anything else.

Irregardless, a PSU tester is a wise tool to have around.

Any recent weather event you might want to mention, also?
Surge Suppressor protecting the system? muhahaha!

 

[whitty1001]

That sounds like you were using a beta version video card driver, was that loaded right before this all started by chance?

WHQL is just verified by M$ drivers via their internal testing as stable, so maybe do a full uninstall of the beta driver and use a stable one, before anything else.

Irregardless, a PSU tester is a wise tool to have around.

I installed the beta driver as it was suggested to try and fix the game crashing problem so that was not the cause. Anyway im going to run the VMT now!

 

[whitty1001]

Attached is a Video Memory Stress Test program.

I suspect you have busted VRAM now as a result of overclocking, Windows running normal might not push hard enough to reach it, but your demanding games will and so should this utility.

If it was regular RAM or something else, you'd have BSOD or some other symptoms.

Anyhow my theory, vmt attached can prove it wrong.

The next thing to check would be Power Supply, need a PSU tester, $15ish on newegg.com

Other thing would be chipset driver for the motherboard or direct-x, but I would have expected other noticeable things (BSODs included), and dxdiag.exe from search box is a safe thing to run, it's the video diagnostic tool, check the Display Tab(s) for errors.

I have a 7950 you should not have needed to overclock that rig for gaming, at all.

Ok so i ran the test twice. the first time no errors were found but i had on screen buffer turned off. The second time i turned it on and apparently 16233 errors were found. Thats a lot im guessing! however all the error messages looked similar here they are.