Windows 10: BSOD DPC WATCHDOG VIOLATION HDAudbus

Still getting error after rolling back to previous graphics driver, here's the dmp file in debugger. Haven't had much luck in finding cause, looks like HDAudBus issue. . .


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


Loading Dump File [C:\Users\maniacalmichael\Desktop\021519-12500-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 17134 MP (**** (UTC - 7:00)
System Uptime: 0 days 15:37:42.812
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`c9c500c0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffd701`eda65bd0=0000000000000133
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: fffff801c9ef3378, 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

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

SYSTEM_SKU: To Be Filled By O.E.M.

SYSTEM_VERSION: To Be Filled By O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: P1.90

BIOS_DATE: 05/20/2016

BASEBOARD_MANUFACTURER: ASRock

BASEBOARD_PRODUCT: Z170A-X1

BASEBOARD_VERSION:

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff801c9ef3378

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C2'00000000 (cache) C2'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: NEW-HOME

ANALYSIS_SESSION_TIME: 02-15-2019 10:07:40.0617

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

LAST_CONTROL_TRANSFER: from fffff801c9c7b0f7 to fffff801c9c500c0

STACK_TEXT:
ffffd701`eda65bc8 fffff801`c9c7b0f7 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd701`eda65bd0 fffff801`c9ae83ba : 00006dd7`1bf7e509 ffffd701`eda49180 00000000`00000282 00000000`00000000 : nt!KeAccumulateTicks+0x1903f7
ffffd701`eda65c30 fffff****171f : hal!HalpTimerClockIpiRoutine+0x1b
ffffd701`eda65f70 fffff801`c9c5197a : ffffab04`c7c2f380 ffffc38d`5bade000 fffff801`c9aa6000 ffffd701`eda49180 : nt!KiCallInterruptServiceRoutine+0xa5
ffffd701`eda65fb0 fffff801`c9c51e67 : 00000000`00000008 ffffab04`c7c2f470 00000000`00000000 fffff801`c9ad5dbe : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffab04`c7c2f300 fffff801`c9b444e0 : ffffffff`ffffffd2 fffff801`c9c5657a 00000000`00000010 00000000`00000202 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffab04`c7c2f490 fffff801`c9b431f0 : ffffab04`c7c2f638 ffffc38d`63a88700 00000000`00000000 00001f80`000002ff : nt!KiChooseTargetProcessor+0x6b0
ffffab04`c7c2f5c0 fffff****bbb0 00000000`00000000 : nt!KiExitDispatcher+0xff
ffffab04`c7c2f720 fffff****200 : nt!KiRetireDpcList+0x1db
ffffab04`c7c2fbe0 00000000`00000000 : ffffab04`c7c30000 ffffab04`c7c29000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


THREAD_SHA1_HASH_MOD_FUNC: 123c0d7b317335b0bc417****8e

FOLLOWUP_IP:
HDAudBus!HdaController::NotificationDpc+201
fffff804`9d6f1451 eb1c jmp HDAudBus!HdaController::NotificationDpc+0x21f (fffff804`9d6f146f)

FAULT_INSTR_CODE: 33451ceb

SYMBOL_STACK_INDEX: c

SYMBOL_NAME: HDAudBus!HdaController::NotificationDpc+201

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: HDAudBus

IMAGE_NAME: HDAudBus.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17134.1

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 201

FAILURE_BUCKET_ID: 0x133_DPC_HDAudBus!HdaController::NotificationDpc

BUCKET_ID: 0x133_DPC_HDAudBus!HdaController::NotificationDpc

PRIMARY_PROBLEM_CLASS: 0x133_DPC_HDAudBus!HdaController::NotificationDpc

TARGET_TIME: 2019-02-15T16:00:27.000Z

OSBUILD: 17134

OSSERVICEPACK: 590

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2019-02-05 19:25:47

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: de6

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_dpc_hdaudbus!hdacontroller::notificationdpc

FAILURE_ID_HASH: {8d805003-5351-4426-ee74-e39512317d42}

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


:)

 

BSOD- DPC Watchdog violation

BSOD - DPC watchdog violation how to fix?

 

BSOD DPC WATCHDOG VIOLATION

According to what I found from your minidump file, ndis.sys is caused this
DPC WATCHDOG VIOLATION BSOD error on your Windows computer.It's a
NDIS 6.20 Wrapper Driver and installed onto your computer through Windows Update. As far as I know, you have installed new Windows updates lately.

You can uninstall those updates out of your computer, restart your PC and check again the result. Remember to do these steps in Safe Mode.

For more solutions to fix DPC watchdog violation BSOD error in case the above method doesn't work, check it out the following link below:

https://usefulpcguide.com/17082/dpc-watchdog-violation/

 

Help! Watchdog Violation

More info on that BSOD

How to Fix DPC_Watchdog_Violation Blue Screen error