Freezing on logon

Discussion in 'ESET Smart Security' started by DBM901, Feb 21, 2013.

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

    DBM901 Registered Member

    Joined:
    Jan 22, 2010
    Posts:
    28
    Narrowed it down to ESET.

    Uninstall it i can logon just fine. Boot into safe mode of course works fine.


    I can run my system all day with no problems, but when i reboot, its a 70% chance i'll have to uninstall it just to reboot successfully again.

    What do i do?

    Windows 7 64bit updated
     
  2. Tyrizian

    Tyrizian Registered Member

    Joined:
    Apr 26, 2012
    Posts:
    2,806
    How many programs do you have running at startup?

    Sometimes running too much can interfere with other programs and quite possibly cause freezing.

    If you have a lot executing on startup (Stuff that isn't needed), try reducing/disabling the number of programs that start, see if that helps any.
     
  3. DBM901

    DBM901 Registered Member

    Joined:
    Jan 22, 2010
    Posts:
    28
    Tried that already.
     
  4. Tyrizian

    Tyrizian Registered Member

    Joined:
    Apr 26, 2012
    Posts:
    2,806
    Including a service or services that might be associated with a program?

    Some programs can be disabled from startup and still have remaining services running....This is why I ask.
     
  5. DBM901

    DBM901 Registered Member

    Joined:
    Jan 22, 2010
    Posts:
    28
    I used System Configuration to disable all startup items.

    Uninstalled my gpu drivers thinking that was it. and it wasnt until i disabled my ESEt that it would boot. Now if i run into the issue i just uninstall and then reinstall, and it works every time.

    If i tried starting it manually i'd get errors about could not load kernel.


    EDIT: i scan with eset daily on my C drive, weekly on others. Ran hitmanpro,combofix,mbam, Super anti spy and spybot.
     
  6. black_harry

    black_harry Registered Member

    Joined:
    Feb 9, 2013
    Posts:
    17
    Hi,

    Can you answer in following questions:

    1. Those locks - how you experiencing them - it is everytime to try to login? It is lock so that you cannot work anymore? Or rather slowdown when logging?

    2. Do you use any other security software? It is very probable that this can be root cause of those lock? Have you tried to uninstall it temporarly?

    3. It is happening on V6 or on other version? If you see this on V6 then try V5 or vice versa.

    I'm asking because I've ESS installed on my W7 machine and it works perfect so I would expect some interactions with other security softwares.

    harry
     
  7. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    The best would be to manually generate a complete memory dump as per the instructions here at the point the system appears to be "frozen", compress it and supply it to ESET Customer care for analysis. Could you confirm or deny that you're using default settings and you didn't switch HIPS to interactive mode for instance?
    Also it would help if renaming any of the following drivers in safe mode makes a difference:
    C:\Windows\System32\drivers\eamonm.sys
    C:\Windows\System32\drivers\ehdrv.sys
     
  8. DBM901

    DBM901 Registered Member

    Joined:
    Jan 22, 2010
    Posts:
    28
    1. They happen after i type in my password and hit enter. It will stay at that screen.
    2.MBAM and Spybot are the only other active programs
    3.This is happening on V6 :)

    The HIPS settings are default I never change them. My other settings i always change.

    If it happens again will follow your steps and submit the information.

    Thanks folks.
     
  9. DBM901

    DBM901 Registered Member

    Joined:
    Jan 22, 2010
    Posts:
    28
    Ok it has happened again. Gave it 15 minutes and it was still stuck.

    I had some trouble doing the complete memory dump thing

    But i renamed the files and youre on to something

    I can boot if i disable eamonm.sys.BAK


    Whats next?
     
  10. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    In that case, we'll need to get a complete memory dump from the point when the system is frozen / unresponsive. Was the problem that BSOD didn't occur after holding Ctrl and pressing Scroll log twice as per the instructions in the KB article even though you enabled manual generation of dumps in the registry? If you have MBAM Pro with real-time protection, could you try uninstalling it temporarily to see if it makes a difference? Or at least try renaming the c:\windows\system32\drivers\mbam.sys driver in safe mode and let us know if it makes a difference.
     
Thread Status:
Not open for further replies.