Bonjour à tous,
J'ai remonté un ancien PC, cependant celui-ci n'arrête pas de planter avec le code "Clock Watchdog Timeout"
Je vous colle ici le message présent dans le minidump
Auriez-vous une idée ?
J'ai testé avec d'autres RAMs, une autre alimentation, une autre CG mais pas de changements.
Citation :
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\110622-4265-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`3e600000 PsLoadedModuleList = 0xfffff801`3f22a290
Debug session time: Sun Nov 6 20:22:04.803 2022 (UTC + 1:00)
System Uptime: 0 days 0:00:53.458
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`3e9f8fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`4247ec90=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: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff9b0191340180, 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: 2718
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 22420
Key : Analysis.IO.Other.Mb
Value: 7
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 32
Key : Analysis.Init.CPU.mSec
Value: 453
Key : Analysis.Init.Elapsed.mSec
Value: 40851
Key : Analysis.Memory.CommitPeak.Mb
Value: 96
Key : Bugcheck.Code.DumpHeader
Value: 0x101
Key : Bugcheck.Code.Register
Value: 0x101
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 110622-4265-01.dmp
BUGCHECK_CODE: 101
BUGCHECK_P1: 18
BUGCHECK_P2: 0
BUGCHECK_P3: ffff9b0191340180
BUGCHECK_P4: 2
FAULTING_PROCESSOR: 2
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: svchost.exe
STACK_TEXT:
fffff801`4247ec88 fffff801`3ea59672 : 00000000`00000101 00000000`00000018 00000000`00000000 ffff9b01`91340180 : nt!KeBugCheckEx
fffff801`4247ec90 fffff801`3e8d83ed : 00000000`00000000 fffff801`39d0c180 00000000`00000246 00000000`00000d5d : nt!KeAccumulateTicks+0x1844a2
fffff801`4247ecf0 fffff801`3e8d8991 : 00000000`00000c00 00000000`000007f7 fffff801`39d0c180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff801`4247ed40 fffff801`3e8d2803 : fffff801`39d0c180 00000000`00000000 fffff801`3f2315f8 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff801`4247ee80 fffff801`3e8db1c2 : ffffd98e`b555cf50 ffffd98e`b555cfd0 ffffd98e`b555cf00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
fffff801`4247ef30 fffff801`3e808a45 : 00000000`1ff3d1ea fffff801`3f2f39e0 fffff801`3f2f3a90 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
fffff801`4247ef60 fffff801`3e9faa4a : ffffd98e`b555cfd0 fffff801`3f2f39e0 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`4247efb0 fffff801`3e9fafb7 : 00000000`00000000 fffff801`3f32f240 ffff9b01`9128b078 fffff801`3e8cd6aa : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd98e`b555cf50 fffff801`3e872125 : ffffd98e`b555d128 ffffd98e`b555d120 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd98e`b555d0e0 fffff801`3ec01433 : 00000000`00000000 ffffd98e`b555db80 00000000`00000001 00000000`00000001 : nt!KeFlushProcessWriteBuffers+0xa9
ffffd98e`b555d120 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpGetProcessInformation+0x183
SYMBOL_NAME: nt!KeAccumulateTicks+1844a2
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.2006
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1844a2
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {95498f51-33a9-903b-59e5-d236937d8ecf}
Followup: MachineOwner
---------
|
Lien du fichier : https://uptobox.com/sbvf61o2mx1r
Message édité par chawat le 11-11-2022 à 15:43:28