NOD32 v4 in Win 7 64-bit CPU Use Issue

Discussion in 'ESET NOD32 Antivirus' started by djshack, Oct 20, 2009.

Thread Status:
Not open for further replies.
  1. djshack

    djshack Registered Member

    Joined:
    Oct 20, 2009
    Posts:
    3
    Anyone notice that NOD32 x64 (newest 4.x version) on Windows 7 x64 just about ALWAYS uses ~50% CPU? (The kernel, not the GUI.) I noticed this yesterday, as I've had it running for quite sometime. I've monitored it at MANY different times, and it's always there, regardless of file activity on my computer. I've switched to MSE currently due to significantly lower (i.e. "normal") CPU utilization.

    I don't have anything abnormal going on on my system (a T400). No firewall other than Windows, no other antivirus, etc. And yes, ThreatSense is on, but what good is NOD32 if I can't use that.
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    Check the statistics window if the last scanned file changes or if it basically remains same and the number of scanned files rises quickly. Then you could try excluding that file from scanning. Also you can try setting real-time protection to scan only files with default extensions (ie. files that are know to potentially carry malicious code) instead of all files.
     
  3. djshack

    djshack Registered Member

    Joined:
    Oct 20, 2009
    Posts:
    3
    Thanks for that hint. I found out it was Backblaze online backup that was causing the problem. And, I also found this as a documented issue on the Backblaze website regarding NOD32 (they recommended just excluding the Backblaze ProgramData folder, which is exactly what caused the issue).

    Now, my question is, why is NOD32 the only antivirus app the causes this problem? According to the Backblaze site (http://www.backblaze.com/help-windows.html#nod32), it's the only antivirus program mentioned that rescans a file every time one line is added to it. Is this not a normal antivirus procedure?
     
Thread Status:
Not open for further replies.