Frequent DPC_WATCHDOG_VIOLATION when trying to load webpages and/or videos; How do I fix this?

N C 0 Reputation points
2023-07-12T19:34:40.23+00:00

Computer Info: Alienware M17x R3 running Windows 10 Pro 64bit, NVIDIA Geforce Gtx 460m gpu, Intel(R) Core(TM) i7-2820QM CPU @ 2.30GHz 2.30 GHz, 16gb DDR3 ram. Recently Formatted both new Samsung 870 EVO SSDs (500gb each) with a new Windows 10 installation; they are in a Raid 0 array. Using Bitdefender total security/vpn

Was previously getting the following in dump file crashes:

SYMBOL_NAME:  nvlddmkm+555496

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  555496

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner

So I downloaded the oldest available NVIDIA driver for the GPU and am now getting the following in the dump file:

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: fffff803816fb320, 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: 5609

    Key  : Analysis.Elapsed.mSec
    Value: 6568

    Key  : Analysis.IO.Other.Mb
    Value: 18

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 26

    Key  : Analysis.Init.CPU.mSec
    Value: 2280

    Key  : Analysis.Init.Elapsed.mSec
    Value: 95912

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 102

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x133

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_DPC_cng!EntropyPoolAdd

    Key  : Failure.Hash
    Value: {1b7527b9-0871-f0b3-8cdf-026e0620f281}

    Key  : Hypervisor.Enlightenments.Value
    Value: 69193628

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 41fcf9c

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 0

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4722927

    Key  : Hypervisor.Flags.ValueHex
    Value: 4810ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : SecureKernel.HalpHvciEnabled
    Value: 1

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff803816fb320

FILE_IN_CAB:  MEMORY.DMP

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


DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff8a0c43a29480 -- (.trap 0xffff8a0c43a29480)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff803835b88e8
rdx=ffff9201e00c87e4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80380d408d8 rsp=ffff8a0c43a29610 rbp=000000000001f400
 r8=0000000000000080  r9=000000000001f400 r10=fffff80380c1e610
r11=ffff81fb05a00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KxWaitForSpinLockAndAcquire+0x28:
fffff803`80d408d8 7446            je      nt!KxWaitForSpinLockAndAcquire+0x70 (fffff803`80d40920) [br=0]
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT:  
ffff9201`e0112e18 fffff803`80e43b82     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9201`e0112e20 fffff803`80c813c3     : 000009f6`f3c9a577 ffff9201`e00c0180 00000000`00000000 ffff9201`e00c0180 : nt!KeAccumulateTicks+0x1bff62
ffff9201`e0112e80 fffff803`80c80eaa     : ffffb787`43ea5240 ffff8a0c`43a29500 fffff803`84337300 00000000`00009101 : nt!KeClockInterruptNotify+0x453
ffff9201`e0112f30 fffff803`80d3ec85     : ffffb787`43ea5240 ffff9201`e0112f40 00000000`0000000c ffff0b28`bbb80fe1 : nt!HalpTimerClockIpiRoutine+0x1a
ffff9201`e0112f60 fffff803`80dfe05a     : ffff8a0c`43a29500 ffffb787`43ea5240 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9201`e0112fb0 fffff803`80dfe827     : ffffb787`44ed6f20 00000000`ffffffff ffffb787`6112d97c fffff803`80d9fb73 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8a0c`43a29480 fffff803`80d408d8     : 00000000`00000002 ffffffff`ffffffff 000000b5`00000001 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8a0c`43a29610 fffff803`80c1e698     : fffff803`835b88e8 00000000`00000002 00000000`00000000 ffff1325`180bb6f1 : nt!KxWaitForSpinLockAndAcquire+0x28
ffff8a0c`43a29640 fffff803`8351fc5f     : 00000000`00000080 00000000`00000000 ffff9201`e00c0180 fffff803`80c83c50 : nt!KeAcquireSpinLockRaiseToDpc+0x88
ffff8a0c`43a29670 fffff803`8351fb93     : ffffb787`43e9d530 00000000`00000000 ffffb787`4c8f1300 ffff8a0c`43a298a0 : cng!EntropyPoolAdd+0x67
ffff8a0c`43a29710 fffff803`8351f9fd     : ffffb787`4c8f1560 ffff8a0c`43a29b34 ffff8a0c`43a29b38 ffff8a0c`43a29b31 : cng!EntropyProvideData+0x183
ffff8a0c`43a29800 fffff803`80d21f8d     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cng!EntropyTimingCallback+0x1d
ffff8a0c`43a29830 fffff803`80c8b57e     : ffff9201`e00c3240 ffffb787`43fdb000 ffff8a0c`43a29b60 ffff9201`00000002 : nt!KiEntropyDpcRoutine+0x3d
ffff8a0c`43a29860 fffff803`80c8a864     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffff8a0c`43a299d0 fffff803`80e009be     : ffffffff`00000000 ffff9201`e00c0180 00000000`00000000 ffff9201`e00cb240 : nt!KiRetireDpcList+0x1f4
ffff8a0c`43a29c60 00000000`00000000     : ffff8a0c`43a2a000 ffff8a0c`43a24000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  cng!EntropyPoolAdd+67

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  67

FAILURE_BUCKET_ID:  0x133_DPC_cng!EntropyPoolAdd

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1b7527b9-0871-f0b3-8cdf-026e0620f281}

Followup:     MachineOwner

Any help or advice would be appreciated!

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,159 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. 2023-09-13T09:22:17.2833333+00:00

    Hello

    The DPC_WATCHDOG_VIOLATION (133) error is usually related to a device driver issue and appears on a Blue Screen of Death (BSOD). The error message is triggered by the DPC Watchdog Timer when it detects a DPC (Deferred Procedure Call) is running past its predetermined runtime.

    In your case, it seems like the cng.sys file might be causing the issue. This file is a system file that is associated with the Cryptography Next Generation (CNG) feature of Windows. It’s used for software-based encryption and decryption.

    Here are some steps you can take to resolve this issue:

    Update Your Drivers: The DPC Watchdog Violation error can be caused by outdated or incorrectly installed drivers. You should check if there are any updates available for your drivers, especially those related to the cng.sys file.

    Check for System File Corruption: Use the System File Checker tool to repair missing or corrupted system files. To do this, open Command Prompt as an administrator and type sfc /scannow.

    Check for Malware: Run a full system scan with your antivirus software to check for any malware that might be causing the issue.

    Perform a System Restore: If none of the above solutions work, you might want to consider performing a system restore to revert your system back to a state before the issue started occurring.

    Remember to always back up your data before making any major changes to your system.

    0 comments No comments

  2. Docs 15,071 Reputation points
    2023-09-14T02:37:55.3933333+00:00

    Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    https://www.elevenforum.com/t/bsod-posting-instructions.103/

    .

    .

    .

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    .

    .

    .

    0 comments No comments