cmdagent.exe causing problems

Since upgrading to 509 I’ve been getting occasional crashes caused by cmdagent. A second clean install hasn’t helped. Five days ago I mailed a crash dump to cpfbugs at but haven’t heard back. This is the latest from Event Viewer:

[b]Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 5/30/2009
Time: 4:51:32 AM
User: N/A
Computer: 6V8D
Faulting application cmdagent.exe, version 3.9.15467.508, faulting module mem.cav, version 3.9.11087.504, fault address 0x00002640.

For more information, see Help and Support Center at Microsoft Support.
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 63 6d 64 ure cmd
0018: 61 67 65 6e 74 2e 65 78 agent.ex
0020: 65 20 33 2e 39 2e 31 35 e 3.9.15
0028: 34 36 37 2e 35 30 38 20 467.508
0030: 69 6e 20 6d 65 6d 2e 63 in mem.c
0038: 61 76 20 33 2e 39 2e 31 av 3.9.1
0040: 31 30 38 37 2e 35 30 34 1087.504
0048: 20 61 74 20 6f 66 66 73 at offs
0050: 65 74 20 30 30 30 30 32 et 00002
0058: 36 34 30 640 [/b]

Version 3.9.15467.508 and 3.9.11087.504? Is that normal for a module number? CIS says it is version 3.9.95478.509.

The crashes can happen at almost anytime, uninstalling a program with Revo, scanning with CAV, or even just surfing. The strange part is I had no problem whatsoever with RC1 or RC2.

Any help will be appreciated.

XP SP3, CIS in Stateful, Safe, Safe, Proactive Security Modes, no other real-time security programs.

Exact same details to every byte on me too, running Win XP Corporate SP3 build 2600 with all updates.
Recent drivers, no faults in device control or anything.

Third time this happens to me, every time it seems to be related to scheduled scans for me.
I dont run manual scans nor does it happen everytime on scheduled so i dont know if its the
fact its scheduled or not when it happens.

Last time i was playing Call of Duty 4 whilst having only daemontools, creative soundcard tray tool, nvidia tray tool and mozilla firefox 3.0 running in the background. Scheduled scan started, played for awhile then suddenly
some 30minutes into the scan the computer locks up on blacks screen the game still running judging from the
sounds of online match but unable to do anything. Some 15minutes after i was able to get to desktop (ctrl+alt+del, break or the likes had zero effect) by crashing explorer (hit winamp hotkey on keyboard until it crashed :slight_smile: )

Attempted to open any program just caused the computer to hang once again, scan showed being locked
at 90k+ scanned files.

It happens to me also when a scheduled scan is run, except scan doesn’t run - I get a popup with info as follows:

Application popup: cmdagent.exe - Application Error : The instruction at “0x02002640” referenced memory at “0x07644ec7”. The memory could not be “read”.

i click ok. message box closes, then when i click x button to try and close scan window, get an error message saying something along the lines of: You don’t have permissions to close this, with a red exclamtion mark. I click ok, then can close scan window.

This needs to be looked into.

Thanks, dev00790.

Jahn could you submit the minidump here in this topic: Comodo Forum ?

Usually you won’t get feedback when submitting a bug. Just trust it is picked up and prioritised. Not all bugs are easy to solve. So these things take time.

Thank you, I will do that. :slight_smile:

For comparison, here’s my error report:

cmdagent.exe application error

The instruction at “0x021b2640” referernced memory at “0x078b4b76”. The memory could not be “read”. Check OK to terminate the program.

end snip

Hope this helps. Looks like the same instruction reference…


Carls. Please make sure your memory is not faulty. Download Microsoft Windiag and let it run as instructed. Let it make at least ten round in the default test settings. When an error occurs your memory is faulty. Please undo all overclocks before testing.

All done (there went two weekends…). Memory checked perfectly, so I tried the same setup on a second box. Finally got the same lockup, after many tries. It appears to be related to:

  1. using a non-admin signon user (i.e.,no software installs allowed); 2) only at startup when there may be a competitive program starting up too (possible guilty parties: PCTools Spyware Dr. and/or Secunia PSI). This 2) is pretty speculative since the lockup is not repeatable.

Why bother reporting this at all? Because it occurred on two separate XP and Vista boxes, which although the problem is not consistently repeatable, indicates to me that something’s amiss. Maybe someone with some free weekend time willing to do a series of cold starts with the same initial conditions?