Following the rollout of Splunk UF 10 into production on Windows servers, users have reported a sharp increase in resource utilization. The problem is characterized by elevated CPU and memory usage, eventually causing the Universal Forwarder to crash.
Windows Event Viewer frequently logs faults associated with the splunk-winevtlog.exe process, which is responsible for collecting Windows Event Logs. The errors reference KERNELBASE.dll, a Windows system module, suggesting the crash is directly tied to Event Log ingestion on Windows OS.
Example fault details from Windows:
Faulting application: splunk-winevtlog.exe
Faulting module: KERNELBASE.dll
Exception code: 0xeeab5254
Application path: C:\Program Files\SplunkUniversalForwarder\bin\splunk-winevtlog.exe
Module path: C:\Windows\System32\KERNELBASE.dll
Or:
Message=Faulting application name: splunk-winevtlog.exe, version: 2307.1792.26801.57135, time stamp: 0x68b1e072
Faulting module name: VCRUNTIME140.dll, version: 14.16.27033.0, time stamp: 0x5d30eadf
Faulting application path: C:\Program Files\SplunkUniversalForwarder\bin\splunk-winevtlog.exe
Faulting module path: C:\Program Files\SplunkUniversalForwarder\bin\VCRUNTIME140.dllIf the crash still continues, try disabling the resolution of the Active Directory Security IDentifier (SID) objects to their canonical names (evt_resolve_ad_obj = 0)
In $SPLUNK_HOME/etc/apps/Splunk_TA_windows/local/inputs.conf
[WinEventLog://Security]
evt_resolve_ad_obj = 0
evt_resolve_ad_obj = <boolean>
* How the input should interact with Active Directory while indexing Windows
Event Log events.
* If you set this setting to true, the input resolves the Active
Directory Security IDentifier (SID) objects to their canonical names for
a specific Windows Event Log channel.
* If you enable the setting, the rate at which the input reads events
on high-traffic Event Log channels can decrease. Latency can also increase
during event acquisition. This is due to the overhead involved in performing
AD translations.
* When you set this setting to true, you can optionally specify the domain
controller name or dns name of the domain to bind to with the 'evt_dc_name'
setting. The input connects to that domain controller to resolve the AD
objects.
* If you set this setting to false, the input does not attempt any resolution.
* Default: false (disabled) for all channels
This issue has been fixed in Splunk versions 10.0.2, 9.4.6 and 9.3.8.
[URGENT] All splunk forwarders upgraded to 10.0 version are crashing
Universal forwarder version 10 memory leak
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |