hdmi Problem: No HDMI signal after turning screen on, for 24/7 running PC after a few hours (RTX 4080)

[docmars]

Hey all! I'm having a weird issue:

 

Summary

In a nutshell, I leave my PC on 24/7, and sometimes when I return to my PC + turn on the TV (only display connected), there's about a 30-40% chance (recently) it won't get a signal from my PC, and I must force a shutdown/reboot to get it back. After that, everything works fine. It happened twice within 48 hours recently, and in the past it was rare and would happen every few weeks or so. This has happened both with my RTX 3070, and now my RTX 4080, so it doesn't seem GPU dependent. Is my TV missing a handshake? Is my PC not receiving a handshake from my display(s)? My TV says HDMI is connected fine, just no signal -- for both displays and both HDMI cables I've tried.

 

What might cause this?

 

Recent steps:

• 2 nights ago
  • Used my PC, usual browsing, a little gaming, etc.
  • Left PC on, turned TV off, went to bed
• Next day (~18 hours later)
  • I turn my TV back on and there's no HDMI signal. Tried replugging, tried switching input sources then back to PC. Nothing. Needed to force shutdown
  • Boots fine, back to Windows
  • Checked Event Viewer, no GPU or driver warnings/errors, no system/kernel errors were to be seen in the time between using my PC last, and the time of issue
  • Used my PC all evening
  • Left PC on, turned TV off, went to bed
• Today (~10 hours later)
  • Turn on TV, no HDMI signal again
  • Plugged in a different monitor, different HDMI cable, same port, still no HDMI signal
  • Forced shutdown, booted back up, everything's fine on monitor and TV both after swapping back
  • No events in Event Viewer related to GPU/drivers, system failures, kernel issues, etc.
  • Everything's fine now that it's back on

Environment:

• Windows 10 22H2 19045.3086
• Power mode: High performance, PCIe power management disabled, Sleep display disabled
• NV Control Panel / display:
  • Power management mode: Normal (will try Maximum Performance for a while)
  • G-SYNC enabled for Fullscreen + Windowed
  • Resolution: 3840 × 2160 @ 120hz
• TV - Samsung QN90B 65"
  • PC input type
  • Game mode enabled
  • Input Signal Plus enabled for HDMI

Specs:

• GIGABYTE B450 AORUS M - BIOS F63b
• Ryzen 5600X
• 32GB DDR4-3200
• MSI RTX 4080 - ‎G408016GXT
• MSI 850W PSU - MPG A850G PCIE5

Temps:

No thermal issues ever, really. Performance is always great, no slowness, etc.

• GPU: ~53 C idle, ~75 C load
• CPU: ~36-40 idle, ~55 C max at load (Prime95, all cores), ~high 60's when gaming
• MOBO: 26-36 C max for all 3 sensors

Other notes:

• Outside of this issue, system has been perfectly stable while using it. No HDMI signal issues or anything during use. No overheating of any kind, no artifacts, or anything GPU-related.

I'm stumped at this point. Forcing shutdowns isn't the end of the world, but it shouldn't be necessary to get my display back. Are there other ways to force HDMI to retry its handshake / test for a signal? Replugging doesn't seem to work, on either end.

 

Any help or suggestions would be appreciated!

Edited June 24, 2023 by docmars
Added section for temp ranges, clarify summary

[Bombastinator]

51 minutes ago, docmars said:

Hey all! I'm having a weird issue:

 

Summary

In a nutshell, I leave my PC on 24/7, and sometimes when I return to my PC + turn on the TV (only display connected), there's about a 30-40% chance it won't get a signal from my PC, and I must force a shutdown/reboot to get it back. After that, everything works fine. This has happened both with my RTX 3070, and now my RTX 4080, so it doesn't seem GPU dependent. Is my TV missing a handshake? Is my PC not receiving a handshake from my display(s)? My TV says HDMI is connected fine, just no signal -- for both displays and both HDMI cables I've tried.

 

What might cause this?

 

Recent steps:

• 2 nights ago
  • Used my PC, usual browsing, a little gaming, etc.
  • Left PC on, turned TV off, went to bed
• Next day (~18 hours later)
  • I turn my TV back on and there's no HDMI signal. Tried replugging, tried switching input sources then back to PC. Nothing. Needed to force shutdown
  • Boots fine, back to Windows
  • Checked Event Viewer, no GPU or driver warnings/errors, no system/kernel errors were to be seen in the time between using my PC last, and the time of issue
  • Used my PC all evening
  • Left PC on, turned TV off, went to bed
• Today (~10 hours later)
  • Turn on TV, no HDMI signal again
  • Plugged in a different monitor, different HDMI cable, same port, still no HDMI signal
  • Forced shutdown, booted back up, everything's fine on monitor and TV both after swapping back
  • No events in Event Viewer related to GPU/drivers, system failures, kernel issues, etc.
  • Everything's fine now that it's back on

Environment:

