win10 dpc_watchdog_violation (133)

      最近的蓝屏现象总是发生在使用优酷观看视频时，十分期望并感谢您的帮助。The recent blue screen phenomenon always happens when watching videos using Youku. We look forward to and thank you for your help.以下是最近一次的dump文件分析结果：The following is the analysis result of the latest dump 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: 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: fffff804254fb320, 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: 2374

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 95787

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  081622-11171-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff804254fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
fffff804`28a918d8 fffff804`24c36f70     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`254fb320 : nt!KeBugCheckEx
fffff804`28a918e0 fffff804`24a64c7d     : 0000382f`547f1740 fffff804`1ffb8180 00000000`00000246 00000000`001743bc : nt!KeAccumulateTicks+0x1d5510
fffff804`28a91940 fffff804`24a65221     : 00000000`00000000 00000000`000ddde4 fffff804`1ffb8180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff804`28a91990 fffff804`24a5f093     : fffff804`1ffb8180 00000000`00000000 fffff804`25431868 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff804`28a91ad0 fffff804`24a67a92     : fffff804`28a91c50 fffff804`28a91cd0 fffff804`28a91c00 00000000`00000009 : nt!KeClockInterruptNotify+0x2e3
fffff804`28a91b80 fffff804`24a2d885     : 00000037`77aae20e fffff804`254f3a20 fffff804`254f3ad0 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
fffff804`28a91bb0 fffff804`24bf980a     : fffff804`28a91cd0 fffff804`254f3a20 00000000`00800000 fffff804`24b1962a : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`28a91c00 fffff804`24bf9d77     : ffffffff`ffffffff 00000000`00000009 00000000`0000000f 00000000`00000040 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`28a91c50 fffff804`3a19524f     : ffffcf0c`15489000 00000000`00000000 00000000`00400a02 fffff804`24bf9d84 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`28a91de0 ffffcf0c`15489000     : 00000000`00000000 00000000`00400a02 fffff804`24bf9d84 00000002`00001000 : e2kw10x64+0x524f
fffff804`28a91de8 00000000`00000000     : 00000000`00400a02 fffff804`24bf9d84 00000002`00001000 00000000`00000000 : 0xffffcf0c`15489000


SYMBOL_NAME:  e2kw10x64+524f

MODULE_NAME: e2kw10x64

IMAGE_NAME:  e2kw10x64.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  524f

FAILURE_BUCKET_ID:  0x133_ISR_e2kw10x64!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9c01ef11-2991-5d8d-8377-7166c710aa5a}

Followup:     MachineOwner
---------      欢迎咨询本站！。建议全盘搜索一下e2kw10x64.sys找到后鼠标右击该文件，属性，详细信息，看下具体的情况。