"DPC WATCHDOG VIOLATION" mavi ekran hatası

Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Users\Emir\Desktop\060821-13328-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 (Service Pack 16) MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff802`44400000 PsLoadedModuleList = 0xfffff802`4502a1b0

Debug session time: Tue Jun  8 22:32:54.729 2021 (UTC + 3:00)

System Uptime: 2 days 0:23:20.141

Loading Kernel Symbols

...............................................................

................................................................

................................................................

...............

Loading User Symbols

Loading unloaded module list

..................................................

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff802`447f6cf0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff802`4807be20=0000000000000133

0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        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: fffff802450fa320, 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                                   ***

***                                                                   ***

*************************************************************************

*** WARNING: Unable to verify checksum for win32k.sys



KEY_VALUES_STRING: 1



    Key  : Analysis.CPU.mSec

    Value: 6374



    Key  : Analysis.DebugAnalysisManager

    Value: Create



    Key  : Analysis.Elapsed.mSec

    Value: 91688



    Key  : Analysis.Init.CPU.mSec

    Value: 468



    Key  : Analysis.Init.Elapsed.mSec

    Value: 85212



    Key  : Analysis.Memory.CommitPeak.Mb

    Value: 83



    Key  : WER.OS.Branch

    Value: vb_release



    Key  : WER.OS.Timestamp

    Value: 2019-12-06T14:06:00Z



    Key  : WER.OS.Version

    Value: 10.0.19041.1





BUGCHECK_CODE:  133



BUGCHECK_P1: 0



BUGCHECK_P2: 501



BUGCHECK_P3: 500



BUGCHECK_P4: fffff802450fa320



DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED



TRAP_FRAME:  fffff8024806cb00 -- (.trap 0xfffff8024806cb00)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000010072 rbx=0000000000000000 rcx=ffffdd89baefe7b0

rdx=000000000010a01c rsi=0000000000000000 rdi=0000000000000000

rip=fffff80258655092 rsp=fffff8024806cc90 rbp=fffff8024806cd20

 r8=fffff8024806ccb0  r9=000000000010a01c r10=ffffdd89bfb67d40

r11=000000000000000c r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl nz ac pe nc

nvlddmkm+0x85092:

fffff802`58655092 488b5c2440      mov     rbx,qword ptr [rsp+40h] ss:0018:fffff802`4806ccd0=0000000000000020

Resetting default scope



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXPNP: 1 (!blackboxpnp)





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT:  1



PROCESS_NAME:  System



STACK_TEXT:

fffff802`4807be18 fffff802`4481ee32     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

fffff802`4807be20 fffff802`44616ac3     : 000071f4`eb5cb1ea fffff802`3fe20180 00000000`00000000 fffff802`3fe20180 : nt!KeAccumulateTicks+0x205b12

fffff802`4807be80 fffff802`446165aa     : fffff802`450f3800 fffff802`4806cb80 fffff802`46fcdf00 00000000`00005001 : nt!KeClockInterruptNotify+0x453

fffff802`4807bf30 fffff802`4467e795     : fffff802`450f3800 00000000`00000000 00000000`00000000 ffffb3b3`3a1dc8cd : nt!HalpTimerClockIpiRoutine+0x1a

fffff802`4807bf60 fffff802`447f879a     : fffff802`4806cb80 fffff802`450f3800 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

fffff802`4807bfb0 fffff802`447f8d07     : 00000000`00000000 00000000`00000000 04808080`80052242 42c1dc10`01080c52 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

fffff802`4806cb00 fffff802`58655092     : 00000000`0010a01c ffffdd89`c86cc000 ffffdd89`c86cd098 00000000`0010a01c : nt!KiInterruptDispatchNoLockNoEtw+0x37

fffff802`4806cc90 00000000`0010a01c     : ffffdd89`c86cc000 ffffdd89`c86cd098 00000000`0010a01c 00000000`00000000 : nvlddmkm+0x85092

fffff802`4806cc98 ffffdd89`c86cc000     : ffffdd89`c86cd098 00000000`0010a01c 00000000`00000000 00000000`00000000 : 0x10a01c

fffff802`4806cca0 ffffdd89`c86cd098     : 00000000`0010a01c 00000000`00000000 00000000`00000000 ffffdd89`bad99cf0 : 0xffffdd89`c86cc000

fffff802`4806cca8 00000000`0010a01c     : 00000000`00000000 00000000`00000000 ffffdd89`bad99cf0 fffff802`586e440d : 0xffffdd89`c86cd098

fffff802`4806ccb0 00000000`00000000     : 00000000`00000000 ffffdd89`bad99cf0 fffff802`586e440d 00000000`00000020 : 0x10a01c





SYMBOL_NAME:  nvlddmkm+85092



MODULE_NAME: nvlddmkm



IMAGE_NAME:  nvlddmkm.sys



STACK_COMMAND:  .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET:  85092



FAILURE_BUCKET_ID:  0x133_DPC_nvlddmkm!unknown_function



OS_VERSION:  10.0.19041.1



BUILDLAB_STR:  vb_release[/SPOILER]



OSPLATFORM_TYPE:  x64



OSNAME:  Windows 10



FAILURE_ID_HASH:  {15c3af0e-5564-7a80-2e26-65b5115ecc4d}



Followup:     MachineOwner

---------