New GPU, works great, but whenever the PC sleeps the monitor loses the signal

tempestatem

Commendable
Dec 26, 2016
17
0
1,510
So on christmas I got a Geforce GTX 1060 6GB GPU, and I installed it myself and it worked perfectly when I turned it on. However, once my computer goes to sleep, the monitor completely loses the signal to my PC, which is normal, but when i wake it back up it still says no signal. I have the HDMI plugged into the GPU, and into the HDMI 1 outlet on the monitor. I tried switching outlets and it didn't make a difference. The only way to fix it is to completely shut off my PC and turn it back on, but I don't want to do that every time it goes to sleep..
Any thoughts on how I can fix this issue? (I can supply my setup if needed)
 
Solution
I probably should have been more clear too, what psu exactly. Size means nothing. Older psus are primarily group regulated design and as such can have issues with ultra low power states such as in deep sleep. Newer designs use a DC to DC system and as such are very tolerant of low power states.

In low power states, there's minimal voltages running through the system, the cpu designating exactly how low it needs. In group regulated designs, often this is below actual output of the psu and it basically stalls, not off but not enough to turn it self back on when trying to wake from sleep. This results in monitors not turning on, pc lights being on but nothing doing anything, it's like it's stuck sleeping and requires a hard shut down to...


Yes, my apologies for not being clear. I'll fix it in the question.
 
unless its a laptop (nope), dont use sleep.
if its idling less than 20min, leave it on. more than that, turn it off.
cheaper on the power bill and better for your components.
plus win/ram is a little sensitive to not get shutdown/powered down regularly.
 
What cpu and what psu. Chances are it's a C-states issue. This is easily resolved in either bios or Windows power advanced settings. Disable sleep states below C3. Also, hibernation needs to go, permanently removed from the system, not just turned off.
http://www.sevenforums.com/tutorials/819-hibernate-enable-disable.html
Works in any version of Windows. Side benefit is that it'll also free up 75% of ram size on the C: drive so for those with smaller SSDs, that's usually 6-12Gb.
 


Its a 750W PSU and the CPU is an AMD FX-6300

Also I forgot to mention my OS is Windows 10
 
I probably should have been more clear too, what psu exactly. Size means nothing. Older psus are primarily group regulated design and as such can have issues with ultra low power states such as in deep sleep. Newer designs use a DC to DC system and as such are very tolerant of low power states.

In low power states, there's minimal voltages running through the system, the cpu designating exactly how low it needs. In group regulated designs, often this is below actual output of the psu and it basically stalls, not off but not enough to turn it self back on when trying to wake from sleep. This results in monitors not turning on, pc lights being on but nothing doing anything, it's like it's stuck sleeping and requires a hard shut down to reset the psu and allow it to start normally.

The only cure for this is either a new psu that's DC to DC, or in bios/windows power disable c-states lower than C3. IF there is hibernation / hybrid sleep enabled, this too should be disabled. Hibernation is a function of laptops, that have 0 issue with low power states since batteries are output on demand at any level.

Hyberfil.sys is the major component of hibernation, but it's also used by Fast Boot, (almost useless with an SSD boot drive) and fast boot can cause issues similar to deep sleep issues, usually requiring hitting the power 2x or more which bypasses fast boot and becomes a regular slow boot. Hyberfil.sys also quarantines 75% of your ram size for its own use so if you have 16Gb of ram, you loose access to 12Gb automatically. On a 120Gb ssd, that's a good chunk of space.

Permanently removing Hyberfil.sys will not hurt a pc in any way, its totally useless. Just follow the directions. Between setting c-states and removing Hyberfil.sys, this should fix the issue, does in 90% of cases, but if it doesn't, at least it's a possibility thats off the table.
 
Solution