Remove From My Forums

蓝屏死机（含Kernel Dump）

问题

登录进行投票

蓝屏……CLOCK_WATCHDOG_TIMEOUT

配置：
AMD A10-5800K
ASRock FM2A85X Extreme4
8GB DDR3 1600 * 2
剩下略

问题：
1. 平时应用没问题
2. 但是一旦使用Chrome看视频有非常高的机率死机
3. 死机之后可能是以下两种情况之一：A 画面定格声音鬼畜 B 蓝屏错误代码为 CLOCK_WATCHDOG_TIMEOUT 存储内核转储文件后重启
4. 重启之后可能很快再次死机也有可能正常使用直到使用Chrome再次看视频（回到2）

已尝试解决方案：
1. 重装系统并更换驱动：无效。试过8.1 和 10，完全一样的问题。
2. 内存测试：通过。不论是单插任何一条或者是两条都插，都会出问题，并且内存测试都正常。
3. 给CPU略加电压：无效。
4. 检查温度：正常，死机时50来度。
5. 更换浏览器：略好，Edge下死机所用时间略长，比如说Chrome的期望是20分钟，Edge就是1个小时。
6. 怀疑是定时器问题，在UEFI设置中关闭高精度定时器（HPET）：无效。

于是没辙了。打了两份蓝屏的Kernel Dump，用WinDBG看了下，问题似乎出在同一个处理器核心上……所以目前怀疑是CPU挂了……

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Desktop\010216-36500-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 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.17.amd64fre.th2_release.151121-2308
Machine Name:
Kernel base = 0xfffff801`e088c000 PsLoadedModuleList = 0xfffff801`e0b6ac70
Debug session time: Sat Jan  2 20:43:20.625 2016 (UTC + 8:00)
System Uptime: 0 days 0:02:24.609
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 101, {30, 0, ffffd0004ebaf180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd0004ebaf180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10586.17.amd64fre.th2_release.151121-2308

SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.

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:  P1.20

BIOS_DATE:  11/23/2012

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  FM2A85X Extreme4

BASEBOARD_VERSION:                        

DUMP_TYPE:  2

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffd0004ebaf180

BUGCHECK_P4: 2

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CPU_COUNT: 4

CPU_MHZ: ed1

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 10

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  MWICBCUKeyTool

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  * HIDDEN *

ANALYSIS_SESSION_TIME:  01-02-2016 21:17:49.0640

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:  
fffff801`e267dce8 fffff801`e09e84d1 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffd000`4ebaf180 : nt!KeBugCheckEx
fffff801`e267dcf0 fffff801`e08a8266 : fffff801`e0b71e50 00000000`00000001 00000000`00000000 fffff801`e0ba9180 : nt! ?? ::FNODOBFM::`string'+0xb3d1
fffff801`e267dd80 fffff801`e08aa4af : 00000000`00000000 00000000`00000000 fffff801`e0b71e08 00000000`00000001 : nt!KiUpdateRunTime+0x56
fffff801`e267dde0 fffff801`e081ba46 : 00000000`00000000 fffff801`e0ba9180 00000000`0000000c 00000089`4ab279c9 : nt!KeClockInterruptNotify+0x44f
fffff801`e267df40 fffff801`e0890387 : fffff801`e08664b0 00000000`00000000 00000000`10bfb39c 00000000`00000000 : hal!HalpTimerClockInterrupt+0x56
fffff801`e267df70 fffff801`e09cfb8a : fffff801`e08664b0 fffff801`e0ba9180 00000000`00000001 ffffd000`222e81d8 : nt!KiCallInterruptServiceRoutine+0x87
fffff801`e267dfb0 fffff801`e09cffb7 : 00000000`00000000 00000000`10df10a2 fffff801`e0ba9180 ffffd000`222e7da0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`222e7d50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  35992f6588c65aebceca792cfd310ad615a59da2

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  84dfbb77328c67307674ad910bf5c4569b6adff1

THREAD_SHA1_HASH_MOD:  a9cc1cb37e3d9e930b1afbb48ba59d1f86f35b81

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function

PRIMARY_PROBLEM_CLASS:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function

TARGET_TIME:  2016-01-02T12:43:20.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-11-22 17:24:24

BUILDDATESTAMP_STR:  151121-2308

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.17.amd64fre.th2_release.151121-2308

ANALYSIS_SESSION_ELAPSED_TIME: 74d1

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_4_proc_analysis_inconclusive!unknown_function

FAILURE_ID_HASH:  {c17bf7e9-6a42-8b0a-186c-578c6eecf153}

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

Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\010216-38312-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 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.17.amd64fre.th2_release.151121-2308
Machine Name:
Kernel base = 0xfffff801`de075000 PsLoadedModuleList = 0xfffff801`de353c70
Debug session time: Sat Jan  2 21:48:19.741 2016 (UTC + 8:00)
System Uptime: 0 days 1:02:06.625
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 101, {30, 0, ffffd000293af180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd000293af180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10586.17.amd64fre.th2_release.151121-2308

SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.

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:  P1.20

BIOS_DATE:  11/23/2012

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  FM2A85X Extreme4

BASEBOARD_VERSION:                        

DUMP_TYPE:  2

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffffd000293af180

BUGCHECK_P4: 2

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CPU_COUNT: 4

CPU_MHZ: ed1

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 10

CPU_STEPPING: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  ThunderPlatfor

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  * HIDDEN *

ANALYSIS_SESSION_TIME:  01-02-2016 21:59:07.0547

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:  
fffff801`dfe7dce8 fffff801`de1d14d1 : 00000000`00000101 00000000`00000030 00000000`00000000 ffffd000`293af180 : nt!KeBugCheckEx
fffff801`dfe7dcf0 fffff801`de091266 : fffff801`de35adf0 00000000`00000001 00000000`00000000 fffff801`de392180 : nt! ?? ::FNODOBFM::`string'+0xb3d1
fffff801`dfe7dd80 fffff801`de0934af : 00000000`00000000 00000000`00000000 fffff801`de35ae98 00000000`00000000 : nt!KiUpdateRunTime+0x56
fffff801`dfe7dde0 fffff801`de004a46 : 00000000`00000000 fffff801`de392180 00000000`0000000c 00000ce1`cffd39aa : nt!KeClockInterruptNotify+0x44f
fffff801`dfe7df40 fffff801`de079387 : fffff801`de04f4b0 00000000`00000000 00000000`00000001 00000000`00000000 : hal!HalpTimerClockInterrupt+0x56
fffff801`dfe7df70 fffff801`de1b8b8a : fffff801`de04f4b0 fffff801`de392180 00000000`0000ffff 00000000`0d99e6e0 : nt!KiCallInterruptServiceRoutine+0x87
fffff801`dfe7dfb0 fffff801`de1b8fb7 : 00000000`00000000 00000000`00000001 fffff801`de392180 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`226edc60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  35992f6588c65aebceca792cfd310ad615a59da2

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  84dfbb77328c67307674ad910bf5c4569b6adff1

THREAD_SHA1_HASH_MOD:  a9cc1cb37e3d9e930b1afbb48ba59d1f86f35b81

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function

BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function

PRIMARY_PROBLEM_CLASS:  CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE!Unknown_Function

TARGET_TIME:  2016-01-02T13:48:19.000Z

OSBUILD:  10586

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2015-11-22 17:24:24

BUILDDATESTAMP_STR:  151121-2308

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.17.amd64fre.th2_release.151121-2308

ANALYSIS_SESSION_ELAPSED_TIME: 9a06

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:clock_watchdog_timeout_4_proc_analysis_inconclusive!unknown_function

FAILURE_ID_HASH:  {c17bf7e9-6a42-8b0a-186c-578c6eecf153}

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

2016年1月27日 13:54

答案

0

登录进行投票
您好，

从您上传的dump文件来看，此错误是因为处理器没有相应中断。

详情可以参考如下文档：

http://blogs.msdn.com/b/ntdebugging/archive/2011/10/26/debugging-a-clock-watchdog-timeout-bugcheck.aspx

建议您升级或者重装您的各个驱动程序，特别是显卡驱动程序看看是否可以解决。

可以尝试如下解决方案：

蓝屏错误疑难解答

http://windows.microsoft.com/zh-cn/windows-10/troubleshoot-blue-screen-errors
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
- 已建议为答案 Karen HuModerator 2016年2月4日 7:00
- 已标记为答案 MeipoXuMicrosoft contingent staff, Moderator 2016年2月5日 8:40
2016年1月28日 7:32

回复

|

引用

版主
0

登录进行投票
WatchDog 而是一种“看门狗”计时器测试用驱动，很多其它设备驱动要用到它。

从故障现象看，可能你用的 Chrome 浏览器或其使用的视频插件与看门狗计时器驱动存在兼容问题。

Alexis Zhang

http://mvp.microsoft.com/zh-cn/mvp/Jie%20Zhang-4000545
http://blogs.itecn.net/blogs/alexis

推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

本帖是回复帖，原帖作者是楼上的 <EraserKing_CN>；

| 1. 平时应用没问题
| 2. 但是一旦使用Chrome看视频有非常高的机率死机
- 已建议为答案 Karen HuModerator 2016年2月4日 7:01
- 已标记为答案 MeipoXuMicrosoft contingent staff, Moderator 2016年2月5日 8:40
2016年2月1日 14:09

回复

|

引用

全部回复

0

登录进行投票
您好，

从您上传的dump文件来看，此错误是因为处理器没有相应中断。

详情可以参考如下文档：

http://blogs.msdn.com/b/ntdebugging/archive/2011/10/26/debugging-a-clock-watchdog-timeout-bugcheck.aspx

建议您升级或者重装您的各个驱动程序，特别是显卡驱动程序看看是否可以解决。

可以尝试如下解决方案：

蓝屏错误疑难解答

http://windows.microsoft.com/zh-cn/windows-10/troubleshoot-blue-screen-errors
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
- 已建议为答案 Karen HuModerator 2016年2月4日 7:00
- 已标记为答案 MeipoXuMicrosoft contingent staff, Moderator 2016年2月5日 8:40
2016年1月28日 7:32

回复

|

引用

版主
0

登录进行投票
WatchDog 而是一种“看门狗”计时器测试用驱动，很多其它设备驱动要用到它。

从故障现象看，可能你用的 Chrome 浏览器或其使用的视频插件与看门狗计时器驱动存在兼容问题。

Alexis Zhang

http://mvp.microsoft.com/zh-cn/mvp/Jie%20Zhang-4000545
http://blogs.itecn.net/blogs/alexis

推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

本帖是回复帖，原帖作者是楼上的 <EraserKing_CN>；

| 1. 平时应用没问题
| 2. 但是一旦使用Chrome看视频有非常高的机率死机
- 已建议为答案 Karen HuModerator 2016年2月4日 7:01
- 已标记为答案 MeipoXuMicrosoft contingent staff, Moderator 2016年2月5日 8:40
2016年2月1日 14:09

回复

|

引用

产品

Resources

Solutions

更新

试用版

相关站点

培训

认证

其他资源

产品支持

其他支持

不是 IT 专业人员？

积极答复者

蓝屏死机（含Kernel Dump）

问题

答案

全部回复