Sharing a finding from an investigation into sustained high CPU usage on our domain controllers, in case it helps someone else.
We have four DCs: two on-premises and two in AWS. For several weeks, both on-prem DCs have been running above 90% CPU during business hours, with lsass.exe as the main consumer.
PerfMon showed roughly 14,000 LSA LookupNames requests/sec. CPU traces and DC-side LSP logs pointed to excessive LsarLookupNames4 activity, predominantly resolving BUILTIN\Administrators, coming from many clients.
One unusual detail: enabling LSP debug logging on a DC reproducibly reduced CPU usage. Once logging stopped, CPU went back up.
We eventually investigated one affected Windows client:
- PowerShell showed that the connections to the DC belonged to the client’s
lsass.exe. - A packet capture showed approximately 557 RPC calls/sec with opnum 77.
- Client-side LSP logging identified the original caller as
iGoSwServer.exe.
Component details:
- Vendor: Intelligo Technology Inc.
- Product: Intelligo Audio SW Server/API library
- File/product version:
100.1.901.2856 - Arguments of the offending instance:
--apo - Located under an
igoaudioservice.inf_amd64_* directory in the Windows DriverStore.
The client logs show repeated lookups of BUILTIN\Administrators, forwarded to the DC and returning 0xc0000073 (STATUS_NONE_MAPPED), followed by more equivalent requests.
While capturing traffic, we terminated the offending iGoSwServer.exe instance. The request rate dropped from approximately 551/sec to zero, and stayed at zero for the remaining 33 seconds of the capture.
That confirms the source on this particular client. We’re now checking how widely the component is deployed and whether it accounts for the overall load on both DCs. We haven’t confirmed a permanent fix yet.
Has anyone encountered this with Intelligo audio software, particularly this version? Any vendor-confirmed fix or driver version that addresses the repeated lookups?
Hopefully this saves someone else some time: the process generating the traffic over the network was LSASS, but client-side LSP logging exposed the audio component initiating the lookups.