ESS 5b with prolonged 100% CPU

Discussion in 'ESET NOD32 Antivirus/Smart Security Beta' started by osip, May 30, 2011.

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

    osip Registered Member

    Joined:
    Oct 25, 2006
    Posts:
    610
    ESS beta on my desktop test system runs with 100 % cpu during very long time, almost constantly. Slows down my pc so it's almost unusable. Funny, I didn't experienced this at the beginning, only last 4-5 days. In this very moment my cpu is on 100% more than 40 minutes. Endless startup scan's.
    Win 7ultx32SP1, keyscrambler pro, winpatrol, admuncher.
    CPU.png
     
  2. osip

    osip Registered Member

    Joined:
    Oct 25, 2006
    Posts:
    610
    Discovered that taskeng.exe was blocked in HIPS rules. Is this by default or have I blocked by mistake when temp opening the interactive mode ? Could this be a reason for endless startup scan with 100% CPU ? Discovered it when my startup scan had been running 30 minutes, allowed and restarted the pc before scan finished. Seems OK for now, will see .
    taskeng.png


    Oh, no, when typing this ESS updated and now I'm at 100% CPU again with a new startup scan. How do I stop the startup scan ? It runs forever !

    added: this time the startup scan took about 5 min at 100% CPU. An improvement comparing to above.

    added again: damn it, seems as I found the reason of my CPU problem by myself, taskeng.exe was blocked in HIPS rules.30 min now with normal values.
     
    Last edited: May 31, 2011
  3. toxinon12345

    toxinon12345 Registered Member

    Joined:
    Sep 8, 2010
    Posts:
    1,200
    Location:
    Managua, Nicaragua
    deleting all rules in the list, and then changing the filtering mode to automatic does makes any difference? o_O o_O
     
  4. osip

    osip Registered Member

    Joined:
    Oct 25, 2006
    Posts:
    610
    I was temp testing the interactive mode and believe that I blocked taskeng by mistake, changed shortly after back to aut filtering mode. After this my CPU problems started. I'm now in automatic mode but changed the rule (didn't delete it) to allow with notification.
     
Thread Status:
Not open for further replies.