High CPU and High Disk access from ESET

[Guest]

A few computers seem to be struggling with either very high CPU or Disk Access, seems to have got worse since December. Some machines where users report a problem ESET will be 100% Disk constantly others 100% CPU

 

Tried to get Logs from a disk usage one but failed with

 

January 18, 2022 08:24:14Operating systemFailedFailed to start applicationLog collector failed to produce diagnostic archiveJanuary 18, 2022 08:23:58Operating systemRunningTask startedJanuary 18, 2022 08:23:58ESET Management AgentStartingStarting taskJanuary 18, 2022 08:19:22Operating systemFailedFailed to start applicationLog collector failed to produce diagnostic archiveJanuary 18, 2022 08:18:58Operating systemRunningTask startedJanuary 18, 2022 08:18:58ESET Management AgentStartingStarting task

 

High CPu logs attached

 

 

Get-Process | Sort-Object CPU -Descending | select -First 5 ; (Get-Date).DateTime

Handles  NPM(K)    PM(K)      WS(K)     CPU(s)     Id  SI ProcessName                                                                                                          
-------  ------    -----      -----     ------     --  -- -----------                                                                                                          
   3874       0      196        124  56,891.89      4   0 System                                                                                                               
    803      51    53936     196148  50,097.92   1928   0 ekrn                                                                                                                 
   1572      94   400364     109064  13,769.41   2656   1 dwm                                                                                                                  
   6504      65   170924     104768   8,236.44   9044   1 Teams                                                                                                                
 111745    5538   522048     289872   6,531.22   9728   1 WINWORD                                                                                                              
18 January 2022 09:31:47
 

 

 

b03dd87b-a4fd-46df-b52d-643821fb1b6e_era-diagnostic-logs_2022-01-18_09-20-36.zip

Edited January 18, 2022 by robg
edit

[Guest]

Don't know if this helps , is one that had high disk access 100% from ESET, also CPU

Get-Process | Sort-Object CPU -Descending | select -First 5 ; (Get-Date).DateTime

Handles  NPM(K)    PM(K)      WS(K)     CPU(s)     Id  SI ProcessName                                                                                                          
-------  ------    -----      -----     ------     --  -- -----------                                                                                                          
    810      49    52188     184540  21,268.75   1620   0 ekrn                                                                                                                 
    752      29   346320     352520   7,931.50   6196   2 chrome                                                                                                               
    478       9     2124       8104   6,318.91   4088   0 WTabletServicePro                                                                                                    
   5286       0      196        140   5,757.95      4   0 System                                                                                                               
   1151      51   157628      81032   5,627.80   6576   2 Teams                                                                                                                
18 January 2022 09:46:04

 

January 18, 2022 09:45:24	ESET Management Agent	Starting	Starting task
January 18, 2022 09:45:24	Operating system	Running	Task started
January 18, 2022 09:45:43	Operating system	Failed	Failed to start application	Log collector failed to produce diagnostic archive

 

 

[Marcos 5,231]

Please enable advanced OS logging in the advanced setup -> tools -> diagnostics when the issue occurs and leave it enabled for 3-5 minutes. After disabling logging, wait until C:\ProgramData\ESET\ESET Security\Diagnostics\ESET\Diagnostics\EsetPerf.etl is created, then collect fresh logs with ELC and supply the generated archive.