Santy
These were related to your video driver. There is a known problem with the most recent drivers on some systems. As a workaround untill a less buggy driver is released I would remove the current driver and then install a much older driver (say
1 year older).... If you continue to crash I would remove Kaspersky and use the built in defender in its place
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: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff800c27e843a to fffff800c27c59a0
STACK_TEXT:
fffff800`c47aac88 fffff800`c27e843a : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff800`c47aac90 fffff800`c26c89b7 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1258a
fffff800`c47aad20 fffff800`c260d67f : 00000000`000000ff ffffd000`2ed7e0b0 fffff800`c26599b0 ffffe001`0000b201 : nt!KeClockInterruptNotify+0x787
fffff800`c47aaf40 fffff800`c275aeb3 : fffff800`c2659900 00000000`00000008 fffff800`c47aaf50 00000000`0000000c : hal!HalpTimerClockInterrupt+0x4f
fffff800`c47aaf70 fffff800`c27c6e2a : fffff800`c2659900 ffffe001`31101470 00000000`000001fa ffffe001`31361b60 : nt!KiCallInterruptServiceRoutine+0xa3
fffff800`c47aafb0 fffff800`c27c720f : 00000000`00000002 ffffe001`32e5ace0 ffffd000`2ed7e0b0 ffffe001`311ab000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff800`c479c710 fffff800`c272f09e : 00000000`0000eca9 00000000`00000000 ffffd000`3473c180 ffff8048`36320dd0 : nt!KiInterruptDispatchLBControl+0x11f
fffff800`c479c8a0 fffff800`c272f062 : 00000000`00000002 ffffe001`00000001 00000000`00000000 fffff800`c2978180 : nt!KxWaitForSpinLockAndAcquire+0x22
fffff800`c479c8d0 fffff801`01edcefc : 00000000`00000000 00000000`00315704 fffff800`c479ca20 fffff800`c26caa89 : nt!KeAcquireSpinLockRaiseToDpc+0x32
fffff800`c479c900 00000000`00000000 : 00000000`00315704 fffff800`c479ca20 fffff800`c26caa89 fffff800`c2978180 : nvlddmkm+0xd9efc
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+d9efc
fffff801`01edcefc ?? ???
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: nvlddmkm+d9efc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 54b0548e
FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm+d9efc
BUCKET_ID: 0x133_DPC_nvlddmkm+d9efc
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_dpc_nvlddmkm+d9efc
FAILURE_ID_HASH: {81acacb6-4e68-8882-f150-6f5501a9582b}
Followup: MachineOwner
---------