dpc watchdog violation pc random crash?!!

odiukurac70

Prominent
Dec 12, 2017
69
0
630
0
my pc started crashing a lot recently, not sure why, i've looked into a memory dump, but can't really understand why it is happening, my gpu is gt 1030 and processor is i3 4170, any help would really be appreciated, here is the memory dump: Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`d9a19000 PsLoadedModuleList = 0xfffff801`d9dc7290
Debug session time: Thu Oct 18 09:08:23.084 2018 (UTC - 4:00)
System Uptime: 0 days 0:37:41.765
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff801d9e66378
Arg4: 0000000000000000

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: TheCrew.exe

CURRENT_IRQL: d

LAST_CONTROL_TRANSFER: from fffff801d9c14495 to fffff801d9bc2490

STACK_TEXT:
fffff801`dbc70b78 fffff801`d9c14495 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`d9e66378 : nt!KeBugCheckEx
fffff801`dbc70b80 fffff801`d9af81ad : 000007a8`d1723512 fffff801`d886d180 00000000`00000246 00000000`00023571 : nt!KeAccumulateTicks+0x1187d5
fffff801`dbc70be0 fffff801`d9af9293 : fffff780`00000340 fffff801`d886d180 00000000`00023571 00000000`00000000 : nt!KiUpdateRunTime+0x5d
fffff801`dbc70c30 fffff801`da36d883 : 000007a8`d171b17e ffffd807`081eeb10 00000000`00000000 fffff801`dbc69280 : nt!KeClockInterruptNotify+0x8f3
fffff801`dbc70f40 fffff801`d9b45d75 : fffff801`da3cecb0 00000000`00040108 00000000`00000000 ffffd807`06e71940 : hal!HalpTimerClockInterrupt+0x63
fffff801`dbc70f70 fffff801`d9bc3d4a : fffff801`dbc69300 fffff801`da3cecb0 00000000`00000000 ffffd807`06e71940 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`dbc70fb0 fffff801`d9bc4237 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff801`dbc69280 fffff809`77086a61 : fffff809`770a99fc ffffd807`06fec000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`dbc69418 fffff809`770a99fc : ffffd807`06fec000 00000000`00000000 00000000`00000000 ffffd807`06fec000 : nvlddmkm+0x1e6a61
fffff801`dbc69420 ffffd807`06fec000 : 00000000`00000000 00000000`00000000 ffffd807`06fec000 ffffd807`00000020 : nvlddmkm+0x2099fc
fffff801`dbc69428 00000000`00000000 : 00000000`00000000 ffffd807`06fec000 ffffd807`00000020 fffff801`dbc69460 : 0xffffd807`06fec000


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+1e6a61
fffff809`77086a61 c3 ret

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: nvlddmkm+1e6a61

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5bbe7e34

FAILURE_BUCKET_ID: X64_0x133_nvlddmkm+1e6a61

BUCKET_ID: X64_0x133_nvlddmkm+1e6a61

Followup: MachineOwner
---------
 

Similar threads


ASK THE COMMUNITY

TRENDING THREADS