1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Event viewer errors

Discussion in 'Windows XP' started by coolwaters, 2005/08/15.

  1. 2005/08/15
    coolwaters

    coolwaters Inactive Thread Starter

    Joined:
    2004/04/01
    Messages:
    106
    Likes Received:
    0
    whilst checking my event viewer I came across this

    Event Type: Warning
    Event Source: avast!
    Event Category: Client
    Event ID: 90
    Date: 13/08/2005
    Time: 23:10:14
    User: N/A
    Computer:
    Description:
    AAVM - scanning warning: x_AavmCheckFileDirectEx [UNI]: C:\WINDOWS\SYSTEM32\DRIVERS\TCPIP.SYS (C:\WINDOWS\SYSTEM32\DRIVERS\TCPIP.SYS) returning error, 00000005.


    Event Type: Error
    Event Source: avast!
    Event Category: Client
    Event ID: 90
    Date: 13/08/2005
    Time: 23:10:14
    User: N/A
    Computer: me
    Description:
    AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of C:\WINDOWS\SYSTEM32\DRIVERS\TCPIP.SYS failed, 00000005.

    plus an
    application error:
    Event Type: Warning
    Event Source: Userenv
    Event Category: None
    Event ID: 1517
    Date: 15/08/2005
    Time: 07:40:26
    User: NT AUTHORITY\SYSTEM
    Computer: me
    Description:
    Windows saved user registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.

    This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Any idea how I can sort this out?
     
  2. 2005/08/15
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Since the top two warnings were both generated by Avast! I'd suggest asking on their Support Forum.

    The last one usually happens if an application you install loads a new service and uses your logged on account to start the service. I treat these as non-happenings on any systems I support since there is no harm done and the reboot does clear things out. However, if it worries you, you can probably locate the offending piece.

    Start->run->services.msc and when the widow opens look at the right-most column where it says what logon the service is using. Your problem child will be one that is not using Local System or Network Service.

    Any of those you find can be changed. Right-click the service name, left-click properties, click the log on tab. Try changing it first to Local System and if that doesn't work, next try Network Service. You can look at some of the existing ones to see exactly how to do these.
     
    Newt,
    #2

  3. to hide this advert.

  4. 2005/08/16
    coolwaters

    coolwaters Inactive Thread Starter

    Joined:
    2004/04/01
    Messages:
    106
    Likes Received:
    0
    re

    thankyou :)
     

Share This Page

  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.