Results 1 to 4 of 4

Thread: vsdatant.sys Error?

  1. #1
    gober Guest

    Default vsdatant.sys Error?

    Hi,

    Sometimes i got BSOD and i already try to discuss with other forum and they tell to me dump error report show vsdatant.sys. How must i do? original topic http://www.msfn.org/board/Bad-pool-c...58#entry790158

    DUMP
    indows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp.080413-2111
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Thu Aug 21 04:48:05.484 2008 (GMT+2)
    System Uptime: 0 days 4:15:37.190

    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 00000007, Attempt to free pool which was already freed
    Arg2: 00000cd4, (reserved)
    Arg3: 02060001, Memory contents of the pool block
    Arg4: 888ac380, Address of the block of pool being deallocated

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    STACK_TEXT:
    bacf78b8 8054b583 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
    bacf7908 ae962782 888ac380 00000000 bacf7950 nt!ExFreePoolWithTag+0x2a3
    bacf7918 ae962450 888f9c68 888f9cfc 888f9cfc tcpip!TCPClose+0x16
    bacf7950 ae8ef0c1 8a0af5e8 888f9c68 ae8ee9cd tcpip!TCPDispatch+0x101
    bacf795c ae8ee9cd 8a0af5e8 888f9c68 00000002 vsdatant+0x450c1
    bacf7990 ae8ef04a 8a0af5e8 888f9c68 888f9c68 vsdatant+0x449cd
    bacf79b4 ae8eeee7 897e87a0 ae8ef057 888f9c68 vsdatant+0x4504a
    bacf79bc ae8ef057 888f9c68 8a0ab5e0 8a0a60d8 vsdatant+0x44ee7
    bacf79ec 8053721f 00000000 bacf7a28 80537283 vsdatant+0x45057
    bacf7a40 bab384c9 ae999690 bab384d4 ae998000 nt!ExNotifyCallback+0x43
    bacf7a58 ae965c0b 02999680 ae965c16 898636f4 TDI!CTEScheduleDelayedEvent+0x35
    bacf7a70 ae95b65a 8a0b0da8 02cf7ab0 00000001 tcpip!LoopXmit+0x6a
    bacf7aa0 ae95b79f ae9994c0 0100007f 88bf0880 tcpip!SendIPPacket+0x193
    bacf7bec 888e5d68 00000000 89032c68 00000000 tcpip!IPTransmit+0x289e
    bacf7c48 804ef18f 8a0af5e8 888f9c68 888f9c68 0x888e5d68
    bacf7cbc 80583af8 888e5d68 00000000 00000000 nt!IopfCallDriver+0x31
    bacf7cf4 805bb466 008e5d80 00000000 888e5d68 nt!IopDeleteFile+0x132
    bacf7d10 805266ca 888e5d80 00000000 8052667e nt!ObpRemoveObjectRoutine+0xe0
    bacf7d28 ae88bc0f 88944468 889443f0 ae888cb6 nt!ObfDereferenceObject+0x4c
    bacf7d3c ae88bbbc 889443f0 ae88a7a8 bacf7d68 afd!AfdFreeConnectionResources+0x38
    bacf7d4c ae88886a 88944468 8a12a1f0 8a215740 afd!AfdFreeConnection+0x5c
    bacf7d68 80576ad5 8a215740 00000000 8056485c afd!AfdDoWork+0x51
    bacf7d7c 8053876d 8a12a1f0 00000000 8a5bd8b8 nt!IopProcessWorkItem+0x13
    bacf7dac 805cff64 8a12a1f0 00000000 00000000 nt!ExpWorkerThread+0xef
    bacf7ddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

    FOLLOWUP_IP:
    vsdatant+450c1
    ae8ef0c1 c20c00 ret 0Ch

    1: kd> !pool 888ac380
    Pool page 888ac380 region is Nonpaged pool
    888ac000 size: 228 previous size: 0 (Free) GeN-
    888ac228 size: 70 previous size: 228 (Allocated) GeN-
    888ac298 size: 8 previous size: 70 (Free) AfdC
    888ac2a0 size: d0 previous size: 8 (Allocated) FMsl
    888ac370 size: 8 previous size: d0 (Free) File
    *888ac378 size: 30 previous size: 8 (Free) *TCPc
    Pooltag TCPc : TCP/IP network protocol, Binary : TCP
    888ac3a8 size: c58 previous size: 30 (Free) Ddk

    1: kd> dc 888ac378 888ac3a8-1
    888ac378 02060001 63504354 88adb188 00000000 ....TCPc........
    888ac388 bad00101 02040001 00000000 888ac394 ................
    888ac398 888ac394 899a9c18 888f9c68 00000000 ........h.......

    1: kd> lmvm vsdatant
    start end module name
    ae8aa000 ae9090e0 vsdatant (no symbols)
    Loaded symbol image file: vsdatant.sys
    Image path: \SystemRoot\System32\vsdatant.sys
    Image name: vsdatant.sys
    Timestamp: Wed Jul 09 17:33:32 2008 (4874DA4C)
    CheckSum: 00068FDC
    ImageSize: 0005F0E0
    File version: 7.0.483.0
    Product version: 7.0.483.0
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 2.0 Dll
    File date: 00000000.00000000
    Translations: 0409.04e4
    CompanyName: Zone Labs, LLC
    ProductName: TrueVector Device Driver
    InternalName: vsdatant
    OriginalFilename: vsdatant.sys
    ProductVersion: 7.0.483.000
    FileVersion: 7.0.483.000
    FileDescription: TrueVector Device Driver
    LegalCopyright: Copyright
    1998-2006, Zone Labs, LLC

    Thank
    Anton

    Operating System:Windows XP Pro
    Software Version:7.0
    Product Name:ZoneAlarm Pro

  2. #2
    Join Date
    Dec 2005
    Posts
    9,057

    Default Re: vsdatant.sys Error?

    <blockquote><hr>gober wrote:
    Hi,

    Sometimes i got BSOD and i already try to discuss with other forum and they tell to me dump error report show vsdatant.sys. How must i do? original topic http://www.msfn.org/board/Bad-pool-c...58#entry790158

    DUMP
    indows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp.080413-2111
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Thu Aug 21 04:48:05.484 2008 (GMT+2)
    System Uptime: 0 days 4:15:37.190

    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 00000007, Attempt to free pool which was already freed
    Arg2: 00000cd4, (reserved)
    Arg3: 02060001, Memory contents of the pool block
    Arg4: 888ac380, Address of the block of pool being deallocated

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    STACK_TEXT:
    bacf78b8 8054b583 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
    bacf7908 ae962782 888ac380 00000000 bacf7950 nt!ExFreePoolWithTag+0x2a3
    bacf7918 ae962450 888f9c68 888f9cfc 888f9cfc tcpip!TCPClose+0x16
    bacf7950 ae8ef0c1 8a0af5e8 888f9c68 ae8ee9cd tcpip!TCPDispatch+0x101
    bacf795c ae8ee9cd 8a0af5e8 888f9c68 00000002 vsdatant+0x450c1
    bacf7990 ae8ef04a 8a0af5e8 888f9c68 888f9c68 vsdatant+0x449cd
    bacf79b4 ae8eeee7 897e87a0 ae8ef057 888f9c68 vsdatant+0x4504a
    bacf79bc ae8ef057 888f9c68 8a0ab5e0 8a0a60d8 vsdatant+0x44ee7
    bacf79ec 8053721f 00000000 bacf7a28 80537283 vsdatant+0x45057
    bacf7a40 bab384c9 ae999690 bab384d4 ae998000 nt!ExNotifyCallback+0x43
    bacf7a58 ae965c0b 02999680 ae965c16 898636f4 TDI!CTEScheduleDelayedEvent+0x35
    bacf7a70 ae95b65a 8a0b0da8 02cf7ab0 00000001 tcpip!LoopXmit+0x6a
    bacf7aa0 ae95b79f ae9994c0 0100007f 88bf0880 tcpip!SendIPPacket+0x193
    bacf7bec 888e5d68 00000000 89032c68 00000000 tcpip!IPTransmit+0x289e
    bacf7c48 804ef18f 8a0af5e8 888f9c68 888f9c68 0x888e5d68
    bacf7cbc 80583af8 888e5d68 00000000 00000000 nt!IopfCallDriver+0x31
    bacf7cf4 805bb466 008e5d80 00000000 888e5d68 nt!IopDeleteFile+0x132
    bacf7d10 805266ca 888e5d80 00000000 8052667e nt!ObpRemoveObjectRoutine+0xe0
    bacf7d28 ae88bc0f 88944468 889443f0 ae888cb6 nt!ObfDereferenceObject+0x4c
    bacf7d3c ae88bbbc 889443f0 ae88a7a8 bacf7d68 afd!AfdFreeConnectionResources+0x38
    bacf7d4c ae88886a 88944468 8a12a1f0 8a215740 afd!AfdFreeConnection+0x5c
    bacf7d68 80576ad5 8a215740 00000000 8056485c afd!AfdDoWork+0x51
    bacf7d7c 8053876d 8a12a1f0 00000000 8a5bd8b8 nt!IopProcessWorkItem+0x13
    bacf7dac 805cff64 8a12a1f0 00000000 00000000 nt!ExpWorkerThread+0xef
    bacf7ddc 805460de 8053867e 00000001 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

    FOLLOWUP_IP:
    vsdatant+450c1
    ae8ef0c1 c20c00 ret 0Ch

    1: kd> !pool 888ac380
    Pool page 888ac380 region is Nonpaged pool
    888ac000 size: 228 previous size: 0 (Free) GeN-
    888ac228 size: 70 previous size: 228 (Allocated) GeN-
    888ac298 size: 8 previous size: 70 (Free) AfdC
    888ac2a0 size: d0 previous size: 8 (Allocated) FMsl
    888ac370 size: 8 previous size: d0 (Free) File
    *888ac378 size: 30 previous size: 8 (Free) *TCPc
    Pooltag TCPc : TCP/IP network protocol, Binary : TCP
    888ac3a8 size: c58 previous size: 30 (Free) Ddk

    1: kd> dc 888ac378 888ac3a8-1
    888ac378 02060001 63504354 88adb188 00000000 ....TCPc........
    888ac388 bad00101 02040001 00000000 888ac394 ................
    888ac398 888ac394 899a9c18 888f9c68 00000000 ........h.......

    1: kd> lmvm vsdatant
    start end module name
    ae8aa000 ae9090e0 vsdatant (no symbols)
    Loaded symbol image file: vsdatant.sys
    Image path: \SystemRoot\System32\vsdatant.sys
    Image name: vsdatant.sys
    Timestamp: Wed Jul 09 17:33:32 2008 (4874DA4C)
    CheckSum: 00068FDC
    ImageSize: 0005F0E0
    File version: 7.0.483.0
    Product version: 7.0.483.0
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 2.0 Dll
    File date: 00000000.00000000
    Translations: 0409.04e4
    CompanyName: Zone Labs, LLC
    ProductName: TrueVector Device Driver
    InternalName: vsdatant
    OriginalFilename: vsdatant.sys
    ProductVersion: 7.0.483.000
    FileVersion: 7.0.483.000
    FileDescription: TrueVector Device Driver
    LegalCopyright: Copyright
    1998-2006, Zone Labs, LLC

    Thank
    Anton

    Operating System:
    Windows XP Pro
    Software Version:
    7.0
    Product Name:
    ZoneAlarm Pro

    <hr></blockquote>
    See Demystifying the 'Blue Screen of Death' as per MS.

    The listing for the "0x000000C2: BAD_POOL_CALLER" seen here.
    This has some basic information.

    The best source of informationfor the bsod and the "bug codes" (as described by MS themselves) is to be found at MS.
    See Bug Check 0xC2: BAD_POOL_CALLER.

    Usually solution for a bad pool caller is update the drivers.
    Update windows drivers as seen here.
    Additionally the hidden drivers can be updated by checking the "show hidden devices" in the View in the toolbar, once the Device Manager has been opened.

    Very often it is not the first driver/application listed in the events of the bsod, but the last driver/application in the listing of events. Yes the vsdatant.sys is in trouble, but what caused this to happen is the more appropiate question.
    It could be out dated drivers for the hardware and for windows that is the cause of the bsod.
    It could be a driver from some other security application that caused the vsdatant.sys issue.
    Or perhaps a driver left over from a previous uninstallation.

    Hardware is often a cause of the bsod. Bad memory cards and bad sectors in the hard disk drive (or even a failing hard disk drive) can be the cause of a bsod. Probably the most common hardware issues. Included is the sound/graphics/network cards as sources of hardware issues for the bsod.
    Overheating of the drive or the cpu or the motherboard can cause issues. So can overclocking the cpu/memory/bus speeds/etc.
    Power spikes in the power supply or a uneven power levels can cause issues.


    MS initiated years ago the bug reporting about the bsod from the consumers. MS immediately saw and still sees to this day that most bsod issues are not caused by the operating system but by the drivers and the hardware.
    Bad drivers and bad hardware is the main cause of all bsod problems.

    After doing the update of the drivers, I would suggest to do a disk check and a system file check and then followed up by a hard drive defragmentation.
    If the problem still persists, then check the memory cards doing a mem test as found here.

    If you posses a hardware diagnotics disk for your computer as supplied by the manufacture of the computer or from the manufactures of the various components that make your computer, I would strongly suggest to use this extra checking tool(s).
    It can prove to be a valuable and very useful tool.


    Oldsod.

    Message Edited by Oldsod on 08-24-2008 09:55 AM
    Best regards.
    oldsod

  3. #3
    gober Guest

    Default Re: vsdatant.sys Error?

    Dear Oldsod,

    I already update all my latest driver, but sometime i still got BSOD. Here my SS memory test http://piload.com/files/show/mmznqm3to1vmzdwmqgiw.jpg

    Btw how to check my hardisk? I'm used raid 0 controller.

    Anyways i also try to ask other forum and they are say maybe the problem from vmware or ZA ( http://www.msfn.org/board/Bad-pool-c...26#entry791426 ). i already uninstall vmware and still same. I'm still waiting from microsoft support email before try uninstall ZA and let see later

    Thank you
    Anton

  4. #4
    Join Date
    Dec 2005
    Posts
    9,057

    Default Re: vsdatant.sys Error?

    Raid.... I am not even going to get involved with that.
    Maybe done in the controller or in the bios to get the check disk performed and I am unsure if the saved data is useable once finished.
    Best check with the vendor of the drives or the computer or the array configuration.
    They should have some knowledge base or FAQ or some technical support.

    The mem looks good.
    VM and windows and the ZA should be okay, as far as I know of but that was almost a year ago.
    So my own knowledge base maybe a little out dated.

    Oldsod.
    Best regards.
    oldsod

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
  •