1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Server 2003 BSOD - 0x000000C5

Discussion in 'Windows Server System' started by fatmcgav, 2009/04/01.

  1. 2009/04/01
    fatmcgav

    fatmcgav Inactive Thread Starter

    Joined:
    2009/04/01
    Messages:
    2
    Likes Received:
    0
    Hi there,

    I'm having some issues with one of our Windows Server 2003 SP2 X64 servers.

    Over the last 48 hours it has locked up 4 times and required an ASR reboot.

    The Event Viewer shows:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c5 (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff800011a9eba). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

    The WinDbg output from the latest memory dump is below.


    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [D:\HOPS\don\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*d:\windows\websymbols*http://msdl.microsoft.com/download/...ls*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Page 65a8ab too large to be in the dump file.
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    Page 65a8ab too large to be in the dump file.
    Unable to read PsLoadedModuleList
    Page 65a8ab too large to be in the dump file.
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    KdDebuggerData.KernBase < SystemRangeStart
    Windows Server 2003 Kernel Version 3790 MP (2 procs) Free x64
    Product: Server, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x00000000`00000000 PsLoadedModuleList = 0xfffff800`011d4140
    Debug session time: Wed Apr 1 15:53:36.015 2009 (GMT+1)
    System Uptime: 0 days 2:47:24.250
    Page 65a8ab too large to be in the dump file.
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    Page 65a8ab too large to be in the dump file.
    Unable to read PsLoadedModuleList
    Page 65a8ab too large to be in the dump file.
    **************************************************************************
    THIS DUMP FILE IS PARTIALLY CORRUPT.
    KdDebuggerDataBlock is not present or unreadable.
    **************************************************************************
    KdDebuggerData.KernBase < SystemRangeStart
    Loading Kernel Symbols
    Page 65a8ab too large to be in the dump file.
    Unable to read PsLoadedModuleList
    GetContextState failed, 0xD0000147
    CS descriptor lookup failed
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Page 65a8ab too large to be in the dump file.
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get program counter
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck C5, {0, 2, 1, fffff800011a9eba}

    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

    ReadControl failed - kernel symbols must be loaded first
    ReadControl failed - kernel symbols must be loaded first
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    <SNIP>
    Unable to get current machine context, NTSTATUS 0xC0000147
    ReadControl failed - kernel symbols must be loaded first
    ReadControl failed - kernel symbols must be loaded first
    ReadControl failed - kernel symbols must be loaded first
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

    GetContextState failed, 0xD0000147
    <SNIP>
    GetContextState failed, 0xD0000147
    ?: kd> !analyze -v
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get program counter
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_CORRUPTED_EXPOOL (c5)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is
    caused by drivers that have corrupted the system pool. Run the driver
    verifier against any new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff800011a9eba, address which referenced memory

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

    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

    ReadControl failed - kernel symbols must be loaded first
    ReadControl failed - kernel symbols must be loaded first
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147
    GetContextState failed, 0xD0000147
    <SNIP>
    Unable to get current machine context, NTSTATUS 0xC0000147
    ReadControl failed - kernel symbols must be loaded first
    ReadControl failed - kernel symbols must be loaded first
    ReadControl failed - kernel symbols must be loaded first

    BUGCHECK_STR: 0xC5_2

    CURRENT_IRQL: 2

    FAULTING_IP:
    +1de952f01bbdfdc
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147
    Page 65a8ab too large to be in the dump file.
    Page 65a8ab too large to be in the dump file.
    fffff800`011a9eba ?? ???

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    STACK_TEXT:
    GetContextState failed, 0xD0000147
    Unable to get current machine context, NTSTATUS 0xC0000147


    STACK_COMMAND: kb

    SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    BUCKET_ID: CORRUPT_MODULELIST

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

    GetContextState failed, 0xD0000147
    GetContextState failed, 0xD0000147

    Any ideas what could be causing this?

    Regards
    Gavin
     
    fatmcgav,
    #1
  2. 2009/04/01
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Nothing to be had from a corrupt dump.

    THIS DUMP FILE IS PARTIALLY CORRUPT

    SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
     
    Arie,
    #2


  3. to hide this advert.

  4. 2009/04/01
    fatmcgav

    fatmcgav Inactive Thread Starter

    Joined:
    2009/04/01
    Messages:
    2
    Likes Received:
    0
    Arie,

    Ok, cheers for confirming.

    Is there anything i can do to ensure i get a non-corrupt dump the next time it hangs up?

    Cheers
    Gavin
     
    fatmcgav,
    #3
  5. 2009/04/01
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Not that I know.

    There are several issues that could cause the error, see this Google search.
     
    Arie,
    #4

Share This Page

  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.
    Accept Learn More...