Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Collector Data Processor causes high CPU and memory utilization

Collector Data Processor causes high CPU and memory utilization

Updated 11 July 2017


This article describes an issue where the SolarWinds Collector Data Processor is running at 80% or more and the CPU usage spikes at 100% in NPM 11.X releases.


A similar issue was noticed after upgrade come migration from NPM 12.2 to 12.3 on Windows Server 2016 where the collector and IIS processes taking more than 80% of CPU constantly on Main poller and the additional poller was running normally.


  • NPM 11.5 or earlier
  • After upgrade come migration of NPM 12.2 to 12.3 and SAM 6.6.1


  1. MSMQ was unable to write the results of polling jobs to the database resulting in the process running out of memory. MSMQ folder (C:\Windows\System32\msmq\Storage\) is not full when checked. NPM 11.5 uses a 32-bit Collector Data Processor and is able to access up to 1 GB of memory per 1 processor.
  2. Untrusted apps are blocked by default via GPO on the system which caused a broken installation that created empty files in Solarwinds installation folders



Symptom 1 Resolution:  

SolarWinds recommends upgrading to NPM 12.0 to fix the issue.


Symptom 2 Resolution:

  1. Right-click the installer (NPM 12.3 )
  2. Click properties
  3. Check "Unblock" under General Tab -> Attributes section
  4. Right-click the installer and run as administrator 
  5. Once the installer copies files, run the config wizard when prompted



Last modified