Why does Pilot's network filter click when I'm using a Chrome browser window?

Question

Google Chrome

Maybe someone will consider me crazy, but I am now writing this question in the Chrome browser, and the Pilot surge protector quietly clicks under my ear.
It clicks only when the window of this browser is active and any actions are performed in it, for example:
- blinking of the cursor (carriage) for entering text;
- highlighting a web page element by pointing the cursor;
- scrolling a web page;
I tried to perform the described actions in Internet Explorer - the network filter is silent.
Also, there is no clicking when working in Windows Explorer.
I have a Samsung laptop connected via a native power supply. Also connected to the laptop is a separate keyboard and AOC monitor. The lid-screen of the laptop is closed.
By the way, disconnecting the AOC monitor from power by pulling out the wire does not change anything: the Pilot surge protector continues to click in time with the blinking text input cursor, even if this cursor is not displayed on any screen.
Tell me how? How is this related? This click is driving me crazy...

Answer 1

All my life I have been fiddling with technology, the most funny things have happened. The pilot almost always has filters and a current fuse, it can click during current surges. The pilot can be more difficult with electronics. One thing I can say is that it’s better to set up backups just in case, because if video card activity breaks through as a hindrance, this may indicate a failure of electronic components, capacitors for example. And a considerable probability of further breakdown "with puff".

Answer 2

I had something like that, when the life span of the PSU was ending

Answer 3

Your example is so incredible for me that I believe you, because I see no reason to lie like that :)
I have an old computer, which I now use only for watching movies, and so it had a problem: I turn it off (it doesn’t matter how, I press the button or through the start menu), then I turn it on and Windows does not boot. It stops, the loading light flashes and that's it. And so it can stand in a frozen state for at least a day. Reboot or shutdown didn't help. It only helped to cut it out of the network, and in the on state (or frozen). It got to the point that I began to cut it down by pressing the pilot button. Windu changed, in total put 5 different assemblies (pirate xp). And only six months later, something switched over there and everything began to work. This example will not help you in any way, I just told you for an example of the strange behavior of a computer)