Too much disk IO

Comodo Internet Security - CIS AntiVirus Help - CIS
#1

Hi;

Every morning when I start my laptop, cmdagent starts checking for updates.
Until the end of the update it’s impossible to use the computer.
The level of disk IO forbid the launch of an other program.
Don’t ever think of starting reading your mails for example.
If you look down here you will see the enormous : Write KB = 837 768
Do you think a next version will correct this problem soon ?

Thanks for the product, it’s best than all other tested competitors.

[Current Process Pane]

CMD = “C:\Program Files\Comodo\COMODO Internet Security\cmdagent.exe”
Curr Dir = C:\WINDOWS\system32
Path = C:\Program Files\Comodo\COMODO Internet Security\cmdagent.exe
User Name = AUTORITE NT \ SYSTEM
PID/Parent PID = 1880 / 1600
Started by = C:\WINDOWS\system32\services.exe
Virtual KB Curr = 224 548 Peak = 559 260
Working Set KB Curr = 10 980 Peak = 293 592
Page File KB Curr = 65 684 Peak = 319 888
System Pool KB Paged = 102 Nonpaged = 15
Private KB = 65 684
Handles Count = 413
Faults Count = 1 047 642
Objects = USER = 6 GDI = 9
Windows = 0
Reads = 715 Read KB = 2 921
Writes = 439 Write KB = 837 768
Other IOs = 48 240 Other KB = 5 846

#2

no answers from support team, so I show you some more of the same problem.
I didn’t start my PC during the weekend.
This morning back to work and AV update as usual.
You see here under the total amout of write KB.
I started the PC half an hour ago and I still difficulties using it because of the disk IO’s
And as I write this memo the amount is still growing !!!
Thank you cmdagent ;D

[Current Process Pane]

CMD = “C:\Program Files\Comodo\COMODO Internet Security\cmdagent.exe”
Curr Dir = C:\WINDOWS\system32
Path = C:\Program Files\Comodo\COMODO Internet Security\cmdagent.exe
User Name = AUTORITE NT \ SYSTEM
PID/Parent PID = 1684 / 1432
Started by = C:\WINDOWS\system32\services.exe
Virtual KB Curr = 428 020 Peak = 460 464
Working Set KB Curr = 196 788 Peak = 310 388
Page File KB Curr = 217 760 Peak = 320 736
System Pool KB Paged = 306 Nonpaged = 16
Private KB = 217 760
Handles Count = 403
Faults Count = 2 225 848
Objects = USER = 6 GDI = 9
Windows = 0
Reads = 709 Read KB = 2 921
Writes = 1 338 Write KB = 2 199 920
Other IOs = 61 719 Other KB = 7 078

#3

Hello gillou78,

This certainly is not normal, can you tell me how your real-time settings are ?
And does it help if you disabled updates on the real-time settings tab ?
Can you finish a complete manual scan or does CIS crash on it ?

Just to be sure, are you running 3.11.x.552 ?
What other security software do you have installed, no matter if real-time or on-demand?

#4

Hi gillour78

Do you have Comodo System Cleaner installed? If so check out this thread.

https://forums.comodo.com/general_discussion_off_topic_anything_and_everything/servicesexe_at_30_cpu_and_high_memory_usage-t43930.0.html

If not just ignore this.

John

#5

Hello,

First of all thank you for helping me.

Answers to Ronny first :
Where do I find the real-time settings ? I looked at CIS settings and did not find any real-time !!
The complete scan works OK, no crash.

Answer to John,

I have system cleaner installed and will follow the link and come back to tell you if there is better to find from this side.

Kind regards

Gillou

#6

I forgot to say I am running 3.11.xxx.552

;D

#7

You can find it by opening the CIS GUI clicking on AV and then in the bottom right click on “Scanner Settings” this should bring up these options:

#8

I used to have cmdagent running too much at startups.

When I disabled the option in the screenshot above, “Scan memory on start”, the problem stopped. :slight_smile:

#9

Thank you Ronny for your kind help.
I just changed the settings.
Due to time zone delay , I will give you the result tomorrow morning European time.

Have a good day.

Gilou

#10

Hello folks,

So the news are as follow and attached :
I changed the settings as you can see in the picture attached.
So no more memory scan at start up.
Something weird happen after 5 minutes.
The disk IO went to a frenzy and it reached more than 400 000.
But more worying is the “Faults Count = 537 619”
I don’t know what “Faults Count” is but the level is impressing.

If you have any sugestions you’re welcome.

Best regards

Gillou

