閱讀687 返回首頁    go 微軟 go windows

Window2008r2 自動重啟 dmp文件顯示 Probably caused by : ntkrnlmp.exe (

Symbol search path is: srv*
Executable search path is: 
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff800`c3074000 PsLoadedModuleList = 0xfffff800`c333b9b0
Debug session time: Thu Jan 11 13:04:24.791 2018 (UTC + 8:00)
System Uptime: 64 days 4:07:50.842
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
.............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {0, 501, 500, 0}

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

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

nt!KeBugCheckEx:
fffff800`c31c40a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffd000`20be9ca0=0000000000000133
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding this single DPC timeout

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  9600.16384.amd64fre.winblue_rtm.130821-1623

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  ThinkServer TD350            

SYSTEM_SKU:  LENOVO_MT_ND

SYSTEM_VERSION:  70DGA030CN          

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  TB5TS393

BIOS_DATE:  11/15/2016

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  ThinkServer TD350            

BASEBOARD_VERSION:  70DGA030CN          

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

CPU_COUNT: 8

CPU_MHZ: 6a0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 4f

CPU_STEPPING: 1

CPU_MICROCODE: 6,4f,1,0 (F,M,S,R)  SIG: B00001D'00000000 (cache) B00001D'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  LAPTOP-94QMJ9F4

ANALYSIS_SESSION_TIME:  01-11-2018 20:16:34.0184

ANALYSIS_VERSION: 10.0.17061.1000 amd64fre

LAST_CONTROL_TRANSFER:  from fffff800c31f3c82 to fffff800c31c40a0

STACK_TEXT:  
ffffd000`20be9c98 fffff800`c31f3c82 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd000`20be9ca0 fffff800`c30f0aec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1f6f2
ffffd000`20be9d30 fffff800`c300be5f : 00000000`00000000 ffffd000`20bac180 002168da`3ba4042e fffff800`c3074000 : nt!KeClockInterruptNotify+0x77c
ffffd000`20be9f40 fffff800`c3109703 : ffffe000`00401c00 fffff800`c31791db 00000000`00000000 fffff800`c30580b0 : hal!HalpTimerClockInterrupt+0x4f
ffffd000`20be9f70 fffff800`c31c552a : ffffe000`00401c00 fffff800`c304e680 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd000`20be9fb0 fffff800`c31c590f : 00000000`00000000 00000000`00000000 ffffe000`00f61bd0 ffffe000`22ea68d0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`20bdb5d0 fffff800`c31092d8 : ffffd000`20bdb770 fffff800`c303b013 ffffd000`20bdb8b9 00000000`00000003 : nt!KiInterruptDispatchLBControl+0x11f
ffffd000`20bdb760 fffff800`c324c13e : ffffd000`20bac180 cc0001c0`00010090 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x18
ffffd000`20bdb790 fffff800`c31092b0 : 00000000`00000002 00000000`00000000 ffffe000`001ec700 ffffe000`001ec6b0 : nt!KiAcquireSpinLockInstrumented+0x62
ffffd000`20bdb7e0 fffff800`c302647a : ffffd000`20baef02 00000000`00000007 00000000`00000000 ffffd000`20baef02 : nt!KeAcquireSpinLockRaiseToDpc+0x40
ffffd000`20bdb810 fffff800`c3013c9b : 00000000`00000002 ffffd000`20baef00 00000000`00000007 ffffd000`20bac180 : hal!HalpCmcPollProcessor+0x11a3a
ffffd000`20bdb860 fffff800`c30f7e90 : ffffd000`20baef00 fffff800`c30f3879 ffffd000`20bdb990 ffffd000`20bb15c0 : hal!HalpCmciPollProcessor+0x17
ffffd000`20bdb890 fffff800`c30f7111 : 00000000`00000000 fffff800`006756d7 ffffd000`20bac180 ffffd000`00000002 : nt!KiExecuteAllDpcs+0x1b0
ffffd000`20bdb9e0 fffff800`c31c7bea : ffffd000`20bac180 ffffd000`20bac180 ffffd000`20bb8200 ffffe000`147c0080 : nt!KiRetireDpcList+0xe1
ffffd000`20bdbc60 00000000`00000000 : ffffd000`20bdc000 ffffd000`20bd6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


THREAD_SHA1_HASH_MOD_FUNC:  d158102a7f379649e58024175d6bf3f8dfb21389

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  fb863b72ab352683a818a037356193533771a579

THREAD_SHA1_HASH_MOD:  71495f5dc76583b831df6604d3fc09b831b1263e

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+1f6f2
fffff800`c31f3c82 cc              int     3

FAULT_INSTR_CODE:  442ccdcc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+1f6f2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5215d156

IMAGE_VERSION:  6.3.9600.16384

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1f6f2

FAILURE_BUCKET_ID:  0x133_DPC_nt!_??_::FNODOBFM::_string_

BUCKET_ID:  0x133_DPC_nt!_??_::FNODOBFM::_string_

PRIMARY_PROBLEM_CLASS:  0x133_DPC_nt!_??_::FNODOBFM::_string_

TARGET_TIME:  2018-01-11T05:04:24.000Z

OSBUILD:  9600

OSSERVICEPACK:  16384

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

OSEDITION:  Windows 8.1 Server TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2013-08-22 16:52:38

BUILDDATESTAMP_STR:  130821-1623

BUILDLAB_STR:  winblue_rtm

BUILDOSVER_STR:  6.3.9600.16384.amd64fre.winblue_rtm.130821-1623

ANALYSIS_SESSION_ELAPSED_TIME:  469

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_dpc_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH:  {12e2b1b6-39a2-9cfe-dc70-25086917b8e2}

Followup:     MachineOwner

您好！

 

我們了解到您關於Windows 10係統故障的問題，

 

我們需要分析您藍屏日誌文件來了解藍屏的原因，

 

建議您將您收集到的dump文件上傳之後國內網盤，

 

再將分享鏈接提供給我們，以便於我們為您進行分析並解決藍屏問題。


dmp 文件上傳到了百度網盤

https://pan.baidu.com/s/1o9beyVK

您好！

 

我們了解到您關於係統藍屏的問題，

 

根據您提供的dump文件，無法準確的定位到藍屏問題所在，

 

建議您嚐試以下方案重新收集新的dump文件並上傳過來：

 

“Win+R”打開運行，鍵入：verifier.exe，打開驅動程序驗證程序管理器，

 

選擇“創建自定義設置”，點擊“下一步”，勾選“雜項檢查”，點擊“下一步”，

 

選擇“自動選擇這台計算機上安裝的所有驅動程序”，點擊“完成”，

 

重啟您的計算機，待下一次出現藍屏現象，收集該dump文件即可。

最後更新：2018-01-17 12:04:06

  上一篇：go windows10郵件應用，綁定QQ郵箱，每次開機之後都需要重新輸入密碼
  下一篇：go 斷開VPN後，Edge 和IE 無法上網