Problem with turning off the display device

I'm running windows 10 pro on an intel NUC7i5. I'm using my TV as a monitor connected via an HDMI cable.
As long as I keep the TV on, windows runs reliably. In fact I have never seen it stop or crash even when running continuously for weeks at a stretch. However if I turn off my TV, then when I turn the TV back on again many hours later, about half the time the display is visible and the other half the time the screen is completely blank (as if the display hdmi cable has been disconnected). If I simply unplug the display hdmi cable and plug it back in again the display will again come alive (about half the time) and then windows will again behave normally. The other half the time I have to reboot the nuc to restart windows. (It restarts normally every time.)

Is there something windows could be doing that requires the display to be alive? I'm generally running Kodi although I don't think the problem has anything to do with what program I am running. I could do more testing to verify that, although it takes a long time to collect the data. Also, in the power applet I have said that windows should never sleep or hibernate. At one point I tried allowing it to sleep, but I believe I saw a similar problem where only a blank screen would appear when windows woke up.

Does anyone know what the issue could be? Or if not what experiments can I run to narrow down the problem?

Thank
~Paul

Also, in the power applet I have said that windows should never sleep or hibernate.

What I'd also look for is other settings in Power Options that can put things like the USB ports to sleep in the interest of saving energy, such as MultiMedia settings.

Ok, I looked thru the many dozens of Power options and disabled anything that gave any suggestion that it might save energy. At first, I thought this improved things, but after a few days, it started showing a blank screen about 3/4 of the times that I turn the TV back on. This is worse than before, but perhaps could be just a statistical variation. Also lately the trick of unplugging the HDMI cable and replugging it back in hasn't worked, so now a reboot seems to be the only recourse. (Again this could be just a statistical variation). In any case, the problem has clearly not been solved so I'm hoping someone out there can suggest something else to try.
Thanks
~Paul