Eset NOD32 Version 4 EAMON.SYS causing BSOD

Discussion in 'ESET NOD32 Antivirus' started by PCRxInc, Jan 22, 2010.

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

    PCRxInc Registered Member

    Joined:
    Jan 22, 2010
    Posts:
    1
    I have three machines that are on a Windows 2003 Domain that are running Windows XP SP3. When listening to music they get a BSOD with the following message: Tech Info:
    ***Stop: 0X00000050
    ***eamon.sys - address A8762616 base at A875E000, Datastamp 4aa9dc2f
    Beginning dump of physical memory
    Physical memory dump complete
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    BSOD can be caused by several things from a bad driver (the case of an older Novell driver or drivers that crash on passing a long path) to a problem in eamon.sys itself. Certain issues potentially resulting in BSOD were fixed in newer builds. Unfortunately, you didn't specify which version you're using so I can only recommend installing the latest release build 4.0.474 or trying 4.2.22 beta on one of the problematic computers.

    Should the problem persist, we'll need to get a kernel or complete memory dump generated when BSOD occurs. Please find instructions for configuring generation of memory dumps here.
     
  3. Juansa

    Juansa Registered Member

    Joined:
    Jan 29, 2010
    Posts:
    1
    Hi everybody,
    Here happens too.
    Esset 4.0.474.0 in Windows Server 2008 Enterprise SP2.
    I have many dumps recollected if you want.
    With Windbg I trying know what is the cause and I thing it's eamon.sys.
    "Probably caused by : hardware ( eamon+5e0d )"


    Juansa
    Spain
     
  4. Rmuffler

    Rmuffler Former Eset Moderator

    Joined:
    Jun 26, 2008
    Posts:
    995
    Location:
    San Diego, CA USA
    Hello Juansa,

    Our team would like to take a look at the memory dumps. Please contact your local support team to submit them. Include as much information as possible. For Spain, you can reach our support team at the following:

    Email: ayuda@eset.es
    Tel: +34 902.33.48.33

    Thank you,
    Richard
     
  5. chvss

    chvss Registered Member

    Joined:
    Jan 28, 2010
    Posts:
    8
    I have just spent all morning working with Microsoft because both of my Citrix servers were down after their nightly reboot.

    Turns out it was ehdrv.sys - an ESET file.

    I now need to find out which of my other 30 servers are going to have the same problem.

    Very unhappy.
     
  6. Rmuffler

    Rmuffler Former Eset Moderator

    Joined:
    Jun 26, 2008
    Posts:
    995
    Location:
    San Diego, CA USA
    Hello chvss,

    Please contact our support engineers with a memory dump. The contact information for our U.S. office is below.

    Toll Free. +1 (866) 343-ESET [3738]
    Tel. +1 (619) 876-5400

    Thank you,
    Richard
     
  7. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    thanx Marcos,

    Your posting saved me today :D .
    I saw the same problem as described. A client computer (Win XPpro SP3) was still using Novell Client32 v4.9 SP2.
    I updated the client to 4.91 SP5 and executed redrtest.
    After installation (& reboot of coarse) the problem was fixed..

    Greetings from a sunny holland

    Alexander
     
  8. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    The issue with older Novell clients often resulting in BSOD is known, it's a bug that was fixed in the latest client build 4.91.
     
Thread Status:
Not open for further replies.