New
#1
DPC_Watchdog_Violation because of nvlddmkm.sys, Please Help!
Hello, everyday I get a BSOD once or twice while doing normal stuff, such as watching YouTube, playing video games, or just browsing the internet. It is caused by nvlddmkm.sys. How do I fix this? My version of Windows is Windows 10 22H2 Build number 19045.4529, I have a NVIDIA GeForce GTX 1660 TI, and my graphics drivers are up-to-date (According to NVIDIA)! YouTube or Google is no help! Also, it freezes randomly from time to time before a BSOD. Here is the DMP file.
*******************************************************************************
* *
* 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: fffff802696fb320, 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: 4093
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 6136
Key : Analysis.Init.CPU.mSec
Value: 781
Key : Analysis.Init.Elapsed.mSec
Value: 35096
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff802696fb320
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff802`6f27ec88 fffff802`68e1ed32 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff802`6f27ec90 fffff802`68c1c53d : 0000051b`a3a4ed7d fffff802`67e60180 00000000`00000246 00000000`0002203d : nt!KeAccumulateTicks+0x205a12
fffff802`6f27ecf0 fffff802`68c1cae1 : 00000000`00000000 00000000`00014464 fffff802`67e60180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff802`6f27ed40 fffff802`68c16953 : fffff802`6f26fdc0 00000000`00000000 fffff802`69631460 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff802`6f27ee80 fffff802`68c1f312 : fffff802`6f26fdc0 fffff802`6f26fe40 fffff802`6f26fe00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
fffff802`6f27ef30 fffff802`68c7e795 : 00000005`11a79d3f fffff802`696f39a0 fffff802`696f3a50 ffffa28c`e94b012b : nt!HalpTimerClockInterrupt+0xe2
fffff802`6f27ef60 fffff802`68df86ca : fffff802`6f26fe40 fffff802`696f39a0 00000000`00000069 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`6f27efb0 fffff802`68df8c37 : ffff868f`15395098 ffff868f`15394000 ffff868f`15395098 fffff802`7532489b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`6f26fdc0 fffff802`68c3a390 : fffff802`7532489b ffff868f`15394000 fffff802`753a53a6 ffff868f`15394000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`6f26ff58 fffff802`7532489b : ffff868f`15394000 fffff802`753a53a6 ffff868f`15394000 00000000`00000000 : nt!KzLowerIrql
fffff802`6f26ff60 ffff868f`15394000 : fffff802`753a53a6 ffff868f`15394000 00000000`00000000 00000000`00000001 : nvlddmkm+0x9489b
fffff802`6f26ff68 fffff802`753a53a6 : ffff868f`15394000 00000000`00000000 00000000`00000001 fffff802`75325b37 : 0xffff868f`15394000
fffff802`6f26ff70 ffff868f`15394000 : 00000000`00000000 00000000`00000001 fffff802`75325b37 00000000`00000001 : nvlddmkm+0x1153a6
fffff802`6f26ff78 00000000`00000000 : 00000000`00000001 fffff802`75325b37 00000000`00000001 ffff868f`15394000 : 0xffff868f`15394000
SYMBOL_NAME: nvlddmkm+9489b
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 9489b
FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}
Followup: MachineOwner
Quote