Welcome, Guest. Please login or register.
October 13, 2008, 11:59:23 AM

Login with username, password and session length

199894 Posts
22949 Topics
55061 Members

Latest Member: maziyarsm

Search:     Advanced search | Tag Cloud
+  Welcome to the Comodo Forum
|-+  Desktop Security Products
| |-+  Comodo Firewall
| | |-+  Help for v2
| | | |-+  High CPU usage
« previous next »
Pages: 1 [2] Go Down Print
Author Topic: High CPU usage  (Read 10069 times)
archer23
Newbie
*
Offline Offline

Posts: 5


« Reply #15 on: September 21, 2007, 10:38:36 PM »

I noticed there haven't been any posts on this subject for a while, but i appear to be having problems very similar in nature. For the past few nights I've left my pc running peer to peer overnight and woke up to find that it has rebooted its self and is waiting for me to enter my windows password. Even stranger still my modem was still showing signs of high activity even though i wasn't logged into windows.
Have there been any further developments into this issue? I will replace my pc's power supply soon as it is old anyway but i don't feel as if that is the problem.

Commodo F/W Version: 2.4.184.18
OS: Win xp sp2
Logged
Soyabeaner
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 7455



« Reply #16 on: September 22, 2007, 07:10:27 AM »

Currently there are really only two options with CFP:
1) ** FAQs/Threads - Read Me First **:
Quote

2) Beta test CFP v3 or wait for the final
Logged
oyzz
Newbie
*
Offline Offline

Posts: 0


« Reply #17 on: October 01, 2007, 10:39:16 PM »

You can try this one.  I've done lots of testing and monitoring with cmdagent.exe and found that monitor dll injections (MDI) has been the main cause.  If you turn it off for a few days, then turn it back on.  It might solve the issue like it did for me.
Forgive my ignorance but how could I turn off the MDI? I am totally a newbie to this. My cmdagent.exe takes 80-99% of CPU power frequently. That's really killing me.
Logged
Soyabeaner
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 7455



« Reply #18 on: October 01, 2007, 10:50:05 PM »

security
advanced
application behavioral analysis
configure
monitor dll injections

BTW, oyzz, you have 0 posts even though you just created one Huh
Logged
Zito
Comodo's Hero
*****
Offline Offline

Posts: 210


« Reply #19 on: October 02, 2007, 02:52:33 AM »

Running ProcMon and opening http://img186.imageshack.us/my.php?image=comodo0023tb.png in IE6 logged 438,940(!!!) file operations between cmdagent.exe and cpf.exe

Unless you absolutely can't do without it, disable NetBT. This will close ports 137, 138 and 139 (the first two can be seen in your screenshot) and substantially reduce inbound connection attempts. You can do that by right clicking your LAN connection in Network Properties --> Properties --> double click Internet Protocol (TCP/IP) --> Advanced (button) --> WINS (tab) --> checkmark the radio button called "Disable NetBIOS over TCP/IP". Apply/OK in the usual way.
Logged

CoolerMaster Praetorian aluminium case
Enermax Infiniti 720W PSU
AMD Athlon 64 X2 6000+
ASUS Crosshair motherboard
320GB WD Caviar SATA 3.0 HD
320GB Seagate 7200.10 SATA 3.0 HD
2GB Corsair Twin2X2048-6400C4
ASUS DVD-RW 1814BLT
Club3D 8800 GTX
NEC floppy drive
Windows XP Pro SP2
WomenAreMen
Newbie
*
Offline Offline

Posts: 2


« Reply #20 on: October 02, 2007, 05:21:00 AM »

Here are my 2 cents if you don't mind.

CPU shows spikes with following when I close utorrent.exe (BT client version 1.7.5.).
System
cpf.exe
BOX425.exe

comoro firewall pro version 2.4.18.184
I'm on WIN XP pro SP2

Comodo "tests":
  • Changing Monitor DLL injections/ Monitor COM/OLE doesn't change anything.
  • When I close comodo spikes are gone.
  • Starting comodo firewall with utorrent closed brings spikes back again.
  • Turning off all monitors besides network monitor changes nothing.
  • Turning off network monitor gets rid of the CPU spikes with utorrent running or not (!)

For Network Monitor, I have a rule for utorrent:
ALLOW TCP or UDP IN or OUT FROM IP [Any] TO IP [Any] WHERE SOURCE PORT IS [Any]  AND DESTINATION PORT IS (port I set for utorrent). This rule works, as the port is opened when the rule is there, and without the rule, the port is indicated as closed.

First I thought the rules allowed leaks when the programs weren't actually making use of their specific rules, which caused some conflict and caused it to spike up the CPU or something.

Oddly enough, even after removing that utorrent rule, the CPU spikes remained whether utorrent was running or not.

So while I can say with high certainty that my CPU spikes are correlated with the network monitor, I'm not sure what's causing it exactly.
« Last Edit: October 02, 2007, 05:22:32 AM by WomenAreMen » Logged
Alexo
Comodo Family Member
***
Offline Offline

Posts: 62


« Reply #21 on: October 02, 2007, 06:06:03 AM »

Unless you absolutely can't do without it, disable NetBT. This will close ports 137, 138 and 139 (the first two can be seen in your screenshot) and substantially reduce inbound connection attempts. You can do that by right clicking your LAN connection in Network Properties --> Properties --> double click Internet Protocol (TCP/IP) --> Advanced (button) --> WINS (tab) --> checkmark the radio button called "Disable NetBIOS over TCP/IP". Apply/OK in the usual way.
Won't it disable file sharing on hte LAN?
Logged
Little Mac
Global Moderator
Comodo's Hero
*****
Offline Offline

Posts: 6017



« Reply #22 on: October 02, 2007, 11:06:59 AM »

Quote from: WomenAreMen
So while I can say with high certainty that my CPU spikes are correlated with the network monitor, I'm not sure what's causing it exactly.
Try disabling "Do Protocol Analysis" and also "Block Fragmented IP Datagrams" (if enabled); do so one at a time, and reboot after the change.  One of those may help.

Quote from: Alexo
Won't it disable file sharing on hte LAN?
If you're sharing resources across a LAN, you may not be able to disable NetBIOS and some other Windows processes/services.

LM
Logged

date
dcfldd split=2G conv=noerror hashwindow=0 hash=md5 bs=32768 hashlog=/mnt/sda1/images/hash.log if=/dev/hda of=/mnt/sda1/images/LM.dd
date
cat LM.dd.* | md5sum > verify.log
date
Tags:
Pages: 1 [2] Go Up Print 
« previous next »
Jump to:  

SSL Firewall
Page created in 0.148 seconds with 19 queries.
Powered by SMF 1.1.5 | SMF © 2006, Simple Machines LLC
Seo4Smf v0.2 © Webmaster's Talks
Design by 7dana.com