Monitor turns off, no signal in the middle of game.

BroImMcLovin

Commendable
Feb 18, 2016
24
0
1,510
I've been experiencing this problem lately. My computer is only a year old. But, right in the middle of any game my screen turns black, monitor displays "No Signal" and I cannot solve it without restarting my computer. I usually hear a windows dialogue box open right when this happens but I'm unable to read it due to my screen being black, and I'm able to hear Skype still. I've read around and found it might be related to an overheating issue? Well, I just today cleaned my cpu, and cooler off and re applied thermal paste, and I'm not even over clocking my CPU. Side note: Everything runs just fine while I'm doing normal browsing, even watching YouTube, but about 15 minutes into any game my problem arises.

Here are my specs in case it helps:
CPU: i5 6600k
CPU Cooler: Hyper 212 Evo
GPU: MSI GTX 970 Gaming 4G
Ram: 16gb DDr4 Ripjaw V Series 3200.
SSD: Kingston 120GB
HDD: WD 500GB
Motherboard: MSI Gaming M3
And I have 2 fans as well. Because before my PC would just straight up shut off, until I installed the fans, now it's doing this current issue, not shutting all the way off, but still unable to operate until I restart.
 
Sounds like a GPU problem to me. Try to run the game on which this is happening at lower details. Also, install MSI Afterburner if you haven't already, and monitor your GPU's temperatures. It could be overheating, but the signal getting interrupted because of that seems a little out of place. But it could be - overheating causes all sorts of issues.

If your GPU seems to run higher than 80C, try to increase the fan speed, or, if you have overclocked the GPU, try to dial in a lesser overclock.

Do report back with GPU temps. Also, what display interface are you using? HDMI or DP or DVI or VGA? If you are using a converter, make sure it's working fine. The issue doesn't seem to be your CPU. But you might as well report CPU temps from MSI Afterburner also.
 
It pretty much has been happening on every game, from Runescape, to Tales from the borderlands, and even Left 4 Dead. For the longest time my GPU was on only a 2400 MHZ overclock, and I just recently upped it to 3200, but my issues have been going on well before I upped the overclock. As far as Temp, it was sitting at about 137 F and then I messed with fan control settings which seemed to be on OFF, and it said something about "Starting it for the first time" and I noticed my temps rapidly started dropping. My Fans seemed to be off according to afterburner, and after messing with a cog my fan speeds went to auto, and Temps started dropping. I hope this is all that it was. I will report back after playing Left 4 Dead for a while. If it doesn't happen I may have found the problem. Edit: I'm sure you figured I was referring to my Ram, being overclocked to 3200, not the GPU. -.-
 
I hope this fixes this. Just in case it doesn't, try running a stress test, and if you're getting the same problem, I would consider trying to replace the GPU. Not buying a new one, just try to either borrow someone's, or try installing yours into someone else's PC, and see if the same problem occurs. If it does, you'll probably have to return that GPU if it's still in warranty.
If the same doesn't happen in a different PC, then your GPU isn't the problem. Things that could be wrong now include the power supply, the motherboard, or the display. Your motherboard might be having a second PCI-E slot - try installing it onto the second one. If it works fine, then the slot is messed, and you should send the motherboard back.
Hope this helps.
 
Well, I think that was the problem because while Idle I got temps of 140F when I first checked afterburner, and now I'm getting 105F while playing a game... so I hope this solved it. It's just shocking because I can't believe my fans weren't on before, and I don't know why it only just started acting up like this.
 
Yep. I just played for 6 hours, and not a single hiccup. Thanks so much. I never would've thought that my GPU fans weren't running and that's what could've caused the issue.