Windows 10: Blue screen after resuming from hibernate

Discus and support Blue screen after resuming from hibernate in Windows 10 BSOD Crashes and Debugging to solve the problem; 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... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by MohamadSattar, Dec 21, 2020.

  1. Blue screen after resuming from hibernate


    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 AMD64Copyright 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 availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff801`61c00000 PsLoadedModuleList = 0xfffff801`6282a2b0Debug session time: Mon Dec 21 14:45:51.043 2020 UTC + 3:30System Uptime: 0 days 20:54:54.875Loading Kernel Symbols..........................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list..................................................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff801`61ff5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`5ef98c90=00000000000001330: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor 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 timeoutArg4: 0000000000000000Debugging 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 133BUGCHECK_P1: 1BUGCHECK_P2: 1e00BUGCHECK_P3: fffff801628fa320BUGCHECK_P4: 0DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDTRAP_FRAME: ffffc7054fd8e7d0 -- .trap 0xffffc7054fd8e7d0NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffa28c3c784710 rbx=0000000000000000 rcx=ffffa28c3c784710rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff80161e43944 rsp=ffffc7054fd8e960 rbp=ffffa28c35f4e080 r8=0000000000000001 r9=0000000000000001 r10=0000fffff8016200r11=ffff868e8381e6c0 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncnt!KiAcquireKobjectLockSafe+0x14:fffff801`61e43944 720c jb nt!KiAcquireKobjectLockSafe+0x22 fffff801`61e43952 [br=0]Resetting default scopeCUSTOMER_CRASH_COUNT: 1PROCESS_NAME: Telegram.exeSTACK_TEXT: fffff801`5ef98c88 fffff801`6203aa0c : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`628fa320 : nt!KeBugCheckExfffff801`5ef98c90 fffff801`61e7541d : 00001200`a390a1f3 fffff801`5da02180 00000000`00200246 00000000`004987b8 : nt!KeAccumulateTicks+0x1c880cfffff801`5ef98cf0 fffff801`61e759c1 : fffff801`69bc1856 00000000`002bd3cf fffff801`5da02180 00000000`00001001 : nt!KiUpdateRunTime+0x5dfffff801`5ef98d40 fffff801`61e6f833 : fffff801`5da02180 00000000`00000000 fffff801`628315c8 00000000`00000000 : nt!KiUpdateTime+0x4a1fffff801`5ef98e80 fffff801`61e781f2 : ffffc705`4fd8e7d0 ffffc705`4fd8e850 ffffc705`4fd8e800 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3fffff801`5ef98f30 fffff801`61f27ef5 : 000000af`5b0e38ee fffff801`628f3960 fffff801`628f3a10 ffffc900`ce3ea500 : nt!HalpTimerClockInterrupt+0xe2fffff801`5ef98f60 fffff801`61ff722a : ffffc705`4fd8e850 fffff801`628f3960 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5fffff801`5ef98fb0 fffff801`61ff7797 : ffffa28c`3c784710 fffff801`61ff1a80 ffffc900`ce3ea500 fffff801`61eec5ca : nt!KiInterruptSubDispatchNoLockNoEtw+0xfaffffc705`4fd8e7d0 fffff801`61e43944 : 00000000`00000000 00000000`00008620 00000000`00000520 00000000`001f0003 : nt!KiInterruptDispatchNoLockNoEtw+0x37ffffc705`4fd8e960 fffff801`61e4a8e5 : 00000000`00000000 00000000`00200202 ffffc705`4fd8e9b0 fffff801`6222af81 : nt!KiAcquireKobjectLockSafe+0x14ffffc705`4fd8e990 fffff801`61e4a31a : ffffa28c`3d18e060 00000000`00000000 ffffa28c`3d18e060 00000000`00000000 : nt!KiExitDispatcher+0x195ffffc705`4fd8ea00 fffff801`621fae1d : 00000000`00000000 ffffc705`4fd8eb80 00000000`0565e438 ffffa28c`3d815880 : nt!KeSetEvent+0xeaffffc705`4fd8ea90 fffff801`620071b8 : ffffa28c`39cb7080 ffffa28c`00000000 00000000`00000000 ffffa28c`00000000 : nt!NtSetEvent+0xbdffffc705`4fd8eb00 00000000`77da1cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x2800000000`0565ed28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77da1cfcSYMBOL_NAME: nt!KeAccumulateTicks+1c880cMODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.19041.685STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1c880cFAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicksOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}Followup: MachineOwner---------0: kd> lmvm ntBrowse full module liststart end module namefffff801`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.

    :)
     
    MohamadSattar, Dec 21, 2020
    #1
  2. ericsc00 Win User

    BSOD Resuming from hibernation state

    Widows 10 1709 - just powered up from hibernation, instant blue screen. This is one particular instance of several blue screen experienced on several devices - not all happening at hibernation resume but hoping someone might have some insight.



    Thanks!
     
    ericsc00, Dec 21, 2020
    #2
  3. Try3 Win User
    Resume from Hibernate Issue

    This indicates that your computer is restarting i.e. resume from hibernation is failing.

    Your initial step ought to be to go to the computer maker's support website to download then reinstall the latest display adapter driver. While you are there, check for any updated bios.

    Denis
     
  4. Blue screen after resuming from hibernate

    Blue screen of death upon resuming from Hibernation?

    Hi Izaak,

    There are some factors that we need to consider regarding this issue like hardware is malfunctioning. To properly assist you with this issue, we suggest that you follow the steps provided in this

    article
    to troubleshoot blue screen errors.

    Let us know if you need any assistance.
     
    Anthony Gal, Dec 21, 2020
    #4
