win10 多次蓝屏

Question

Minidump文件代码如下

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

Loading Dump File [C:\Windows\Minidump\111222-7546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff8017e000000 PsLoadedModuleList = 0xfffff8017ec2a290
Debug session time: Sat Nov 12 14:00:24.697 2022 (UTC + 8:00)
System Uptime: 0 days 0:05:53.359
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
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8017e3f7d50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff80179dd5c90=0000000000000101
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: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffb701bf8d5180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec  
Value: 2155  

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 2151  

Key  : Analysis.IO.Other.Mb  
Value: 0  

Key  : Analysis.IO.Read.Mb  
Value: 0  

Key  : Analysis.IO.Write.Mb  
Value: 0  

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

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

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

Key  : Bugcheck.Code.DumpHeader  
Value: 0x101  

Key  : Bugcheck.Code.Register  
Value: 0x101  

Key  : Dump.Attributes.AsUlong  
Value: 8  

Key  : Dump.Attributes.KernelGeneratedTriageDump  
Value: 1  

FILE_IN_CAB: 111222-7546-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffffb701bf8d5180

BUGCHECK_P4: 2

FAULTING_PROCESSOR: 2

FAULTING_THREAD: ffffb701bf8e0340

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffffa066ca3fc20 0000000000000000 : fffffa066ca40000 fffffa066ca39000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME: nt!KiIdleLoop+54

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1682

STACK_COMMAND: .process /r /p 0xfffff8017ed24a00; .thread 0xffffb701bf8e0340 ; kb

BUCKET_ID_FUNC_OFFSET: 54

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_IDLE_THREAD_INTERRUPTS_DISABLED_nt!KiIdleLoop

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c899d515-25dc-e1c8-629e-155791332b8c}

Followup: MachineOwner

Answer 1

Hello

BUGCHECK_CODE： 101 CLOCK_WATCHDOG_TIMEOUT
The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked.

This error can be caused by wrong or corrupt hardware drivers. It may also occur due to Random Access Memory (RAM) issues, the CPU (Central Processing Unit) being overclocked, and BIOS problems.

The Minidump points to ntkrnlmp.exe, but the source of the problem is not ntkrnlmp.exe, but the data it is responsible for handling (programs, processes, and other items). If one of these programs is causing problems, it can stop ntkrnlmp.exe and crash your computer.

You can try the following troubleshooting steps until your computer works normally again:

• Disconnect External Devices
• Use another power adapter
• Update BIOS
• Run Windows Memory Diagnostic Tool
• Run Windows Troubleshooter
• Update Drivers
• Run System File Checker
• Fix Windows Registry
• Scan Your System for Malware
• Temporarily Disable Your Antivirus
• Check power hardware (if you recently replaced RAM or other components on your PC)

Reference documents：https://blog.pcrisk.com/windows/12822-clock-watchdog-timeout

Best Regards,
Wesley Li