服务器2016系统重启,WINDOWS SERVER 2016突然无故重启系统

最新推荐文章于 2023-10-08 13:22:17 发布

art 信贷

最新推荐文章于 2023-10-08 13:22:17 发布

阅读量945

点赞数 1

文章标签：服务器2016系统重启

Loading User Symbols

Loading unloaded module list

...........

For analysis of this file, run!analyze -vnt!KeBugCheckEx:

fffff801`42d622e0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff801`44e02d90=0000000000000133

0: 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: fffff80142fab540, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding this single DPC timeout

Debugging Details:

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

*** WARNING: Unable to verify timestamp for SISIPSNetFilter.sys

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

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: TickPeriods ***

*** ***

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

Debugger extension ext.analyze execution is cancelled.

PC: 00007ffa`03bb4b59 VA: 000000fb`0787ac30 R/W: 9 Parameter: 00000000`00000000

NatVis script unloaded from 'C:\Users\Administrator\Downloads\WinDbg Preview1.1910.3003.0\Microsoft.WinDbg_1.1910.3003.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'

NatVis script unloaded from 'C:\Users\Administrator\Downloads\WinDbg Preview1.1910.3003.0\Microsoft.WinDbg_1.1910.3003.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'

NatVis script unloaded from 'C:\Users\Administrator\Downloads\WinDbg Preview1.1910.3003.0\Microsoft.WinDbg_1.1910.3003.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'

NatVis script unloaded from 'C:\Users\Administrator\Downloads\WinDbg Preview1.1910.3003.0\Microsoft.WinDbg_1.1910.3003.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'

NatVis script unloaded from 'C:\Users\Administrator\Downloads\WinDbg Preview1.1910.3003.0\Microsoft.WinDbg_1.1910.3003.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'

NatVis script unloaded from 'C:\Users\Administrator\Downloads\WinDbg Preview1.1910.3003.0\Microsoft.WinDbg_1.1910.3003.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'

NatVis script unloaded from 'C:\Users\Administrator\Downloads\WinDbg Preview1.1910.3003.0\Microsoft.WinDbg_1.1910.3003.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'

NatVis script unloaded from 'C:\Users\Administrator\Downloads\WinDbg Preview1.1910.3003.0\Microsoft.WinDbg_1.1910.3003.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'

NatVis script unloaded from 'C:\Users\Administrator\Downloads\WinDbg Preview1.1910.3003.0\Microsoft.WinDbg_1.1910.3003.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'

NatVis script unloaded from 'C:\Users\Administrator\Downloads\WinDbg Preview1.1910.3003.0\Microsoft.WinDbg_1.1910.3003.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'

NatVis script unloaded from 'C:\Users\Administrator\Downloads\WinDbg Preview1.1910.3003.0\Microsoft.WinDbg_1.1910.3003.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'

Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64

Loading Dump File [C:\Users\Administrator\Desktop\031521-146937-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 14393 MP (8 procs) Free x64

Product: Server, suite: TerminalServer SingleUserTS

Built by: 14393.4104.amd64fre.rs1_release.201202-1742

Machine Name:

Kernel base = 0xfffff803`33285000 PsLoadedModuleList = 0xfffff803`335890a0

Debug session time: Mon Mar 15 12:19:38.659 2021 (UTC + 8:00)

System Uptime: 5 days 2:02:42.862

Loading Kernel Symbols

...............................................................

................................................................

..................................................

Loading User Symbols

Loading unloaded module list

.............

For analysis of this file, run!analyze -vnt!KeBugCheckEx:

fffff803`333e22e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffbf01`af806d90=0000000000000133

5: 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: fffff8033362b540, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains