Again, left overnight, no forms of Linux seem affected.-Asudem
Saying that Linux is unaffected is pretty close to pointless as Linux won't be affected
unless it is a physical hardware issue, (eg. intermittent contact in the keyboard), as that is the only common ground between Linux and Windows.
It would have relevance if Linux used the same drivers and ran the same processes ... but then it would be Windows. So it still doesn't exclude peripherals from the equation.
It did this the night of the fresh Win10 install on a new hard drive about a month ago. So it survived an entire Hard Drive and OS clean install.
In the absence of information, can we assume that most, if not all, of the Windows telemetry has not been disabled?
Considering this has been occurring since OS installation and the amount of crap that Windows collects and sends back to Microsoft at who knows what times, it
might be related to that.
EDIT2: Found this in my security audit. Should I be concerned? Why would chome.exe be in there while I'm using it to read this reply?
It's Google, they along with Microsoft want to collect everything about you, this is common knowledge - since you've knowingly installed Chrome I would have thought you'd expect to see it's grubby little feet trampling through your machine
Event ID 4798But if it makes you feel easier, I'm not seeing anything like that for Vivaldi, Iridium, or Slimjet - all based on the same source code. I don't use any type of browser account for syncing, bookmarks, passwords, etc - so who knows, it may be related to that.
However: None of this can explain what turns my monitor back off after turning it on.
Find what's turning it on since the second event can't happen without the first event.