ผู้สอบถาม
ขอวิธีเเก้ไข Blue Screen DPC_WATCHDOG_VIOLATION [Windows10]

คำถาม
-
ปัญหาเกิดขึ้นในระหว่างที่ใช้คอมพิวเตอร์ อาการคือคอมพิวเตอร์จะค้าง เมาส์ขยับไม่ได้ไปสักพัก เเละขึ้น Blue Screen ที่มี Stop Code ขึ้นมาว่า DPC_WATCHDOG_VIOLATION มักจะเกิดอาการนี้อยู่บ่อยครั้งมาก เเละเมื่อผม ใช้ Windbg เปิด Dump file มามีข้อความ
Microsoft (R) Windows Debugger Version 10.0.15063.400 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\james\Desktop\052617-8218-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`0c283000 PsLoadedModuleList = 0xfffff800`0c5cf5a0
Debug session time: Fri May 26 21:14:12.714 2017 (UTC + 7:00)
System Uptime: 0 days 0:36:51.562
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, fffff8000c664348, 0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
1: 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: 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: fffff8000c664348, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.15063.296 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: B85M-HD3
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: To be filled by O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: FH
BIOS_DATE: 08/13/2015
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: B85M-HD3
BASEBOARD_VERSION: x.x
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8000c664348
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: 4
CPU_MHZ: c15
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: ZEROED_STACK_0x133
BUGCHECK_STR: 0x133
PROCESS_NAME: League of Lege
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: DESKTOP-LUE8LGD
ANALYSIS_SESSION_TIME: 05-30-2017 13:03:38.0134
ANALYSIS_VERSION: 10.0.15063.400 amd64fre
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000c3ef310
STACK_TEXT:
ffff9b81`801e9bc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964
THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: ZEROED_STACK_0x133
PRIMARY_PROBLEM_CLASS: ZEROED_STACK
FAILURE_BUCKET_ID: ZEROED_STACK_0x133
TARGET_TIME: 2017-05-26T14:14:12.000Z
OSBUILD: 15063
OSSERVICEPACK: 296
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-04-28 06:52:30
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.15063.296
ANALYSIS_SESSION_ELAPSED_TIME: 4ef
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:zeroed_stack_0x133
FAILURE_ID_HASH: {6a989cd5-40e4-233b-794c-d6318e86cad7}
Followup: MachineOwner
---------
ผมควรเเก้ไขอย่างไรครับ
ตอบทั้งหมด
-
สวัสดีค่ะ
รบกวนลองทําตามขั้นบทความตอนต่อไปนี้
Bug Check 0x133 DPC_WATCHDOG_VIOLATION (for programmers)
Troubleshoot blue screen errors
หวังว่าจะช่วยให้คุณได้ค่ะ
ขอบคุณค่ะMSDN Community Support Please remember to click Mark as Answer ,the responses that resolved your issue, and to click Unmark as Answer if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
- เสนอเป็นคำตอบโดย Julia TuoModerator 4 มกราคม 2562 2:50