Windows 10: DPC_WATCHDOG_VIOLATION (133) when closing monitor of laptop

Dear all,


Since yesterday I have trouble with my computer when I close the monitor of my laptop. It is a Lenovo ThinkPad X1 Yoga 2nd. I installed WinDBG and extracted the following information from the memory.dmp file. Any Idea what is the reason for this problem?


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


Loading Dump File [C:\Users\SebastianF\Documents\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 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff800`1f80a000 PsLoadedModuleList = 0xfffff800`1fbb8150
Debug session time: Sun Dec 30 12:22:08.478 2018 (UTC + 1:00)
System Uptime: 0 days 0:41:12.297
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000063`deb8e018). Type ".hh dbgerr001" for details
Loading unloaded module list
............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`1f9b40a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`21c6dbd0=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: fffff8001fc57378, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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


PROCESSES_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: LENOVO

SYSTEM_PRODUCT_NAME: 20JES03T00

SYSTEM_SKU: LENOVO_MT_20JE_BU_Think_FM_ThinkPad X1 Yoga 2nd

SYSTEM_VERSION: ThinkPad X1 Yoga 2nd

BIOS_VENDOR: LENOVO

BIOS_VERSION: N1NET42W (1.29 )

BIOS_DATE: 07/06/2018

BASEBOARD_MANUFACTURER: LENOVO

BASEBOARD_PRODUCT: 20JES03T00

BASEBOARD_VERSION: SDK0J40697 WIN

DUMP_TYPE: 1

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8001fc57378

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

CPU_COUNT: 4

CPU_MHZ: b58

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 8e

CPU_STEPPING: 9

CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 8E'00000000 (cache) 8E'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: svchost.exe

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: DESKTOP-A21G089

ANALYSIS_SESSION_TIME: 12-30-2018 12:34:29.0482

ANALYSIS_VERSION: 10.0.18303.1000 amd64fre

LAST_CONTROL_TRANSFER: from fffff8001f9df10b to fffff8001f9b40a0

STACK_TEXT:
fffff800`21c6dbc8 fffff800`1f9df10b : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff800`21c6dbd0 fffff800`1f84c3ba : 0000068c`a6cfadce fffff800`1f5c3180 00000000`00000282 00000000`00000000 : nt!KeAccumulateTicks+0x19040b
fffff800`21c6dc30 fffff800`2016051b : 0000068c`a6cee12f 00000000`00008101 00000000`00000000 fffff800`201bfbb0 : nt!KeClockInterruptNotify+0x9da
fffff800`21c6df40 fffff800`1f911a65 : fffff800`201bfbb0 00000000`00000002 ffffc080`67387970 fffff800`21c66e00 : hal!HalpTimerClockIpiRoutine+0x1b
fffff800`21c6df70 fffff800`1f9b595a : fffff800`21c66a10 fffff800`201bfbb0 ffff8280`54f603ac 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`21c6dfb0 fffff800`1f9b5e47 : 00000000`00000000 ffff8280`54f60310 ffff8280`00000000 fffff800`201604e6 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff800`21c66990 fffff803`6760c93a : 00000000`00000000 00000000`00000000 ffff8280`54f31210 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`21c66b20 fffff803`6760a542 : ffff8280`54f60310 ffff8280`54f60310 fffff803`6761d0f0 00007d7f`ab09ff01 : ISH+0xc93a
fffff800`21c66bf0 fffff803`63981fad : ffff8280`54f31b70 fffff800`21c66d60 ffff8280`54f31c20 fffff800`1f5c3180 : ISH+0xa542
fffff800`21c66c20 fffff800`1f849367 : fffff800`21c66cb8 ffff8280`52cfb000 ffff8280`5a10b080 fffff800`00000002 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9d [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410]
fffff800`21c66c60 fffff800`1f8489bb : 00000000`00000010 00000000`00000000 00000000`002b45e8 00000000`00000019 : nt!KiExecuteAllDpcs+0x2e7
fffff800`21c66da0 fffff800`1f9baff5 : 00000000`00000000 fffff800`1f5c3180 fffff30b`5b81ed60 ffffc080`673878c0 : nt!KiRetireDpcList+0x1db
fffff800`21c66fb0 fffff800`1f9badf0 : ffff8280`00000000 fffff800`201604e6 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff30b`5b81eca0 fffff800`1f9ba725 : ffffaa01`a31f0c00 fffff800`1f9b5a21 fffff30b`5b81efe0 ffffc080`673878c0 : nt!KiDispatchInterruptContinue
fffff30b`5b81ecd0 fffff800`1f9b5a21 : fffff30b`5b81efe0 ffffc080`673878c0 00000000`00001000 00000000`06131000 : nt!KiDpcInterruptBypass+0x25
fffff30b`5b81ece0 fffff803`6417c59e : fffff30b`5b81ef80 00000000`00000000 fffff30b`00000000 00000000`00000008 : nt!KiInterruptDispatch+0xb1
fffff30b`5b81ee70 fffff803`6417c93f : fffff30b`5b81efe0 fffff30b`5b81f0d0 ffff8280`64633018 00000000`00000000 : Ntfs!NtfsRestartInsertAttribute+0x126
fffff30b`5b81eeb0 fffff803`6417c19c : 00000000`00000000 fffff30b`5b81f0d0 ffff8280`64633018 ffff9306`fbf28160 : Ntfs!NtfsCreateAttributeWithAllocation+0x37f
fffff30b`5b81f070 fffff803`6417be3b : ffff9306`fbf28160 ffff8280`64633018 ffff8280`64633001 00000000`00000000 : Ntfs!NtfsAllocateAttribute+0x180
fffff30b`5b81f140 fffff803`6417b8a8 : ffff8280`64633018 ffff9306`fbf28010 ffffaa01`00000000 ffff8280`549e8180 : Ntfs!NtfsCreateNonresidentWithValue+0x10b
fffff30b`5b81f230 fffff803`6414d71a : ffff9306`fbf28160 00000000`00000000 00000000`00000000 ffff8280`64633018 : Ntfs!NtfsConvertToNonresident+0x2dc
fffff30b`5b81f3e0 fffff803`6414ef18 : ffff8280`64633018 ffff8280`61a66260 ffff8280`5bd31010 ffff9306`fbf28160 : Ntfs!NtfsSetAllocationInfo+0x5fa
fffff30b`5b81f510 fffff803`6414e1d8 : ffff8280`64633018 ffff8280`5bd31010 ffff8280`5bd31000 ffff9306`fbf28350 : Ntfs!NtfsCommonSetInformation+0xc48
fffff30b`5b81f5f0 fffff800`1f8a2e69 : 00000000`00000006 ffff8280`5bd31010 ffff8280`64633018 fffff30b`5b81f630 : Ntfs!NtfsFsdSetInformation+0xd8
fffff30b`5b81f690 fffff803`63467207 : fffff30b`5b81f760 fffff803`634653b4 00000000`00000000 00000000`00000006 : nt!IofCallDriver+0x59
fffff30b`5b81f6d0 fffff803`634651c6 : fffff30b`5b81f760 00000000`00000001 00000000`00000001 00000063`dfe7ec00 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x157
fffff30b`5b81f740 fffff800`1f8a2e69 : ffff8280`5bd31030 fffff800`1f8482c4 000c0000`20206f49 00000000`00000000 : FLTMGR!FltpDispatch+0xb6
fffff30b`5b81f7a0 fffff800`1f88e6a4 : 00000063`dfe7ec58 00000000`00000000 00000063`dfe7ec00 00000000`00000008 : nt!IofCallDriver+0x59
fffff30b`5b81f7e0 fffff800`1f88c003 : ffff8280`61a662f8 00000000`00000000 00000063`dfe7ea68 00000000`00000028 : nt!IopCallDriverReference+0xf4
fffff30b`5b81f850 fffff800`1f9c4743 : 00000000`00005cd0 00000063`dfe7ec00 00000000`00000000 00000000`00000008 : nt!NtSetInformationFile+0x6a3
fffff30b`5b81f990 00007fff`2107ae84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000063`dfe7ebc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`2107ae84


THREAD_SHA1_HASH_MOD_FUNC: 67093f0804bda2aee65f5764ee737f2b4b941a8a

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ed75f619ec31e38052ff752276d3784d37e19584

THREAD_SHA1_HASH_MOD: a3bee0f626e9cb70f5fd5c78b4abdb9eab844c14

FOLLOWUP_IP:
ISH+c93a
fffff803`6760c93a 4c8d9c24a0000000 lea r11,[rsp+0A0h]

FAULT_INSTR_CODE: 249c8d4c

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: ISH+c93a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ISH

IMAGE_NAME: ISH.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 58ef3581

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: c93a

FAILURE_BUCKET_ID: 0x133_DPC_ISH!unknown_function

BUCKET_ID: 0x133_DPC_ISH!unknown_function

PRIMARY_PROBLEM_CLASS: 0x133_DPC_ISH!unknown_function

TARGET_TIME: 2018-12-30T11:22:08.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-12-14 07:53:05

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 63bb

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_dpc_ish!unknown_function

FAILURE_ID_HASH: {b2fb73b9-7006-5917-9656-a04c08c79f92}

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

:)

 

