1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Bad Pool Caller

Discussion in 'Windows 7' started by antariksh, Jul 22, 2012.

Thread Status:
Not open for further replies.
Advertisement
  1. antariksh

    antariksh Thread Starter

    Joined:
    Jul 22, 2012
    Messages:
    4
    I am Experiencing Bad Pool Caller BSOD
    While Running a Backup over FTP Software called QLC Backtrack
    I am Backing up over WiFi. Total Data size in approx 50Gb
    My Operating System: Windows 7 Home Premium
    Machine: Dell Studio 15 Laptop

    I am Attaching herewith minidump file and wer file
    i ran Memory test tool in dell dignostics
    No errors were found.

    Please Help


    OS Version: Microsoft Windows 7 Home Premium, Service Pack 1, 64 bit
    Processor: Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz, Intel64 Family 6 Model 37 Stepping 5
    Processor Count: 4
    RAM: 1972 Mb
    Graphics Card: ATI Mobility Radeon HD 4500 Series, 512 Mb
    Hard Drives: C: Total - 233299 MB, Free - 171293 MB; D: Total - 233308 MB, Free - 165114 MB;
    Motherboard: Dell Inc., 0NJWJR
    Antivirus: Quick Heal Internet Security 13.00, Updated and Enabled

    Update:
    I ran a sfc /scannow

    windows resource protection did not find any integrity violations
    Also ran memory test.
    No errors found
     

    Attached Files:

  2. Lance1

    Lance1

    Joined:
    Aug 4, 2003
    Messages:
    5,489
    The file responsible is wstif.sys which belongs to Quick Heal AntiVirus Try disabling Quick Heal and run the backup and then re-enable Quick Heal AntiVirus.
     
  3. antariksh

    antariksh Thread Starter

    Joined:
    Jul 22, 2012
    Messages:
    4
    Thank you sir for pointing out the exact file.
    I have contacted Quick Heal Antivirus Support
    i will see if they can assist me in this matter
     
  4. Lance1

    Lance1

    Joined:
    Aug 4, 2003
    Messages:
    5,489
    Your Welcome. Let us know how it goes.
     
  5. antariksh

    antariksh Thread Starter

    Joined:
    Jul 22, 2012
    Messages:
    4
    Dear Lance1
    Quick Heal Support is asking me how i could determine that wstif.sys is causing the BSOD.
    What do i tell them?
     
  6. Lance1

    Lance1

    Joined:
    Aug 4, 2003
    Messages:
    5,489
    Give them the crash dump file. Here it is. Copy and past it into notepad and send it to them.

    PHP:
    Microsoft (RWindows Debugger Version 6.12.0002.633 AMD64
    Copyright 
    (cMicrosoft CorporationAll rights reserved.


    Loading Dump File [C:\Users\Lance1\Desktop\072212-18392-01\072212-18392-01.dmp]
    Mini Kernel Dump FileOnly registers and stack trace are available

    Symbol search path is
    SRV*your local folder for symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is
    Windows 7 Kernel Version 7601 (Service Pack 1MP (4 procsFree x64
    Product
    WinNtsuiteTerminalServer SingleUserTS Personal
    Built by
    7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Machine Name
    :
    Kernel base 0xfffff800`02c5a000 PsLoadedModuleList = 0xfffff800`02e9e670
    Debug session time
    Sun Jul 22 01:12:44.862 2012 (UTC 6:00)
    System Uptime0 days 0:51:37.035
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................................
    Loading User Symbols
    Loading unloaded module 
    list
    ........
    *******************************************************************************
    *                                                                             *
    *                        
    Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !
    analyze -v to get detailed debugging information.

    BugCheck C2, {7109b300c3fffffa8003fc4c40}

    Unable to load image \SystemRoot\system32\drivers\wstif.sysWin32 error 0n2
    *** WARNINGUnable to verify timestamp for wstif.sys
    *** ERRORModule load completed but symbols could not be loaded for wstif.sys
    GetPointerFromAddress
    unable to read from fffff80002f08100
    Probably caused by 
    wstif.sys wstif+333b )

    FollowupMachineOwner
    ---------

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

    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 allocationetc.
    Arguments:
    Arg10000000000000007Attempt to free pool which was already freed
    Arg2
    000000000000109b, (reserved)
    Arg300000000000300c3Memory contents of the pool block
    Arg4
    fffffa8003fc4c40Address of the block of pool being deallocated

    Debugging Details
    :
    ------------------


    POOL_ADDRESS:  fffffa8003fc4c40 

    FREED_POOL_TAG
    :  LPBA

    BUGCHECK_STR
    :  0xc2_7_LPBA

    CUSTOMER_CRASH_COUNT
    :  1

    DEFAULT_BUCKET_ID
    :  VISTA_DRIVER_FAULT

    PROCESS_NAME
    :  javaw.exe

    CURRENT_IRQL
    :  0

    LAST_CONTROL_TRANSFER
    :  from fffff80002e03be9 to fffff80002cd91c0

    STACK_TEXT
    :  
    fffff880`0817eec8 fffff800`02e03be9 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`000300c3 nt!KeBugCheckEx
    fffff880
    `0817eed0 fffff880`0157833b 00000000`00000000 fffffa80`01e8b450 fffffa80`06c75180 fffffa80`06c75180 nt!ExDeferredFreePool+0x1201
    fffff880
    `0817ef80 00000000`00000000 fffffa80`01e8b450 fffffa80`06c75180 fffffa80`06c75180 fffff880`0157f0c0 wstif+0x333b


    STACK_COMMAND
    :  kb

    FOLLOWUP_IP

    wstif+333b
    fffff880
    `0157833b ??              ???

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  wstif+333b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: wstif

    IMAGE_NAME:  wstif.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4f588ded

    FAILURE_BUCKET_ID:  X64_0xc2_7_LPBA_wstif+333b

    BUCKET_ID:  X64_0xc2_7_LPBA_wstif+333b

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

     
  7. antariksh

    antariksh Thread Starter

    Joined:
    Jul 22, 2012
    Messages:
    4
    Thank you for the above crash dump analysis

    Please help me with debugging this file also this is a seperate PC with Same problem.
    Is this also Due to Quick heal??
    Please also post crash dump file of this PC.

    OS Version: Microsoft Windows 7 Ultimate, 32 bit
    Processor: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz, x64 Family 6 Model 37 Stepping 5
    Processor Count: 4
    RAM: 1909 Mb
    Graphics Card: Intel(R) HD Graphics, 730 Mb
    Hard Drives: C: Total - 76837 MB, Free - 59177 MB; D: Total - 199999 MB, Free - 194234 MB; E: Total - 199999 MB, Free - 199322 MB;
    Motherboard: Intel Corporation, DH55TC
    Antivirus: Quick Heal Internet Security 13.00, Updated and Enabled
     

    Attached Files:

  8. Lance1

    Lance1

    Joined:
    Aug 4, 2003
    Messages:
    5,489
    Yes, its the same error.

    PHP:
    Microsoft (RWindows Debugger Version 6.12.0002.633 AMD64
    Copyright 
    (cMicrosoft CorporationAll rights reserved.


    Loading Dump File [C:\Users\Lance1\Desktop\072412-13681-01\072412-13681-01.dmp]
    Mini Kernel Dump FileOnly registers and stack trace are available

    Symbol search path is
    SRV*your local folder for symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is
    Windows 7 Kernel Version 7600 MP (4 procsFree x86 compatible
    Product
    WinNtsuiteTerminalServer SingleUserTS
    Built by
    7600.16385.x86fre.win7_rtm.090713-1255
    Machine Name
    :
    Kernel base 0x82c4b000 PsLoadedModuleList 0x82d93810
    Debug session time
    Tue Jul 24 07:02:29.295 2012 (UTC 6:00)
    System Uptime0 days 0:11:51.824
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................
    Loading User Symbols
    Loading unloaded module 
    list
    ......
    *******************************************************************************
    *                                                                             *
    *                        
    Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !
    analyze -v to get detailed debugging information.

    BugCheck D1, {408208d85c718}

    Unable to load image \SystemRoot\system32\drivers\wstif.sysWin32 error 0n2
    *** WARNINGUnable to verify timestamp for wstif.sys
    *** ERRORModule load completed but symbols could not be loaded for wstif.sys
    *** WARNINGUnable to verify timestamp for emltdi.sys
    *** ERRORModule load completed but symbols could not be loaded for emltdi.sys
    Probably caused by 
    wstif.sys wstif+5718 )

    FollowupMachineOwner
    ---------

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalidaddress at an
    interrupt request level 
    (IRQLthat is too high.  This is usually
    caused by drivers using improper addresses
    .
    If 
    kernel debugger is available get stack backtrace.
    Arguments:
    Arg100000408memory referenced
    Arg2
    00000002IRQL
    Arg3
    00000000value 0 read operationwrite operation
    Arg4
    8d85c718address which referenced memory

    Debugging Details
    :
    ------------------


    READ_ADDRESSGetPointerFromAddressunable to read from 82db3718
    Unable to read MiSystemVaType memory at 82d93160
     00000408 

    CURRENT_IRQL
    :  2

    FAULTING_IP

    wstif+5718
    8d85c718 8b4708          mov     eax
    ,dword ptr [edi+8]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID
    :  VISTA_DRIVER_FAULT

    BUGCHECK_STR
    :  0xD1

    PROCESS_NAME
    :  javaw.exe

    TRAP_FRAME
    :  ab1634b4 -- (.trap 0xffffffffab1634b4)
    ErrCode 00000000
    eax
    =ffffffff ebx=8d85c540 ecx=850e80e0 edx=850bf940 esi=8d8641a8 edi=00000400
    eip
    =8d85c718 esp=ab163528 ebp=ab16353c iopl=0         nv up ei pl nz na pe nc
    cs
    =0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
    wstif
    +0x5718:
    8d85c718 8b4708          mov     eax,dword ptr [edi+8ds:0023:00000408=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER
    :  from 8d85c718 to 82c917eb

    STACK_TEXT
    :  
    ab1634b4 8d85c718 badb0d00 850bf940 ab1634d4 nt!KiTrap0E+0x2cf
    WARNING
    Stack unwind information not availableFollowing frames may be wrong.
    ab16353c 8d86150d 8d864180 850e80e0 86b1f4f0 wstif+0x5718
    ab163554 8d85b6e9 8d864600 850bf940 854b5128 wstif
    +0xa50d
    ab163584 8d857711 85e4d9d0 8549d810 c000009a wstif
    +0x46e9
    ab1635b0 8d857e1d 00000000 85e4d9d0 00000000 wstif
    +0x711
    ab1635dc 8d85824c 00000000 85e4d9d0 854475e0 wstif
    +0xe1d
    ab163618 8d85847c 85e4d9d0 8549d810 8d864600 wstif
    +0x124c
    ab163634 82c874bc 85e4d9d0 8549d810 c0000010 wstif
    +0x147c
    ab16364c 8d85a204 85e4d028 ab163670 82c874bc nt
    !IofCallDriver+0x63
    ab163658 82c874bc 85e4d028 8549d810 8549d810 wstif
    +0x3204
    ab163670 937639eb 850bf940 86b87800 ab163698 nt
    !IofCallDriver+0x63
    ab163680 82c874bc 86b87800 8549d810 850bf99c emltdi
    +0x9eb
    ab163698 82e8b62d 8ce17d75 ab163840 00000000 nt
    !IofCallDriver+0x63
    ab163770 82e6c1d7 85e4d9d0 a5dd26e0 b968b468 nt
    !IopParseDevice+0xed7
    ab1637ec 82e9224d 00000000 ab163840 00000240 nt
    !ObpLookupObjectName+0x4fa
    ab163848 82e8a5ab ab163a9c 84dd26e0 ab163800 nt
    !ObOpenObjectByName+0x159
    ab1638c4 82ec1d99 ab163adc 02000000 ab163a9c nt
    !IopCreateFile+0x673
    ab163920 8d87f031 ab163adc 02000000 ab163a9c nt
    !IoCreateFileEx+0x9e
    ab163b64 8d87bfb0 850e40c8 853e32a0 00000016 afd
    !AfdTdiCreateAO+0x573
    ab163bec 8d888504 b529fcf8 85e427e0 ab163c14 afd
    !AfdBind+0x37a
    ab163bfc 82c874bc 85e427e0 85631a48 85631a48 afd
    !AfdDispatchDeviceControl+0x3b
    ab163c14 82e88eee b529fcf8 85631a48 85631b24 nt
    !IofCallDriver+0x63
    ab163c34 82ea5cd1 85e427e0 b529fcf8 00000000 nt
    !IopSynchronousServiceTail+0x1f8
    ab163cd0 82ea84ac 85e427e0 85631a48 00000000 nt
    !IopXxxControlFile+0x6aa
    ab163d04 82c8e42a 000007ec 000004d0 00000000 nt
    !NtDeviceIoControlFile+0x2a
    ab163d04 772064f4 000007ec 000004d0 00000000 nt
    !KiFastCallEntry+0x12a
    2cfff0e0 00000000 00000000 00000000 00000000 0x772064f4


    STACK_COMMAND
    :  kb

    FOLLOWUP_IP

    wstif+5718
    8d85c718 8b4708          mov     eax
    ,dword ptr [edi+8]

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME
    :  wstif+5718

    FOLLOWUP_NAME
    :  MachineOwner

    MODULE_NAME
    wstif

    IMAGE_NAME
    :  wstif.sys

    DEBUG_FLR_IMAGE_TIMESTAMP
    :  4f588df1

    FAILURE_BUCKET_ID
    :  0xD1_wstif+5718

    BUCKET_ID
    :  0xD1_wstif+5718

    Followup
    MachineOwner
    ---------

     
  9. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/1062102