Faulting application egui.exe, version 4.0.437.0

Discussion in 'ESET NOD32 Antivirus' started by limexp, May 28, 2009.

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

    limexp Registered Member

    May 28, 2009
    Dear admin,
    I have installed eav 3 and eav 4.0.437 on Vista 32bit Sp1. Egui crashed with the following details.

    I have the same eav4 installed on my winXp machine and it's working fine.

    I am going nowhere with this issue. I have the sysInpector log ready if you need it. Please help!!:'(

    Kind regards

    Log Name: Application
    Source: Application Error
    Date: 29/05/2009 00:32:58
    Event ID: 1000
    Task Category: (100)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: mycomputer
    Faulting application egui.exe, version 4.0.437.0, time stamp 0x4a0c161b, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0150004, fault offset 0x00009cac, process id 0xdc0, application start time 0x01c9dfeca09dbd40.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <TimeCreated SystemTime="2009-05-28T23:32:58.000Z" />
    <Security />
  2. SamSa

    SamSa Eset Staff Account

    May 14, 2009
    Uninstall ESET with the ESET uninstaller

    Then try the following:
    1. Restart your computer into SafeMode as the Administrator.
    2. Delete the following folders and registry keys:

    C:\Program Files\ESET
    C:\Program Data\ESET

    Registry keys:

    3. Boot back into normal mode and download "Windows Installer CleanUp Utility:


    4. Run this program and make sure ESET is gone from the list.

    5. Make sure you have any other anti-virus program removed.

    6. Reinstall ESET.
  3. limexp

    limexp Registered Member

    May 28, 2009
    Hi Samsa,
    I have followed your instructions by uninstalling trojan remover, delete reg and eset folder. The app crash issue still persist.

    I have upgraded Vista Sp2 service pack, clean install -> no luck. Eset window service is running ok, but application crashed as soon as i tried to load eset gui, SysInspector from the program files.

    However, running standalone Eset SysInspector downloaded from website is fine.

    Is there any tool i can log the loading of egui? App crash in event log does not give me much details apart from telling me the faulting module is ntdll.dll

    Should i pm you Process Monitor and SysInspector log?

    thanks in advance

  4. limexp

    limexp Registered Member

    May 28, 2009
    Dear admin,
    I have logged an official customer service ticket. Please pick up the thread and escalate as needed.

    ESET New Case Customer Notification - 308646

  5. nubdonut

    nubdonut Registered Member

    Apr 7, 2009
    Hi limexp,

    Any reply from the admin? I am also experiencing this error everytime i change the scheduler.
  6. limexp

    limexp Registered Member

    May 28, 2009
    Nobody yet to reply.:doubt: I am waiting how long it take for eset to get to the bottom of the issue.
  7. edwin3333

    edwin3333 Registered Member

    Aug 29, 2007
    My guess;

    I recommend to remove 3, reboot 2 times, then install 4. Not install 4 on top of 3. The reason is this prevents an issue that sometimes occurs where the non-pnp device drivers prevent 4 from installing correctly, and two reboots are required for the uninstall to work right.

    Uninstall Nod32, reboot. Go into device manager, select devices, select VIEW / Show hidden devices. Go into non-pnp drivers. If the uninstall is complete, you should not have ehdrv, epfwtdir, amon, imon... There are others, the forum has posts - I can't recall them all.

    We have 675 PC's and afflicts perhaps 1-2% of our PCs. Server OSes more than others.
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.