DPC_WATCHDOG_VIOLATION

The minidump files showed two different errors, a DPC_WATCHDOG_VIOLATION (133) error and a SYSTEM_SERVICE_EXCEPTION (3b) error.

The DPC_WATCHDOG_VIOLATION may be caused by a wireless driver, the athwnx.sys.

Which wireless adapter do you have and which driver is installed?

Also, what ASUS software is installed?

 

Display/Monitor/Laptop

I was able to close laptop and see on my monitor and now after Norton update I cannot? Any suggestions

 

Windows 10 sleeps when using external monitor and closing the laptop lid.

Hey Likitha

Thanks for your response.

Before we assist further, I would like to ask you a few questions:

• Have you set Sleep function to activate on closing the laptop lid?
• Did you check if the laptop goes to sleep when not connected to external monitor and lid closed?

To respond to your questions

(1) I have set the sleep function to operate on laptop lid close only when the laptop is on battery power. When it is plugged in I have set it to do not sleep ever.

(2) I have tested that it does *not* go to sleep when I the laptop is plugged in and I close the laptop lid

Further information:

(1) When I first turned the laptop on I attached it to the monitor and closed the lid. It then ran successfully for approximately an hour before hibernating.

(2) I then restarted the system, external monitor plugged in, lid closed and it went to hibernate after approximately 2 minutes.