"NOD could not open...unable to access the kernel" What did that mean?

Discussion in 'ESET NOD32 Antivirus' started by Supersnake, Jul 21, 2008.

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

    Supersnake Registered Member

    Joined:
    Jul 12, 2003
    Posts:
    121
    When I restarted my computer a small window displayed saying that "NOD had some kind of trouble..unable to access the kernel" , and after the restart I saw that the NOD icon was not appearing in the system tray. Note that I didn't get any red shield from Windows Security indicating that I had no anti-virus program running.

    I then manually launched NOD from the Programs Files folder and NOD launched just fine. I immediately did another restart and NOD self loaded just fine. Any idea what happened? Perhaps this was merely a coincidence but right before the restart I installed Diskeeper 7 and had it defrag my drive - and no I don't want to hear that the defrag was responsible unless you really are sure you know what you are saying because I did not defrag the paging file, master filing table or boot sectors o_O

    Thanks.

    NOD-AV 3.0.667
    Vista Ultimate
     
    Last edited: Jul 21, 2008
  2. BFG

    BFG Registered Member

    Joined:
    Oct 27, 2004
    Posts:
    482
    Location:
    San Diego
    Hello,

    Does the Vista Event Viewer say anything about NOD32 at that time?

    Thank you,
    BFG
     
  3. Supersnake

    Supersnake Registered Member

    Joined:
    Jul 12, 2003
    Posts:
    121
    1 Application Event and 2 System Events only and none of the descriptions have the string "NOD" or "ESET" in them. I guess I will just have to write it off as an isolated incident unless it reoccurs.
    Thanks,
    Supersnake

    Application
    Source WMI
    Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.


    System
    Source Http
    Event 15016
    Unable to initialize the security package Kerberos for server side authentication. The data field contains the error number. [I let Windows look this one up in the Event Help site and it told me I could ignore this problem]

    Event 1108
    The event logging service encountered an error while processing an incoming event published from Microsoft-Windows-Security-Auditing.
     
    Last edited: Jul 22, 2008
Thread Status:
Not open for further replies.