Noted this comment elsewhere about waking up: (Ok, yours isn't a sleep problem..)
...with the Realtek PCIE GBE Ethernet controller. Just go to the device manager, and right click to select the properties for it. On the advanced tab, look for "Wake on pattern match" and set that to disable. After clicking on OK, just do a reboot to ensure the driver is loaded with the new settings. This fixed it for me, and it may be effective for the Atheros GB drivers too.
my NIC is Intel(R) 82579V Gigabit Network Connection (on the motherboard) there are no Wake options of any kind in the Advanced tab, at least not with the word Wake in it
I actually had to remove some of the standard filters because everything in the log looks quite normal and i'm not seeing anything related to the monitor.
Booting to Safe Mode sounds like a good idea, however, it creates some complications in my testing. If the monitor was on it stays on, if it was on and turned off it generally doesn't come back on. I have been able to keep the monitor off entirely on bootup by doing remote logins for testing. I'm 100% sure the remote login has nothing to do with it since it occurs in the middle of the night without the remote login, and it takes up to 3 minutes after login at startup for the monitor to come on. Lack of network access and the program to allow remote login is likely to have the system sitting at the login screen forever, which I have tested, if I don't login it can sit for 20+ minutes with nothing happening.
Assuming the origin of whatever signal is being sent to the monitor results from some software activity and not from the hardware interface to which the monitor is connected, it should be in Proc Mon's log.
Don't expect to see sthg obviously related to a monitor..
If you eliminate that, it's a pure hardware issue...
Last edited by dalchina; 03 Dec 2015 at 12:44.
I could imagine its the hardware, except that it happens at very specific times, and at boot only after certain things happen in Windows. Which means its almost definitely the system and not the hardware, just can't imagine what it is.
So does it happen if you do a clean boot? I can't recall you saying you'd tried it.
If it does, then run proc mon in the same state, setting Proc Mon's filter so no processes are displayed.
Then schedule it or leave it to run to capture an event.
I have the exact same issue, (but the opposite) happens once a day, turns off completely, however I am running on two screens, one using a DVI to HDMI adapter out of the GPU (which this screen works fine) however the second, (using Amazonbasics HDMI cable straight out of the GPU) Will turn off once every 24 hours, usually 3 or 4 mins after boot. sometimes it works fine and sometimes it does not.
Any suggestions?
Cheers,
Jason
P.S I recently swapped the HDMI's over with another one, I will report back if anything happens.
Last edited by Jason45PC; 24 Jan 2016 at 07:52.
I surrendered after searching through the proc mon logs for several days and trying to filter out the unlikely events. I ended up getting a new monitor which stopped the problem. Then my video card died and got a new one of those to but the problem hasn't happened since the new monitor. I think certain types of monitors might get a wake up call from Cortana or something for the mic, however I couldn't pin it down to that in procmon with absolute certainty.
Hi, it's definitely worth searching through this forum for similar situations e.g.
Monitor turns off after 2 minutes of inactivity - Page 3 - Windows 10 Forums
For whatever reason Win 10 is more sensitive to and throwing up more problems related to some hardware or configurations from mice thru WiFi to monitors including dual monitor configurations than previous editions.
Quote