AMON unable to load - HELP!

Discussion in 'NOD32 version 2 Forum' started by hrafn, Aug 19, 2007.

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

    hrafn Registered Member

    Joined:
    Aug 19, 2007
    Posts:
    2
    I have been running NOD32 2.7 successfully for the past 2 months. After installing the most recent WinXP security updates, I experienced a hang on reboot, which caused me to force the shut down by powering off; the system did a chkdsk on boot. Before the system was fully up, it did a BSOD. On reboot AMON was unable to load. I have included the most recent log entries below. I rebooted a couple of times with the same result. Can anyone help me out here?

    Time Module Event User
    8/19/2007 13:31:20 PM Kernel Error initializing file submission system (Used to send suspicious files for analysis)
    8/19/2007 13:31:20 PM AMON Unable to load file system monitor.
    8/19/2007 13:31:20 PM Kernel Virus Scanner could not be initialized. NOD32 System modules may not function properly.
    8/19/2007 13:24:39 PM AMON Unable to load file system monitor. ASGARD\rbc
    8/19/2007 13:24:38 PM AMON Unable to load file system monitor. ASGARD\rbc
    8/19/2007 13:24:38 PM AMON Unable to load file system monitor. ASGARD\rbc
    8/19/2007 13:24:36 PM AMON Unable to load file system monitor. ASGARD\rbc
    8/19/2007 13:24:35 PM AMON Unable to load file system monitor. ASGARD\rbc
    8/19/2007 13:22:57 PM AMON Unable to load file system monitor. ASGARD\rbc
    8/19/2007 13:22:39 PM AMON Unable to load file system monitor. ASGARD\rbc
    8/19/2007 13:20:07 PM Kernel Error initializing file submission system (Used to send suspicious files for analysis)
    8/19/2007 13:20:07 PM AMON Unable to load file system monitor.
    8/19/2007 13:20:07 PM Kernel Virus Scanner could not be initialized. NOD32 System modules may not function properly.
    8/19/2007 13:14:48 PM Kernel Error initializing file submission system (Used to send suspicious files for analysis)
    8/19/2007 13:14:48 PM AMON Unable to load file system monitor.
    8/19/2007 13:14:48 PM Kernel Virus Scanner could not be initialized. NOD32 System modules may not function properly.
    8/19/2007 13:11:17 PM Kernel The virus signature database has been successfully updated to version 2470 (20070819).
    8/17/2007 20:10:23 PM Kernel The virus signature database has been successfully updated to version 2469 (2007081:cool:.
     
  2. ASpace

    ASpace Guest

    Hi ! Try to reinstall NOD32:

    1) Download the latest fresh version of NOD32 v 2.7 for your operating system
    Trial version or Full paid version

    2) Open Control Panel-> Add/Remove programs and Uninstall NOD32

    3) Reboot when prompt

    4) After restart , go to C:\Program files and manually delete the folder ESET

    5) Install NOD32 from the file you downloaded in step 1
    Use "Typical" install

    6) Make sure you have stable internet connection and NOD32 (nod32krn.exe) is allowed to go through your firewall. Then Update NOD32 !
     
  3. hrafn

    hrafn Registered Member

    Joined:
    Aug 19, 2007
    Posts:
    2
    Thanks for the reply. I went through another couple of reboots upon which everything loaded properly following a new virus signature update. I am not sure exactly what that means, but everything appears to be working properly.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.