Error encountered during startup and while the system is idle.
Error encountered during startup and while the system is idle.
Hey, my friend is facing some major issues with her PC that I've tried to fix. She's having crashes and BSODs both when the system is idle and during startup. All drivers are up to date, and a fresh Windows 10 install was completed. However, the BIOS version isn't updated. I've attempted various solutions myself, but the problems persist. I adjusted the CPU voltage to offset mode with +0.1, following advice from Reddit about the 5900x shutting down during idle. Here are some DMP files and event logs you can check:
https://imgur.com/a/43CS2WG
View: https://imgur.com/a/43CS2WG
https://drive.google.com/file/d/1jdxKl2X...drive_link
https://drive.google.com/file/d/1katt5Qx...drive_link
She has the following specifications:
A520M-A-PRO
Ryzen 9 5900x
7700 XT
G.Skill f4-2400c 15-8GNT
I really need someone to help me out, I'm running low on ideas.
I'll be away tonight but will send more details if needed.
A520M-A-PRO is compatible with the 5900x processor.
Your friend may have used an incorrect power supply model and its age is unknown.
Additionally, please note the PSU make and model, as well as its condition.
To add: G.Skill f4-2400c 15-8GNT is recommended.
It seems you recently upgraded the processor, and this system was likely assembled without much consideration for cost efficiency, especially since Ryzen systems perform best with DDR4-3600MHz RAM.
how? the board is AM4?..
she wanted it as cheaply as possible, but upgrading later. I recommended an AM5 build but she didn't want that... also the PSU is a 750W Cooler Master thing, though it's a bit old but never had issues before.
I omitted including your email details to avoid accessing the .dmp files, thank you. Regarding your inquiry, the board does not have heatsinks on its VRM and features a subpar VRM design that would be insufficient for a high-end Ryzen 9 processor's power requirements.
This document outlines the setup for Debugger Extensions Gallery repositories. It specifies configuration options, repository details, and environment settings. The process involves preparing the necessary tools, enabling features, and validating system information. A debug session is initiated, followed by monitoring for completion and analyzing the resulting logs.
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.203 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42
Microsoft ® Windows Debugger Version 10.0.27725.1000 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Maja Kaminska\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 (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff807`34a00000 PsLoadedModuleList = 0xfffff807`3562a7c0
Debug session time: Wed Nov 6 12:27:46.048 2024 (UTC + 1:00)
System Uptime: 0 days 19:11:41.640
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`34dfe310 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffbb83`8482fa30=000000000000005c
17: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
HAL_INITIALIZATION_FAILED (5c)
Arguments:
Arg1: 0000000000000110
Arg2: fffff7e9c0003000
Arg3: 000000000000002a
Arg4: 00000000000005e3
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1078
Key : Analysis.Elapsed.mSec
Value: 1076
Key : Analysis.IO.Other.Mb
Value: 13
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 20
Key : Analysis.Init.CPU.mSec
Value: 531
Key : Analysis.Init.Elapsed.mSec
Value: 32758
Key : Analysis.Memory.CommitPeak.Mb
Value: 88
Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.KiBugCheckData
Value: 0x5c
Key : Bugcheck.Code.LegacyAPI
Value: 0x5c
Key : Bugcheck.Code.TargetModel
Value: 0x5c
Key : Failure.Bucket
Value: 0x5C_HAL_TIMER_INITIALIZATION_FAILURE_nt!HalpPowerStateCallback
Key : Failure.Hash
Value: {d2ad2d0d-ba46-7153-578f-8440fbc73077}
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: 5c
BUGCHECK_P1: 110
BUGCHECK_P2: fffff7e9c0003000
BUGCHECK_P3: 2a
BUGCHECK_P4: 5e3
FILE_IN_CAB: MEMORY.DMP
FAULTING_THREAD: ffffde08aa467040
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffffbb83`8482fa28 fffff807`34e9c50f : 00000000`0000005c 00000000`00000110 fffff7e9`c0003000 00000000`0000002a : nt!KeBugCheckEx
ffffbb83`8482fa30 fffff807`34d1283f : ffffde08`814b2790 ffffde08`814820e0 00000000`00580012 ffffde08`a020b040 : nt!HalpPowerStateCallback+0xf562f
ffffbb83`8482fa70 fffff807`34d1276c : ffffde08`aa467040 fffff807`35397fe0 ffffde08`814c2a60 fffff807`35621080 : nt!ExNotifyWithProcessing+0xc7
ffffbb83`8482fad0 fffff807`35398017 : fffff807`35725401 ffffde08`814a1180 ffffde08`aa467040 00000000`00000000 : nt!ExNotifyCallback+0xc
ffffbb83`8482fb00 fffff807`34c22525 : ffffde08`aa467040 fffff807`3507f860 ffffde08`814c2a60 00000000`00000000 : nt!PopUnlockAfterSleepWorker+0x37
ffffbb83`8482fb30 fffff807`34d29905 : ffffde08`aa467040 00000000`00000080 ffffde08`814a1180 f3ec9519`a1ea9500 : nt!ExpWorkerThread+0x105
ffffbb83`8482fbd0 fffff807`34e07318 : ffffa980`60e00180 ffffde08`aa467040 fffff807`34d298b0 45269619`791f9619 : nt!PspSystemThreadStartup+0x55
ffffbb83`8482fc20 00000000`00000000 : ffffbb83`84830000 ffffbb83`84829000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!HalpPowerStateCallback+f562f
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .process /r /p 0xffffde08814a1180; .thread 0xffffde08aa467040 ; kb
BUCKET_ID_FUNC_OFFSET: f562f
FAILURE_BUCKET_ID: 0x5C_HAL_TIMER_INITIALIZATION_FAILURE_nt!HalpPowerStateCallback
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d2ad2d0d-ba46-7153-578f-8440fbc73077}
Followup: MachineOwner
Hey,
a few days back I posted a thread about a crashing PC.
Someone commented that the board's VRM wasn't sufficient, which I agree with, but I think there could be other factors involved too.
I also shared some .DMP files, though I haven’t received any response yet—those seem really important.
Google Drive wasn’t an option, so what other methods could we use to send them?
I’m hoping someone will take a moment to review those .DMP files if there’s a safe or trusted way to post them.
Thanks
Share your documents on platforms such as Dropbox or File.io, then send the connection for review.
Keep it simple—stay in one thread unless needed.