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.

Solved: Blue screen crash. BAD_POOL_CALLER

Discussion in 'Windows 7' started by Memorize, Dec 27, 2012.

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

    Memorize Thread Starter

    Joined:
    Dec 26, 2012
    Messages:
    8
    Hello tech's.

    I have had the error screen of BAD_POOL_CALLER now a few times. normal once every few days. I've only seen it happen when gaming and I can't figure it out. I don't have a application to read dmp files. It would be great for some help.

    Here is the minidump file.

    Thanks :)
     

    Attached Files:

  2. Lance1

    Lance1

    Joined:
    Aug 4, 2003
    Messages:
    5,618
    Welcome again Memorize!

    That's a shortcut in the zip file. you need to make a Copy of the dump file. copy it to a folder on the desktop and zip it up and upload.
     
  3. Memorize

    Memorize Thread Starter

    Joined:
    Dec 26, 2012
    Messages:
    8
    Ah crap I wasn't paying attention. Here ya go :)

    Maybe I did it right this time :p
     

    Attached Files:

    • dmp.zip
      File size:
      48.4 KB
      Views:
      21
  4. huggie54

    huggie54

    Joined:
    Feb 17, 2008
    Messages:
    2,637
    hiya,this is related to network drivers,try this.Open a command prompt, right click on the command prompt icon and select run as administrator, then type this command, netsh winsock reset

    Press enter

    Reboot/restart your computer.
     
  5. huggie54

    huggie54

    Joined:
    Feb 17, 2008
    Messages:
    2,637
    sorry these are for windows 7.
    Fix Winsock Manually on Windows 7

    1. Open up the command line utility and enter:

    netsh winsock reset catalog (resets winsock entries)
    netsh int ip reset reset.log hit (resets TCP/IP stack)


    2. Reboot your PC
     
  6. Memorize

    Memorize Thread Starter

    Joined:
    Dec 26, 2012
    Messages:
    8
    Thanks for the quick response.

    I did both cmd lines, and restarted. As I won't be able to tell if this works right away. I'll let you guys know if I crash again within 48 hours. Is there anything else in the crash log that has a sign that could be the cause?

    Cheers :)
     
  7. Lance1

    Lance1

    Joined:
    Aug 4, 2003
    Messages:
    5,618
    The problem file is "dxgmms1.sys" Directx runs in conjunction with the video card so I would update the video drivers. Please post the results.

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


    Loading Dump File [C:\Users\LG-PC7\Desktop\dmp\dmp\122612-6723-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 (8 procsFree x64
    Product
    WinNtsuiteTerminalServer SingleUserTS
    Built by
    7601.17944.amd64fre.win7sp1_gdr.120830-0333
    Machine Name
    :
    Kernel base 0xfffff800`03c5c000 PsLoadedModuleList = 0xfffff800`03ea0670
    Debug session time
    Wed Dec 26 20:13:01.960 2012 (UTC 8:00)
    System Uptime0 days 5:28:19.756
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module 
    list
    .............
    *******************************************************************************
    *                                                                             *
    *                        
    Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !
    analyze -v to get detailed debugging information.

    BugCheck 1000007E, {ffffffffc0000005fffff88004955cf7fffff880063df568fffff880063dedc0}

    Probably caused by dxgmms1.sys dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b )

    FollowupMachineOwner
    ---------

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

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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 hitbut this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code
    but ...
    If 
    this happensmake sure a debugger gets connected, and the
    system is booted 
    /DEBUG.  This will let us see why this breakpoint is
    happening
    .
    Arguments:
    Arg1ffffffffc0000005The exception code that was not handled
    Arg2
    fffff88004955cf7The address that the exception occurred at
    Arg3
    fffff880063df568Exception Record Address
    Arg4
    fffff880063dedc0Context Record Address

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


    EXCEPTION_CODE: (NTSTATUS0xc0000005 The instruction at 0x%08lx referenced memory at 0x%08lxThe memory could not be %s.

    FAULTING_IP
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
    fffff880
    `04955cf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

    EXCEPTION_RECORD:  fffff880063df568 -- (.exr 0xfffff880063df568)
    ExceptionAddress: fffff88004955cf7 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x000000000000002b)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000054
    Attempt to read from address 0000000000000054

    CONTEXT:  fffff880063dedc0 -- (.cxr 0xfffff880063dedc0)
    rax=fffff8a00d813e10 rbx=0000000000000000 rcx=fffffa8012507000
    rdx=fffffa8013fed9a0 rsi=fffffa8012507000 rdi=fffffa8012507000
    rip=fffff88004955cf7 rsp=fffff880063df7a0 rbp=fffffa801444de60
     r8=fffffa8014856401  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000148 r12=fffffa8013fed9a0 r13=0000000000000001
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b:
    fffff880
    `04955cf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh ds:002b:00000000`00000054=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

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

    EXCEPTION_PARAMETER1:  0000000000000000

    EXCEPTION_PARAMETER2:  0000000000000054

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003f0a100
     0000000000000054 

    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b
    fffff880
    `04955cf7 0fba63540d      bt      dword ptr [rbx+54h],0Dh

    BUGCHECK_STR
    :  0x7E

    DEFAULT_BUCKET_ID
    :  NULL_CLASS_PTR_DEREFERENCE

    LAST_CONTROL_TRANSFER
    :  from fffff88004952ed3 to fffff88004955cf7

    STACK_TEXT
    :  
    fffff880`063df7a0 fffff880`04952ed3 00000000`00000000 fffffa80`143d84c8 00000000`000000af 00000000`00000000 dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x2b
    fffff880
    `063df7d0 fffff880`0496d65d 00000000`00000000 fffff8a0`093fdbd0 fffffa80`00000000 fffffa80`14856460 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
    fffff880
    `063df9a0 fffff880`0496d398 fffff880`03695040 fffff880`0496cd00 fffffa80`00000000 fffffa80`00000000 dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880
    `063dfb90 fffff880`0496ce96 00000000`00000000 fffffa80`11943ce0 00000000`00000080 fffffa80`124df010 dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880
    `063dfbc0 fffff800`03f71e5a 00000000`013a341d fffffa80`12506060 fffffa80`0c9f49e0 fffffa80`12506060 dxgmms1!VidSchiWorkerThread+0xd6
    fffff880
    `063dfc00 fffff800`03ccbd26 fffff880`03690180 fffffa80`12506060 fffff880`0369b0c0 00000000`00000000 nt!PspSystemThreadStartup+0x5a
    fffff880
    `063dfc40 00000000`00000000 fffff880`063e0000 fffff880`063da000 fffff880`063df540 00000000`00000000 nt!KxStartSystemThread+0x16


    SYMBOL_STACK_INDEX
    :  0

    SYMBOL_NAME
    :  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

    FOLLOWUP_NAME
    :  MachineOwner

    MODULE_NAME
    dxgmms1

    IMAGE_NAME
    :  dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP
    :  4ce799c1

    STACK_COMMAND
    :  .cxr 0xfffff880063dedc0 kb

    FAILURE_BUCKET_ID
    :  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

    BUCKET_ID
    :  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+2b

    Followup
    MachineOwner
    ---------

     
  8. Memorize

    Memorize Thread Starter

    Joined:
    Dec 26, 2012
    Messages:
    8
    Well I already have the latest drivers for my card, its a SLI Nvidia 670 setup with v. 310.70 WHQL drivers. Anything else Lance?

    Cheers.
     
  9. Lance1

    Lance1

    Joined:
    Aug 4, 2003
    Messages:
    5,618
    Try running dxdiag from the run command. (Windows key + R) let it run, just a minute or two, check the display tad. At the bottom, does it say there are any issues? Also check the input tab.
     
  10. Memorize

    Memorize Thread Starter

    Joined:
    Dec 26, 2012
    Messages:
    8
    I ran both 32 and 64 bit, nothing on the 32. I did find a small update for my sound card but the diag was just a WHQL logo problem. Nothing on the input and display tab's.
     
  11. Lance1

    Lance1

    Joined:
    Aug 4, 2003
    Messages:
    5,618
    I have seen issues with the latest drivers. Lets try going back to legacy drivers. If you have the install CD for the card, uninstall the latest drivers and install the drivers from the CD.
     
  12. Memorize

    Memorize Thread Starter

    Joined:
    Dec 26, 2012
    Messages:
    8
    I don't have my CD with me, not until i go home after the holidays. I'll download and install the oldest driver for my card and see if this works. Thanks for everything so far lance :) I'll post back with any changes.
     
  13. Lance1

    Lance1

    Joined:
    Aug 4, 2003
    Messages:
    5,618
    Thanks Memorize, Keep us posted.
     
  14. Memorize

    Memorize Thread Starter

    Joined:
    Dec 26, 2012
    Messages:
    8
    GPU drivers have update quite a bit since the last post and I believe it to be fixed after my sound card update and the dx diag. Solved for me.
     
  15. 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/1082614

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice