Question about BSoD and unusual actions during shutdown.
Question about BSoD and unusual actions during shutdown.
My device has begun experiencing BSoD errors recently and I've been attempting to diagnose the issue. The problem seems to have worsened over the past week. Normally, the system doesn't shut down, but today the power company had to shut it down for seven hours. During that time, unusual behavior was observed from the machine. Four LEDs on the motherboard appeared, and some fan LEDs would briefly flash.
I found a video here:
https://drive.google.com/file/d/1dvhcKvS...sp=sharing
At 0:25 and 1:16, the flashing occurs approximately every fifty seconds.
I tried turning off the power supply, removing components one by one, and then restarting it. I waited to see if the issue reappeared. This process continued until only the CPU and a 24-pin connector remained. Even after removing the 2x8 pin for the CPU, the blinking persisted.
System details:
Z790 AORUS ELITE AX DDR4
Intel Core i9 13900K
Corsair Vengence LPX 2x16 2666
NVIDIA GeForce RTX 3090
KINGSTON SKC3000S1024G (NVMe)
Apacer AS2280Q4 2TB (NVMe)
ST2000DM008-2FR102 2TB (SATA)
Corsair RM850x ATX 3.1
All components are new as of November 2023, and the power supply was brand new this year. Could anyone provide any insights? I have a spare 750W PS that I plan to test, but it won't be available for several days. Is the motherboard faulty? Or is it the power supply unit? Have you encountered similar issues before?
Thank you very much if anyone can help.
Welcome to the forums, newcomer!
What BIOS version are you using for your motherboard?
NVIDIA GeForce RTX 3090
+
Corsair RM850x ATX 3.1
The RTX 3000 series was known for its high transient load spikes;
View: https://www.youtube.com/watch?v=wnRyyCsuHFQ
It’s why advice was given to overprovision wattages when choosing a PSU, aside from ensuring a solid unit. For the RTX 3090, users were recommended to opt for a reliable 1.5KW PSU. No joke. You should consider borrowing or checking availability of a suitable PSU and see if the problem continues.
Do you have any grounding concerns? Have you tried moving to a different wall outlet?
BIOS v F12c (likely the initial step to consider). I see F14 is also available.
I’m familiar with the 3090 and the spikes, but none of these problems occurred a week ago or so.
I didn’t notice the flickering of the LEDs when the system was off before. It’s new.
I never experienced a 'just system shutdown'. I receive a BSoD and a dump that began with svchost and changed locations.
Could you suggest that the PS has been affected by the spikes from the 3090?
I’ve also moved outlets, but there’s no improvement.
After flashing the BIOS, also clear the CMOS.
I’m familiar with the 3090 and its spikes, but these problems haven’t occurred in about a week.
How long has your PSU been in this build?
Could you mean that the PSU was affected by the 3090 issues?
That’s possible, but you’d need a similar build with more power to confirm.
If you have a .dmp file, please share it. You’ll need to upload it to a service like DropBox and then send the link here.
PSU was purchased in March of this year.
I have analyzed each dump I get.
I will give you the latest one here:
Code:
8: 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: 0000000000000006, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffc3000d2e5180, The PRCB address of the hung processor.
Arg4: 000000000000001c, The index of the hung processor.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1546
Key : Analysis.Elapsed.mSec
Value: 1583
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: 249
Key : Analysis.Init.Elapsed.mSec
Value: 2070
Key : Analysis.Memory.CommitPeak.Mb
Value: 99
Key : Bugcheck.Code.KiBugCheckData
Value: 0x101
Key : Bugcheck.Code.LegacyAPI
Value: 0x101
Key : Failure.Bucket
Value: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks
Key : Failure.Hash
Value: {95498f51-33a9-903b-59e5-d236937d8ecf}
Key : Hypervisor.Enlightenments.Value
Value: 0
Key : Hypervisor.Enlightenments.ValueHex
Value: 0
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 0
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0
Key : Hypervisor.Flags.Phase0InitDone
Value: 0
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 0
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 16908288
Key : Hypervisor.Flags.ValueHex
Value: 1020000
Key : Hypervisor.Flags.VpAssistPage
Value: 0
Key : Hypervisor.Flags.VsmAvailable
Value: 0
Key : Hypervisor.RootFlags.AccessStats
Value: 0
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 0
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0
Key : Hypervisor.RootFlags.MceEnlightened
Value: 0
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0
Key : Hypervisor.RootFlags.Value
Value: 0
Key : Hypervisor.RootFlags.ValueHex
Value: 0
Key : SecureKernel.HalpHvciEnabled
Value: 0
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 101
BUGCHECK_P1: 6
BUGCHECK_P2: 0
BUGCHECK_P3: ffffc3000d2e5180
BUGCHECK_P4: 1c
FILE_IN_CAB: 9-30MEMORY.DMP
FAULTING_PROCESSOR: 1c
PROCESS_NAME: Voicemod.exe
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
STACK_TEXT:
ffffc300`0c493c88 fffff801`53c26aee : 00000000`00000101 00000000`00000006 00000000`00000000 ffffc300`0d2e5180 : nt!KeBugCheckEx
ffffc300`0c493c90 fffff801`53a275ed : 00000000`00000000 ffffc300`0c440180 00000000`00000246 00000000`0008349a : nt!KeAccumulateTicks+0x20271e
ffffc300`0c493cf0 fffff801`53a27b91 : 00000000`00083200 00000000`0004e40e ffffc300`0c440180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffc300`0c493d40 fffff801`53a218e3 : ffffc300`0c440180 00000000`00000000 fffff801`544319a0 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffc300`0c493e80 fffff801`53a29fe2 : ffffd384`e88f7090 ffffd384`e88f7110 ffffd384`e88f7100 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
ffffc300`0c493f30 fffff801`53b43a65 : 00000013`90506d7b ffff830e`b5b28c40 ffff830e`b5b28cf0 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffc300`0c493f60 fffff801`53bff5aa : ffffd384`e88f7110 ffff830e`b5b28c40 00000000`00000000 ffff830e`d80f4080 : nt!KiCallInterruptServiceRoutine+0xa5
ffffc300`0c493fb0 fffff801`53bffdd7 : 00000000`0f09d79a fffff801`53ac4ab6 ffffc300`00000000 ffff830e`d04ae080 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd384`e88f7090 fffff801`53abbdf0 : 00000000`00000000 00000000`0000000c 00000000`00000002 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd384`e88f7220 fffff801`53abbc35 : ffff9701`00000001 ffffd384`e88f7398 ffff830e`da0b6700 ffffd384`e88f73f0 : nt!KeFlushMultipleRangeTb+0x140
ffffd384`e88f72c0 fffff801`53abb713 : ffff830e`da0b6700 1a000001`4b428867 00000000`00000000 00000274`9e300000 : nt!MiFlushTbList+0x85
ffffd384`e88f72f0 fffff801`53abb1e3 : ffffd384`e88f7858 ffffd384`e88f7620 ffffd384`e88f7570 ffff9701`3a4f1800 : nt!MiTerminateWsleCluster+0x363
ffffd384`e88f74a0 fffff801`53ab7e9b : ffff830e`da0b6700 00000000`00000000 ffff9701`3a4f1800 00000000`00000000 : nt!MiDeleteVaTail+0x23
ffffd384`e88f74d0 fffff801`53a1c328 : 00000000`00000001 ffff830e`00000000 ffff830e`da0b6550 ffff830e`d04ae080 : nt!MiDeletePagablePteRange+0x4ab
ffffd384`e88f77e0 fffff801`53e1e889 : 00000000`00000000 00000000`00000000 00000274`00000000 ffff830e`da0b6080 : nt!MiDeleteVad+0x378
ffffd384`e88f78e0 fffff801`53e1e662 : ffff830e`d9821720 00000000`00000000 ffff830e`da0b6080 00000000`00000000 : nt!MiUnmapVad+0x49
ffffd384`e88f7910 fffff801`53e1e4d9 : ffffc024`e0eabb17 00000074`f5bcf3c0 00000274`9d465060 00000000`00000000 : nt!MiUnmapViewOfSection+0x152
ffffd384`e88f79f0 fffff801`53c11505 : ffff830e`d04ae080 00000274`9e300000 00000000`00000000 ffff830e`da0b6080 : nt!NtUnmapViewOfSectionEx+0x99
ffffd384`e88f7a40 00007ff9`bbfb0ea4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000074`f5bcf408 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`bbfb0ea4
SYMBOL_NAME: nt!KeAccumulateTicks+20271e
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 20271e
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
---------
BTW, this is nothing new to me other than the issues I am having I have never seen before in 25 years of building systems. I have spent the last week trying to figure out what is wrong. I do not have the ability right now to swap every piece of HW to test. I have to wait a few days just to get another PS just to test it.
I have updated everything in GCC and the BIOS to F14.
So now I wait to see what happens next.
After completing the tests on the RMA, there were no indications that the PSU was faulty. I recently bought an HX1500i (2025) C20 and should arrive by Monday. I'm curious to see if any more unusual BSODs occur afterward.