Windows Vista 32-Bit BSOD

Discussion in 'ESET NOD32 Antivirus' started by TechNoob, Jul 29, 2010.

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

    TechNoob Registered Member

    Joined:
    Jul 29, 2010
    Posts:
    5
    I recently reformatted my PC and got BSOD (DRIVER_IRQL_NOT_LESS_OR_EQUAL) during restart/shut down after Windows Update. According to the Minidump, the cause of this was the driver eamonm.sys (ESET NOD32 Antivirus).

    The 2nd time, I got another BSOD... it occured during installation restart/shutdown process (after Windows Update for Service Pack 1). Posted the minidump on the tech forum and said it might have a connection to NOD32.

    Any help would be appreciated. THANKS!
     
  2. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    What is your installed build ? What other security software do you have installed, if any | your Windows Operating System Build is ? |

    You may manually uninstall you current build. If you do so, you may export your current settings and re-import them later.

    Running older builds regardless of O/S is the primary cause of the eamon.sys issue which is remedied in the current build.
     
  3. TechNoob

    TechNoob Registered Member

    Joined:
    Jul 29, 2010
    Posts:
    5
    It's the Windows Vista Home edition.

    The only other security software I have on is Malwarebytes' Anti-malware 1.46

    ESET NOD32 Antivirus 4.2.58.3 is what I have installed.
     
  4. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    You indicated you had posted your minidump elsewhere, please post it here for analysis by ESET I strongly suspect it is another issue as you have recently re-installed your system.
     
  5. TechNoob

    TechNoob Registered Member

    Joined:
    Jul 29, 2010
    Posts:
    5
    It is in BMP, how do i convert it to a (gif, jpg, log, png, txt)?
     
  6. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Assuming the bitmap file points to eamon.sys being the primary issue, please post it for us to peruse.

    You may contact ESET, ask a Tech Representative to help you generate a new minidump file.

    Have you configured NOD32 to notifying me about Windows updates
    If so, disable this feature.

     
    Last edited: Jul 29, 2010
  7. jeramy_t

    jeramy_t Registered Member

    Joined:
    Aug 12, 2009
    Posts:
    22
  8. TechNoob

    TechNoob Registered Member

    Joined:
    Jul 29, 2010
    Posts:
    5
    Thanks guys, I got it resolved by using 4.2.62.0 instead of 4.2.58.0
     
  9. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Most welcome for the help, although last time I looked, there was no 4.2.62.0 build ? Did you download this build from the ESET Download Center

     
  10. TechNoob

    TechNoob Registered Member

    Joined:
    Jul 29, 2010
    Posts:
    5
    Got it from Marco via PMs
     
  11. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    If this is the case, I have requested a copy for evaluation purposes. If the BSOD issue was remedied with this build this is a result you would have wanted.

    Regards,

     
  12. rgo

    rgo Registered Member

    Joined:
    Jul 25, 2010
    Posts:
    3
  13. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    A recent update of the virus signature database to 5338 resolved a similar issue with Microsoft Windows 7, so the fix included in it may work for Windows Vista as well. This update is automatically downloaded by ESET's software, so there is nothing you need to do to obtain the fix.

    Regards,

    Aryeh Goretsky
     
  14. xMarkx

    xMarkx Registered Member

    Joined:
    Dec 1, 2008
    Posts:
    447
    Hello,

    Update 5338 did not resolve the issue for me on Windows Vista SP2 (32-bit) with ESET NOD32 Antivirus 4.2.58.3 as I still got the BSOD. I had to do a system restore and then install the update again with ESET disabled. Do you know if today's updates (August 10 patch Tuesday) with ESET enabled are going to result in a stop error (any reports of this happening)?

    Thanks,

    Mark
     
  15. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Those having problems with BSOD after Windows update, please post here the information about installed modules (Help -> About). If possible, compress the memory dump created during BSOD, upload it somewhere and PM me the link. Some people confirmed that installing the not-yet-released version 4.2.6x eventually resolved the problem even though it was supposed to have been fixed with the real-time protection module build 1004.
     
    Last edited: Aug 11, 2010
  16. e36

    e36 Registered Member

    Joined:
    Apr 13, 2004
    Posts:
    80
    Here's my info on a NOD32 AV 4.2.58.3 and WU blue-screened PC:

    Vista Home Premium SP2 32-bit (all updates)

    Virus signature database: 5356 (20100810)
    Update module: 1031 (20091029)
    Antivirus and antispyware scanner module: 1284 (20100729)
    Advanced heuristics module: 1110 (2010080:cool:
    Archive support module: 1119 (20100806)
    Cleaner module: 1048 (20091123)
    Anti-Stealth support module: 1020 (20100713)
    SysInspector module: 1216 (20100517)
    Self-defense support module : 1016 (20100404)
    Real-time file system protection module: 1004 (20100727)
     
    Last edited: Aug 11, 2010
  17. pondlife152

    pondlife152 Registered Member

    Joined:
    Apr 23, 2008
    Posts:
    105
    Location:
    UK
    Here's my info

    Windows Vista Home Premium 32bit with SP2
    NOD32 V4.2.53.3

    Virus signature database: 5358 (20100811)
    Update module: 1031 (20091029)
    Antivirus and antispyware scanner module: 1284 (20100729)
    Advanced heuristics module: 1110 (2010080:cool:
    Archive support module: 1119 (20100806)
    Cleaner module: 1048 (20091123)
    Anti-Stealth support module: 1020 (20100713)
    SysInspector module: 1216 (20100517)
    Self-defense support module : 1016 (20100404)
    Real-time file system protection module: 1004 (20100727)

    For some reason I've got no data on this latest crash. No minidump file.
     
    Last edited: Aug 11, 2010
  18. xMarkx

    xMarkx Registered Member

    Joined:
    Dec 1, 2008
    Posts:
    447
    Wasn't it supposed to be fixed with virus signature database update 5338?
     
  19. 1Jnodder

    1Jnodder Registered Member

    Joined:
    Apr 8, 2009
    Posts:
    28
    Here's my info.
    NOD32 version 4.2.58.3
    Windows Vista Home Premium (32-bit)
    Version 6.0.6002 Service Pack 2

    Virus signature database: 5359 (20100811)
    Update module: 1031 (20091029)
    Antivirus and antispyware scanner module: 1284 (20100729)
    Advanced heuristics module: 1110 (2010080:cool:
    Archive support module: 1120 (20100811)
    Cleaner module: 1048 (20091123)
    Anti-Stealth support module: 1021 (20100811)
    SysInspector module: 1216 (20100517)
    Self-defense support module : 1016 (20100404)
    Real-time file system protection module: 1004 (20100727)

    I don't know how find the other info you asked for: the memory dump created during BSOD
     
    Last edited: Aug 12, 2010
  20. pondlife152

    pondlife152 Registered Member

    Joined:
    Apr 23, 2008
    Posts:
    105
    Location:
    UK
    Look in the C:\Windows\Minidump folder for a Minidump (*.dmp) file with the same date as the crash.

    However, for some reason I do not have one for Tuesday's crash. Not sure why.
     
  21. 1Jnodder

    1Jnodder Registered Member

    Joined:
    Apr 8, 2009
    Posts:
    28
    I looked in my minidump folder and nothing in there for 8-10.
     
  22. de Silentio

    de Silentio Registered Member

    Joined:
    Jun 30, 2010
    Posts:
    12
    I had this problem on all of my Vista SP2 computers (stupid me for not testing the windows updates first).

    I did figure out a fix for it.

    Simply boot with a Vista or XP DVD, get into Command Prompt, delete the eamonm.sys file from C:\windows\system32\drivers and reboot. This will break ESET, but the updates will finish without a problem.

    Shame on Eset for having these problems, by the way.
     
  23. xMarkx

    xMarkx Registered Member

    Joined:
    Dec 1, 2008
    Posts:
    447
    Hello,

    Instead of deleting eamonm.sys and breaking ESET, you can just temporarily disable ESET in Settings before installing windows updates. Have you tried the new build with any windows updates yet (on Vista SP2)?

    Regards,

    Mark
     
  24. de Silentio

    de Silentio Registered Member

    Joined:
    Jun 30, 2010
    Posts:
    12
    I had a Vista SP2 machine break at around 1:00 p.m. today, Nod32 was up to date, but I'm not sure what build it was.

    The problem I had was that the windows updates were pushed through WSUS to all of my Vista SP2 machines that were in use (all the principles, secrataries and administrative personel... Good thing school's not in session yet) so I could not disable Eset (since the windows update had already been applied).

    In my previous post I presented a fix for windows updates that have already been applied and computers that are in an endless "update loop". I didn't find a solution like this on the net (although there may be one), so I thought I would let people know.

    Thanks for the suggestion to disable Nod32, but I have a rather large network of Vista Sp2 machines that get updated at random times (especially in the summer), so disabling Nod32 is not feasible.

    Regards.

    P.S. Sorry if I sound standoffish, that's not my intention. :) I always enjoy discussion, but sometimes have a hard time sounding polite (even though I mean well).

    -- Post Edit --

    I was running version 5375 of the virus signature database and Nod32 version 4.2.58.3. After upgrading my Nod32 clients to v. 4.2.61.12, I now longer had the BSOD problem
     
    Last edited: Aug 18, 2010
  25. jshessel

    jshessel Registered Member

    Joined:
    Aug 9, 2010
    Posts:
    3
    Hi-- Just reposting here from another thread:

    Just wanted to post that I've also run into the same situation and discovered that disabling Nod32 before install and reboot of Windows Vista 32 updates avoids the aemonm.sys BSOD error.

    Because of instabilities in my system a month ago, I reinstalled VISTA using the restore feature on my Asus, installing NOD32 v 4.2 as soon as I had a clean install. Much to my chagrin, much of my re-installation experience involved MANY BSODs as a result of Nod32, and it wasn't until I reinstalled the 2nd time that I realized that it was a result of the AV software.

    If I forget to turn off Nod32 before an update installation, I always get a BSOD.

    I've been a subscriber to Nod32 for 4 years now, and have had all of my clients move to Eset's products for their security needs. This is the absolute first time I've ever seen a defect in anything Eset's done and I hope there will be a prompt fix for this issue.

    My vitals:


    OS: Windows Vista 32bit. Fully updated
    Eset Product: Eset Nod32 Antivirus version 4.2.58.3
    Virus signature database: 5353 (20100809)
    Update module: 1031 (20091029)
    Antivirus and antispyware scanner module: 1284 (20100729 )
    Advanced heuristics module: 1110 ( 20100808 )
    Archive support module: 1119 ( 20100806 )
    Cleaner module: 1048 ( 20091123 )
    Anti-Stealth support module: 1019 ( 20100525 )
    SysInspector module: 1216 ( 20100517 )
    Self-defense support module : 1016 ( 20100404 )
    Real-time file system protection module: 1004 ( 20100727 )
     
Thread Status:
Not open for further replies.