locked
Debug Crash Dump Memory RRS feed

  • Pergunta

  • Bom dia Pessoal,

    Fiz um debug de um miniDump do meu servidor que deu tela azul e reiniciou, até achei uma informação que bate com o que pode ter acontecido, mas queria ver se alguém pode me ajudar  ou me explicar como analisar esse log. Acho que deu alguns erros na hora de gerar o Dump.

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


    Loading Dump File [C:\Mini051112-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: c:\symbols
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x86 compatible
    Product: Server, suite: TerminalServer
    Built by: 6002.18484.x86fre.vistasp2_gdr.110617-0336
    Machine Name:
    Kernel base = 0x81c04000 PsLoadedModuleList = 0x81d1bc70
    Debug session time: Fri May 11 09:07:39.165 2012 (UTC - 3:00)
    System Uptime: 0 days 13:32:10.103
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Loading unloaded module list
    .....
    TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\oca.ini, error 2
    TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\winxp\triage.ini, error 2
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 103, {1, 8a21b5b0, 88f421c8, 85ca0130}

    *** WARNING: Unable to verify timestamp for AlfaFF.sys
    *** ERROR: Module load completed but symbols could not be loaded for AlfaFF.sys
    *** WARNING: Unable to verify timestamp for CtxSbx.sys
    *** ERROR: Module load completed but symbols could not be loaded for CtxSbx.sys
    *** WARNING: Unable to verify timestamp for CtxAltStr.sys
    *** ERROR: Module load completed but symbols could not be loaded for CtxAltStr.sys
    TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2
    Probably caused by : mup.sys ( mup!MupFsdIrpPassThrough+6c )

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

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

    MUP_FILE_SYSTEM (103)
    MUP file system detected an error.
    Arguments:
    Arg1: 00000001, MUP_BUGCHECK_NO_FILECONTEXT
     Could not locate MUP file context corresponding to a file object.
    Arg2: 8a21b5b0, Irp Address if an IRP was used, NULL otherwise.
    Arg3: 88f421c8, FILE_OBJECT Address whose MUP file context could not be found
    Arg4: 85ca0130, DEVICE_OBJECT Address

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

    TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2

    DEVICE_OBJECT: 85ca0130

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT_SERVER

    BUGCHECK_STR:  0x103

    PROCESS_NAME:  EXCEL.EXE

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 8cf62b40 to 81cd1b3f

    STACK_TEXT: 
    be1a36ec 8cf62b40 00000103 00000001 8a21b5b0 nt!KeBugCheckEx+0x1e
    be1a3714 81c48976 85ca0130 8a21b5b0 8a21b5b0 mup!MupFsdIrpPassThrough+0x6c
    be1a372c 8239bba7 00000000 8ca23290 00000000 nt!IofCallDriver+0x63
    be1a3750 8239c7c7 be1a3770 85ca5ce8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251
    be1a3788 823cfd2e 85ca5618 8a38d068 be1a37e0 fltmgr!FltPerformSynchronousIo+0xb9
    WARNING: Stack unwind information not available. Following frames may be wrong.
    be1a3798 823cca31 85ca5618 8ca23290 be1a37b8 AlfaFF+0x7d2e
    be1a37e0 823c9a77 8a38d068 be1a3854 88ff4038 AlfaFF+0x4a31
    be1a3818 823c9db1 0038d068 be1a3854 88099a20 AlfaFF+0x1a77
    be1a3830 823980f3 8a38d068 be1a3854 88099a20 AlfaFF+0x1db1
    be1a3894 8239b090 0038d008 00000000 8a38d008 fltmgr!FltpPerformPostCallbacks+0x1f1
    be1a38a8 8239b5c6 8a38d008 8cb15c10 be1a38e8 fltmgr!FltpProcessIoCompletion+0x10
    be1a38b8 8239bc37 85ca5ce8 8cb15c10 8a38d008 fltmgr!FltpPassThroughCompletion+0x94
    be1a38e8 823ae643 be1a3908 00000104 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2e1
    be1a3934 81c48976 85ca5ce8 85ca5880 8cb15c10 fltmgr!FltpCreate+0x2a1
    be1a394c a120e41b 86e21a80 86defa28 be1a396c nt!IofCallDriver+0x63
    be1a395c a120a3ee 86defa28 00000000 be1a3984 CtxSbx+0x541b
    be1a396c 81c48976 86defa28 8cb15c10 00000000 CtxSbx+0x13ee
    be1a3984 a13f18fa 8cb15d34 8cb15c10 86e21a80 nt!IofCallDriver+0x63
    be1a39b0 a13f1b52 86e21a80 8cb15c10 8cb566a4 CtxAltStr+0x48fa
    be1a39d0 81c48976 86e21a80 8cb15c10 88f42224 CtxAltStr+0x4b52
    be1a39e8 81e436b7 74f5c1a3 8a397af4 85ca0118 nt!IofCallDriver+0x63
    be1a3ab8 81e31aec 85ca0130 00000000 8a397a50 nt!IopParseDevice+0xf61
    be1a3b48 81e3f084 00000000 be1a3ba0 00000040 nt!ObpLookupObjectName+0x5a8
    be1a3ba8 81e24272 0635f950 00000000 00000001 nt!ObOpenObjectByName+0x13c
    be1a3d54 81c4ec7a 0635f950 0635f928 0635f90c nt!NtQueryAttributesFile+0x125
    be1a3d54 77265ca4 0635f950 0635f928 0635f90c nt!KiFastCallEntry+0x12a
    0635f90c 00000000 00000000 00000000 00000000 0x77265ca4


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    mup!MupFsdIrpPassThrough+6c
    8cf62b40 bb100000c0      mov     ebx,0C0000010h

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  mup!MupFsdIrpPassThrough+6c

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: mup

    IMAGE_NAME:  mup.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  49e01914

    FAILURE_BUCKET_ID:  0x103_mup!MupFsdIrpPassThrough+6c

    BUCKET_ID:  0x103_mup!MupFsdIrpPassThrough+6c

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

    2: kd> lmvm mup
    start    end        module name
    8cf5d000 8cf6c000   mup        (pdb symbols)          c:\symbols\mup.pdb\653FD04795A841BBBE6B11E2ADDDE1A12\mup.pdb
        Loaded symbol image file: mup.sys
        Mapped memory image file: c:\symbols\mup.sys\49E01914f000\mup.sys
        Image path: \SystemRoot\System32\Drivers\mup.sys
        Image name: mup.sys
        Timestamp:        Sat Apr 11 01:14:12 2009 (49E01914)
        CheckSum:         00019334
        ImageSize:        0000F000
        File version:     6.0.6002.18005
        Product version:  6.0.6002.18005
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.6 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     MUP.SYS
        OriginalFilename: MUP.SYS
        ProductVersion:   6.0.6002.18005
        FileVersion:      6.0.6002.18005 (lh_sp2rtm.090410-1830)
        FileDescription:  Multiple UNC Provider driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    2: kd> !devobj ffffffff85ca0130 f
    81d13524: Unable to get value of ObpRootDirectoryObject
    85ca0130: Could not read device object or _DEVICE_OBJECT not found



    Atenciosamente
    Fabrício Castro Maluf
    E-mail: fab.maluf@gmail.com

    sexta-feira, 11 de maio de 2012 14:56

Respostas

  • Então eu havia publicado uma planilha no XenApp, e justamente quando estava fazendo testes a máquina deu o problema, eu vi que no Debug apareceu o EXCEl, mas queria saber mais detalhes.



    Atenciosamente
    Fabrício Castro Maluf
    E-mail: fab.maluf@gmail.com

    segunda-feira, 21 de maio de 2012 14:47

Todas as Respostas

  • Olá Fabrício.

    Esse problema ocorre quando você ta com o Excel aberto, trabalhando nele?

    Abraço.


    Richard Juhasz - Microsoft LATAM Forum Support Engineer
    http://www.forumguys.com.br

    quarta-feira, 16 de maio de 2012 13:33
  • Então eu havia publicado uma planilha no XenApp, e justamente quando estava fazendo testes a máquina deu o problema, eu vi que no Debug apareceu o EXCEl, mas queria saber mais detalhes.



    Atenciosamente
    Fabrício Castro Maluf
    E-mail: fab.maluf@gmail.com

    segunda-feira, 21 de maio de 2012 14:47