locked
系統啟動時發生 Crash Dump (藍屏) RRS feed

  • 一般討論

  • Hello!!

       I need help to analyse this dump file. My server crashed every time when startup.

       The Server :

         IBM System X

         Windows Server 2008 R2

       Thanks a lot !!!


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


    Loading Dump File [G:\Mini042914-11.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
    Product: LanManNt, suite: TerminalServer SingleUserTS
    Built by: 6002.18881.amd64fre.vistasp2_gdr.130707-1535
    Machine Name:
    Kernel base = 0xfffff800`02656000 PsLoadedModuleList = 0xfffff800`0281ae30
    Debug session time: Tue Apr 29 17:59:46.418 2014 (UTC + 8:00)
    System Uptime: 0 days 0:03:22.370
    Loading Kernel Symbols
    .

    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.

    ..............................................................
    ................................................................
    ........
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 4E, {7, 1fbed4, 1, 0}

    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+aee6 )

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

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

    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: 0000000000000007, A driver has unlocked a page more times than it locked it
    Arg2: 00000000001fbed4, page frame number
    Arg3: 0000000000000001, current share count
    Arg4: 0000000000000000, 0

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


    BUGCHECK_STR:  0x4E_7

    CUSTOMER_CRASH_COUNT:  11

    DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

    PROCESS_NAME:  svchost.exe

    CURRENT_IRQL:  2

    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

    LAST_CONTROL_TRANSFER:  from fffff8000270107d to fffff800026ad150

    STACK_TEXT: 
    fffffa60`068b84f8 fffff800`0270107d : 00000000`0000004e 00000000`00000007 00000000`001fbed4 00000000`00000001 : nt!KeBugCheckEx
    fffffa60`068b8500 fffff800`026be21a : fffffa80`05f3c7c0 00000000`00000000 02000000`00000000 fffffa80`060caee0 : nt! ?? ::FNODOBFM::`string'+0xaee6
    fffffa60`068b8540 fffff800`0278c8fa : fffffa80`00000000 fffffa60`00000001 00000000`00000001 fffffa60`00000000 : nt!MiDeferredUnlockPages+0x3ca
    fffffa60`068b85f0 fffff800`0278a268 : fffffa80`0a2f0000 fffffa60`019667f0 fffff6fb`7ea00288 00000000`00000008 : nt!MiFreePoolPages+0xfa
    fffffa60`068b8700 fffffa60`03698f67 : 00000000`00000016 fffffa80`00000070 fffffa80`00000000 00000000`6770534e : nt!ExFreePoolWithTag+0x598
    fffffa60`068b87b0 fffffa60`0369a8ac : fffffa80`0a2e3c70 fffffa80`0a2e3ba0 00000000`00000000 fffffa80`0a2e3bd8 : nsiproxy!NsippEnumerateObjectsAllParameters+0x477
    fffffa60`068b89a0 fffffa60`0369a99f : 00000000`00000003 00000000`00000001 fffffa80`06cf97d0 fffffa80`078b81b0 : nsiproxy!NsippDispatchDeviceControl+0x70
    fffffa60`068b89e0 fffff800`0291abee : fffffa80`0a2e3c00 fffffa80`078b81b0 00000000`00000001 00000000`00000001 : nsiproxy!NsippDispatch+0x4b
    fffffa60`068b8a10 fffff800`02923626 : 00000000`02cac750 00000000`000005ac 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5be
    fffffa60`068b8b40 fffff800`026acbf3 : fffffa80`09deb560 00000000`02cac738 fffffa60`068b8bc8 00000000`02cac8d0 : nt!NtDeviceIoControlFile+0x56
    fffffa60`068b8bb0 00000000`77cc6eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`02cac7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cc6eea


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+aee6
    fffff800`0270107d cc              int     3

    SYMBOL_STACK_INDEX:  1

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

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  51da19e2

    IMAGE_VERSION:  6.0.6002.18881

    FAILURE_BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+aee6

    BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+aee6

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_0x4e_7_nt!_??_::fnodobfm::_string_+aee6

    FAILURE_ID_HASH:  {672c4b20-45f5-4a81-24c6-adb205249a4a}

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

    2014年4月29日 下午 12:20

所有回覆

  • Hi Jackie X

    有事件檢視器的相關資訊嗎

    因為這樣子的資訊真的沒有辦法分析真正的問題

    2014年4月30日 上午 10:07
  • Hi Jackie X

    歡迎您將後續測試結果回報至論壇, 或將對您有幫助的回覆標示為解答,

    以利討論的進行並幫助其他有類似問題的朋友. 謝謝您!

    2014年5月5日 上午 06:13