none
3 Serverfreezes in 36 Stunden RRS feed

 > 

  • Frage

  • Question
    Anmelden
    0
    Anmelden

    Hallo zusammen,

    wir haben einen SBS 2011 auf physischer Hardware, der plötzlich Probleme macht. In den letzten 36 Stunden ist der Server 3x mit einem Bluescreen eingefroren, obwohl automatischer Reboot bei Bluescreen aktiviert ist. Vorher hatte dieser Server keine Probleme. Die Auswertung der 3 Minidumps hat uns leider nicht viel Erkenntnis gebracht. Wir haben jetzt heute morgen den RAM des Servers getauscht und hoffen, dass es nicht wieder auftritt. Vielleicht kennt sich jemand besser mit den Minidumps aus und kann da noch etwas rauslesen?

    Freitag, 22. Mai 2015 09:06
    |

Antworten

Alle Antworten

  • Question
    Anmelden
    0
    Anmelden

    1. Dump 20.05. 22h:

    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000002, A list entry was corrupt
    Arg2: 000000000034d0a4, entry in list being removed
    Arg3: 000000000043fdff, highest physical page number
    Arg4: 0000000000000001, reference count of entry being removed

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


    BUGCHECK_STR:  0x4E_2

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    PROCESS_NAME:  vds.exe

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff8000228dc7d to fffff8000227c8c0

    STACK_TEXT: 
    fffff880`0bd02f18 fffff800`0228dc7d : 00000000`0000004e 00000000`00000002 00000000`0034d0a4 00000000`0043fdff : nt!KeBugCheckEx
    fffff880`0bd02f20 fffff800`022c02ab : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0a725c11 : nt!MiUnlinkPageFromLockedList+0x8d
    fffff880`0bd02fa0 fffff800`022bedf8 : fffff8a0`15891000 fffff8a0`15951000 fffffa80`15702380 fffffa80`15702380 : nt!MiFlushSectionInternal+0x6bb
    fffff880`0bd031e0 fffff800`022be35c : 00000000`00000000 fffff980`591ac100 00000000`00000000 fffff880`018e00ba : nt!MmFlushSection+0x1f4
    fffff880`0bd032a0 fffff880`018af2e7 : fffffa80`1702ff30 00000000`00000000 fffffa80`00000000 00000000`00000001 : nt!CcFlushCache+0x7bc
    fffff880`0bd033a0 fffff880`018a5137 : fffff8a0`0497db40 fffff8a0`0560b140 fffff8a0`0560b140 fffffa80`147096e0 : Ntfs!NtfsFlushUserStream+0xb7
    fffff880`0bd03420 fffff880`018487c8 : fffffa80`147096e0 fffffa80`11016180 fffffa80`17ff9701 fffffa80`1104e000 : Ntfs!NtfsFlushVolume+0x2a7
    fffff880`0bd03550 fffff880`01835b9f : fffffa80`147096e0 fffff800`02289500 fffffa80`11050320 00000000`00000001 : Ntfs!NtfsVolumeDasdIo+0x1b8
    fffff880`0bd03600 fffff880`01837398 : fffffa80`147096e0 fffffa80`17ff9750 fffff880`0bd03701 fffffa80`1569f700 : Ntfs!NtfsCommonRead+0x5bf
    fffff880`0bd03770 fffff880`01402bcf : fffffa80`17ff9aa8 fffffa80`17ff9750 fffffa80`1569f7c0 00000000`00000000 : Ntfs!NtfsFsdRead+0x1b8
    fffff880`0bd03820 fffff880`014016df : fffffa80`1104d630 00000000`00000001 fffffa80`1104d600 fffffa80`17ff9750 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`0bd038b0 fffff800`0258481b : 00000000`00000000 fffffa80`11c09f20 00000000`00000001 fffffa80`17ff9750 : fltmgr!FltpDispatch+0xcf
    fffff880`0bd03910 fffff800`02565693 : fffffa80`11c09f20 fffffa80`11c09f20 fffffa80`11c09f20 fffff800`023fbe80 : nt!IopSynchronousServiceTail+0xfb
    fffff880`0bd03980 fffff800`0227bb53 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x631
    fffff880`0bd03a70 00000000`772bdc1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0102e2b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772bdc1a


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MiUnlinkPageFromLockedList+8d
    fffff800`0228dc7d cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+8d

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  553e7b7b

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8d

    BUCKET_ID:  X64_0x4E_2_nt!MiUnlinkPageFromLockedList+8d

    Followup: MachineOwner

    Freitag, 22. Mai 2015 09:07
    |
  • Question
    Anmelden
    0
    Anmelden

    2. Dump 22.05. 01h:

    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041790, The subtype of the bugcheck.
    Arg2: fffffa8006fc4aa0
    Arg3: 000000000000ffff
    Arg4: 0000000000000000

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


    BUGCHECK_STR:  0x1a_41790

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    PROCESS_NAME:  conhost.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff800022f68d8 to fffff800022868c0

    STACK_TEXT: 
    fffff880`095a3ee8 fffff800`022f68d8 : 00000000`0000001a 00000000`00041790 fffffa80`06fc4aa0 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`095a3ef0 fffff800`02257785 : fffffa80`1867e060 fffffa80`00000000 fffff8a0`000000a6 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x33968
    fffff880`095a47a0 fffff800`0255a166 : fffff8a0`0e967780 fffff880`095a4ae0 fffffa80`18953940 fffffa80`18953940 : nt!MmCleanProcessAddressSpace+0x95
    fffff880`095a47f0 fffff800`0253fecd : 00000000`00000000 fffff8a0`0e76b501 000007ff`fffdb000 fffffa80`18a7a060 : nt!PspExitThread+0x56a
    fffff880`095a48f0 fffff800`0227a0da : fffff8a0`0e76b4e0 fffff800`02592982 fffff880`095a4b60 00000000`fffeffff : nt!PsExitSpecialApc+0x1d
    fffff880`095a4920 fffff800`0227a420 : 00000000`40000001 fffff880`095a49a0 fffff800`0253fe40 00000000`00000001 : nt!KiDeliverApc+0x2ca
    fffff880`095a49a0 fffff800`02285bf7 : fffffa80`18953940 fffff880`095a4b60 00000000`001593d0 00000000`001014d0 : nt!KiInitiateUserApc+0x70
    fffff880`095a4ae0 00000000`7734dc6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    00000000`00aef8d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7734dc6a


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+33968
    fffff800`022f68d8 cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33968

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  553e7b7b

    FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33968

    BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33968

    Followup: MachineOwner

    Freitag, 22. Mai 2015 09:08
    |
  • Question
    Anmelden
    0
    Anmelden

    3. Dump 22.05. 9h:

    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: fffff68203520a60, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff800022abd91, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 0000000000000005, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800024cb100
     fffff68203520a60

    FAULTING_IP:
    nt!MiDispatchFault+d1
    fffff800`022abd91 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

    MM_INTERNAL_CODE:  5

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  w3wp.exe

    CURRENT_IRQL:  0

    TRAP_FRAME:  fffff88004d656e0 -- (.trap 0xfffff88004d656e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0406a414c1486558 rbx=0000000000000000 rcx=000000000406a414
    rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800022abd91 rsp=fffff88004d65870 rbp=fffff680003b91f0
     r8=00000406a414c148  r9=0000000000000000 r10=0000000fffffffff
    r11=fffff68000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!MiDispatchFault+0xd1:
    fffff800`022abd91 4b8b1c1c        mov     rbx,qword ptr [r12+r11] ds:fffff680`00000000=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff800023087aa to fffff8000228e8c0

    STACK_TEXT: 
    fffff880`04d65578 fffff800`023087aa : 00000000`00000050 fffff682`03520a60 00000000`00000000 fffff880`04d656e0 : nt!KeBugCheckEx
    fffff880`04d65580 fffff800`0228c9ee : 00000000`00000000 fffff682`03520a60 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3fda1
    fffff880`04d656e0 fffff800`022abd91 : 00000000`00000214 00000000`000005a0 00000000`00000630 00000000`00000638 : nt!KiPageFault+0x16e
    fffff880`04d65870 fffff800`0229baf9 : 00000000`772f0578 00000000`7723e16a fffffa80`18298088 00000000`00000000 : nt!MiDispatchFault+0xd1
    fffff880`04d65980 fffff800`0228c9ee : 00000000`00000008 00000000`7723e16a fffff880`04d65b01 00000000`00000000 : nt!MmAccessFault+0x359
    fffff880`04d65ae0 00000000`7723e16a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`009efbb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7723e16a


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MiDispatchFault+d1
    fffff800`022abd91 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  nt!MiDispatchFault+d1

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  553e7b7b

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  X64_0x50_nt!MiDispatchFault+d1

    BUCKET_ID:  X64_0x50_nt!MiDispatchFault+d1

    Followup: MachineOwner

    Freitag, 22. Mai 2015 09:09
    |
  • Question
    Anmelden
    0
    Anmelden

    Hallo InfoCN, 

    kann Speicher sein aber auch Memorycontroller in CPU oder auf dem Mobo. 

    Ich würde zusätzlich nochmal Firmware und Treiber auf den aktuellen Stand bringen und vll den Serverhersteller nochmal auf die Hardware schauen lassen. 

    LG 

    Flo 

    Freitag, 22. Mai 2015 09:30
    |
  • Question
    Anmelden
    0
    Anmelden
    seit tauschen des RAMs läuft er wieder wie gewohnt. danke
    • Als Antwort markiert InfoCN Montag, 8. Juni 2015 08:09
    Montag, 8. Juni 2015 08:09
    |