DPC_WATCHDOG_VIOLATION Blue Screen continuously. Please advise, how do I fix this? Any help appreciated.

Question

DPC_WATCHDOG_VIOLATION Blue Screen continuously. Please advise, how do I fix this? Any help appreciated.

Anonymous

It seems watching a video for long enough (doesn't happen upon immediately playing a video but I can't get through them) or even a long enough download is the trigger. I have already: updated all drivers, made sure SSD firmware is up to date and ran chkdsk through command prompt. Before doing those things, I completely cleared my harddrives and reinstalled windows 10.

System info:

Alienware M17x R3

Bitdefender Total Security Antivrus/VPN

Two Samsung 870 EVO SATA 500GB SSDs make up a Raid 0 Array
Processor Intel(R) Core(TM) i7-2820QM CPU @ 2.30GHz 2.30 GHz
Installed RAM 16.0 GB
Device ID C182****-****-****-****-685D********
Product ID *****-*****-*****-*****
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 10 Pro
Version 22H2
Installed on ‎5/‎16/‎2023
OS build 19045.3086
Experience Windows Feature Experience Pack 1000.19041.1000.0

Event Viewer Warnings/Errors/Info:

Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 6/14/2023 3:47:07 PM Event ID: 10016 Task Category: None Level: Warning Keywords: Classic User: SYSTEM Computer: ****** Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.SecurityAppBroker and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 10016 0 3 0 0 0x8080000000000000 5638 System ****** application-specific Local Launch Windows.SecurityCenter.SecurityAppBroker Unavailable NT AUTHORITY SYSTEM S-1-5-18 LocalHost (Using LRPC) Unavailable Unavailable

Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 6/14/2023 3:47:07 PM Event ID: 10016 Task Category: None Level: Warning Keywords: Classic User: SYSTEM Computer: ****** Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscBrokerManager and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 10016 0 3 0 0 0x8080000000000000 5637 System ****** application-specific Local Launch Windows.SecurityCenter.WscBrokerManager Unavailable NT AUTHORITY SYSTEM S-1-5-18 LocalHost (Using LRPC) Unavailable Unavailable Log Name: System Source: ACPI Date: 6/14/2023 3:44:52 PM Event ID: 13 Task Category: None Level: Error Keywords: Classic User: N/A Computer: ****** Description: : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 13 0 2 0 0 0x80000000000000 5597 System ****** 0000C00001000000000000000D0005C0000000000000000000000000000000000000000000000000809698001300FFFF7300FC36A332FFFF1310A200630002005300AE037300646DA362FFFF13100807A3024800130A2F003382020015081B0010080D0090019F00600003005000680270000800101A210030830300151012002109110011132301A105000211122C00410201001618D500A6042A01161A3100368001001518150023901400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

Log Name: System Source: Service Control Manager Date: 6/14/2023 3:29:04 PM Event ID: 7026 Task Category: None Level: Information Keywords: Classic User: N/A Computer: ****** Description: The following boot-start or system-start driver(s) did not load: dam Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 7026 0 4 0 0 0x8080000000000000 5555 System ****** dam

This is from the most recent minidump file:

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8013defb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

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: 5171

    Key  : Analysis.Elapsed.mSec
    Value: 6687

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

    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  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8013defb320

BUGCHECK_P4: 0

FILE_IN_CAB:  061423-12671-01.dmp

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

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8013a11c630 -- (.trap 0xfffff8013a11c630)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe38f8c530000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801497c5496 rsp=fffff8013a11c7c8 rbp=fffff8013a11c810
 r8=0000000000000000  r9=0000000000000009 r10=0000000000000001
