Results 1 to 2 of 2

Thread: blue screen message

  1. #1
    alex_w Guest

    Default blue screen message

    Hello I have searched this topic quite through so I thought i would post this here.
    I am getting a big blue screen message saying BAD_POOL_CALLER and then shuts down.
    I read up and it sayed that i needed to update my zonealarm but i tryed and it sayed it was fully updated and also i just got this software like 2 months ago.
    I removed the software and now it is fine but I am just trying to find the problem cause i do like this software.

    I debugged the error through WinDbr and I got this:
    Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\Alex\Desktop\blue screen error\blue screen error\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*c:\websymbols*ttp://
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Sat Mar 22 22:14:04.137 2008 (GMT-4)
    System Uptime: 0 days 0:01:50.844
    Loading Kernel Symbols
    .................................................. .................... .................................................. ................
    Loading User Symbols

    Loading unloaded module list
    ************************************************** ******************** *********
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** ******************** *********

    Use !analyze -v to get detailed debugging information.

    BugCheck C2, {7, cd4, 2060004, 88d31688}

    *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys

    Probably caused by : vsdatant.sys ( vsdatant+450c1 )

    Followup: MachineOwner

    0: kd> !analyze -v
    ************************************************** ******************** *********
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** ******************** *********

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

    Debugging Details:

    POOL_ADDRESS: 88d31688 Nonpaged pool


    BUGCHECK_STR: 0xc2_7_TCPc


    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from 8054a583 to 804f9deb

    bad038b8 8054a583 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
    bad03908 a98883f5 88d31688 00000000 bad03950 nt!ExFreePoolWithTag+0x2a3
    bad03918 a9887c85 89d28008 89d2809c 89d2809c tcpip!TCPClose+0x16
    bad03950 a983a0c1 890f2f18 89d28008 a98399cd tcpip!TCPDispatch+0x101
    WARNING: Stack unwind information not available. Following frames may be wrong.
    bad0395c a98399cd 890f2f18 89d28008 00000002 vsdatant+0x450c1
    bad03990 a983a04a 890f2f18 89d28008 89d28008 vsdatant+0x449cd
    bad039b4 a9839ee7 88c21680 a983a057 89d28008 vsdatant+0x4504a
    bad039bc a983a057 89d28008 89061d68 89103e18 vsdatant+0x44ee7
    bad039cc 80502909 88db6810 88a85538 88db680b vsdatant+0x45057
    89103e18 890f2f18 00000000 890f2f18 00000000 nt!KiReadyThread+0x305
    89103e1c 00000000 890f2f18 00000000 00000000 0x890f2f18


    a983a0c1 c20c00 ret 0Ch


    SYMBOL_NAME: vsdatant+450c1

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: vsdatant

    IMAGE_NAME: vsdatant.sys


    FAILURE_BUCKET_ID: 0xc2_7_TCPc_vsdatant+450c1

    BUCKET_ID: 0xc2_7_TCPc_vsdatant+450c1

    Followup: MachineOwner

  2. #2
    Join Date
    Dec 2005

    Default Re: blue screen message

    Usually a bad driver or out of date driver.

    Try updating all your drivers ...printer, all deivces found in the Device Manager, vendor's hardware updater, windows update. video card, sound card, mother board, usb driver, network connections, etc.

    Sometimes that can even be wrong and the latest driver has bugs whereas the previous older driver had not issues and worked fine. Not usually seen but not unheard of.

    A kernel-mode process or driver incorrectly attempted to perform memory operations the usual quote or a long that line.

    Best regards.

Thread Information

Users Browsing this Thread

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


Posting Permissions

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