Question BSOD Problems

[orbitals]

Hello I have been having some problems with my PC with two BSODs for about a month now and was looking for some help. The two error codes I have been getting are CLOCK_WATCHDOG_TIMEOUT and WHAE_UNCORRECTABLE_ERROR. I will also be linking the dump file below if that helps. If anyone would be willing to look into it I would appreciate it.



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


Loading Dump File [C:\Users\User\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80562e00000 PsLoadedModuleList = 0xfffff80563a2a2d0
Debug session time: Mon Feb 6 10:46:34.289 2023 (UTC - 5:00)
System Uptime: 2 days 20:41:26.453
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000d335842018). Type ".hh dbgerr001" for details Loading unloaded module list ................................... For analysis of this file, run !analyze -v 4: kd> !analyze -v ******************************************************************************* [LIST] [*]* [*]Bugcheck Analysis * [*]* [/LIST] ******************************************************************************* 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: 000000000000000c, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffffd900820e7180, The PRCB address of the hung processor. Arg4: 0000000000000009, The index of the hung processor. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1702 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 1667 Key : Analysis.Init.CPU.mSec Value: 656 Key : Analysis.Init.Elapsed.mSec Value: 9841 Key : Analysis.Memory.CommitPeak.Mb Value: 90 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: MEMORY.DMP BUGCHECK_CODE: 101 BUGCHECK_P1: c BUGCHECK_P2: 0 BUGCHECK_P3: ffffd900820e7180 BUGCHECK_P4: 9 FAULTING_PROCESSOR: 9 PROCESS_NAME: chrome.exe STACK_TEXT: ffffd90081d7fc88 fffff8056325748e : 0000000000000101 000000000000000c 0000000000000000 ffffd900820e7180 : nt!KeBugCheckEx ffffd90081d7fc90 fffff805630cb31d : 0000000000000000 ffffd90081d28180 0000000000000246 0000000000f17d9d : nt!KeAccumulateTicks+0x18f38e ffffd90081d7fcf0 fffff805630cb8c1 : 0000000000f17b00 00000000008ff08d ffffd90081d28180 0000000000000001 : nt!KiUpdateRunTime+0x5d ffffd90081d7fd40 fffff805630c5733 : ffffd90081d28180 0000000000000000 fffff80563a318e0 0000000000000000 : nt!KiUpdateTime+0x4a1 ffffd90081d7fe80 fffff805630ce0f2 : ffffc402f9aa68a0 ffffc402f9aa6920 ffffc402f9aa6900 000000000000000c : nt!KeClockInterruptNotify+0x2e3 ffffd90081d7ff30 fffff80563011235 : 0000023fc6ce1fef ffffc6074b2e7ac0 ffffc6074b2e7b70 0000000000000000 : nt!HalpTimerClockInterrupt+0xe2 ffffd90081d7ff60 fffff805631fc16a : ffffc402f9aa6920 ffffc6074b2e7ac0 0000000000000001 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffd90081d7ffb0 fffff805631fc937 : 0000000000000000 00001f80001f0cbf 000000000ae1c4aa ffffc402f9aa6a70 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffffc402f9aa68a0 fffff805630242eb : fffff80563b23080 fffff8056302425c ffff91800bfd7cb0 fffff8056315944f : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffffc402f9aa6a30 fffff8056302425c : ffff91800bfd7cb0 fffff8056315944f 0000000000000000 0000000000000010 : nt!KeYieldProcessorEx+0x1b ffffc402f9aa6a40 fffff805630cd7a5 : 000000990ae22f13 0000000000000004 ffff9480000017e8 0000000000000000 : nt!KxSetTimeStampBusy+0x28 ffffc402f9aa6a70 fffff805630cd51b : 0000000000000004 0000000000000000 0000000000000000 0000000000000002 : nt!KxFlushEntireTb+0x185 ffffc402f9aa6ac0 fffff80563134336 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KeFlushTb+0x7b ffffc402f9aa6b20 fffff80563099b91 : 0000000000000000 0000000000000000 ffff91800aa152e0 ffff91800aa152e0 : nt!MiFlushEntireTbDueToAttributeChange+0x3a ffffc402f9aa6c10 fffff80563048845 : 8a0000038b1ba96b 0000000000000001 ffff91800aa15302 0000000000000000 : nt!MiChangePageAttributeBatch+0x91 ffffc402f9aa6c80 fffff805630455c8 : ffffc402f9aa7050 0000000000000000 0000000000000001 0000000000000000 : nt!MiGetPageChain+0xd75 ffffc402f9aa6ec0 fffff80563044b18 : ffffc402f9aa7050 ffffc402f9aa72a0 ffffc60700000000 0000000000000000 : nt!MiResolvePrivateZeroFault+0x6e8 ffffc402f9aa6ff0 fffff80563043eed : 00000000c0000016 0000000000000002 0000000000000000 0000000000000002 : nt!MiResolveDemandZeroFault+0x208 ffffc402f9aa70e0 fffff80563041fd9 : 0000000000000111 0000000000000004 00000000c0000016 0000000000000000 : nt!MiDispatchFault+0x22d ffffc402f9aa7220 fffff80563209cd8 : 0000000000000009 0000000000000000 ffffc402f9aa73d8 fffffffffffc2f70 : nt!MmAccessFault+0x189 ffffc402f9aa73c0 00007fffafa77585 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x358 000000d3361fc0e0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007fffafa77585


