BSOD on windows XP boot

Discussion in 'ESET Smart Security' started by Iger, Jun 2, 2010.

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

    Iger Registered Member

    Joined:
    Jun 2, 2010
    Posts:
    3
    Hello!

    I install Eset smart security 4.2.40.0.
    Once I reboot my PC - the windows XP will BSOD (SESSION3_INITIALIZATION_FAILED) upon booting. I can only log into safe mode. If I uninstall ESS - the XP boots fine. If I re-install and disable self-defense - the XP boots fine.

    I have dual boot with Vista and Vista is the bootmanager, so XP is on second drive. XP doesn't generate memory.dmp upon BSOD during startup, so I had to resort to the dump initiated from keyboard with ctrl+scrllock. I hope it helps. I uploaded both the dump and the SysInspector log captured immediately after the installation of ESS to ftp.nod.sk/support.

    System spec (don't remember if it's gathered by SysInspector):
    Motherboard: Abit IP35
    RAM: 2GB with mild overclock
    CPU: Intel E6750
    GPU: Nvidia 8800GT 512mb

    Thanks in advance.
     
  2. Iger

    Iger Registered Member

    Joined:
    Jun 2, 2010
    Posts:
    3
    Hello!

    Any news on my issue?
    EDIT: Have you received the files I submitted?
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    PM sent.
     
  4. Iger

    Iger Registered Member

    Joined:
    Jun 2, 2010
    Posts:
    3
    Hello!

    I'm sorry it took me that long to get back.
    Your advice was to edit the registry setting:

    as a possible way to have memory dump file be captured by windows.

    I must report, that once I set the key's value to 2 the BSOD doesn't occur anymore even with the self-defense enabled (I suppose it was indeed running, as upon rebooting, I can't change the aforementioned key back from 2 to 1).
    I've confirmed this finding by disabling the self-defense, rebooting, setting the key back to 2 and re-enabling self-defense - the crash re-appeared.

    Seems like the answer is close :)
    What exactly does ehdrv (Eset Helper driver) do? What does setting this registry value to 2 do? Am I better running with this value set to 2 or with running w/o self-defense enabled? And will there be a fix? :)

    Thanks for the reply!
     
Thread Status:
Not open for further replies.