Number of times this software crashed during the last 24-hour reporting period.

Software crash and hang information is obtained from Windows event data. For background information on Windows events and the event viewer refer to  https://support.microsoft.com/en-gb/help/302542/how-to-diagnose-system-problems-with-event-viewer-in-microsoft-windows

Average disk I/O write rate per second during the last 24-hour reporting period.

For background information on analyzing disk storage performance refer to  https://docs.microsoft.com/en-gb/archive/blogs/cotw/analyzing-storage-performance

Average Virtual Memory Usage KB during the last 24-hour reporting period.

For an explanation of Windows Virtual Memory organization refer to  https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/physical-and-virtual-memory-in-windows-10/e36fb5bc-9ac8-49af-951c-e7d39b979938  and  https://support.microsoft.com/en-us/help/2160852/ram-virtual-memory-pagefile-and-memory-management-in-windows

This is an easier notion than Processor Time Seconds. This is the average of the processor consumption of each instance. Each instance of this process will have caused different percentages of compute resource in all the processors and cores to be used over time (unless they have specifically requested certain core affinity). For each minute each process is running, a profile of the usage is built for the whole day. This value is the average of all of those samples. There is no way to work out, for any one of the process instances involved, how long any particular instance was running for. This could indicate a process that is going wild with resources, but it would take more investigation on the device to discover for how long this is happening. It is perfectly possible to see all the values in this column adding up to more than 100% as the processes were not necessarily running at the same time.

For further information on Processor time refer to  https://social.technet.microsoft.com/wiki/contents/articles/12984.understanding-processor-processor-time-and-process-processor-time.aspx

An indicator of how reactive a process is to activity by other processes on the device. Typically, anti-virus products watch and respond to potentially suspicious activity such as increased network traffic. Anti-virus products will differ in their impact on the overall performance of a device.

Responsiveness Impact % is used to indicate how sensitive a process that appears to be to the use of system resources by other processes on a device. For example Security Protection software present on a device may reveal a spike in its activity whenever a new process is started on that device. This would typically be because the Security Protection software may wish to ensure that the new process starting on the device is present in a security white-list. Other software may also react to activity by other processes and by reacting they impact system resource uses, thereby adversely affect the user's experience. So it is useful to be able to identity software with the highest Responsiveness Impact on a device and potentially investigate further.

Responsiveness Impact % represents the proportion of the increased CPU activity detected by the 1E Client as a result of performing a set of operating system level operations that can be attributed to a given running process. Examples of these would be Windows registry and resource creation operations.

It is reported as a percentage to normalize results across devices that offer a range of computing power.

For example if  software.exe  on a device is attributed a Responsiveness Impact of 53% this means that more than half of the spike in CPU usage caused by software monitoring activity on that device can be attributed to  software.

Average number of Windows handles used by this software during the last 24-hour reporting period.

For further information on Windows handles refer to  https://docs.microsoft.com/en-us/windows/win32/sysinfo/handles-and-objects

For tips on examining open handles for any Windows process refer to  https://docs.microsoft.com/en-us/sysinternals/downloads/handle  and  https://techcommunity.microsoft.com/t5/windows-blog-archive/pushing-the-limits-of-windows-handles/ba-p/723848

Average Physical Memory Usage KB during the last 24-hour reporting period.

Please refer to  https://docs.microsoft.com/en-us/sysinternals/downloads/rammap  for a useful tool to examine physical memory allocation on a device.