Windows 10: Event viewer 10016/ DPC_WATCHDOG_Violation

Hello,


I have an issue with my PC which was built new a few months ago Windows 10 18363.720 that when playing some games it crashed to computer shut down very suddenly like power outage and restart soon after, the shut downs occurs at very specific time when playing starcraft 2/monster hunter like it will crash exactly at some point that I somewhat found a pattern of when it goona crash and it appears the crashed happens very random when playing Overwatch. It is not likely the temperature problem as the crash will happen when the exact crash point in game has reached even the computer was just start up plus there was no problem playing some other games.

My computer config:

I9-9900KF CPU

Corsair Hydro X series liquid cooling system

32GB 3200MHZ DDR4 CORSAIR VENGENCE RGB Memory

Gigabyte Nvidia Gefore RTX 2080 TI WaterBlock

Western Digital SN750 Black NvMe 500G System drive

Rog Maximus XI Formula motherboard

Corsair HX1000i 1000w Plat power supply


I checked my event viewer and here is what i found:

"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to the user DESKTOP-48CG3M3\wangz SID S-1-5-21-3752654539-2848951858-2110324924-1001 from address LocalHost Using LRPC running in the application container Unavailable SID Unavailable. This security permission can be modified using the Component Services administrative tool." I keep getting this error frequently

I've tried change the permission thing and owner for both entries to me as administrator wangz and I aslo changed settings for PerAppRuntimeBroker it usually called runtime broker tho in component services as showing below. However the 10016 error still there.








Here is the event 41 im getting each time the system crashes




So I checked the MEMORY.dmp file and mini dump file in WINDBG and here is what i get


Loading Dump File [C:\Windows\minidump\021520-8500-01.dmp]

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



WARNING: Whitespace at end of path element

Error: Empty Path.

WARNING: Whitespace at end of path element

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

WARNING: Whitespace at end of path element

Windows 10 Kernel Version 18362 MP 16 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 18362.1.amd64fre.19h1_release.190318-1202

Machine Name:

Kernel base = 0xfffff806`3b000000 PsLoadedModuleList = 0xfffff806`3b448190

Debug session time: Sat Feb 15 10:41:33.792 2020 UTC - 4:00

System Uptime: 2 days 10:42:59.984

Loading Kernel Symbols

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

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

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

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

Loading User Symbols

Loading unloaded module list

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

For analysis of this file, run !analyze -v

1: 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: fffff8063b573358, 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 ksUSBa64.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 ***

*** ***

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



KEY_VALUES_STRING: 1





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



DUMP_TYPE: 2



BUGCHECK_P1: 0



BUGCHECK_P2: 501



BUGCHECK_P3: 500



BUGCHECK_P4: fffff8063b573358



DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED



CPU_COUNT: 10



CPU_MHZ: e10



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 9e



CPU_STEPPING: c



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



BUGCHECK_STR: 0x133



PROCESS_NAME: MonsterHunterWorld.exe



CURRENT_IRQL: d



ANALYSIS_SESSION_HOST: DESKTOP-48CG3M3



ANALYSIS_SESSION_TIME: 03-20-2020 22:47:58.0587



ANALYSIS_VERSION: 10.0.18362.1 amd64fre



LAST_CONTROL_TRANSFER: from fffff8063b1eeb3d to fffff8063b1c1510



STACK_TEXT:

ffffcd00`fd7c9b08 fffff806`3b1eeb3d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

ffffcd00`fd7c9b10 fffff806`3b01f897 : 0000fbcc`5e0b7e03 ffffcd00`fd820180 00000000`00000286 fffffc05`c0836ee0 : nt!KeAccumulateTicks+0x1cc0dd

ffffcd00`fd7c9b70 fffff806`3af601e1 : 00000000`00000000 ffff910a`ac89e400 fffffc05`c0836f60 ffff910a`ac89e4b0 : nt!KeClockInterruptNotify+0xc07

ffffcd00`fd7c9f30 fffff806`3b002a25 : ffff910a`ac89e400 00000000`00000000 00000000`00000000 ffff8aec`2afc94a5 : hal!HalpTimerClockIpiRoutine+0x21

ffffcd00`fd7c9f60 fffff806`3b1c2faa : fffffc05`c0836f60 ffff910a`ac89e400 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

ffffcd00`fd7c9fb0 fffff806`3b1c3517 : 00000000`00000000 00001f80`001c0224 fffff806`432bf000 fffff806`432bf1e0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