r11=fffff8013a11c730 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x555496:
fffff801`497c5496 c3              ret
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  firefox.exe

STACK_TEXT:  
fffff801`3a123c88 fffff801`3d643b14     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`3defb320 : nt!KeBugCheckEx
fffff801`3a123c90 fffff801`3d486e3d     : 000001c7`ab9c473b fffff801`38ba2180 00000000`00000246 00000000`0000d1d3 : nt!KeAccumulateTicks+0x1bfef4
fffff801`3a123cf0 fffff801`3d47dec1     : fffff801`493b1856 00000000`00007d10 fffff801`38ba2180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff801`3a123d40 fffff801`3d481253     : fffff801`38ba2180 00000000`00000000 fffff801`3de31550 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff801`3a123e80 fffff801`3d488ae2     : fffff801`3a11c630 fffff801`3a11c6b0 fffff801`3a11c600 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff801`3a123f30 fffff801`3d53ec65     : 00000001`f4459973 fffff801`3def3aa0 fffff801`3def3b50 ffffc180`8ce97b40 : nt!HalpTimerClockInterrupt+0xe2
fffff801`3a123f60 fffff801`3d5fdfca     : fffff801`3a11c6b0 fffff801`3def3aa0 00000000`00000000 ffffe38f`8c520000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`3a123fb0 fffff801`3d5fe797     : ffffe38f`00000000 00001f80`005f02d4 ffffe38f`8c534000 00000000`00000016 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff801`3a11c630 fffff801`497c5496     : fffff801`49601923 ffffe38f`8c530000 fffff801`3a11c810 ffffe38f`8c528000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`3a11c7c8 fffff801`49601923     : ffffe38f`8c530000 fffff801`3a11c810 ffffe38f`8c528000 ffffe38f`8c520000 : nvlddmkm+0x555496
fffff801`3a11c7d0 ffffe38f`8c530000     : fffff801`3a11c810 ffffe38f`8c528000 ffffe38f`8c520000 fffff801`3a11c800 : nvlddmkm+0x391923
fffff801`3a11c7d8 fffff801`3a11c810     : ffffe38f`8c528000 ffffe38f`8c520000 fffff801`3a11c800 00000000`00000000 : 0xffffe38f`8c530000
fffff801`3a11c7e0 ffffe38f`8c528000     : ffffe38f`8c520000 fffff801`3a11c800 00000000`00000000 ffffe38f`00000000 : 0xfffff801`3a11c810
fffff801`3a11c7e8 ffffe38f`8c520000     : fffff801`3a11c800 00000000`00000000 ffffe38f`00000000 00000000`00000002 : 0xffffe38f`8c528000
fffff801`3a11c7f0 fffff801`3a11c800     : 00000000`00000000 ffffe38f`00000000 00000000`00000002 00000000`00000018 : 0xffffe38f`8c520000
fffff801`3a11c7f8 00000000`00000000     : ffffe38f`00000000 00000000`00000002 00000000`00000018 ffffe38f`8c5287d8 : 0xfffff801`3a11c800

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

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

9 answers

Answer 1

Anonymous

No problem.

I read between the lines and downloaded the oldest available driver for the gpu for Windows 10. So far, so good! I'll update if that changes for those unfortunate enough to view this hoping for a solution.

Again, thanks for your replies.

Answer 2

Anonymous

Yes, the initial driver version helps to help you troubleshoot this issue. Feel free to come back to the community with any updates.

Answer 3

Hello,OstentatiousSerendipity

I'm sorry for misunderstanding your graphics card model.

After comprehensive observation, you should still need to troubleshoot the problem from the graphics card's own driver. I'm afraid we can't give more suggestions from Windows. The driver version given by some manufacturers may not be the most suitable for you, so I suggest you contact the Laptop manufacturer to ask if there is a better driver version to choose.

Answer 4

Hello Chandy,

Thanks for your reply.

I tried reinstalling the the driver a you said (not the latest, but the one before it) and it did not solve the issue. The graphics card is not a 1660ti though actually. It is a 460m. What made you think it was 1660ti? Perhaps therein lies a clue of solving this issue. But I've never GPU overclocked and it isn't overheating (fans cleaned, working properly & also looked at temps with CPU-Z.

So I re-downloaded the latest NVIDIA driver and BDODs seem more frequent. Happens from just simply loading a website sometimes. Do you have any other ideas/possible solutions? When you said old version how old did you mean?

Answer 5

Hello，OstentatiousSerendipity

Welcome to the Microsoft Community.

DPC_WATCHDOG_VIOLATION errors are usually caused by outdated or incompatible drivers, hardware problems, or corrupted system files. Based on the information you provided, it seems that you have taken some measures including formatting the drive and doing a clean install of Windows 10, then we may need to consider other dimensions to this issue. First of all, you can view the current causes of BSOD, as shown in the figure:

According to the analysis, the possible cause of the error is nvlddmkm.sys, which is an NVIDIA Windows kernel-mode driver file. This file is responsible for communicating with your NVIDIA graphics card and allowing it to function properly.

However, sometimes this file can become corrupt, outdated, or incompatible with your version of Windows and cause errors. There are some possible solutions you can try to fix this issue:

1->Reinstall the driver that is suitable for your graphics card, but don't choose the latest, but the old version of the driver. From your device, it seems that the graphics card on this laptop is 1660ti. If you are not familiar with how to find the old version of the driver, please contact Nvidia's technical support. The following official download link from Nvidia may be helpful:

Official GeForce Drivers | NVIDIA

Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate and safe information. Watch out for ads on the site that may advertise products frequently classified as PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

2-> If you have performed GPU overclocking in BIOS before, please roll back this operation. This can help you reduce the stress on your graphics card and prevent it from overheating or malfunctioning.

3-> Checking overheating can cause system instability and cause blue screen errors. Make sure the laptop's cooling system is functioning properly and that the vents aren't clogged with dust or debris. Keep your laptop cool with a cooling pad or external fan.

I hope the above solution can alleviate the current PC BSOD problem, if there is any result, please feel free to reply.

Best regards,

Chandy |Microsoft Community Support Specialist

Share via

DPC_WATCHDOG_VIOLATION Blue Screen continuously. Please advise, how do I fix this? Any help appreciated.

9 answers