New
#11
Ok, sorry, I should have asked. What state is your PC in during the night?
Monitor turns on by itself
-
-
New #12
Its on in normal running mode, just the power button on the monitor off. Sometimes playing audio before bed usually ending before the monitor wakes up, but its turned on without any programs running other than the OS and whatever background processes are running at the time.
-
New #13
Hi, in Device Manager, find the Properties sheet for your monitor; have a look at the Events tab- is there anything helpful there?
It may be that you will need to use Systinternals process monitor, note a time when the monitor comes on, and from the log created by process monitor, try to identify what is happening.
Also have you checked your scheduled tasks?
Is your computer on a LAN?
-
New #14
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.
-
New #15
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?
-
New #16
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.
-
New #17
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.
-
New #18
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.
-
-
New #19
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.
-
New #20
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.
Quote
Related Discussions
