☰

分析 Windows 7 中的蓝屏死机

tag-icon • tag-icon windows-7 bsod windbg
分析 Windows 7 中的蓝屏死机

六个月前买了一台新电脑。从第一天起，它就表现得很奇怪。

它挂起了（没有 BSOD），唯一的办法就是重启它。在这种情况下，我不知道出了什么问题，因为没有核心转储。我查看了所有事件日志，没有发现任何异常。

有时它会让系统出现 BSOD。我有一个完整的核心转储文件，但无法找出罪魁祸首。

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

.


Loading Dump File [G:\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: F:\Program Files\Debug Symbols;SRV*F:\Program Files\Debug Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e45670
Debug session time: Thu Feb 16 18:33:27.793 2012 (UTC + 2:00)
System Uptime: 1 days 0:06:38.979
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
................................................................
................................................................
....................................
Loading unloaded module list
.............................................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff880009eb180, 1}

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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009eb180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`0a086328 fffff800`02cd48c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009eb180 : nt!KeBugCheckEx
fffff880`0a086330 fffff800`02c87497 : 00000000`00000000 fffff800`00000001 00000000`000186a0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0a0863c0 fffff800`031f3895 : fffff800`03219460 fffff880`0a086570 fffff800`03219460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a0864c0 fffff800`02c79173 : fffff800`02df2e80 00000000`00000001 00000000`00000001 fffff800`02c00000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a0864f0 fffff800`02c52667 : fffff800`02df2e80 fffff800`02e00cc0 00000000`00000046 fffff800`02c786dc : nt!KiInterruptDispatchNoLock+0x163
fffff880`0a086680 fffff800`02f86def : 00000000`00000000 fffff880`0a086b60 00000000`00000000 00000000`00000001 : nt!KeFlushProcessWriteBuffers+0x6b
fffff880`0a0866f0 fffff800`02f87449 : 00000000`03b55e30 fffff800`02f734de 00000000`00000000 fffff800`02c7bda1 : nt!ExpQuerySystemInformation+0x13af
fffff880`0a086aa0 fffff800`02c7bed3 : 00000000`00000000 000007fe`f80cc001 ffffffff`fffe7960 000007fe`f80d0b00 : nt!NtQuerySystemInformation+0x4d
fffff880`0a086ae0 00000000`77a9167a : 000007fe`f80c107b 00000000`01a3f901 ffffffff`fffe7960 00000000`00c4a9f0 : nt!KiSystemServiceCopyEnd+0x13
00000000`01a3f268 000007fe`f80c107b : 00000000`01a3f901 ffffffff`fffe7960 00000000`00c4a9f0 00000000`00c4a9f0 : ntdll!NtQuerySystemInformation+0xa
00000000`01a3f270 000007fe`f80c12cf : 00000000`00000052 00004e20`00013880 000007fe`f80cc048 00000000`00000000 : mmcss!CiSchedulerWait+0x61
00000000`01a3f2e0 00000000`77a9112b : 00000000`000000c0 00000000`1736e5d0 00000000`002a90b0 000007fe`f80c1101 : mmcss!CiSchedulerWorkerApc+0x3e1
00000000`01a3f3b0 00000000`77a9165a : 000007fe`f80c1aaf 00000000`002a90b0 000007fe`f80c303e 00000000`0fd1bf50 : ntdll!KiUserApcDispatch+0x2b
00000000`01a3f8a8 000007fe`f80c1aaf : 00000000`002a90b0 000007fe`f80c303e 00000000`0fd1bf50 00000000`00000000 : ntdll!NtDelayExecution+0xa
00000000`01a3f8b0 000007fe`f80c3c3d : 00000000`0000001b 0004c2c2`00130b08 00000000`0000002e 00000000`00000002 : mmcss!CiSchedulerInitiailize+0x143
00000000`01a3f910 00000000`ffdb1344 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mmcss!CsServiceMain+0x1ea
00000000`01a3f9c0 000007fe`ffd3a82d : 00000000`00000001 00000000`1736e5c8 00000000`00000000 00000000`00000000 : svchost!ServiceStarter+0x1e8
00000000`01a3fa50 00000000`7783652d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : sechost!ScSvcctrlThreadW+0x25
00000000`01a3fa80 00000000`77a6c521 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
00000000`01a3fab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

