Results 1 to 7 of 7

Thread: vsdatant.sys calling PQV2i.sys causes intermittent BSOD

  1. #1
    RustySam Guest

    Default vsdatant.sys calling PQV2i.sys causes intermittent BSOD

    I am running XP SP3 and Zone Alarm Extreme Security Ver 9.1.037.000. I also have Norton Ghost 9.0 (PQV2I.sys) installed. Very intermittently during a re-boot I get a BSOD blaming PQV2i.sys. The reboot always works ok. If I look at the minidump it always shows vsdatant.sys making an OpenFile call to PQV2i.sys. It then appears to wind up accessing a memory location that is not valid (status 0xc0000005)

    I have put the service on manual so the PQV2i.sys driver is NOT loaded (until Ghost is started) during the boot. I suspect something on the system that occurred before the last shutdown is setting a flag that makes vsdatant.sys think the driver will be loaded on bootup. Main reason for this thinking is that it is very intermittent and can not discern a pattern. I do not use Ghost 9.0 regularly (just to build images) and have not started it prior to the last couple of times I have seen the problem.

    I had the identical problem with ZoneAlarm Pro (just upgraded). Not sure but believe I may have had this problem prior to putting the service on manual.

    Would appreciate any insight anyone can provide. Do not believe it to be a specific ZoneAlarm problem but not sure what the initiates the problem.

    MINIDUMP FOLLOWS

    BugCheck 1000008E, {c0000005, 804e37ee, f7b786bc, 0}

    Unable to load image vsdatant.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for vsdatant.sys
    *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
    Probably caused by : PQV2i.sys ( PQV2i+3871 )

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

    ================================================== ===========================================
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    FAULTING_IP:
    nt!IopfCallDriver+28
    804e37ee 8b7108 mov esi,dword ptr [ecx+8]

    TRAP_FRAME: f7b786bc -- (.trap 0xfffffffff7b786bc)
    ErrCode = 00000000
    eax=0000000d ebx=8681d008 ecx=000004d5 edx=8681d008 esi=8681d008 edi=00000000
    eip=804e37ee esp=f7b78730 ebp=f7b78750 iopl=0 nv up ei ng nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210282
    nt!IopfCallDriver+0x28:
    804e37ee 8b7108 mov esi,dword ptr [ecx+8] ds:0023:000004dd=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from f761f871 to 804e37ee

    STACK_TEXT:
    f7b78730 f761f871 8681d220 8681e0d8 8604a700 nt!IopfCallDriver+0x28
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f7b78750 f76237af 000004d5 8681d008 8722c2e0 PQV2i+0x3871
    f7b78790 f76235f6 8722c2e0 86800478 8722c2e0 PQV2i+0x77af
    f7b78818 80505382 c0000001 f7b78900 00000000 PQV2i+0x75f6
    f7b78848 8056ec4a 87338b20 8683c688 f7b7897c nt!IopCheckVpbMounted+0x5b
    f7b78938 80563fec 8683c688 00000000 871afe38 nt!IopParseDevice+0x3d8
    f7b789c0 8056866a 00000000 f7b78a00 00000040 nt!ObpLookupObjectName+0x56a
    f7b78a14 8056f42b 00000000 00000000 580ea800 nt!ObOpenObjectByName+0xeb
    f7b78a90 8056f4fa f7b78c8c 00100001 f7b78c54 nt!IopCreateFile+0x407
    f7b78aec 8056f5c2 f7b78c8c 00100001 f7b78c54 nt!IoCreateFile+0x8e
    f7b78b2c b2eca85b f7b78c8c 00100001 f7b78c54 nt!NtOpenFile+0x27
    f7b78b98 804de7ec f7b78c8c 00100001 f7b78c54 vsdatant+0x2e85b
    f7b78b98 804dcfdd f7b78c8c 00100001 f7b78c54 nt!KiFastCallEntry+0xf8
    f7b78c28 f7745f76 f7b78c8c 00100001 f7b78c54 nt!ZwOpenFile+0x11
    f7b78d60 80564610 868024a0 872d2f08 805622fc VolSnap!VspDeleteDiffAreaFilesWorker+0xa0
    f7b78d74 804e426b 872d2f08 00000000 873c43c8 nt!IopProcessWorkItem+0x13
    f7b78dac 8057c9ca 872d2f08 00000000 00000000 nt!ExpWorkerThread+0x100
    f7b78ddc 804f88ea 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    PQV2i+3871
    f761f871 ?? ???

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: PQV2i+3871

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: PQV2i

    IMAGE_NAME: PQV2i.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4108c452

    FAILURE_BUCKET_ID: 0x8E_PQV2i+3871

    BUCKET_ID: 0x8E_PQV2i+3871

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

  2. #2
    Join Date
    Jun 2006
    Location
    The 3rd Coast - South Central Texas
    Posts
    10,466

    Default Re: vsdatant.sys calling PQV2i.sys causes intermittent BSOD

    Quote Originally Posted by RustySam View Post
    I am running XP SP3 and Zone Alarm Extreme Security Ver 9.1.037.000. I also have Norton Ghost 9.0 (PQV2I.sys) installed. Very intermittently during a re-boot I get a BSOD blaming PQV2i.sys. The reboot always works ok. If I look at the minidump it always shows vsdatant.sys making an OpenFile call to PQV2i.sys. It then appears to wind up accessing a memory location that is not valid (status 0xc0000005)

    ---------
    1.) I have the latest version of ZA Extreme 9.1.008.000
    I've never heard of ZA Extreme ver..1.037.000 ?

    If you have a Current Valid ZA License key, you can Contact the ZA Tech Support Directly by Live Chat Link in my Signature..

    Please provide full details of your BSOD problem as well as your:
    OS (XP SP 2-3 / Vista SP1-2 / Windows 7), your zonealarm product and it's version number . Brand of Computer and CPU..
    GeorgeV
    ZoneAlarm® Extreme Security


    Click here for ZA Support
    Monday-Saturday__ 6am to 10pm Central time
    Closed Sundays and Holidays

  3. #3
    RustySam Guest

    Default Re: vsdatant.sys calling PQV2i.sys causes intermittent BSOD

    My Internet provider also provides the zone alarm product (along with the license key) which they describe as

    "
    ©2003-2009 CheckPoint Software Technologies Ltd. All right reserved. ZoneAlarm® Extreme Security and ZoneAlarm ForceField™ are registered trademarks of Check Point Software Technologies Ltd. or its affiliates."

    I just moved from ver 8.x.x.x within the last couple of weeks. This version is the latest for xp and install file zaZAX_Setup_en.exe is version 9.1.370

    Zone alarm specs from the Product Tab are
    ZoneAlarm Extreme Security Version 9.1.037.000
    TrueVector security engine version 9.1.037.000
    Driver version
    9.1.037.000
    Anit-virus/Anti-spyware engine version 8.0.2.412
    Dat file version 998770976
    AntiSpam version 6.0.0.2383
    ZoneAlarm ForceField 1.5.53.4

    I have a Dell Dimension 8250 with Pentium 4 CPU 2.53GHz 1 Gb ram
    Running XP Professional Ver 2002 Service Pack 3 patched to date

  4. #4
    Join Date
    Jun 2006
    Location
    The 3rd Coast - South Central Texas
    Posts
    10,466

    Default Re: vsdatant.sys calling PQV2i.sys causes intermittent BSOD

    Quote Originally Posted by RustySam View Post
    My Internet provider also provides the zone alarm product (along with the license key) which they describe as

    "©2003-2009 CheckPoint Software Technologies Ltd. All right reserved. ZoneAlarm® Extreme Security and ZoneAlarm ForceField™ are registered trademarks of Check Point Software Technologies Ltd. or its affiliates."

    I just moved from ver 8.x.x.x within the last couple of weeks. This version is the latest for xp and install file zaZAX_Setup_en.exe is version 9.1.370

    Zone alarm specs from the Product Tab are
    ZoneAlarm Extreme Security Version 9.1.037.000
    TrueVector security engine version 9.1.037.000
    Driver version 9.1.037.000
    Anit-virus/Anti-spyware engine version 8.0.2.412
    Dat file version 998770976
    AntiSpam version 6.0.0.2383
    ZoneAlarm ForceField 1.5.53.4

    I have a Dell Dimension 8250 with Pentium 4 CPU 2.53GHz 1 Gb ram
    Running XP Professional Ver 2002 Service Pack 3 patched to date

    Thank you for your feedback..

    1.) it looks like your ISP has negotiated a modified Version of zoneAlarm to meet their Requirements?, in that case No other User outside of your IP providers Networks would have any Idea what's wrong with your version?
    You may have to Contact your IP Provider's Tech support for help..


    2.) If your ZA License key was provided to your IP Provider from Checkpoint, then you can Contact Checkpoint Tech support and inform them about your IP Provided version of ZAX and Details of your BSOD..

    Click on the Tech Support Link in my signature..

    3.) we are all Users here, Generally when you get a BSOD, that usually indicate one of two things.. A.) a Fault with your Windows OS?

    B.) Conflict between Two different Software Programs trying to ACCESS the Same Reserved Memory Location in Windows at the same time..


    Good Luck with either Tech Support..
    GeorgeV
    ZoneAlarm® Extreme Security


    Click here for ZA Support
    Monday-Saturday__ 6am to 10pm Central time
    Closed Sundays and Holidays

  5. #5
    naivemelody Guest

    Default Re: vsdatant.sys calling PQV2i.sys causes intermittent BSOD

    You may want to take a look at this post by 'drobison' - click here > http://forums.zonealarm.com/showthread.php?t=63698

    Check to see if the "vsdatant.sys" are correctly listed in your pc. If not, try to follow the steps outlined.

  6. #6
    RustySam Guest

    Default Re: vsdatant.sys calling PQV2i.sys causes intermittent BSOD

    Thanks for info. As I said initially I do not believe this to be a ZoneAlarm problem per-see (dump says PQV2i.sy to blame), but more realted to Norton Ghost setting a flag (PQV2i service loaded and running when it is not) that fools vsdatant into attempting an invalid operation. Just hoped someone else had experienced this and had some insight.

    When I checked the status of the vsdatant.sys driver (it was ok) I found the ZA Force Field driver icsak.sys anti-key logger did have a problem. I uninstalled the driver and re-installed ZA to correct the issue.

    The BSOD only occurs on a boot and is very intermittent and I could go 2 or 3 weeks without it occurring. Not sure what I am doing different to trigger it intermittently.

    Since I am thinking about replacing Ghost anyway I will not peruse this further (but still accepting any insight someone may have).

    Thanks

  7. #7
    RustySam Guest

    Default Re: vsdatant.sys calling PQV2i.sys causes intermittent BSOD

    Just an update. I had a problem with the ForceField Toolbar and enabled and disabled ForceField and rebooted several times while troubleshooting.

    This also seemed to bring up the BSOD (still related to PQV2i.sys) which I had 4 times within a hour or two as opposed to not seeing it for a week. So perhaps anything to do with ZA configuration or change may trigger the problem?

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
  •