Black screen when playing games.

HighlandCoo

Reputable
Jun 3, 2015
3
0
4,510
So i've had this issue for a while but I've just been dealing with it. But It's starting to cut out during critical points of gaming and I just can't put up with it anymore.
Basically this only happens when i'm playing a game. I've tried fullscreen and Windowed mode and it happens on both settings. The games i'm playing aren't even graphically demanding. Although, my graphics card is preeeetty old. I can't afford to buy a new one right now though.

So what happens is: I'm playing a game, it doesn't matter how long I've been playing it for as it varies each time. And then Both my screens just go black. And the LED on my keybaord and mouse both cut out for a second and then start up again. The fan in my computer also slows down and then fires up again as if I've just restarted. Then the main issue is My screens stay black. They both come up with "No signal found" And then I need to hold down the power button to turn the PC off.
And then I have to wait ten minutes or so to turn it back on. If I try to turn it on instantly after it cuts out, It'll just cut out during startup.
Here are my specs:

Windows 7 Home Premium 64-bit
AMD Athlon II X4 640 Processor (4 CPUs), ~3.0GHz
8192MB RAM

AMD Radeon HD 6700 Series, 4095 MB
1920 x 1080​

I do believe it's something to do with my graphics card but I'm not 100% sure. I think it might just be dying on me slowly. I do plan on replacing it but not until September or there abouts. And i'd rather be able to game in peace until then without these interruptions.

If anyone can help me out and might know the issue then that'd be hugely appreciated.
 


I think it might have but I'm not sure if it'll be good enough to run games. And sometimes it doesn't happen for days so I'd have to use it for god knows how long.
Yes, I just cleaned it recently. I must say I didn't clean it thoroughly. I'm gonna go get a can of air to do it properly soon.
PSU is 550 and yes it's connected. It's been fine in the past. It's only recently when I upgraded from 32-bit to 64-bit it's started happening. Could it be something to do with faulty drivers?