0: kd> lmvm Unknown_Module
start             end                 module name
0: kd> !thread @@c++((nt!_kprcb *)0xfffff880009eb180)->CurrentThread)
THREAD fffffa8008dd3060  Cid 0308.1374  Teb: 000007fffffd4000 Win32Thread: 0000000000000000 RUNNING on processor 0
Impersonation token:  fffff8a015aa7530 (Level Delegation)
Owning Process            fffffa80087fc390       Image:         svchost.exe
Attached Process          N/A            Image:         N/A
Wait Start TickCount      5563600        Ticks: 401 (0:00:00:06.255)
Context Switch Count      134512             
UserTime                  00:00:00.000
KernelTime                00:00:06.240
Win32 Start Address sechost!ScSvcctrlThreadW (0x000007feffd3a808)
Stack Init fffff8800a086c70 Current fffff8800a086830
Base fffff8800a087000 Limit fffff8800a081000 Call 0
Priority 27 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0a086328 fffff800`02cd48c9 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009eb180 : nt!KeBugCheckEx
fffff880`0a086330 fffff800`02c87497 : 00000000`00000000 fffff800`00000001 00000000`000186a0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0a0863c0 fffff800`031f3895 : fffff800`03219460 fffff880`0a086570 fffff800`03219460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a0864c0 fffff800`02c79173 : fffff800`02df2e80 00000000`00000001 00000000`00000001 fffff800`02c00000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a0864f0 fffff800`02c52667 : fffff800`02df2e80 fffff800`02e00cc0 00000000`00000046 fffff800`02c786dc : nt!KiInterruptDispatchNoLock+0x163 (TrapFrame @ fffff880`0a0864f0)
fffff880`0a086680 fffff800`02f86def : 00000000`00000000 fffff880`0a086b60 00000000`00000000 00000000`00000001 : nt!KeFlushProcessWriteBuffers+0x6b
fffff880`0a0866f0 fffff800`02f87449 : 00000000`03b55e30 fffff800`02f734de 00000000`00000000 fffff800`02c7bda1 : nt!ExpQuerySystemInformation+0x13af
fffff880`0a086aa0 fffff800`02c7bed3 : 00000000`00000000 000007fe`f80cc001 ffffffff`fffe7960 000007fe`f80d0b00 : nt!NtQuerySystemInformation+0x4d
fffff880`0a086ae0 00000000`77a9167a : 000007fe`f80c107b 00000000`01a3f901 ffffffff`fffe7960 00000000`00c4a9f0 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0a086ae0)
00000000`01a3f268 000007fe`f80c107b : 00000000`01a3f901 ffffffff`fffe7960 00000000`00c4a9f0 00000000`00c4a9f0 : ntdll!NtQuerySystemInformation+0xa
00000000`01a3f270 000007fe`f80c12cf : 00000000`00000052 00004e20`00013880 000007fe`f80cc048 00000000`00000000 : mmcss!CiSchedulerWait+0x61
00000000`01a3f2e0 00000000`77a9112b : 00000000`000000c0 00000000`1736e5d0 00000000`002a90b0 000007fe`f80c1101 : mmcss!CiSchedulerWorkerApc+0x3e1
00000000`01a3f3b0 00000000`77a9165a : 000007fe`f80c1aaf 00000000`002a90b0 000007fe`f80c303e 00000000`0fd1bf50 : ntdll!KiUserApcDispatch+0x2b (TrapFrame @ 00000000`01a3f718)
00000000`01a3f8a8 000007fe`f80c1aaf : 00000000`002a90b0 000007fe`f80c303e 00000000`0fd1bf50 00000000`00000000 : ntdll!NtDelayExecution+0xa
00000000`01a3f8b0 000007fe`f80c3c3d : 00000000`0000001b 0004c2c2`00130b08 00000000`0000002e 00000000`00000002 : mmcss!CiSchedulerInitiailize+0x143
00000000`01a3f910 00000000`ffdb1344 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mmcss!CsServiceMain+0x1ea
00000000`01a3f9c0 000007fe`ffd3a82d : 00000000`00000001 00000000`1736e5c8 00000000`00000000 00000000`00000000 : svchost!ServiceStarter+0x1e8
00000000`01a3fa50 00000000`7783652d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : sechost!ScSvcctrlThreadW+0x25
00000000`01a3fa80 00000000`77a6c521 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
00000000`01a3fab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d

答案1

我找到了崩溃/挂起的原因，或者至少我设法阻止它崩溃。

我安装了所有最新的驱动程序，但电脑仍然每隔一天就会死机。我重新安装了操作系统（和所有最新的驱动程序），但电脑仍然不断崩溃/死机。

我决定开始“移除”硬件。由于这台计算机基本上就是一块主板（上面有所有东西），因此几乎没有什么硬件需要移除。我首先更换了我的 Microsoft Wireless mouse 1000，换成了普通的 USB 鼠标。从那以后，计算机就再也没有挂起过。我确实有最新的鼠标驱动程序，所以我猜最新的驱动程序不够好。

最后要说的是，无线鼠标是随无线键盘一起提供的，我现在还在用。所以问题只出在鼠标上。

答案2

我将使用资源监视器来查看挂起之前是否有高系统中断请求。

要打开 RM，请使用 Win 键 + R 键，然后输入 resmon 并按回车键，转到 cpu 选项卡，单击 cpu 列的顶部以将最高 cpu 百分比浮动到顶部，并开始观察图像名称“系统中断”以开始使用高百分比的 cpu 周期。

如果它确实显示系统中断的 CPU 周期较高参见本教程如何追踪它。它通常是由有缺陷的驱动程序引起的，因此有时更新所有驱动程序可以解决问题，而无需进行深入的分析和调试。如果其他方法都失败，请重新安装操作系统，然后更新到最新的驱动程序。

答案3

CLOCK_WATCHDOG_TIMEOUT 的最常见原因是主板超频：

  • 如果您对主板进行超频，请立即撤消该更改。
  • 如果不适用，请最大限度地运行 Windows 更新，然后访问主板制造商，查看是否有适用于您的主板的较新的驱动程序。
  • 如果此方法不起作用并且笔记本电脑是新的，请将其退回至购买它的商店以获得退款。
  • 否则，请备份您的系统并为不久的将来可能需要新主板做好准备。

相关内容