Windows 10: Monitor turns on by itself

Plugged into the router, Network card not allowed to wake the computer.

The events listed for my monitor and the generic monitor only have 11/14 listed which was my clean install.

Do I need to leave the systinternals monitor running at all times to catch the event? It appears to have alot of data streaming through.

 

Hi, Process Monitor will capture EVERYTHING, but
a. make sure you have as little running as possible
b. you can use the VERY comprehensive filtering to eliminate things shown that are recognisable and routine.

Using the filter does NOT remove items from the log, so you can generate both a full and a filtered report at the end.

Of course, you could schedule Process Monitor if you know approximately when the event takes place... (task scheduler).
=============================
A completely different approach is elimination- a whole lot easier to do at least initially.
That is (for example)
- disable as much hardware as you can (device manager)
- do a clean boot
If you can reach a state where this does NOT occur, then you're on your way to identifying the culprit.

I should also have asked whether this is a clean install or upgrade. I.e. are there many programs installed?
What AV are you using?

 

Clean Install, formatted the drive when I did it. Had waited a bit cause of the issues win10 was having with clean installs on initial release. I do have lots installed currently, but having tested during the clean install I waited to try and see the cause and aside from Windows itself after the install it occurred that night with nothing else installed. I tried to turn all the timed stuff nightly maintenance to different times but it hasn't helped.

using a Geforce GTX 670, standard soundblaster on the motherboard

Got the process monitor, will have it running tonight or in the morning on bootup. It does seem far more comprehensive than the EventLog.

 

Thanks. Suggest you do a clean boot and see what happens, then if the monitor still turns on, you have potentially far less logged by Proc Mon.

 

It only happens once a day between 3 and 5 am, or on a boot if the system was shut down at that time, so I have to wait till tonight for the clean boot. I really want to blame the Windows Automatic Updates but having changed the time it checks, and made sure there was nothing to update I can't exactly pin it on that. Also have it request reboots.

 

Ok so, forgot to set the procmon to start as admin so I had to remember to hit yes on my remote connection before it started. It also did something interesting which is instead of taking 3 minutes after login to turn the monitor on it came on the moment I hit yes to the process monitor. As interesting as that is though, hundreds of megs of log data is taking me awhile to sort through even filtering out things that are unlikely to be it.

 

Hi, the key to using the filter is before you start trying to capture a new event is
a. Simplify what's running- as little activity / background tasks as possible.
b. You can turn off your AV for this and disconnect your internet connection
c. Note what is reported by Proc Mon, and apply filters to anything you reasonably can that may not be of interest to reduce what is displayed to a minimum.. you should be able to reach a point with, say, 20-30 filters or less where almost nothing appears to be displayed by Proc Mon.
d. Then capture your event and see what appears.

Remember you can still always look at the full capture.

Presumably your monitor doesn't wake up if you are in Safe Mode?
Try that, then a clean boot, then consider a Proc Mon capture.

 

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...

 

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.

 

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.