• Windows 10 22H2 19045.3086
• Power mode: High performance, PCIe power management disabled, Sleep display disabled
• NV Control Panel / display:
  • Power management mode: Normal (will try Maximum Performance for a while)
  • G-SYNC enabled for Fullscreen + Windowed
  • Resolution: 3840 × 2160 @ 120hz
• TV - Samsung QN90B 65"
  • PC input type
  • Game mode enabled
  • Input Signal Plus enabled for HDMI

Specs:

• GIGABYTE B450 AORUS M - BIOS F63b
• Ryzen 5600X
• 32GB DDR4-3200
• MSI RTX 4080 - ‎G408016GXT
• MSI 850W PSU - MPG A850G PCIE5

Other notes:

• Outside of this issue, system has been perfectly stable while using it. No HDMI signal issues or anything during use. No overheating of any kind, no artifacts, or anything GPU-related.

I'm stumped at this point. Forcing shutdowns isn't the end of the world, but it shouldn't be necessary to get my display back. Are there other ways to force HDMI to retry its handshake / test for a signal? Replugging doesn't seem to work, on either end.

 

Any help or suggestions would be appreciated!

24/7 machines often have to deal with huge heat so that would fit the scenario. Noticing there are no temps listed.   Does it get slow or glitchy for a while before it goes blank? 
Even if it is idle most of the time there will be parts that aren’t sleeping, and those parts could get hot over time.  Possibly single chips or single linkages.  Throwing a motherboard fan in and seeing if the problem goes away might be interesting if there happens to be such laying around.

Edited June 24, 2023 by Bombastinator

[docmars]

23 minutes ago, Bombastinator said:

24/7 machines often have to deal with huge heat so that would fit the scenario. Noticing there are no temps listed.   Does it get slow or glitchy for a while before it goes blank? 
Even if it is idle most of the time there will be parts that aren’t sleeping, and those parts could get hot over time.  Possibly single chips or single linkages.  Throwing a motherboard fan in and seeing if the problem goes away might be interesting if there happens to be such laying around.

 

No thermal issues here:

• GPU: ~53 C idle, ~75 C load
• CPU: ~36-40 idle, ~55 C max at load (Prime95, all cores), ~high 60's when gaming
• MOBO: 26-36 C max for all 3 sensors

As far as performance goes, I never run into slowness or glitchiness, ever. Temps are always well within good ranges even under load.

[Bombastinator]

7 minutes ago, docmars said:

 

No thermal issues here:

• GPU: ~53 C idle, ~75 C load
• CPU: ~40-50 idle, ~54 C max at load (Prime95, all cores), ~high 60's when gaming
• MOBO: 26-36 C max

As far as performance goes, I never run into slowness or glitchiness, ever. Temps are always well within good ranges even under load.

So working fine, working fine, then boom.  That gpu idle is a hair high. May not be indicative of anything.   Different GPUs have different bingo temps.  There are some that would be right up to the limit for though.  The cpu won’t be an issue.  Motherboard (specifically certain chips or traces ON the motherboard might though which is why I was wondering about the fan.  This is win11 then?  Might also be interesting to run it with just about anything else for a day or two and see what happens

Edited June 24, 2023 by Bombastinator

[docmars]

29 minutes ago, Bombastinator said:

So working fine, working fine, then boom.  That gpu idle is a hair high. May not be indicative of anything.   Different GPUs have different bingo temps.  The cpu won’t be an issue.  Motherboard (specifically certain chips or traces ON the motherboard might though which is why I was wondering about the fan.  This is win11 then?  Might also be interesting to run it with just about anything else for a day or two and see what happens

I'm running Windows 10 (see original post), and I'm able to play recent AAA titles at max detail for hours upon hours, no issues.

 

I appreciate your suggestions, but I think you might be misunderstanding my original problem -- again, the blank screens are only happening after leaving my PC idle for 10-18 hours after I've turned off my TV, but it's hard telling exactly why (or when) it happens. I never experience blank screens while I actively use the system. After a long gaming session, my max temperatures are within the good ranges I listed earlier.

 

This issue is intermittent as well, but occurred twice in a short period here recently, which is abnormal. Most of the time, I only see this happen every few weeks or so.

[Bombastinator]

5 hours ago, docmars said:

I'm running Windows 10 (see original post), and I'm able to play recent AAA titles at max detail for hours upon hours, no issues.

 

I appreciate your suggestions, but I think you might be misunderstanding my original problem -- again, the blank screens are only happening after leaving my PC idle for 10-18 hours after I've turned off my TV, but it's hard telling exactly why (or when) it happens. I never experience blank screens while I actively use the system. After a long gaming session, my max temperatures are within the good ranges I listed earlier.

 

This issue is intermittent as well, but occurred twice in a short period here recently, which is abnormal. Most of the time, I only see this happen every few weeks or so.

You’re right.  I did misunderstand.  That sounds like sleep state stuff.  So which exact cpu, motherboard, and bios may matter.  It could be a bios thing, a microcode thing, an OS thing, or some combination of the above.  Good news is the chance there is something wrong with your hardware is low.  Maybe update the bios (if it isn’t already) to see if that solves your issue.  Also maybe see if people are also having the same issue with a similar build of windows.