Thema:

Blue screen after resuming from hibernate

Loading...
  1. Blue screen after resuming from hibernate - Similar Threads - Blue screen resuming

  2. Windows 11 Pro blue screens after resuming from suspend or hibernate - every time.

    in Windows 10 Gaming
    Windows 11 Pro blue screens after resuming from suspend or hibernate - every time.: I took all the windows updates and also updated my display driver to latest version but no luck. Every time I resume from suspend/hibernate I get blue screen.Here is a link to my minidumps: https://drive.google.com/file/d/1rjQGD3o534zm1uzzyYzMsTLxps73M2TV/view?usp=sharing...
  3. Blue Screen after resume from hibernation: DRIVER_POWER_STATE_FAILURE

    in Windows 10 BSOD Crashes and Debugging
    Blue Screen after resume from hibernation: DRIVER_POWER_STATE_FAILURE: Hello,I usually use the hibernate when I close my computer.I often have a failure after the resstart of my computer from an hibernate and a blue screen occurs.I could have few dumps from the same behavior :DRIVER_POWER_STATE_FAILUREntoskrnl.exe+3f70d0May you please...
  4. Blue Screen after resume from hibernation: DRIVER_POWER_STATE_FAILURE

    in Windows 10 Gaming
    Blue Screen after resume from hibernation: DRIVER_POWER_STATE_FAILURE: Hello,I usually use the hibernate when I close my computer.I often have a failure after the resstart of my computer from an hibernate and a blue screen occurs.I could have few dumps from the same behavior :DRIVER_POWER_STATE_FAILUREntoskrnl.exe+3f70d0May you please...
  5. Blue Screen after resume from hibernation: DRIVER_POWER_STATE_FAILURE

    in Windows 10 Software and Apps
    Blue Screen after resume from hibernation: DRIVER_POWER_STATE_FAILURE: Hello,I usually use the hibernate when I close my computer.I often have a failure after the resstart of my computer from an hibernate and a blue screen occurs.I could have few dumps from the same behavior :DRIVER_POWER_STATE_FAILUREntoskrnl.exe+3f70d0May you please...
  6. Blue Screen on Hibernate/Resume - INTERNAL_POWER_ERROR

    in Windows 10 BSOD Crashes and Debugging
    Blue Screen on Hibernate/Resume - INTERNAL_POWER_ERROR: Hi all,For the past few months, I've had dozens of intermittent crashes/blue screens on hibernate/resume. The "symptom" is that I come back to my PC after a while and the lights are still on but it's asleep and when I go to wake it, nothing happens. After reboot, I realised...
  7. Apps hang after resume from hibernation

    in Windows 10 Performance & Maintenance
    Apps hang after resume from hibernation: Apps that have files open over the network hang after a resume from hibernation, even though the server has been up the whole time. It might even affect apps that simply try to access the network over a connection that no longer exists, including possibly explorer....
  8. Black screen on primary monitor after resuming from hibernate

    in Windows 10 Ask Insider
    Black screen on primary monitor after resuming from hibernate: I have 2 monitors, primary is plugged into my GPU (1070). Secondary is plugged into my IGPU (8700k) When I wake my computer from hibernate the primary monitor displays the MSI boot logo, but when the computer finishes waking from hibernate the primary monitor becomes a black...
  9. After resuming from hibernation, it hibernates again after a few sec.

    in Windows 10 Support
    After resuming from hibernation, it hibernates again after a few sec.: Have an issue that I have not encountered before. After the machine resumes from hibernation, it starts to hibernate again right at the log on screen. Then I have to wake it again and it seems ok. Any ideas what setting can be the reason for this? 83740
  10. "Resume from Hibernation"?

    in Windows 10 Support
    "Resume from Hibernation"?: I have been using Win10 since July. It has been working fine. Just recently I noticed a blue screen at boot up stating, "resume from hibernation". I have never used hibernation in my life. Sleep mode, yes. Hibernation, no. But I have an SSD and don't use sleep anymore. I do a...

Users found this page by searching for:

  1. dpc watchdog violation when resuming from hibernation