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.

BOSD & DMP File Help

Discussion in 'Windows XP' started by wrinklem, Jan 20, 2011.

Thread Status:
Not open for further replies.
  1. wrinklem

    wrinklem Thread Starter

    Joined:
    Jan 5, 2011
    Messages:
    2
    Recently starting using an old Dell Op 3100 after a few years of inop. A couple of days after reinstalling XP SP3, began getting intermittent crashes, with BsoD - performing memory dump. It sometimes occurs in the middle of browsing. Sometimes after being left idle for a few minutes. I installed the Windows Debugging Tools and checked several of the dump files. I can't tell if it's a bad driver (and if it is which one), or if it's corrupted memory. Any assistance would be greatly appreciated. Here are a few of the files:

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 10000050, {e293b000, 0, 8054c0b3, 1}


    Could not read faulting driver name
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+f7 )

    Followup: Pool_corruption
    ---------

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: e293b000, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 8054c0b3, If non-zero, the instruction address which referenced the bad me
    mory
    address.
    Arg4: 00000001, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS: e293b000

    FAULTING_IP:
    nt!ExDeferredFreePool+f7
    8054c0b3 8b5108 mov edx,dword ptr [ecx+8]

    MM_INTERNAL_CODE: 1

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: services.exe

    LAST_CONTROL_TRANSFER: from 8054c09e to 8054c0b3

    STACK_TEXT:
    b13d7b24 8054c09e e28e47f8 00000000 e23c7788 nt!ExDeferredFreePool+0xf7
    b13d7b64 80564705 e23c7778 e56b6f54 89c23288 nt!ExFreePoolWithTag+0x489
    b13d7b88 8056477f e23c7788 00000000 00000000 nt!ObpFreeObject+0x18d
    b13d7ba0 804e36e5 e23c77a0 00000000 e23c77a0 nt!ObpRemoveObjectRoutine+0xe8
    b13d7bc4 805759a0 89686980 00000000 89686bb8 nt!ObfDereferenceObject+0x5f
    b13d7bd8 80575892 89686bb8 00000002 00000000 nt!PsRevertThreadToSelf+0xb1
    b13d7c34 8057584d 89686980 00000000 b13d7d64 nt!PsAssignImpersonationToken+0x28
    b13d7d4c 804de7ec fffffffe 00000005 0097f8b8 nt!NtSetInformationThread+0x207
    b13d7d4c 7c90e514 fffffffe 00000005 0097f8b8 nt!KiFastCallEntry+0xf8
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0097f8bc 00000000 00000000 00000000 00000000 0x7c90e514


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!ExDeferredFreePool+f7
    8054c0b3 8b5108 mov edx,dword ptr [ecx+8]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!ExDeferredFreePool+f7

    FOLLOWUP_NAME: Pool_corruption

    IMAGE_NAME: Pool_Corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: Pool_Corruption

    FAILURE_BUCKET_ID: 0x50_nt!ExDeferredFreePool+f7

    BUCKET_ID: 0x50_nt!ExDeferredFreePool+f7

    Followup: Pool_corruption
    ---------

    kd>



    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 8054c0b9, b0b9cb5c, 0}

    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+fd )

    Followup: Pool_corruption
    ---------

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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 hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 8054c0b9, The address that the exception occurred at
    Arg3: b0b9cb5c, Trap Frame
    Arg4: 00000000

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


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

    FAULTING_IP:
    nt!ExDeferredFreePool+fd
    8054c0b9 8913 mov dword ptr [ebx],edx

    TRAP_FRAME: b0b9cb5c -- (.trap 0xffffffffb0b9cb5c)
    ErrCode = 00000002
    eax=e11d9a28 ebx=5246704e ecx=e11d9c18 edx=047c043f esi=89c26050 edi=000001ff
    eip=8054c0b9 esp=b0b9cbd0 ebp=b0b9cc10 iopl=0 nv up ei ng nz ac pe cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
    nt!ExDeferredFreePool+0xfd:
    8054c0b9 8913 mov dword ptr [ebx],edx ds:0023:5246704e=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: chrome.exe

    LAST_CONTROL_TRANSFER: from 8054c09e to 8054c0b9

    STACK_TEXT:
    b0b9cc10 8054c09e e11d0870 895acda0 896688f8 nt!ExDeferredFreePool+0xfd
    b0b9cc50 8057bb39 e2157b18 895acda0 896688f8 nt!ExFreePoolWithTag+0x489
    b0b9cd14 8057b5ee 00000000 00000000 896688f8 nt!PspExitThread+0x366
    b0b9cd34 8057bbd1 896688f8 00000000 b0b9cd64 nt!PspTerminateThreadByPointer+0x52

    b0b9cd54 804de7ec 00000000 00000000 067dff74 nt!NtTerminateThread+0x70
    b0b9cd54 7c90e514 00000000 00000000 067dff74 nt!KiFastCallEntry+0xf8
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    067dff74 00000000 00000000 00000000 00000000 0x7c90e514


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!ExDeferredFreePool+fd
    8054c0b9 8913 mov dword ptr [ebx],edx

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!ExDeferredFreePool+fd

    FOLLOWUP_NAME: Pool_corruption

    IMAGE_NAME: Pool_Corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: Pool_Corruption

    FAILURE_BUCKET_ID: 0x8E_nt!ExDeferredFreePool+fd

    BUCKET_ID: 0x8E_nt!ExDeferredFreePool+fd

    Followup: Pool_corruption
    ---------

    kd>



    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 8054c0b9, b05aa6dc, 0}

    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+fd )

    Followup: Pool_corruption
    ---------

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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 hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 8054c0b9, The address that the exception occurred at
    Arg3: b05aa6dc, Trap Frame
    Arg4: 00000000

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


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

    FAULTING_IP:
    nt!ExDeferredFreePool+fd
    8054c0b9 8913 mov dword ptr [ebx],edx

    TRAP_FRAME: b05aa6dc -- (.trap 0xffffffffb05aa6dc)
    ErrCode = 00000002
    eax=e2413bf0 ebx=35306847 ecx=e2413ff8 edx=05df0400 esi=89c25028 edi=000001ff
    eip=8054c0b9 esp=b05aa750 ebp=b05aa790 iopl=0 nv up ei ng nz ac pe cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
    nt!ExDeferredFreePool+0xfd:
    8054c0b9 8913 mov dword ptr [ebx],edx ds:0023:35306847=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 4

    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: explorer.exe

    LAST_CONTROL_TRANSFER: from 8054c09e to 8054c0b9

    STACK_TEXT:
    b05aa790 8054c09e e2543008 00000000 e254c008 nt!ExDeferredFreePool+0xfd
    b05aa7d0 bf802a40 e254c008 00000000 b05aa7ec nt!ExFreePoolWithTag+0x489
    b05aa7e0 bf805721 e254c008 b05aa840 bf809534 win32k!HeavyFreePool+0xbb
    b05aa7ec bf809534 e254c008 00000005 78050598 win32k!FreeObject+0x25
    b05aa840 bf809653 00000000 00000000 b05aa864 win32k!SURFACE::bDeleteSurface+0x14
    b
    b05aa850 bf81381d 00000000 00000000 e254c008 win32k!SURFREF::bDeleteSurface+0x12

    b05aa864 bf8138f6 78050598 0144f4b4 b05aa884 win32k!bDeleteSurface+0x20
    b05aa878 804de7ec 78050598 0144f4c8 7c90e514 win32k!NtGdiDeleteObjectApp+0x74
    b05aa878 7c90e514 78050598 0144f4c8 7c90e514 nt!KiFastCallEntry+0xf8
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0144f4c8 00000000 00000000 00000000 00000000 0x7c90e514


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!ExDeferredFreePool+fd
    8054c0b9 8913 mov dword ptr [ebx],edx

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!ExDeferredFreePool+fd

    FOLLOWUP_NAME: Pool_corruption

    IMAGE_NAME: Pool_Corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: Pool_Corruption

    FAILURE_BUCKET_ID: 0x8E_nt!ExDeferredFreePool+fd

    BUCKET_ID: 0x8E_nt!ExDeferredFreePool+fd

    Followup: Pool_corruption
    ---------

    kd>
     
  2. Macboatmaster

    Macboatmaster Trusted Advisor Spam Fighter

    Joined:
    Jan 14, 2010
    Messages:
    22,550
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...
Similar Threads - BOSD File Help
  1. Robertico22
    Replies:
    8
    Views:
    646
Thread Status:
Not open for further replies.

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

  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