ESS causing random BSOD in winxp sp3

Discussion in 'ESET Smart Security' started by simons101, Jun 14, 2008.

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

    simons101 Registered Member

    Joined:
    Jun 14, 2008
    Posts:
    4
    Hi all,
    I have been getting random BSOD's after installing ESS .. minidump below... winxp sp3 ESS ver. 3.0.650.0 , any solutions to this ... o_O


    MODULE_NAME: epfwtdi

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 47d947b8

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    +ffffffff852168ea
    852168ea f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from 851f79f3 to 852168ea

    SYMBOL_ON_RAW_STACK: 1

    STACK_ADDR_RAW_STACK_SYMBOL: fffffffff39cf464

    STACK_COMMAND: dds F39CF464-0x20 ; kb

    STACK_TEXT:
    f39cf444 00000000
    f39cf448 00000000
    f39cf44c 00000000
    f39cf450 868b7568
    f39cf454 868b77cc
    f39cf458 f32e8704
    f39cf45c f39cf488
    f39cf460 b276276c epfwtdi+0x276c
    f39cf464 85159720
    f39cf468 00000001
    f39cf46c 84bae570
    f39cf470 851596f8
    f39cf474 fc8850c0
    f39cf478 00000000
    f39cf47c 558c94e2
    f39cf480 00001240
    f39cf484 2a950000
    f39cf488 00000000
    f39cf48c 94e22a95
    f39cf490 1240558c
    f39cf494 00000000
    f39cf498 fc8850c0
    f39cf49c 85159600
    f39cf4a0 85159720
    f39cf4a4 00000000
    f39cf4a8 fc8850c0
    f39cf4ac fc8850c0
    f39cf4b0 000000e0
    f39cf4b4 00000001
    f39cf4b8 00309343
    f39cf4bc f39cf4e4
    f39cf4c0 00000000


    FOLLOWUP_IP:
    epfwtdi+276c
    b276276c ?? o_O

    SYMBOL_NAME: epfwtdi+276c

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: epfwtdi.sys

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
    ---------

    kd> lmvm epfwtdi
    start end module name
    b2760000 b2772000 epfwtdi T (no symbols)
    Loaded symbol image file: epfwtdi.sys
    Image path: epfwtdi.sys
    Image name: epfwtdi.sys
    Timestamp: Thu Mar 13 15:26:48 2008 (47D947B:cool:
    CheckSum: 00013BD8
    ImageSize: 00012000
    Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
     
  2. simons101

    simons101 Registered Member

    Joined:
    Jun 14, 2008
    Posts:
    4
    No response , thats never a good sign ...o_O
     
  3. Fajo

    Fajo Registered Member

    Joined:
    Jun 13, 2008
    Posts:
    1,812

    Im not support. but I will give you the normal responce from them


    Uninstall
    delete
    Reinstall.

    All things should be magicly fixed :doubt:
     
  4. Kosak

    Kosak Registered Member

    Joined:
    Jul 25, 2007
    Posts:
    711
    Location:
    Slovakia
    Hi, simons101!

    Try to make log from ESET SysInspector and send it to support[at]eset.com for analysis your system.

    Regards
     
  5. denno

    denno Registered Member

    Joined:
    Mar 22, 2006
    Posts:
    49
    Did you do an in-place upgrade to SP3, or is this a fresh install? From reading technet forums, there's quite a few issues around the place where SP3 isn't playing nicely when it's just installed over the top of an SP2 box. Fresh installs using SP3 slipstreamed installation CD are less problematic.
     
  6. simons101

    simons101 Registered Member

    Joined:
    Jun 14, 2008
    Posts:
    4
    Thanks to the above people, (sorry was away, so late responce)
    SP3 over win XP SP2 .. will do a fresh one at some stage just not right now.

    will send data to eset and do a clean install of eset Smart security.

    Thx for your help.
     
  7. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    Before you reinstall ESET Smart Security, please make sure you have the latest device drivers installed for your network interface card.

    Installing the latest service pack does not guarantee that the latest device drivers for your NIC get installed and even Windows Update does not always provide the latest device drivers from the manufacturing.

    Downloading and installing the device drivers from the manufacturer's web site for your NIC will will help rule out the possibility of a conflict with ESET Smart Security.

    Regards,

    Aryeh Goretsky
     
    Last edited: Jul 7, 2008
Thread Status:
Not open for further replies.