see the complete process pane
CMD = “C:\Program Files\Comodo\COMODO Internet Security\cmdagent.exe”
Curr Dir = C:\WINDOWS\system32
Path = C:\Program Files\Comodo\COMODO Internet Security\cmdagent.exe
User Name = AUTORITE NT \ SYSTEM
PID/Parent PID = 1860 / 1596
Started by = C:\WINDOWS\system32\services.exe
Virtual KB Curr = 214 064 Peak = 446 708
Working Set KB Curr = 10 944 Peak = 243 276
Page File KB Curr = 63 404 Peak = 316 224
System Pool KB Paged = 100 Nonpaged = 14
Private KB = 63 404
Handles Count = 412
Faults Count = 537 619
Objects = USER = 6 GDI = 8
Windows = 0
Reads = 142 Read KB = 438
Writes = 289 Write KB = 417 837
Other IOs = 9 379 Other KB = 4 169

[attachment deleted by admin]

#11

I don’t know the tool you are using but it’s probably “page faults”, can you look that up in the help file if those “faults” are of that type ?

#12

Hi Ronny,

Thank you to try to find a solution to this weird problem.
Yiou are right, I checked the help file and “faults count” is for page errors !!

As you can see hereunder we have reach a top at more than 3 millions KB this morning.

Best regards

Gillou

[Current Process Pane]

CMD = “C:\Program Files\Comodo\COMODO Internet Security\cmdagent.exe”
Curr Dir = C:\WINDOWS\system32
Path = C:\Program Files\Comodo\COMODO Internet Security\cmdagent.exe
User Name = AUTORITE NT \ SYSTEM
PID/Parent PID = 1860 / 1596
Started by = C:\WINDOWS\system32\services.exe
Virtual KB Curr = 209 816 Peak = 446 736
Working Set KB Curr = 10 732 Peak = 306 720
Page File KB Curr = 63 616 Peak = 316 456
System Pool KB Paged = 100 Nonpaged = 14
Private KB = 63 616
Handles Count = 414
Faults Count = 2 728 516
Objects = USER = 6 GDI = 8
Windows = 0
Reads = 138 Read KB = 438
Writes = 1 618 Write KB = 3 126 640
Other IOs = 12 406 Other KB = 5 614

#13

Can you try this with Process Explorer from Microsoft also and see if it turns up with the same value’s ?

Also try to boot once with the Real-Time AV slider set to disabled and see if it callms down then ?

#14

Ok I do that, but it can be monitored only at a next day startup.
If I start the system several times during the day, the problem occurs only the first time !!

Gillou

#15

Okay that makes sense in relation with the “Stateful” setting of the AV.

Can you tell a bit more about your system setup ?
Like disk size, CPU etc
And what is your average use of the system does it contain a lot of mp3 file’s for instance or other things that could cause long scan times ?

#16

I have installed the Process Explorer and you will find a picture attached of the results for cmdagent.

here are the informations about my system.
Sorry it’s in French but I am sure you will guess what is what !!

I also have a lot of mp3 files on the disk, 11Go in 2600 files
Sure it doesn’t help the scan !!!
__

Système d’exploitation Microsoft Windows XP Professionnel
Version 5.1.2600 Service Pack 3 Nu 2600
Éditeur Microsoft Corporation
Ordinateur DELLX1
Fabricant Dell Inc.
Modèle Latitude X1
Type PC à base X86
Processeur x86 Family 6 Model 13 Stepping 8 GenuineIntel ~598 Mhz
Version du BIOS/Date Dell Inc. A04, 06/10/2005
Version SMBIOS 2.3
Répertoire Windows C:\WINDOWS
Répertoire système C:\WINDOWS\system32
Périphérique de démarrage \Device\HarddiskVolume1
Option régionale France
Couche d’abstraction matérielle Version = “5.1.2600.5512 (xpsp.080413-2111)”
Utilisateur DELLX1\X1
Fuseaux horaires Paris, Madrid (heure d’été)
Mémoire physique totale 512,00 Mo
Mémoire physique disponible 95,98 Mo
Mémoire virtuelle totale 2,00 Go
Mémoire virtuelle disponible 1,96 Go
Espace pour le fichier d’échange 1,20 Go
Fichier d’échange C:\pagefile.sys

[attachment deleted by admin]

#17

There have been reports from users with 512MB memory systems that putting the pagefile.sys on the AV exclusion list improved performance at system startup, can you try that also ?
And if that doesn’t work try to exclude the root folder of the mp3’s to see if that helps…

#18

Ok I will do that and get back to you tomorrow.
:slight_smile:

#19

Hello,

I made a mistake in the exclusion so I will be able to tell you how things are going only wednesday.

Regards

Gillou

#20

No problem