最近戴尔的塔式服务器的winserver2016总是蓝屏,硬件灯显示正常。
蓝屏内容是DPC_WATCHDOG_VIOLATION
通过蓝屏分析,内容如下:
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\11119\Downloads\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (32 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Edition build lab: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
Machine Name:
Kernel base = 0xfffff800`d6c7e000 PsLoadedModuleList = 0xfffff800`d6f83060
Debug session time: Thu Nov 17 19:20:17.675 2022 (UTC + 8:00)
System Uptime: 0 days 0:04:33.593
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`0047e018). Type ".hh dbgerr001" for details
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`d6dc8510 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffe681`d2af9d90=0000000000000133
14: 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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: 0000000000000000, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
Page 3c00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3c00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3c00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3c00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3c00 not present in the dump file. Type ".hh dbgerr004" for details
Page 3c00 not present in the dump file. Type ".hh dbgerr004" for details
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1359
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 1405
Key : Analysis.IO.Other.Mb
Value: 9
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 19
Key : Analysis.Init.CPU.mSec
Value: 1749
Key : Analysis.Init.Elapsed.mSec
Value: 82836
Key : Analysis.Memory.CommitPeak.Mb
Value: 89
Key : Bugcheck.Code.DumpHeader
Value: 0x133
Key : Bugcheck.Code.KiBugCheckData
Value: 0x133
Key : Bugcheck.Code.Register
Value: 0x133
Key : WER.OS.Branch
Value: rs1_release_inmarket
Key : WER.OS.Timestamp
Value: 2016-11-02T01:00:00Z
Key : WER.OS.Version
Value: 10.0.14393.447
FILE_IN_CAB: MEMORY.DMP
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: 0
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: ffffe681d7297100 -- (.trap 0xffffe681d7297100)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000005b4 rbx=0000000000000000 rcx=000000005de0625d
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800d6d69786 rsp=ffffe681d7297290 rbp=ffffe681d7297400
r8=0000000000000002 r9=fffff800d6c7e000 r10=ffffe681d2ac0ca0
r11=ffffd48912421f90 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KeYieldProcessorEx+0x16:
fffff800`d6d69786 4883c428 add rsp,28h
Resetting default scope
PROCESS_NAME: devenv.exe
STACK_TEXT:
ffffe681`d2af9d88 fffff800`d6e1e102 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
ffffe681`d2af9d90 fffff800`d6d49608 : 003702d2`323ac9c2 003702d2`323ac8d6 fffff780`00000320 fffff802`3418577d : nt! ?? ::FNODOBFM::`string'+0x46762
ffffe681`d2af9df0 fffff800`d6c0c4e5 : ffffd489`0c808400 ffffe681`d2ac0180 ffffe681`d2af0ea0 ffffd489`0c808400 : nt!KeClockInterruptNotify+0xb8
ffffe681`d2af9f40 fffff800`d6cd5357 : ffffd489`0c808400 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15
ffffe681`d2af9f70 fffff800`d6dc9b8a : ffffd489`0c808400 ffffe681`d2af0ea0 ffffe681`d2ac0180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x87
ffffe681`d2af9fb0 fffff800`d6dc9fd7 : ffff1d95`94aab7f3 ffffd489`0e2486c0 ffff1d95`94aab7c3 fffff800`d6dca05e : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffe681`d7297100 fffff800`d6d69786 : ffffffff`ffffffd2 fffff800`d6e02025 00000000`00000010 00000000`00000286 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffe681`d7297290 fffff800`d6e02025 : ffffd489`12421f90 00000000`00000000 00000000`00000000 00000000`00000008 : nt!KeYieldProcessorEx+0x16
ffffe681`d72972c0 fffff800`d6d0da44 : 00000000`00000000 00000000`004a7000 ffffe681`d7297300 fffff800`5de0625d : nt! ?? ::FNODOBFM::`string'+0x2a685
ffffe681`d72973b0 fffff800`d6dcb9d3 : 00000000`00000914 00000000`00000008 00000000`00000000 00000000`004a7000 : nt!KiDeliverApc+0x134
ffffe681`d7297440 00000000`77669660 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0xc3
00000000`05cbd91c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77669660
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+46762
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 46762
FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
OS_VERSION: 10.0.14393.447
BUILDLAB_STR: rs1_release_inmarket
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {89366ad1-5557-ac2b-d015-8f6ec2fdbf31}
Followup: MachineOwner
---------文章来源:https://www.toymoban.com/news/detail-470582.html
求助大神看看这是什么原因造成的,谢谢!文章来源地址https://www.toymoban.com/news/detail-470582.html
到了这里,关于【求助大佬】WinServer2016蓝屏DPC_WATCHDOG_VIOLATION的文章就介绍完了。如果您还想了解更多内容,请在右上角搜索TOY模板网以前的文章或继续浏览下面的相关文章,希望大家以后多多支持TOY模板网!