Random BSOD - Bug Check 0x133 DPC_WATCHDOG_VIOLATION

  • Thread starter Thread starter Ferry_M
  • Start date Start date
F

Ferry_M

Guest
Hi all

My PC has Windows 10 (20H2), and randomly shows BSOD with the exact same error DPC_WATCHDOG_VIOLATION


Some snippets of my errors:

*******************************************************************************​

* *​

* 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: fffff801180fb320, 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​



Key : Analysis.CPU.mSec​

Value: 7843​



Key : Analysis.DebugAnalysisManager​

Value: Create​



Key : Analysis.Elapsed.mSec​

Value: 7877​



Key : Analysis.Init.CPU.mSec​

Value: 9671​



Key : Analysis.Init.Elapsed.mSec​

Value: 179112​



Key : Analysis.Memory.CommitPeak.Mb​

Value: 88​



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​





BUGCHECK_CODE: 133​



BUGCHECK_P1: 0​



BUGCHECK_P2: 501​



BUGCHECK_P3: 500​



BUGCHECK_P4: fffff801180fb320​



DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED​



TRAP_FRAME: ffff810481a37650 -- (.trap 0xffff810481a37650)​

NOTE: The trap frame does not contain all registers.​

Some register values may be zeroed or incorrect.​

rax=00000000439bbdd0 rbx=0000000000000000 rcx=ffff810481a37820​

rdx=ffff81048633a0b8 rsi=0000000000000000 rdi=0000000000000000​

rip=fffff8011764456b rsp=ffff810481a377e0 rbp=ffffa60b200991a0​

r8=fffff8011c0aa230 r9=0000000000000001 r10=fffff8011762c0a0​

r11=ffffc9fc43400000 r12=0000000000000000 r13=0000000000000000​

r14=0000000000000000 r15=0000000000000000​

iopl=0 nv up ei ng nz na pe nc​

nt!KeYieldProcessorEx+0x1b:​

fffff801`1764456b 5b pop rbx​

Resetting default scope​



BLACKBOXBSD: 1 (!blackboxbsd)​





BLACKBOXNTFS: 1 (!blackboxntfs)​





BLACKBOXPNP: 1 (!blackboxpnp)​





BLACKBOXWINLOGON: 1​



CUSTOMER_CRASH_COUNT: 1​



PROCESS_NAME: System​



STACK_TEXT:​

ffffda01`6ef12c88 fffff801`1783abce : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx​

ffffda01`6ef12c90 fffff801`1767541d : 0000e873`03b50165 ffffda01`6eec0180 00000000`00000246 00000000`00bace11 : nt!KeAccumulateTicks+0x1c89ce​

ffffda01`6ef12cf0 fffff801`176759c1 : 00000000`00bac900 00000000`006f582c ffffda01`6eec0180 00000000`00000001 : nt!KiUpdateRunTime+0x5d​

ffffda01`6ef12d40 fffff801`1766f833 : ffffda01`6eec0180 00000000`00000000 fffff801`18031ad0 00000000`00000000 : nt!KiUpdateTime+0x4a1​

ffffda01`6ef12e80 fffff801`176781f2 : ffff8104`81a37650 ffff8104`81a376d0 ffff8104`81a37600 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3​

ffffda01`6ef12f30 fffff801`17727f55 : 000001bd`656843aa ffffa60b`1c68eea0 ffffa60b`1c68ef50 ffff2100`6516b919 : nt!HalpTimerClockInterrupt+0xe2​

ffffda01`6ef12f60 fffff801`177f76fa : ffff8104`81a376d0 ffffa60b`1c68eea0 ffff8104`81a37b10 00005d68`09868690 : nt!KiCallInterruptServiceRoutine+0xa5​

ffffda01`6ef12fb0 fffff801`177f7c67 : ffff8104`00000000 00001f80`007f0274 00000000`439ae05c ffff8104`81a37820 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa​

ffff8104`81a37650 fffff801`1764456b : ffff8104`81a37880 fffff801`1762e09a 00000000`00000000 00000000`001c0000 : nt!KiInterruptDispatchNoLockNoEtw+0x37​

ffff8104`81a377e0 fffff801`1762e09a : 00000000`00000000 00000000`001c0000 ffffda01`6eec0180 00000000`00000000 : nt!KeYieldProcessorEx+0x1b​

ffff8104`81a377f0 fffff801`1762c113 : 00000000`439bbdd0 fffff801`1764520f 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x2a​

ffff8104`81a37820 fffff801`1c091d68 : 00000000`00000001 ffffa60b`200991a0 ffffa60b`200291b0 ffffa60b`1c8a7000 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x73​

ffff8104`81a37850 fffff801`17644f12 : 00000000`00000004 ffffda01`00000001 00000000`00000006 00000000`00000002 : ataport!IdePortTickHandler+0x228​

ffff8104`81a378e0 fffff801`17606eed : 00000000`00000000 fffff801`17732d75 00000000`00000000 00000000`006f5548 : nt!KiProcessExpiredTimerList+0x172​

ffff8104`81a379d0 fffff801`177f97be : ffffffff`00000000 ffffda01`6eec0180 ffffda01`6eecb140 ffffa60b`38475080 : nt!KiRetireDpcList+0x5dd​

ffff8104`81a37c60 00000000`00000000 : ffff8104`81a38000 ffff8104`81a32000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e​





SYMBOL_NAME: ataport!IdePortTickHandler+228​



MODULE_NAME: ataport​



IMAGE_NAME: ataport.SYS​



IMAGE_VERSION: 10.0.19041.488​



STACK_COMMAND: .thread ; .cxr ; kb​



BUCKET_ID_FUNC_OFFSET: 228​



FAILURE_BUCKET_ID: 0x133_DPC_ataport!IdePortTickHandler​



OS_VERSION: 10.0.19041.1​



BUILDLAB_STR: vb_release​



OSPLATFORM_TYPE: x64​



OSNAME: Windows 10​



FAILURE_ID_HASH: {1a227c77-b13d-69d2-f50f-db13cb900ecb}​



Followup: MachineOwner​



At first, I assumed it's my HDD. So I changed my HDD to a new SSD. But the problem persists

For some reason, I noticed the probability of BSOD increased whenever the audio output is working (playing music on Spotify, watching Youtube videos, or even doing video call with Zoom or Google Meet)


I posted my minidumps here:

2021-0412_Minidump.zip


Would appreaciate any help I can get

Best Regards,


Ferry

Continue reading...
 
Back
Top