NOD32 and Vista 64 issue

Discussion in 'ESET NOD32 Antivirus' started by Wi11iam, Jul 6, 2008.

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

    FlyingHorse Registered Member

    Joined:
    Dec 9, 2005
    Posts:
    12
    Location:
    33?59'43.1"N 84?09'03.1"W
    After working with ESET technical support for nearly 2 weeks it seems that my problem has been resolved by updating Daemon Tools to the latest version (4.30.1) which came out earlier today. Now running 3.0.669 and I haven't had a BSOD during startup in over 6 re-boots. :D

    Thank you for the help ESET!
     
  2. jnuzzi

    jnuzzi Registered Member

    Joined:
    Jul 22, 2008
    Posts:
    6
    Location:
    Orlando, FL
    OK, so the information that I posted yesterday was removed by the mods. :(

    So I will now relay to everyone what I was asked to do "in my own words". :rolleyes:

    The reply that I received from support recommended that I add the following applications to the exclusions in ESET NOD32:
    • Microsoft SQL Server
    • Carbonite Secure Backup
    • Apple iPod-related programs
    They also provided a link to a KB article that describes how to do this. Here is the link they provided:
    So, after receiving this email, I added Carbonite and iTunes to the list of web browsers and then put an "X" next to them so that NOD32 will exclude them. After that I re-enabled the "ESET Smart Security" startup item and rebooted. Everything seemed to work and no BSOD. I rebooted again and, again, no BSOD. I then shut down my computer for the night. I started it again this morning and no BSOD.

    This morning I also upgraded my Daemon Tools to the latest version (4.30.1) as suggested by FlyingHorse. I have also rebooted about 3 times today and no BSOD on any of them. :D

    Hopefully this will help the others that have been experiencing the BSOD issue.
     
  3. zerocool

    zerocool Registered Member

    Joined:
    Jul 25, 2008
    Posts:
    1
    Hello,
    I have Windows XP x64, 8GB RAM, ATI 3870x2 video card with catalyst 8.7 installed. NOD32 v667 and v669 would BSOD/crash my computer randomly during logging into my computer. I run none of the applications above that are mentioned to be excluded from NOD32. After taking someones suggestion and reverting back to v650 my BSOD issues have gone away. I thought as most of you did at first that it was a hardware issue then I found this in the forums and decided to revert back to see what happends and all is good with v650. Hopefully this gets fixed soon by eset, but looking through the thread here I also appear to be the only Windows XP x64 person experiencing this issue.
     
  4. element119

    element119 Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    72
    both vista x64 and xp x64 use kernel patch protection. x86 versions of windows dont.
     
  5. Wi11iam

    Wi11iam Registered Member

    Joined:
    Jul 6, 2008
    Posts:
    16
    Just to say i still have the issue,

    I have made the eset service start manually so now i dont get the BSOD from a boot up, but this does not prevent me getting a BSOD from logging out then in.
     
  6. jnuzzi

    jnuzzi Registered Member

    Joined:
    Jul 22, 2008
    Posts:
    6
    Location:
    Orlando, FL
    Have you contacted ESET support regarding this issue?
     
  7. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,441
    Have you already provided ESET support with a complete memory dump from BSOD?
     
  8. element119

    element119 Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    72
    also still waiting, my memory dumps are gone.
    running .650 with no bluescreens.
     
  9. element119

    element119 Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    72
    this issue is about to have its 1 month anniversary
     
  10. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,441
    Unfortunately, I still have not heard who did you contact and what ticket number you were assigned so I could not get to the dump yet. If possible, please provide me this information so that we can analyse the dump.
     
  11. Alaska99

    Alaska99 Registered Member

    Joined:
    Jun 27, 2007
    Posts:
    24
    I don't understand why Eset have not release version 670 to correct the bug..... Too much time elapsed since 669 release...........o_O

    Come on Eset come back of summer holidays......o_O
     
  12. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,441
    If you have submitted a full memory dump from BSOD, please provide me with details as to whom did you send it so that I can ask that distributor/reseller to pass it to us for analysis.
     
  13. Skier

    Skier Registered Member

    Joined:
    Jul 10, 2008
    Posts:
    28
    Marcos,

    I reported a similar (but not identical issue - rebooting with version 667 & 669) to eset.co.uk on 10 July. I had a response on 11 July and have subsequently e-mailed twice more since with not a single acknowledgement or reply. My last e-mail was on 12 July at 10:54.

    I have re-installed v650 and now experience no errors and this currently seems to be the only solution.

    Your question above i.e. 'What bug?' is somewhat disingenuous as it's the same one reported throughout the thread. The comment may well have been toungue-in-cheek but it's all well and good for you to ask people to pass information but my experience is that once this is done it simply disappears into a black hole.

    Any update on this issue would be appreciated. Clearly it has something to do with changes implemented in v667 and also included in v669 so shouldn't be too difficult to pin down.

    Regards

    Skier
     
  14. Gamof

    Gamof Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    6
    Location:
    The Carrier
    The very nature of technical support on forums is simple. You only post when you have problems. As such for every person like yourself with a problem there is more than likely hundreds if not thousands of people that aren't affected at all. This is obviously a software compatibility problem and contrary to what you may think i doubt its easy to pin down. I run 3.0.667 on Vista Ultimate 64 SP1 and have never experienced this BSOD.

    Peace.
     
  15. element119

    element119 Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    72
    and likewise, there is no doubt there are many users who have this problem and have not posted here.
    so i'm waiting for a version that will work for me, till then i will keep .650.
    i'm not going to play around with workarounds and such. i spent too much time on this already before even figuring out it was a problem with eset.
    i pay for this software, i'm not some beta tester or freeloader.
    i bought nod32 because it is supposed to be the best. i haven't lost faith (i still have it installed), but i'm a little disappointed that it hasn't been fixed yet.:(
     
  16. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,441
    We'll definitely need a complete memory dump from someone having this kind of problem. We've seen BSOD caused by old NIC drivers that were interfering with ours so a complete memory dump would be very helpful and much appreaciated.

    As for Skier, our UK partner should have contacted him for details about his ticket. As soon as we receive the dump, we will analyse it and hopefully we'll be able to figure out the cause.
     
  17. element119

    element119 Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    72
    my dumps were eaten by ccleaner and disk cleanup. i did however get a new nic driver through windows update last week. the previous nic driver was maybe a few months old. do you think i should try .669 again?
    Realtek RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC (NDIS 6.0)
    driver version: 6.2071.714.2008
     
  18. Skier

    Skier Registered Member

    Joined:
    Jul 10, 2008
    Posts:
    28
    Marcos,

    I have not been contacted by anyone from EST UK. That's perhaps not surprising as it's the weekend.

    I can send you the dumps from my currently installed version of NOD32 i.e. v650 but obviously they will be of limited value as all works well with that version.

    Regards

    Skier
     
  19. DanL

    DanL Registered Member

    Joined:
    Nov 25, 2004
    Posts:
    159
    Has this issue been resolved yet?

    I'm picking up a new laptop tomorrow that has Vista 64bit.
    Would like to hear this has been fixed before loading Eset.
     
  20. DanL

    DanL Registered Member

    Joined:
    Nov 25, 2004
    Posts:
    159
    Nothing ?
     
  21. element119

    element119 Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    72
    nada:(
     
  22. Wi11iam

    Wi11iam Registered Member

    Joined:
    Jul 6, 2008
    Posts:
    16

    Err...

    I sent the memory dump to yourself (well the link to it atleast in July), i also mentioned that i done so on my ESET support emails who said that they would have forwarded the memory dump on to yourself anyway.

    Ive still not heard anything for weeks from support :(
     
    Last edited: Aug 18, 2008
  23. Skier

    Skier Registered Member

    Joined:
    Jul 10, 2008
    Posts:
    28
    Well v3.0.672 has cured this problem for me. Installed last night, run a scan and now a few re-boots and all is fine - hurrah!

    Regards

    Skier
     
  24. element119

    element119 Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    72
    seems good for me too with .672
     
  25. Zymurgy

    Zymurgy Registered Member

    Joined:
    Jun 21, 2006
    Posts:
    5
    And this is available? My link to download only shows 669 version. :blink:
     
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.