Windows 10 Blue screen after resuming from hibernate

  • Thread starter Thread starter MohamadSattar
  • Start date Start date
M

MohamadSattar

I keep running into blue screen after resuming from hibernate state in Windows 10 pro and it says "dpc watchdog violation" . I tried to find the cause by using WinDBbg and I got the following resaults . Is there any solution for it?


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


Loading Dump File [C:\Windows\Minidump\122120-13687-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`61c00000 PsLoadedModuleList = 0xfffff801`6282a2b0
Debug session time: Mon Dec 21 14:45:51.043 2020 (UTC + 3:30)
System Uptime: 0 days 20:54:54.875
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run
!analyze -v
nt!KeBugCheckEx:
fffff801`61ff5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`5ef98c90=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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff801628fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7905

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-28IEIEU

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 116684

Key : Analysis.Memory.CommitPeak.Mb
Value: 78

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff801628fa320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffc7054fd8e7d0 --
(.trap 0xffffc7054fd8e7d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa28c3c784710 rbx=0000000000000000 rcx=ffffa28c3c784710
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80161e43944 rsp=ffffc7054fd8e960 rbp=ffffa28c35f4e080
r8=0000000000000001 r9=0000000000000001 r10=0000fffff8016200
r11=ffff868e8381e6c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiAcquireKobjectLockSafe+0x14:
fffff801`61e43944 720c jb nt!KiAcquireKobjectLockSafe+0x22 (fffff801`61e43952) [br=0]
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Telegram.exe

STACK_TEXT:
fffff801`5ef98c88 fffff801`6203aa0c : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`628fa320 : nt!KeBugCheckEx
fffff801`5ef98c90 fffff801`61e7541d : 00001200`a390a1f3 fffff801`5da02180 00000000`00200246 00000000`004987b8 : nt!KeAccumulateTicks+0x1c880c
fffff801`5ef98cf0 fffff801`61e759c1 : fffff801`69bc1856 00000000`002bd3cf fffff801`5da02180 00000000`00001001 : nt!KiUpdateRunTime+0x5d
fffff801`5ef98d40 fffff801`61e6f833 : fffff801`5da02180 00000000`00000000 fffff801`628315c8 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff801`5ef98e80 fffff801`61e781f2 : ffffc705`4fd8e7d0 ffffc705`4fd8e850 ffffc705`4fd8e800 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff801`5ef98f30 fffff801`61f27ef5 : 000000af`5b0e38ee fffff801`628f3960 fffff801`628f3a10 ffffc900`ce3ea500 : nt!HalpTimerClockInterrupt+0xe2
fffff801`5ef98f60 fffff801`61ff722a : ffffc705`4fd8e850 fffff801`628f3960 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`5ef98fb0 fffff801`61ff7797 : ffffa28c`3c784710 fffff801`61ff1a80 ffffc900`ce3ea500 fffff801`61eec5ca : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffc705`4fd8e7d0 fffff801`61e43944 : 00000000`00000000 00000000`00008620 00000000`00000520 00000000`001f0003 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffc705`4fd8e960 fffff801`61e4a8e5 : 00000000`00000000 00000000`00200202 ffffc705`4fd8e9b0 fffff801`6222af81 : nt!KiAcquireKobjectLockSafe+0x14
ffffc705`4fd8e990 fffff801`61e4a31a : ffffa28c`3d18e060 00000000`00000000 ffffa28c`3d18e060 00000000`00000000 : nt!KiExitDispatcher+0x195
ffffc705`4fd8ea00 fffff801`621fae1d : 00000000`00000000 ffffc705`4fd8eb80 00000000`0565e438 ffffa28c`3d815880 : nt!KeSetEvent+0xea
ffffc705`4fd8ea90 fffff801`620071b8 : ffffa28c`39cb7080 ffffa28c`00000000 00000000`00000000 ffffa28c`00000000 : nt!NtSetEvent+0xbd
ffffc705`4fd8eb00 00000000`77da1cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0565ed28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77da1cfc


SYMBOL_NAME: nt!KeAccumulateTicks+1c880c

MODULE_NAME:
nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.685

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1c880c

FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

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

0: kd> lmvm nt
Browse full module list
start end module name
fffff801`61c00000 fffff801`62c46000
nt (pdb symbols) C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\4EF9A5375F61FE84B7EAEF54BF025C0E1\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\ProgramData\Dbg\sym\ntoskrnl.exe\C129B8081046000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: C129B808 (This is a reproducible build file hash, not a timestamp)
CheckSum: 00A5C808
ImageSize: 01046000
File version: 10.0.19041.685
Product version: 10.0.19041.685
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 10.0.19041.685
FileVersion: 10.0.19041.685 (WinBuild.160101.0800)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.


Continue reading...
 

Similar threads

J
Replies
0
Views
1
Job_Sparrow Job_Sparrow
J
N
Replies
0
Views
1
nianchu_1025
N
J
Replies
0
Views
19
JC Z1
J
Back
Top