Uptime 35 hours : cmdagent.exe = 54,944,503 Page faults.

Why does cmdagent.exe have sooooo many page faults? 54 million, nearly 55 million? The pc has been running for just 35 hours. I wouldn’t expect that many faults for years and years from all my applications put together.

[attachment deleted by admin]

I do not normally watch page faults, but I checked on the PC I am typing this on, running NIS 2011. It shows about 7.5 million after being on for about 20 hours.

I have 15 million on my machine after about 10 hours uptime.

Page Faults are not errors or anything. There just how many times the operating system needs to load a block of virtual memory from the harddrive back into the PC’s RAM…

usually the more ram you have the lower the page faults. I have been up for 35 hours and CIS is only at about 10 million.

LOL! ONLY 10 million.

Can somebody name any other app that even comes close to 2 million paging faults? I did once with IE and that had 4 tabs open for about 9 hours (went to work and left it) with a tiny temp net files folder. That had 1.8 million faults.

Surely there’s something wrong here? … ahhaaa. wait… there is!
none of my drives have paging set. They all had “no page file”, although my host o/s drive had 2048 - 4096 allocated to it. I setting them all to system managed size. Windows now reports i have 23, 627 Mb for paging of all drives. lol

Will reboot and post back to confirm it helped with the millions of paging errors.

robbie73, any application that using RAM intensively is subject to high page fault numbers. Page faults, as said above, are not errors but the way the virtual memory works. The heavier memory load - the higher page faults number, the more applications running simultaneously - the higher page faults number, the less RAM onboard - the higher page faults number, the more RAM read/write requests to different memory pages, when some of these pages swapped out of physical memory - the higher page faults number. There is no way to control page faults numbers by any particular applications, page faults “controlled” only by central processors and operating system itself.

Thanks for your explanation ntoskrnl.

Still, I have never had that problem with any other app before. I’ve used avg, avast, nod32 and kaspersky, all of which used on access virus scanners, and nod and kaspersky with full internet security. none of them ever caused this kind of number.

Comodo doesn’t use much ram. cmdagent.exe 1.8mb and cfp.exe 4.6mb. It uses lots of CPU tho (which the end user is unable to change the priority of. Can somebody ask the developers to address this please? If I can’t take control of the program running my machine, because of being denied access, then that is malware!)

Attempting to read or write to page 54 million times in just 35 hours is excessive. The reporting of that is a waste of resources as well. It’s almost like a dos attack, endlessly trying to write or read from a location that’s clearly unavailable. Eventually something will have to give, because the number can only be so big and still be stored.
Oh and I changed the page settings and rebooted and the number is still climbing. 2.5 million after being up just 2hrs 25 mins. That’s very roughly one attempt every 0.75 seconds. For a long at the machine is turned on…

Anyway, why is comodo trying to write to inaccessible areas again and again?? should it not learn and and just try a different location?

And why, despite having everything disabled, it still goes on to use 90% of CPU for 10-20 seconds or so when programs launch etc?

one final thing, how do I reset or check the firewall config to it’s defaults? I don’t remember changing anything, but I’d like to be sure that it is set to it’s default.


Suggest you read this page to understand what you are arguing about. The bottom line is: IT IS NOT A PROBLEM.

[Transcribed from Wiki Page fault - Wikipedia]

A page fault is a trap to the software raised by the hardware when a program accesses a page that is mapped in the virtual address space, but not loaded in physical memory.


Contrary to what their name might suggest, page faults are not errors and are common and necessary to increase the amount of memory available to programs in any operating system that utilizes virtual memory, including Microsoft Windows, most modern Unix-like systems (including Mac OS X, Linux, *BSD, Solaris, AIX, and HP-UX), and z/OS. Note that Microsoft uses the term hard fault in its Resource Monitor to mean ‘page fault’ [1].


Suggest you read this page to understand what you are arguing about. The bottom line is: IT IS NOT A PROBLEM.
+1 Seriously, this is NOT a issue
(which the end user is unable to change the priority of
That's a good thing, while you can change the priority of many files, generally most security software will prevent you from changing the priority of the files.

robbie73, modern desktop processors are able to execute billions operations per seconds or trillions of them per hour. 50 millions is nearly invisible shadow of those numbers. :slight_smile:

No. Comodo just reading from (writing to) some memory address, mapped on particular memory page, which swapped out of physical memory milliseconds (or seconds) before, because another application was in need of some memory :slight_smile: “Page faults” is mechanism that provides virtual memory functionality, but not error (or “fault”) by any means.

See my initial reply to your first post. Again, that is with Norton IS 2011.

Regardless, back when I used CIS5, I noticed it push a huge amount of the program into virtual memory. About 500+ meg on my machines. That may be part of the reason of the high page faults.

Right-click on the tray icon and select Manage My Configurations from the Configuration dropdown. Select whichever configuration is active and click the Import button. Then navigate to your CIS program folder. Default configurations are there. Import whichever configuration you’re using.

Just did some Googling on page faults. Most comments tell us not to worry about it.

I am not convinced that the 428 page faults per second that are on your system are indicative of a problem. There may be a lot of programs running that cause cmdagent.exe to work.

There are two types of page faults. Soft faults and hard faults. Hard faults are when Windows needs to actually retrieve data from the hard drive. Windows 7 has a powerful Resource Monitor and that shows no hard faults for cmdagent.exe here. It does show page faults; approx 293 per second.

Soft faults are quickly handled. It is the hard faults that will introduce more of a delay and only a huge amount of them can bog down one’s system.

robbie73- Process Monitor will tell you more about what Comodo is doing hundreds of times per second during those 35 hours.


So don’t worry about it is the concensous. Fair enough.
But only one other app has even been close, and that was 80% less.

So, why does Comodo have all these page faults (yes i already knew ‘faults’ was a misnomer, and i know what a page fault is) and seemingly very very few other apps do?
Is there something about the hardware/ ram/ config I should be looking at? All my disks are SATA 7500 rpm the cpu is 64bit with 32 bit o/s. I forget the ram bus speed.

Do you think an unmatched stick of ram could be the cause? Then again, why is it only Comodo? There’s plenty of free ram in my system… i think i shall turn off the page faults column lol

Thank you for telling me how to check the firewall defaults.

Anybody have any answer why when all the modules and updating are turned off, Cmdagents still works and hogs cpu for a bit whenever an application like IE or visual studio is launched?

robbie73- If you take a look at just a few seconds of Comodo’s activities as they are accounted for in Sysinternals Process Monitor you will have a much deeper understanding of how incredibly busy Comodo actually is!


I suggest you to read the whole page, so that you would understand what you were arguing about. The bottom line is that page faults reduce application and system performance. Definitely there is a space for some improvements in CIS. Instead of paging out most of the program, what causes trashing, CIS could use more available RAM to store necessary data in fast memory for quick access. Devs could give the users an option to choose between better performance and low memory usage.

[attachment deleted by admin]

+1 this is a problem

after trying desperatly to find out what was hogging resources and causing massive latency comodo comes out as the culprit.

after 120 days since the last post here and comodo obviously ignoring the issue it it looks like im going to have to find a replacement security suite as i didnt buy an i7 rig with 9gb in order to suffer really poor performance.

this is my first major disapointment with comodo and its a biggie :\

also i wont be publicly advising people to use comodo in future, and now im off to edit all my posts relating to that. sighs 120days :\

Comodo: 4 mio
Raxco Perfect Disk Agent: 4,5 mio
Win7 sidebar: 5 mio

All the others have below 1 mio.

Uptime: 10 hours