Cannot restart AMON

Discussion in 'NOD32 version 2 Forum' started by blinky, Jun 11, 2005.

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

    blinky Registered Member

    Joined:
    Jun 11, 2005
    Posts:
    6
    Strange, I don't remember having this problem prior to 2.5.

    If I stop AMON (I have allowed manual disabling). I cannot restart the service. When I reboot it loads up fine.

    The error box and log says the following

    Time Module Event
    11/06/2005 21:17:14 AMON Unable to load file system monitor.

    -------------------------------------------

    NOD32 antivirus system information
    Virus signature database version: 1.1136 (20050611)
    Dated: 11 June 2005
    Virus signature database build: 5740

    Information on other scanner support parts
    Advanced heuristics module version: 1.015 (20050602)
    Advanced heuristics module build: 1083
    Internet filter version: 1.002 (2004070:cool:
    Internet filter build: 1013
    Archive support module version: 1.030 (20050419)
    Archive support module build version: 1117

    Information about installed components
    NOD32 for Windows NT/2000/XP/2003 - EMON
    Version: 2.0.0
    NOD32 For Windows NT/2000/XP/2003 - Base
    Version: 2.50.16
    NOD32 For Windows NT/2000/XP/2003 - Internet support
    Version: 2.50.16
    NOD32 for Windows NT/2000/XP/2003 - Standard component
    Version: 2.50.16

    Operating system information
    Platform: Windows XP
    Version: 5.1.2600 Service Pack 2
    Version of common control components: 5.82.2900
    RAM: 1024 MB
    Processor: AMD Athlon(tm) 64 Processor 3000+ (2385 MHz)
     
  2. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Hi Blinky, welcome to Wilders.

    Can you please download a FRESH copy of Nod32 from www.nod32.com

    Uninstall your current version.

    Remove the Eset Folder from C Drive> Program Files.

    Install the FRESH copy of Nod32 that you downloaded above.

    Let us know how you go…

    Cheers :D
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Have you carefully read the warning message shown before you unloaded AMON's driver?
     

    Attached Files:

    • amon.PNG
      amon.PNG
      File size:
      14.6 KB
      Views:
      2,648
  4. BigT

    BigT Registered Member

    Joined:
    Jul 30, 2005
    Posts:
    14
    It seems like stopping AMON is not a very good idea. I've noticed the following:
    1. It doesn't always restart properly w/o a reboot.
    2. It doesn't always stop properly; sometimes it hard locks the machine while trying to stop, necessitating a hard reset.
    ...
     
  5. rumpstah

    rumpstah Registered Member

    Joined:
    Mar 19, 2003
    Posts:
    486
    Hi BigT:

    This would also be dependent on which types of security applications are running at the time.

    I have stopped and restarted AMON thousands of times on different types of machines w/o a reboot (since the release of 2.50.25 and before).

     
  6. BigT

    BigT Registered Member

    Joined:
    Jul 30, 2005
    Posts:
    14
    Hi Rumpstah,
    Has stopping AMON ever hung your machine before?
    I've stopped using this feature because a couple of times this has caused my system to lock up. Although mouse and keyboard input still work, requests to restart or turn off the machine are ignored and killing the NOD32 processes doesn't help. Eventually, Task Manager stops working and a hard reset is the only way to restart the system.

    This is on a fresh install of WinXP SP2 with only video card (Ati) and sound card (nForce) tray icons/software running in the background in addition to NOD32.
     
  7. rumpstah

    rumpstah Registered Member

    Joined:
    Mar 19, 2003
    Posts:
    486
    Hi BigT:

    I have around 9 test machines all of differing hardware (Pentium to AMD x64; Intel boards, ASUS, Abit and Gigabyte to name a few) and when testing malware I disable AMON in many cases to see how well it is cleaned from a particular system.

    In my particular testing environment I have not experienced any hard locks disabling (disabling or unloading) any NOD32 modules (AMON, DMON, IMON).

     
Thread Status:
Not open for further replies.