magna86
20
...there are other unsigned drivers on my machine...
There are ways for non-signed driver to be loaded in kernelspace on x32bit masine. But in the x64bit machine is impossible (for now) as Driver Signing Policy and Kernel Patch Guardl will not allow. Use google for thouse tearms for understanding.
Perhaps it's do do with users who have admin accounts rather than limited user accounts.
This can't applies due to the nature od kernelspace. For understanding, search google for kernelspace, userspace and Rung (CPU).
There is no theoretical possibility for avast driver to be unsignet. These drivers are the force and power of avast. But it may be that some other kernel driver influences with avast’s driver. Guessing …
However, we will examine your theory in this or in case that follows.