Monitor going to sleep while gaming

GPUEnthusiast

Reputable
May 28, 2014
153
0
4,710
I generally am pretty good with PC construction and troubleshooting, but this one has me stumped. In intensive games, my HDMI connection will go away to my monitor. I will hear the audio flicker from my USB headset and the monitor will say "Going to sleep", but the PC is still running. My Roccat Power Grid app is still going and still showing the CPU and GPU under load etc. To fix it, I have to hard reset (hold power button until the PC turns off, then turn back on). This doesn't happen in light titles like Mass Effect 2, but happens in heavy titles like Far Cry 4, Fallout 4, and GTA V. This is a new problem too, I've had this PC for a year and a half and this just started happening recently. I've updated my drivers completely and correctly for my GPU and that still didn't fix it.

Specs are:
Intel Core i5-4690K
Asus Maximus VII Formula Z97
16GB Corsair Vengeance Pro
MSI Radeon R9 290X 4GB Lightning
Corsair AX760 PSU

I'm hoping this isn't damage to the GPU from heavy overclocking in the past. (nothing crazy though, and haven't OCd recently)

I'll test DVI next to see if the problem still happens, but when it happens, removing the HDMI and reinserting doesn't fix it, and neither did a brand new cable.
 
Solution
How did you/how do I test it? Is there a tool I can use?
[/quotemsg]

Mine was visually apparent as the connector had melted obstructing a solid connection, but I did it as a result of someone else's who swapped psus and the new one worked fine.

Unfortunately, like most things, its hardly my area of expertise but I know you need a voltmeter, then test against documented values, otherwise try a surrogate psu and see if the problem still occurs. For voltages, you'd need to google it properly as I've only seen solutions rather than the how tos but in one such instance, the guy's psu dropped 0.3v to the gpu and that was enough variance to cause this.
That doesn't seem like "sleep" as much as a full on crash. Try lowering the overclock a bit more (start at stock, go below if needed) to make sure it's not the card completely crashing.

If you're sure the system isn't completely dead, try taking a screenshot (windows key + prtscn) to see if there's an error that crops up
 

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560
I'm having this exact issue and my specs are similar,

My specs:
I7-4790k
Gtx 980ti
Maximus Formula VII
Avexir Blitz 2x8gb 2133MHz
Seasonic 860p
2xSSD RAID 0 for boot
1TB HDD
2TB SSHD
Display port for Display 1
HDMI for display 2

Only occurs under heavy GPU load, temps are nominal (50C~60C GPU/CPU) when this occurs I lose internet connectivity as I disconnect from voip services and steam, audio plays out for a while keyboard macros still produce relevant lighting effects (K70 RGB) and my NZXT HUE+ still displays relevant CPU temperature colour. PC does not shut itself off, I have left it for a good while, needs hard reset as detailed in your post. Have not managed to find any way to display anything on my monitors, have tried different ports, mobo display-out, nada.

My only conclusion thus-far is that the dreadful win10 anniversary update has done something.

Needless to say, if I solve it, I'll come a-typing otherwise I'll be watching this thread with bated-breath.
 

GPUEnthusiast

Reputable
May 28, 2014
153
0
4,710
@Basroil: I'm not overclocked anymore though, and haven't been for the past three months. My MSI R9 290X runs at the stock 1080 MHz Core that it came at in the box, and my Core i5-4690K runs at the stock 3.9 GHz that it boosts to. I'm hoping it's not OC damage, but I never did anything dumb to my CPU or GPU. I never even messed with voltages on the R9 290X, and only did an OC up to 4.4 GHz on the 4690K.

@Alan Hudson: That sucks to hear man. I'm still on Windows 7 Home Premium. If Microsoft found a way to screw me from across the OS pond, I'll be thoroughly pissed. My brother is loaning me his Radeon HD 7950 3GB today to isolate my GPU as the factor causing this. If it stops happening with the HD 7950, then I'll know my GPU is the culprit. If it keeps happening... then well... back to square one. Could be CPU. Operating system errors with drivers.

I'm only certain of two things: 1. It's not the monitor, because it doesn't happen during general usage or lighter titles, and a monitor can't tell how hard your PC is working. 2. It's not a problem with any of my storage like my SSDs or HDDs because general usage they all work fine, even in hardcore read/write benches.

The next two things I'll test before getting my brother's card installed is:
1. Try using DVI to my monitor instead. If this fixes it, it either indicates a dying HDMI port on my graphics card that somehow gets damaged enough to lose signal during heavy load, or it indicates a driver error with HDMI.
2. Use a CPU benchmark like AIDA64. If this causes it. Well, then I'm sure it's not my GPU, and that leaves it to either CPU, RAM, or motherboard. Though I doubt RAM could do this.
 

GPUEnthusiast

Reputable
May 28, 2014
153
0
4,710
Alrighty. Update number 1.

Installed the HD 7950 3GB from my brother. Booted up GTA V. Played it for almost an hour. Not a single problem. This is good news, because it pretty much solves my problem in the sense that I know what the vector is. Definitely something with the GPU. My next test is to put my graphics card back into the PC and then use the DVI port and see if it happens again. If it does, then it's the graphics card, and it's pretty much guaranteed that I need to call up MSI and RMA the card. If it doesn't, then it's the HDMI port on the card, and that means I can use it quite a bit longer.

Not sure what MSI will do if I RMA the card. They're completely sold out of them, and they sell for well above MSRP on Amazon. Hopefully, they'll be like "Yup, it's busted. Here's an MSI GTX 1070 6G Gaming X since we're out of Lightning 290Xs :DDD"
 

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560


Haha, you're a smarter man than I, wish I'd stayed on 7 after all this.

As for the hour test, mine is totally random, playing modded fallout 4 on max settings crashed after 3.5 hours, sometimes after 10 mins, pls no be GPU error ;_;

Wonder if it's something to do with DX12 or Vulkan trying to run?
 

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560
Got a crash report from the program 'Who Crashed' and it returned this;
On Fri 26/08/2016 12:43:11 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: watchdog.sys (watchdog!WdLogEvent5_WdCriticalError+0xCE)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFCE00E4A9A960, 0xFFFFE30EE4994DA0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Give it a try, it may reveal the same or perhaps something else useful for yourself.
 

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560
For me, it turned out that the PSU had fried the plastic connector connected to the PSU going to the GPU, all I had to do was switch out the cable and stay the heck away from the burnt out socket. Nearly all of these issues seem PSU related, at least the ones I seen, perhaps a test for yours would be in order sir?
 

GPUEnthusiast

Reputable
May 28, 2014
153
0
4,710


How did you/how do I test it? Is there a tool I can use?
 

Alan Hudson

Reputable
Dec 12, 2014
39
0
4,560
How did you/how do I test it? Is there a tool I can use?
[/quotemsg]

Mine was visually apparent as the connector had melted obstructing a solid connection, but I did it as a result of someone else's who swapped psus and the new one worked fine.

Unfortunately, like most things, its hardly my area of expertise but I know you need a voltmeter, then test against documented values, otherwise try a surrogate psu and see if the problem still occurs. For voltages, you'd need to google it properly as I've only seen solutions rather than the how tos but in one such instance, the guy's psu dropped 0.3v to the gpu and that was enough variance to cause this.
 
Solution