none
SBS 2008 x64 BSOD

    Dotaz

  • Dobry den, mel bych dotaz ohedne SBS 2008 x64 SP2
    Občas server spadne do BSOD posledni byla :

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


    Loading Dump File [C:\upload\dump\Mini021710-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: C:\WINDOWS\Symbols
    Executable search path is:
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
    Product: LanManNt, suite: SmallBusiness TerminalServer SmallBusinessRestricted
    Machine Name:
    Kernel base = 0xfffff800`01a16000 PsLoadedModuleList = 0xfffff800`01bdadd0
    Debug session time: Wed Feb 17 22:22:38.922 2010 (GMT+1)
    System Uptime: 0 days 23:21:04.565
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {8, 80050031, 6f8, fffff80001aa9678}

    Probably caused by : ntoskrnl.exe ( nt!IopLockMountedDeviceForRemove+17 )

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

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

    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000006f8
    Arg4: fffff80001aa9678

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


    BUGCHECK_STR:  0x7f_8

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80001a70450

    STACK_TEXT: 
    fffffa60`017dda68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopLockMountedDeviceForRemove+0x17


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!IopLockMountedDeviceForRemove+17
    fffff800`01a70450 48894c2408      mov     qword ptr [rsp+8],rcx

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!IopLockMountedDeviceForRemove+17

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4b1e8a6a

    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!IopLockMountedDeviceForRemove+17

    BUCKET_ID:  X64_0x7f_8_nt!IopLockMountedDeviceForRemove+17

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

    doba do BSOD je ruzna ale vzdy je to chyba UNEXPECTED_KERNEL_MODE_TRAP (7f)

    Server HP ML 110G5 , 1xXEON, 8GB RAM ECC, posledni verze biosu z HP

    Windows memory diagnostika probehne v poradku.

    19. února 2010 10:59

Odpovědi

  • Tak prime běželo cca 4-5h a v pohodě, memtest bohuzel neni mozne pustit na dlouho... :( , ale je divné , že to od te doby zatím nezalehlo, nezda se mi , že by se problém vyřešil sám :) Pokud se to zase projeví , doplním další informace... 
    1. března 2010 11:57

Všechny reakce

  • Aktualizace se urcite instalovali, server neni nainstalovany dlouho, tak se dotahovali vsechny aktualizace (nejen pro server,ale i exchange a pod), tedka se automaticky instaluji jen aktualizace zabezpeceni.

    Na RAM jel ten windows memory diagnostic, zkusim jeste memtest.

    Casy jsou ruzne,ale vetsinou v nocnich/rannich hodinach, teoreticky by mohl jet jeste backup na externi hdd,ale co jsem koukal do logu od backupu tak tam je ze probehl uspesne, takze uz byl asi dobehnutej...

    O vikendu bych po memtestu zkusil jeste prime ten by to mohl zatizit taky dobre nebo pokud by nekdo vedel nejaky lepsi software na test zateze, tak rad vyzkousim :)

    Otestuji to o vikendu a pak doplnim dalsi informace
    19. února 2010 11:42
  • jo, ten Prime95 je OK (sežeň si multithread verzi)..

    napiš jak to dopadlo..
    19. února 2010 11:46
  • Tak prime běželo cca 4-5h a v pohodě, memtest bohuzel neni mozne pustit na dlouho... :( , ale je divné , že to od te doby zatím nezalehlo, nezda se mi , že by se problém vyřešil sám :) Pokud se to zase projeví , doplním další informace... 
    1. března 2010 11:57