none
Windows Server 2003 R2 x64 SP2 crash.........

    General discussion

  • Hey everyone,

    i need some urgent help please, i had the above server become unresponsive last night, i did not see a BSOD, i had a completely black screen on my screen/keyboard console. i also noticed very strange and irregular drive activity on the various drives.

    i tried to get info from the minidmp file but this is what i have.....

    icrosoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\mdasilva\Desktop\Mini071613-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 

    "nt" was not found in the image list.
    Debugger will attempt to load "nt" at given base 00000000`00000000.

    Please provide the full image name, including the extension (i.e. kernel32.dll)
    for more reliable results.Base address and size overrides can be given as
    .reload <image.ext>=<base>,<size>.
    Unable to load image nt, Win32 error 0n2
    Unable to add module at 00000000`00000000
    Debugger can not determine kernel base address
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (16 procs) Free x64
    Product: Server, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
    Debug session time: Tue Jul 16 18:31:02.327 2013 (UTC + 2:00)
    System Uptime: 0 days 13:28:21.824

    "nt" was not found in the image list.
    Debugger will attempt to load "nt" at given base 00000000`00000000.

    Please provide the full image name, including the extension (i.e. kernel32.dll)
    for more reliable results.Base address and size overrides can be given as
    .reload <image.ext>=<base>,<size>.
    Unable to load image nt, Win32 error 0n2
    Unable to add module at 00000000`00000000
    Debugger can not determine kernel base address
    Loading Kernel Symbols

    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffff80001293d01, 0, 2608}

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

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80001293d01, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000002608, Parameter 1 of the exception

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

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


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

    FAULTING_IP: 
    +3262303062633538
    fffff800`01293d01 ??              ???

    EXCEPTION_PARAMETER1:  0000000000000000

    EXCEPTION_PARAMETER2:  0000000000002608

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     0000000000002608 

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

    BUGCHECK_STR:  0x1E_c0000005

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to 000000007814e3c6

    STACK_TEXT:  
    00000000`3623eb08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7814e3c6


    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
    ---------

    please would someone assist, i have never had to use WinDbg and i am very lost, any guidance would be greatly appreciated!!


    Thanks Marco da Silva MCP ID 1637667

    Wednesday, July 17, 2013 10:47 AM

All replies