full scan hangs on uninfected files - can't stop it.

Hi, my freshly instaled and updated Comodo Internet Security suite, free version, hangs when a full Pc scan.
Moreover, it don’t stop, nor from the tray icon, only solution is to reboot the PC. This happened on TWO different and isolated PC’s at home.
iS THIS A BUG?
iS There a solution?

Thanks.

Yeah, the same happened to me. I posted a few weeks ago and never got any response. Yesterday I uninstalled Comodo and moved on to another.

At one time if you had DEP turned on for all programs it was necessary to exclude COMODO otherwise hangs during a system scan were likely. I haven’t tried removing the exclusion to see if a system scan now completes.

No one seems to know how to resolve this issue.
Dennis

This tends to be the GUI (cfp.exe) not being able to keep up with the scan.

So its still scanning but it cant keep up and looks like it hangs.

Mine ran all nite and never finished scanning, stayed stuck on the same file. :-TD
Dennis

Ok thats a bug.

Do you have DEP turned on for all applications?

The only one I have checked is Comodo.

Hi hakunamatata

Please read here:

https://forums.comodo.com/anti_virus_bugs/please_dont_post_cis_310_bugs_he_read_this_first-t42119.0.html

Cheers,
Josh

If you run vista, check whether you have a “users\youraccountname\appdata\local\virtualstore\program files\comodo.…” directory. If so remove (rename) it. Please report any result.

The most important thing to check here is the following, if it seems to never end scanning please check if the process cmdagent.exe is still running, if not it will never end because the engine crashed.

If that’s the case you should have an entry in the windows event log showing cmdagent crashed.
Can you post that message here ?

I have had this problem my self on a friends PC, and the only sollution was to crash cmdagent manualy.

It was stuck at 100% CPU usage.

Can you try this on cmdagent when it’s normally running, i can be that you have to change a few protection settings, after that try to dump cmdagent.exe if it’s stuck at 100% CPU.

Maybe the dump can show what’s going on.

Hi guys…

I have run 2 full scans in the last 24 hours - both hung.

Last nights scan hung on a dll (sorry, but I dont remember which one). Today I arced up a scan while I was out. When I returned home 3 hours later, it had hung at sys32/driver store/file repository/ component.man.

FYI :slight_smile:

PS - CPU usage at both hangs was zero.

(Vista Home Premium 32 bit, HP DV6, 4GB)

A scheduled scan just started here but only lasted 8 minutes before hanging. :frowning:

Screenies attached.

[attachment deleted by admin]

Looks like it runs in to a memory leak on your system while scanning certain files.
Can you try to run Cavscan (right mouse click scan) on let’s say \Program Files and see if that finishes normal.

One other thing, can you also check the windows eventlog to see if there is a record of cmdagent and/or cfp crashing, and post the error message here ?

I don’t think the last displayed “scanned file” is to blame, the scanner dies before the GUI get’s updated probably. By scanning folder by folder you can try to determine which one drives CIS nuts.

One other thing to watch is CPU and Memory usage during the scan, you can use Sysinternals Process Explorer for this (Process Explorer - Sysinternals | Microsoft Learn).

So, is there a fix? I dumped Bit Defender because it wouldn’t scan, now this one is doing the same thing. Only good thing is this one is free.’

Hiya Ronny…

  1. Have run a manual scan on /Program Files. The scan ran perfectly, with no errors :slight_smile:

  2. I have checked the event log and have found errors relating to both the scheduled scan (above) and the other scan I mentioned on page one of this thread.

The first scan:

Log Name: Application Source: Application Error Date: 24/07/2009 12:34:12 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: PC07 Description: Faulting application cmdagent.exe, version 3.10.36658.530, time stamp 0x4a4e117d, faulting module framework.dll, version 3.10.36265.529, time stamp 0x4a4c3d1c, exception code 0xc0000006, fault offset 0x00014828, process id 0x428, application start time 0x01ca0bf5e9f82b96. Event Xml: 1000 2 100 0x80000000000000 9896 Application PC07 cmdagent.exe 3.10.36658.530 4a4e117d framework.dll 3.10.36265.529 4a4c3d1c c0000006 00014828 428 01ca0bf5e9f82b96

The second scheduled scan:

Log Name: Application Source: Application Error Date: 26/07/2009 12:03:50 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: PC07 Description: Faulting application cmdagent.exe, version 3.10.36658.530, time stamp 0x4a4e117d, faulting module framework.dll, version 3.10.36265.529, time stamp 0x4a4c3d1c, exception code 0xc0000006, fault offset 0x00014828, process id 0x450, application start time 0x01ca0d2c992636a6. Event Xml: 1000 2 100 0x80000000000000 10406 Application PC07 cmdagent.exe 3.10.36658.530 4a4e117d framework.dll 3.10.36265.529 4a4c3d1c c0000006 00014828 450 01ca0d2c992636a6
  1. I will manually scan some other folders and report back - and I will keep an eye on memory / CPU usage as well, although during these two scans previously mentioned, CPU usage seemed fine.

Cheers for now.

:slight_smile:

Here we go. A few minutes into a manual scan of /Windows folder, CAV has hung.

From Event Viewer:

Log Name: Application Source: Application Error Date: 26/07/2009 5:41:02 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: PC07 Description: Faulting application cavscan.exe, version 3.10.36658.530, time stamp 0x4a4e110d, faulting module framework.dll, version 3.10.36265.529, time stamp 0x4a4c3d1c, exception code 0xc0000006, fault offset 0x00014828, process id 0x17b4, application start time 0x01ca0dc3f8ebeb39. Event Xml: 1000 2 100 0x80000000000000 10481 Application PC07 cavscan.exe 3.10.36658.530 4a4e110d framework.dll 3.10.36265.529 4a4c3d1c c0000006 00014828 17b4 01ca0dc3f8ebeb39

EDIT - removed incorrect info and second screenie;)

Will scan /Windows again, just to be sure :wink:

[attachment deleted by admin]