Processor Load Data Does Not Match System Provided Proc Use Info

This morning a member of our team was looking at processor load over time on a windows 2008 R2 host and noted that what he saw in SolarWinds NPM did not match what he was seeing when he looked at the system's load through Task Manager and later Perfmon on the system  The data in NPM was consistently higher.  He asked me about this and I did a bit of digging and found a disturbing trend in the source data within SolarWinds.

In short - NPM appears to be recording the same value for min and max CPU  (and hence average CPU) in the CPUMultiLoad_Detail, CPUMultiLoad, and CPULoad tables (my guess would be that the latter is derived from the former).  I am guessing that this is the result of one of the following:

• Stupid-Human-Trick 1 - I'm looking at the wrong tables in the database (but the data I see in the table aligns with what I am seeing in the graphs which are out of line with the graphs that we are seeing in the other sources - so I doubt this is the case)
• Stupid-Human-Trick 2 - I made a mistake on installation which resulted in this averaging before population (possible - although I was pretty careful during the portion of the configuration in which actual decisions were being made).
• Fixed Bug - There is a known issue in the software - apply the update... (note - I did do a bit of digging and did not find this listed
• Active Bug - There is a known bug that is not resolved
• Other?

My money is on the second or third option - but searching for a few did not provide any information on this symptom.  Data and system version information below...

Thanks in advance...

DATA / SYSTEM INFORMATION

For example - the data for the node in question for the last couple of windows from each table follows:

FROM CPUMultiLoad

FROM CPUMultiLoad Detail

FROM CPULoad

SO - The values in the MinLoad, MaxLoad, and AvgLoad fields in the CPULoad table are each the same, and each the rounded average of the full set of values for all processors in the node for the same window in CPUMultiLoad.  I have to assume that there is an issue with my configuration that is causing this behavior (or at least I HOPE that this is not the intended behavior as it certainly is not "good data" regarding min/max/avg CPU load since the last poll.

Am I looking at the wrong data in the database?  What causes this?

Environment Details:

FROM SETTINGS: Orion Platform Details (redacted a couple of items not germane to the question - like the hostname)