SYMBOL_NAME: nt!KeAccumulateTicks+18f38e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 18f38e

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
---------

 

[Fix_that_Glitch]

Do you have your cpu overclocked? What is your build also please?

 

[orbitals]

Do you have your cpu overclocked? What is your build also please?

I have had my CPU overclocked before but I believe I took it off, I will put my specs below.

GPU: NVIDIA GeForce RTX 3080 - 10GB
CPU: Intel i9-11900KF
Motherboard: MSI Z590-A PRO
32 GB Ram

 

[Fix_that_Glitch]

Have you tried resetting your bios to optimal/original settings? It is pointing to a processor problem.

 

[orbitals]

Have you tried resetting your bios to optimal/original settings? It is pointing to a processor problem.

Yes, almost a week ago I reset the bios to the original settings, since doing that I've only been experiencing the blue screen once every day or two. Before I did that though I was getting the BSOD multiple times a day.

 

[Fix_that_Glitch]

With only two a month it may be hard to pinpoint it down. You can run a sfc /scannow to check your os. You can try using one stick of ram at a time to see if the probelm persists. If it does it with both sticks, one at a time you can rule out the memory.

 

[orbitals]

With only two a month it may be hard to pinpoint it down. You can run a sfc /scannow to check your os. You can try using one stick of ram at a time to see if the probelm persists. If it does it with both sticks, one at a time you can rule out the memory.

Just did the scan and got this message.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

 

[Fix_that_Glitch]

Ok so run like that and see if problem persist. If it does, then try the one stick memory method.

 

[orbitals]

Ok so run like that and see if problem persist. If it does, then try the one stick memory method.

Okay thanks for the help! Will reply if it keeps happening.

 

[orbitals]

Ok so run like that and see if problem persist. If it does, then try the one stick memory method.

Bad News; I've still been experiencing the same BSOD. I also tried what you said with taking 1 RAM stick out at a time but the problem still happens. I did notice that the blue screens seems to happen less often when only 1 RAM stick is in the motherboard.

 

[Fix_that_Glitch]

What is your bios version?

 

[orbitals]

What is your bios version?

American Megatrends International, LLC. 1.00, 1/14/2021

 

[johnbl]

two cpu cores were trying to talk to each other and did not get a response in the very short timeout period. you would have to put the actual memory.dmp file on a server, share it for public access and post a link so someone can look at in the debugger and see why it failed.

there can be several common causes of this bugcheck. I think the most common is the case where sofware tries to use a driver on one core while trying failing a driver install on another core.

most of the time you should be able to go into windows control panel device manager and see a failed device install. yellow symbol by the device.
debugger
!pnptriage
command should list the device.

best to provide the memory.dmp file