Diagnosing High CPU in Unrelated Windows Processes Caused by Filter Drivers
A monitoring agent, powershell.exe, and Process Explorer showing high CPU simultaneously may actually be caused by a kernel filter driver inspecting their file activity. Because minifilter pre-operation callbacks run in the context of the originating thread, the time is charged to those processes rather than the driver. The article describes checking privileged versus user time counters, a baseline comparison, and listing filter drivers with fltmc to identify them. It then explains how to map the driver file and vendor using Win32_SystemDriver, and use Process Explorer thread stacks with symbols to find the same third-party driver across unrelated processes.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in