fffffc05`c0836ee0 fffff806`432aef80 : fffff806`432af4ae 00000000`00000000 00000000`00000000 ffff910a`cf7446c0 : nt!KiInterruptDispatchNoLockNoEtw+0x37

fffffc05`c0837078 fffff806`432af4ae : 00000000`00000000 00000000`00000000 ffff910a`cf7446c0 00000000`00000000 : ks!CKsQueue::UpdateByteAvailability

fffffc05`c0837080 fffff806`45ffbedd : 00000000`00000198 00000000`00000000 ffff910a`bfd028f0 00000000`00000408 : ks!KsStreamPointerAdvanceOffsets+0xfe

fffffc05`c08370d0 00000000`00000198 : 00000000`00000000 ffff910a`bfd028f0 00000000`00000408 ffff910a`ba713000 : ksUSBa64+0x5bedd

fffffc05`c08370d8 00000000`00000000 : ffff910a`bfd028f0 00000000`00000408 ffff910a`ba713000 00000000`000005a0 : 0x198





THREAD_SHA1_HASH_MOD_FUNC: 40df052a14f92bb4b6404c127517c77cd709a190



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 75ea9e6bf3e948d3eb7cd577dcc0c07946d52dcf



THREAD_SHA1_HASH_MOD: e95303452370f707e7f6b0d5591764441d252d08



FOLLOWUP_IP:

ks!KsStreamPointerAdvanceOffsets+fe

fffff806`432af4ae 4084ed test bpl,bpl



FAULT_INSTR_CODE: 74ed8440



SYMBOL_STACK_INDEX: 8



SYMBOL_NAME: ks!KsStreamPointerAdvanceOffsets+fe



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: ks



IMAGE_NAME: ks.sys



DEBUG_FLR_IMAGE_TIMESTAMP: 1f5fe6fb



IMAGE_VERSION: 10.0.18362.207



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: fe



FAILURE_BUCKET_ID: 0x133_DPC_ks!KsStreamPointerAdvanceOffsets



BUCKET_ID: 0x133_DPC_ks!KsStreamPointerAdvanceOffsets



PRIMARY_PROBLEM_CLASS: 0x133_DPC_ks!KsStreamPointerAdvanceOffsets



TARGET_TIME: 2020-02-15T14:41:33.000Z



OSBUILD: 18362



OSSERVICEPACK: 657



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: 2005-04-22 21:40:32



BUILDDATESTAMP_STR: 190318-1202



BUILDLAB_STR: 19h1_release



BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



ANALYSIS_SESSION_ELAPSED_TIME: 3b53



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0x133_dpc_ks!ksstreampointeradvanceoffsets



FAILURE_ID_HASH: {1fff6e1b-ec59-22d1-c2e4-14c3d0bb74d5}



Followup: MachineOwner

---------




I havent found a solution for the DPC_WATCHDOG_VIOLATION yet. I've disabled all overclocking on my computer CPU, GPU, and updated every driver including video card and the problem is still there.


Pls help me, I've been working on this error for few days already, its really frustrating. Thanks in advance.

:)

 

Event viewer error 10016

Hi Eve,

For us to narrow down your concern for getting the event viewer error 10016, we would like to know the following:

• Were there any changes made on your computer prior to the issue (i.e., updates, software installation)?
• Is this the first time you experienced the issue?
• When did the issue first begin?

We look forward to your response.

 

Event viewer error with event id 10016

Hello,

Thank you for posting your query on Microsoft Community forum.

I understand that you are getting an error “DistributedCOM 10016” in the event viewer logs.

• Do you face any issues on the computer?
  
• Have you made any recent changes to the computer?

This problem may occur if either of the following conditions is true:

• A program with the class ID (CLSID) that appears in the message tries to start the COM component by using the DCOM infrastructure. However, the user does not have the required permissions to start the COM component.

• The Network Service account does not have the correct permissions.

Event logs are special files that record significant events on your computer, such as when a user logs on to the computer or when a program encounters an error. Whenever these types of events occur, Windows records the event in
an event log that you can read by using Event Viewer. Advanced users might find the details in event logs helpful when troubleshooting problems with Windows and other programs.

If you do not have any issues with app or any other program I would suggest you to ignore it.

Keep us posted if you face any issues related to Windows in future. We will be glad to help you.

 

Event 10016

Thanks Igor,

When I try to play any game on my pc the game crashes and my screen goes black but I can still hear noises. After a while the game closes and when I check event viewer it says event 10016.

I found two other events in event viewer: Event 4109 and Event 4101