CPU consumption over 50%

NextDNS  

NextDNS Hello, I was able to write to you because I stopped the program from the Windows task manager and now it seems to have returned to a normal 0% consumption even if I don't understand why I can't activate the NextDNS adapter. Perhaps as you say it should be uninstalled and reinstalled.

NextDNS Hello after uninstalling and restarting Windows I notice that the Adapter v9 card is still present, should I consider this a normal behavior? 

NextDNS Hello, I'm sorry to bother you, but it seems that the problem is not solved even with the removal and installation of the program. I checked the resources and as you can see from the image the consumption by NextDNS was again high. To restore the normal functioning of the network, it was not even necessary to disable NextDNS, but it was necessary, in the same way as the last time, to finish the task from the task management. Now I must also confess that I also find a slowness in skype in group calls, which I did not remember for a few weeks and having ascertained from my contacts that this type of slowness this time I only have it (like opening and closing the microphone, share etc), I just have to conclude that it could be due to excessive CPU work. I do not know that this is due to NextDNS, but certainly the elements available to me for now could make me think. Maybe my pc is too obsolete (a Toshiba Satellite Pro A200) to be able to support the new functions that are created with modern programming tools and it might encounter some incompatibilities that make it unstable. To conclude, I tell you if it can help you to understand something more about what happens, that the only thing I do outside of the normal functioning of the PC is to disable the network card using a script in Powershell, scheduled and working at login. Wireless and the NextDNS v9 adapter to reactivate them immediately afterwards. I am forced to do this, for now and except for other suggestions, due to the connection problems that Windows reports to me when I turn on the PC, but this happened even before installing NextDNS and it seemed, by the grace of God, also to work as a temporary solution and minimally invasive (i.e. without manually editing the system registry).