Eset 4.2.64 BSOD with Truecrypt

Discussion in 'ESET NOD32 Antivirus' started by nurgle, Aug 23, 2010.

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

    mk4gti Registered Member

    yes the new eamon.sys fix made the problem go away. everything is perfect now thanks! i will look into eset 5 also
  2. ChrisLIX

    ChrisLIX Registered Member

    Somebody would like to send me the file eamon.sys to fix the problem? Thanks++
  3. agoretsky

    agoretsky Eset Staff Account


    You can obtain the release candidate for ESET NOD32 Antivirus v5 from


    Aryeh Goretsky

  4. ChrisLIX

    ChrisLIX Registered Member

    The version 5 isn't suppose to correct this bug right now; A member said he was working on V5 to try the new eamon.sys and I can read in the change log (know issues) : True crypt compatibility issues...
  5. pas7301

    pas7301 Registered Member

    I second that..
    I uninstalled version 5 because of the so many BSOD.. with USB mounted True Crypt volume.
    went back the latest v4 good release and no more BSOD

    I will wait on Version 5...
  6. Jadoube

    Jadoube Registered Member

    I finally got beta 5 build 84 installed and so far so good (about 4 hours) with TrueCrypt file mounted drives... but now I see that the fix isn't in yet? D'oh! Come on programmer guys! I guess I have been lucky so far...

    But what I really have to say is "great software" NOD32 guys! It's such a relief to be back on ESET and off of BitDefender. ESET is a much more polished and professional feeling solution. Nicely done.
  7. MWarner

    MWarner Registered Member

    So, do we feel confident that V5 will solve this TrueCrypt issue? Because it has crept up on me this week as well. With the Beta now closed, approx how long until V5 is released?
  8. Jadoube

    Jadoube Registered Member

    Well... I have been running ESET 5 84 for a week and no blue screens. Am I just lucky? Even though the issue sheet still shows a problem with TrueCrypt I have been stable so far.
    I am about to start the move to a new laptop this weekend... I will try encrypting the system drive on it and see how that goes.
  9. reza666

    reza666 Registered Member

    Just faced this problem myself. Never had problem with mounting an encrypted file but now when i have a partition encrypted it gives me the BSOD when i mount it each time.
    Only way to go around it seems to be to disable NOD during the mounting (havent tried many times so maybe i was lucky)

    Win7pro x64 SP1 and ESET NOD32 Antivirus and TC 7a

    Please can you tell me if the .sys file will help for sure?
    And more importantly where do i download this magical .sys file from?

    ps. i dont like to test V5 if thats beta. I'm pretty happy with my stable system as is so unless its a must i rather stay on current v4.2 and use the fix. Please advice.
  10. reza666

    reza666 Registered Member

    Anyone? Can you please tell me where to get the .sys file ?
  11. Marcos

    Marcos Eset Staff Account

    PM sent.
  12. mantra

    mantra Registered Member

    i would appreciate it too

    will be fixed with an internal update?
  13. reza666

    reza666 Registered Member

    Thanks Marco, the "new" .sys file is working great so far.
    I have a couple of questions for you, when you have the time could you please reply to my PM. Thanks again!
  14. Calafax

    Calafax Registered Member

    I'm posting here because of my frustration with ESET's handling of my private, email approach to them over the TrueCrypt/NOD32 issue.

    A this thread makes clear, ESET is aware of the incompatibility between TrueCrypt and NOD32. Public discussion of this issue, here and elsewhere, goes back a year at least. When I contacted ESET about receiving the EAMON.SYS revision that apparently corrects the incompatibility, ESET's response consisted of a set of suggestions that entail crippling the product for which I've paid them, with no assurance that any of the steps would solve the problem. (And I did implement at least two of their suggestions, without success.)

    This response from ESET followed their request for test results from their system interrogation utility SysInspector, which I had downloaded, installed, run, and whose results I had emailed to ESET. Additionally, I sent them the memory dump they later requested. My original request has never been addressed at all.

    So a fix apparently exists, but ESET will not make it available publicly or even privately to a paying customer who requests it and obviously is willing to serve as another tester. Moreover, ESET continues to say nothing official about correcting the problem.

    Here's the choice ESET offers. On one side is TrueCrypt, a competently designed, free utility for which no comparable, free alternative exists. On the other side is ESET's commercial product for which many alternatives exist, paid and free, and with many of these alternatives enjoying good reputations. ESET and TrueCrypt can blame each other if they choose to, but ESET has far more to lose.

    I'd much prefer to stick with NOD32. I only wish that my original, specific question to ESET had been answered instead of simply triggering a generic, jump-through-the-hoops help desk mechanism.

    The alternative approach appears to consist of public begging for help on this forum. Why should only that succeed? At this point, why should it be necessary at all?
  15. mantra

    mantra Registered Member

    can i have the .sys too ?

    will be included in an internal update ? modules or program?
  16. mantra

    mantra Registered Member

    may i have eamonm.sys too ?
    but is eamonm.sys or eamon.sys
    i use a lot true crypt under w7 and xp sp2

  17. MWarner

    MWarner Registered Member

    I, too, would like the .sys fix for v4 since we're still waiting on v5. Thank you.
  18. focus

    focus Registered Member

    I also would like the .sys fix for v4, if it is available.
  19. reza666

    reza666 Registered Member

    @Mantra: I am using ESET NOD32 Antivirus 4.2 and the .sys worked nicely for me. I'm not sure if i'm allowed to send you the file so i let the staff do this (sorry).
  20. mantra

    mantra Registered Member


    i download the fix, and i should replace the eamonm.sys in safe mode

    i have nod32 v4.2.71.2 , but i haven't in my system eamonm.sys
    i have eamon.sys o_O o_O o_O
  21. Marcos

    Marcos Eset Staff Account

    Re: but

    Most likely you don't use Windows 7 where the issue with TrueCrypt occurred. If you're getting BSOD on Windows XP or 2000, it must be a completely different problem (maybe a clash with other obsolete drivers on your system). A complete memory dump from BSOD would shed more light.
  22. reza666

    reza666 Registered Member

    Re: but

    Just to be sure did you check the C:\WINDOWS\system32\drivers\eamonm.sys
    when in safe mode?
    I checked the folder before safe mode and didnt see it (have show all files) but when rebooted in safe mode it was there.
  23. robman782

    robman782 Registered Member

    Hi, new member here also requesting the fix for this issue. I'm running Windows 7 Home Premium (x64) with TrueCrypt 7a and ESET SS4 (

    I experience BSOD when creating or mounting large tc volume containers. I tried creating the volume on a different system running XP which worked but when I tried to mount this volume on my primary Windows 7 system I get a BSOD even with ESET Real-Time file system and Antivirus protection both disabled. Thanks in advance!

    Update 15-Aug Thanks Marcos for sending the link via PM. Looking forward to much needed relief from this issue. :)
    Last edited: Aug 15, 2011
  24. MWarner

    MWarner Registered Member

    Any chance I could get the link via PM as well for the fix? Running Win 7 x64 with Nod v4.2.71.2?
  25. robman782

    robman782 Registered Member

    No use still getting BSOD must be a different issue... Maybe not related to ESET.
Thread Status:
Not open for further replies.