Startup scan and Regular Scan stuck at "Target: Operating Memory"

Discussion in 'ESET NOD32 Antivirus' started by sunny1943, Aug 11, 2010.

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

    sunny1943 Registered Member

    Joined:
    Aug 11, 2010
    Posts:
    1
    I am currently running the latest NOD32 AV on Win 7 64 bit. Haven't had any problems since updating to the latest verison in July.

    No new software insatllation but today started noticing that on startup, the ekrn.exe is constantly at 25% cpu and in checking the settings etc, realized that startup scan was running at stuck at 0% wtih "Target: Operating Memory" in the on-demand computer scan settings area.

    Attempted to Pause or Stop just leave the buttons greyed out.

    So I went into scheduler to disable start up scan and on reboot, no cpu % spike, but on going into the settings and brining up the comptuer scan settings, the on-demand comptur scanner started again and the same problem recurred with the computer scan being stuck again at "Opearting Memory"

    No ongoing memory problems, did a memory intergrity check and did not show any problems.
    settings and turned
    Hope someone will be able to help me- this has been driving me nuts the whole day!

    Update: I went into the on-demand scanner settings.. threatsense parameter setup and turned "operating memory" option off and the scan is now proceeding- but I suppose that is not a good idea to leave it off unchecked?
     
    Last edited: Aug 11, 2010
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    Does disabling Anti-Stealth and restarting the computer make a difference?
     
  3. Alexei Malinovski

    Alexei Malinovski Registered Member

    Joined:
    Aug 11, 2010
    Posts:
    3
  4. Tumi

    Tumi Registered Member

    Joined:
    Aug 11, 2010
    Posts:
    6
    I'm having the same issue on my Win7 x64 as described by original poster.
    Don't mean to hijack this thread just want to report that turning off "Anti-Stealth" works for me and scanning memory now completes successfully. Hoping to see a "fix". ;)
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    Could somebody create a complete memory dump from the problematic state per the instructions here, compress it, upload it somewhere and PM me the link? Should you need access to an ftp server, let me know. Does anybody have this problem with other than Win7 x64 systems?
     
  6. Nicolus

    Nicolus Registered Member

    Joined:
    Apr 26, 2010
    Posts:
    8
    Again same problem on a Windows 2008 Server 64 bits.
    Both servers are production servers so I can't generate a memory dump...
    It seems that the problem occurs only on 64 bits systems ?

    Marcos, You can contact me by MP if you want I make some tests or if you want more informations.

    Regards
     
  7. angrydog

    angrydog Registered Member

    Joined:
    Aug 11, 2010
    Posts:
    3
    My post from the other thread, also I am running Windows Server '08 R2.

    Link to other thread: https://www.wilderssecurity.com/showthread.php?p=1727666
     
  8. devman

    devman Registered Member

    Joined:
    Aug 11, 2010
    Posts:
    1
    Today, I started to have the same issue on my Win7 x64 workstation. I can't experiment with system crash to generate a memory dump. I find two workabouts as yet to successfully escape this problem:

    • Disabling Anti-Stealth technology
    • Or deselect Operating memory in ThreatSense settings
    Marcos, you can contact me for more information.
     
  9. sloana

    sloana Registered Member

    Joined:
    Aug 11, 2010
    Posts:
    2
    Have the same problem with me. Also, with the long startup scan.


    Windows 7 64 bit Ultimate Edition EN
    4.2.40.0 / 5358 (20100811)
     
  10. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    As of now, we'll keep discussion about this issue in one thread here.
     
Thread Status:
Not open for further replies.