windows server 蓝屏

• 问题

• 

  

  0

  登录进行投票

  你好

  查看日志发现服务器蓝屏重启，

  windbg分析的结果如下：请帮忙分析故障原因，谢谢。

  服务器是windows server 2016

  故障存储段 ，类型 0

  事件名称: BlueScreen

  响应: 不可用

  Cab ID: 0

  
  

  问题签名:

  P1: 133

  P2: 0

  P3: 501

  P4: 500

  P5: fffff80163625540

  P6: 10_0_14393

  P7: 0_0

  P8: 272_2

  P9: 

  P10: 

  
  

  附加文件:

  \\?\C:\Windows\Minidump\120220-16828-01.dmp

  \\?\C:\Windows\TEMP\WER-23250-0.sysdata.xml

  \\?\C:\Windows\MEMORY.DMP

  \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E26.tmp.WERInternalMetadata.xml

  
  

  可在此处获取这些文件:

  C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_5fbbc4e48ee9f27d45ef5615b6d165874bcdb1_00000000_cab_03148ea3

  
  

  分析符号: 

  重新检查解决方案: 0

  报告 ID: 8c874482-dca9-4919-bee6-138dd4d346a2

  报告状态: 4

  *******************************************************************************

  *                                                                             *

  *                        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: fffff80163625540

  
  

  Debugging Details:

  ------------------

  
  

  
  

  CUSTOMER_CRASH_COUNT:  1

  
  

  DEFAULT_BUCKET_ID:  CODE_CORRUPTION

  
  

  BUGCHECK_STR:  0x133

  
  

  PROCESS_NAME:  System

  
  

  CURRENT_IRQL:  d

  
  

  LAST_CONTROL_TRANSFER:  from fffff801632a8c07 to fffff801633d5790

  
  

  STACK_TEXT:  

  fffff801`65057d88 fffff801`632a8c07 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

  fffff801`65057d90 fffff801`632a6c19 : 00ebf3e4`2153f9f8 00000000`00000000 ffffa88f`b61bf400 fffff780`00000320 : nt!KeAccumulateTicks+0x407

  fffff801`65057df0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeClockInterruptNotify+0x469

  
  

  
  

  STACK_COMMAND:  kb

  
  

  CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

      fffff801634cd388-fffff801634cd389  2 bytes - nt!ExFreePoolWithTag+388

  [ fb f6:c2 84 ]

  2 errors : !nt (fffff801634cd388-fffff801634cd389)

  
  

  MODULE_NAME: memory_corruption

  
  

  IMAGE_NAME:  memory_corruption

  
  

  FOLLOWUP_NAME:  memory_corruption

  
  

  DEBUG_FLR_IMAGE_TIMESTAMP:  0

  
  

  MEMORY_CORRUPTOR:  LARGE

  
  

  FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

  
  

  BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

  
  

  Followup: memory_corruption

  ---------

  
  

  0: kd> lmvm memory_corruption

  start             end                 module name

  2020年12月4日 3:32

  回复

  |

  引用