Results 1 to 5 of 5

Thread: ZoneAlarm Causing Blue Screen Again

  1. #1
    jaredr Guest

    Default ZoneAlarm Causing Blue Screen Again

    Well, vsdatant.sys is causing a problem again, here's the link to my original thread;http://forum.zonelabs.org/zonelabs/b...hread.id=83773.
    Problem was solved then and since then I had no problems. Well today everything was going smoothly, I rebooted, got to the welcome screen and it blue screened with the vsdatant error.It rebooted and happened again, I then booted into safe mode and disabled ZA from startup, rebooted normally and it blue screened with no driver or stop error. Had to reboot manually. Rebooted and it's been up ever since, ZA is not running.
    I'm baffled that this was fixed, and now out of the blue I can't get ZA to startup.
    Here's my information:ZoneAlarm Free EditionAcer Asiper 3690Vista Home Premium 32bit SP12GB PC2-5300Intel Dual Core T2060 @ 1.66GHz
    Below is the memory dump.
    Probably caused by : vsdatant.sys ( vsdatant+30d01 )Followup: MachineOwner
    ---------1: kd> !analyze -v
    ************************************************** *****************************
    *











































































    *
    *






















    Bugcheck Analysis


































    *
    *











































































    *
    ************************************************** *****************************KERNEL_MODE_EXCEPTION _NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.
    Usually the exception address pinpoints
    the driver/function that caused the problem.
    Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.
    This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.
    This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.
    This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 00000000, The address that the exception occurred at
    Arg3: a89a1c5c, Trap Frame
    Arg4: 00000000Debugging Details:
    ------------------

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.FAULTING_IP:
    +0
    00000000 ??












    ???TRAP_FRAME:
    a89a1c5c -- (.trap 0xffffffffa89a1c5c)
    ErrCode = 00000010
    eax=8679c1a0 ebx=820130b0 ecx=82083d0d edx=8679f528 esi=867213d0 edi=85e30d68
    eip=00000000 esp=a89a1cd0 ebp=a89a1d0c iopl=0







    nv up ei ng nz na pe nc
    cs=0008
    ss=0010
    ds=0023
    es=0023
    fs=0030
    gs=0000











    efl=00010286
    00000000 ??












    ???
    Resetting default scopeCUSTOMER_CRASH_COUNT:
    2DEFAULT_BUCKET_ID:
    VISTA_DRIVER_FAULTBUGCHECK_STR:
    0x8EPROCESS_NAME:
    svchost.exeCURRENT_IRQL:
    1LAST_CONTROL_TRANSFER:
    from 77bf7f48 to 00000000SYMBOL_ON_RAW_STACK:
    1STACK_ADDR_RAW_STACK_SYMBOL: ffffffffa89a1d08STACK_COMMAND:
    dds A89A1D08-0x20 ; kbSTACK_TEXT:

    a89a1ce8
    8679f540
    a89a1cec
    00000000
    a89a1cf0
    820838db nt!IopCompleteRequest
    a89a1cf4
    861da580
    a89a1cf8
    77bf9a94
    a89a1cfc
    00000000
    a89a1d00
    86721424
    a89a1d04
    8d86ad01 vsdatant+0x30d01
    a89a1d08
    8d86ad5d vsdatant+0x30d5d
    a89a1d0c
    a89a1d2c
    a89a1d10
    820162f7 hal!HalpDispatchSoftwareInterrupt+0x49
    a89a1d14
    00000000
    a89a1d18
    00000000
    a89a1d1c
    a89a1d64
    a89a1d20
    a89a1d64
    a89a1d24
    01f4ef00
    a89a1d28
    00000046
    a89a1d2c
    a89a1d48
    a89a1d30
    8201650c hal!HalpCheckForSoftwareInterrupt+0x64
    a89a1d34
    803d1001
    a89a1d38
    a89a1d64
    a89a1d3c
    a89a1d64
    a89a1d40
    01f4ef3c
    a89a1d44
    803d1001
    a89a1d48
    a89a1d54
    a89a1d4c
    820166d5 hal!HalEndSystemInterrupt+0x73
    a89a1d50
    803d1000
    a89a1d54
    a89a1d64
    a89a1d58
    82026cc9 hal!HalpIpiHandler+0x189
    a89a1d5c
    00000000
    a89a1d60
    000000e1
    a89a1d64
    01f4ef3c
    FOLLOWUP_IP:
    vsdatant+30d01
    8d86ad01 ??












    ???SYMBOL_NAME:
    vsdatant+30d01FOLLOWUP_NAME:
    MachineOwnerMODULE_NAME: vsdatantIMAGE_NAME:
    vsdatant.sysDEBUG_FLR_IMAGE_TIMESTAMP:
    491cb528FAILURE_BUCKET_ID:
    0x8E_vsdatant+30d01BUCKET_ID:
    0x8E_vsdatant+30d01Followup: MachineOwner
    ---------


    Help

    Operating System:Windows Vista Home Premium
    Software Version:8.0
    Product Name:ZoneAlarm (Free)

  2. #2
    prof_fate Guest

    Default Re: ZoneAlarm Causing Blue Screen Again

    Many Acer Computers are having problems, Here is a ZA Forum Link with a Possible Solution..
    http://forum.zonelabs.org/zonelabs/b...ssage.id=81743
    ---------------------------------------------------------
    ZoneAlarm Security Suite version:8.0.059.000
    TrueVector version:8.0.059.000
    Driver version:8.0.059.000
    Anti-virus engine version:6.0.2.678
    Anti-virus signature DAT file version:966221387
    Anti-spyware engine version:5.0.202.0
    Anti-spyware signature DAT file version:01.200812.5055
    AntiSpam version:5.0.61.9957

  3. #3
    jaredr Guest

    Default Re: ZoneAlarm Causing Blue Screen Again


    <blockquote><hr>Prof_Fate wrote:
    Many Acer Computers are having problems, Here is a ZA Forum Link with a Possible Solution..
    http://forum.zonelabs.org/zonelabs/b...ssage.id=81743
    ---------------------------------------------------------
    ZoneAlarm Security Suite version:8.0.059.000
    TrueVector version:8.0.059.000
    Driver version:8.0.059.000
    Anti-virus engine version:6.0.2.678
    Anti-virus signature DAT file version:966221387
    Anti-spyware engine version:5.0.202.0
    Anti-spyware signature DAT file version:01.200812.5055
    AntiSpam version:5.0.61.9957
    <hr></blockquote>
    Well, I've got one of the older Acers, 3690.I had uninstalled all those eAcer programs several months ago, only things left are Acer Registration and eLock Managment which I can't get to uninstall.

  4. #4
    naivemelody Guest

    Default Re: Acer eLock Management

    Click here - pdf &gt; http://websupport.acer.com.tw/upload...Management.pdf
    - follow instructions to unlock your pc - see if this helps.<hr>Then try to re-install ZA again, after first 'properly' un-installing the current corrupted ZA install.

  5. #5
    jaredr Guest

    Default Re: Acer eLock Management


    <blockquote><hr>NaiveMelody wrote:
    Click here - pdf &gt; http://websupport.acer.com.tw/upload...Management.pdf
    - follow instructions to unlock your pc - see if this helps.<hr>Then try to re-install ZA again, after first 'properly' un-installing the current corrupted ZA install.
    <hr></blockquote>
    I wasn't able to launch elock, perhaps also due to the fact I couldn't uninstall it.I downloaded and installed the latest version, rebooted, and tried start elock but it wouln't start, taskmanager showed it open but close two seconds later.I tried uninstalling elock and was successful.
    I performed
    a &quot;proper&quot; installation of ZA, rebooted, and am here now. So far so good.I ordered the recovery media for my acer laptop yesterday, I've been needing to reinstall Vista for quite some time but when I bought my laptop it didn't come with the media discs, *shakes fists at OEM* So I'll be doing a fresh install.
    Thank you, everyone, for all your help! May lock this now.

    Message Edited by JaredR on 12-24-2008 06:57 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •