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 restart with dump

Discussion in 'Windows Server System' started by techaview, 2007/06/26.

  1. 2007/06/26
    techaview

    techaview Inactive Thread Starter

    Joined:
    2007/01/08
    Messages:
    9
    Likes Received:
    0
    Hi

    I have a windows 2000 server with sp4 restart by itself with dump generated. Using windows debugger, below is the output. Any kind-hearted care to share what is the problem? though i suspect is memory problem (RAM). Thanks!

    Using !analyze -v

    Symbol search path is: SRV*c:\local cache*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
    Product: Server
    Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e1b8
    Debug session time: Thu Jun 21 17:14:50.906 2007 (GMT+8)
    System Uptime: 0 days 4:50:58.415
    Loading Kernel Symbols
    ....................................................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffdf00c). Type ".hh dbgerr001" for details
    Loading unloaded module list
    .......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {41284, 2d0000, 8046f930, c0502000}

    Probably caused by : memory_corruption ( nt!MiLocateWsle+ca )

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

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

    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 00041284, A PTE or the working set list is corrupt.
    Arg2: 002d0000
    Arg3: 8046f930
    Arg4: c0502000

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


    BUGCHECK_STR: 0x1a_41284

    DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

    PROCESS_NAME: MpGMemStat.exe

    LAST_CONTROL_TRANSFER: from 8044daca to 8044d3e2

    STACK_TEXT:
    f24b7a2c 8044daca 8046f930 002d0000 c0300000 nt!MiLocateWsle+0xca
    f24b7a58 8044d90a c0000b40 002d0000 00000000 nt!MiDeletePte+0x142
    f24b7b18 80445f6b e1c4e9ec 002d0fff 00000000 nt!MiDeleteVirtualAddresses+0x294
    f24b7bc8 8043fb68 814ee640 814edc68 00000000 nt!MiRemoveMappedView+0x1e8
    f24b7c80 804aa293 814ee8b0 81502020 00000001 nt!MmCleanProcessAddressSpace+0x366
    f24b7d30 804a9d10 00000000 f24b7d64 0012feb0 nt!PspExitThread+0x4d1
    f24b7d54 80465691 ffffffff 00000000 00000000 nt!NtTerminateProcess+0x154
    f24b7d54 77f8dd8b ffffffff 00000000 00000000 nt!KiSystemService+0xc4
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0012ff6c 00000000 00000000 00000000 00000000 0x77f8dd8b


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiLocateWsle+ca
    8044d3e2 e969ffffff jmp nt!MiLocateWsle+0xca (8044d350)

    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 3ee6c002

    SYMBOL_NAME: nt!MiLocateWsle+ca

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+ca

    BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+ca

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

    kd> lmvm nt
    start end module name
    80400000 805a3a00 nt (pdb symbols) c:\local cache\ntoskrnl.pdb\3EE650B31\ntoskrnl.pdb
    Loaded symbol image file: c:\local cache\ntoskrnl.dbg\3EE6C0021a3a00\ntoskrnl.dbg
    Image path: ntoskrnl.exe
    Image name: ntoskrnl.exe
    Timestamp: Wed Jun 11 13:37:06 2003 (3EE6C002)
    CheckSum: 001AC775
    ImageSize: 001A3A00
    File version: 5.0.2195.6717
    Product version: 5.0.2195.6717
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 1.0 App
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: Microsoft Corporation
    ProductName: Microsoft(R) Windows (R) 2000 Operating System
    InternalName: ntoskrnl.exe
    OriginalFilename: ntoskrnl.exe
    ProductVersion: 5.00.2195.6717
    FileVersion: 5.00.2195.6717
    FileDescription: NT Kernel & System
    LegalCopyright: Copyright (C) Microsoft Corp. 1981-1999
     
  2. 2007/06/26
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    That's what it looks like.

    Start by testing your memory. Run Memtest86 or Windows Memory Diagnostic.
     
    Arie,
    #2

  3. to hide this advert.

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.