BSOD Smart Security v4.2.35

Discussion in 'ESET Smart Security' started by TitaniumDust, Mar 12, 2010.

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

    TitaniumDust Registered Member

    Joined:
    Mar 12, 2010
    Posts:
    4
    I'm a long time registered ESET user, and wanted to report a BSOD for Smart Security v4.2.35. I'm running Windows 7 Home Premium x64, with 6GB of memory. I have and can provide the minidump and memory.dmp files upon request by ESET. The BSOD was 0xD1, file eamonm.sys, and I think the message was DRIVER_IRQL_NOT_LESS_OR_EQUAL but I'm not sure. I've reinstalled v4.0.474 to be safe.

    Problem signature
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 1033

    Extra information about the problem
    BCCode: d1
    BCP1: 0000000000030003
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF88007462745
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1
     
  2. TitaniumDust

    TitaniumDust Registered Member

    Joined:
    Mar 12, 2010
    Posts:
    4
    I thought I'd add some info on this BSOD which may be useful. I couldn't find an edit button so I just replied.

    My computer is 24-hour prime95 stable and 2-hour memtest stable. Since reinstalling v4.0.474, I haven't had any issues, and hadn't with that version since it came out, whenever that was. At the time of the BSOD, I was using SyncBack Pro to do a backup - and it was in the process of the scanning the source files to decide what to copy, when the BSOD occurred. I still have memory.dmp and minidump files. I'm not sure what to expect here, I guess I won't install v4.2.35 and just wait until the next version? o_O

    Edit: Just submitted a support request online.
     
    Last edited: Mar 19, 2010
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    PM with instructions sent.
     
  4. TitaniumDust

    TitaniumDust Registered Member

    Joined:
    Mar 12, 2010
    Posts:
    4
    Thank you Marcos! PM sent after directions followed.
     
  5. TitaniumDust

    TitaniumDust Registered Member

    Joined:
    Mar 12, 2010
    Posts:
    4
    As a followup, I had the same BSOD occur again under the same conditions, this time with v4.2.40. A complete memory dump (6GB uncompressed!) was obtained. I sent a PM, and I am awaiting word as to what, if any, direction should be taken.
     
Thread Status:
Not open for further replies.