Question BSOD/crashes while idle and when booting.

perez jens

Distinguished
Nov 8, 2013
258
0
18,790
Hey,

My friend has some serious problems with her PC that I build.
She is experiencing crashes and BSOD's while idle and when booting up sometimes.
all drivers are up to date, fresh windows 10 install.. only BIOS isnt up to date.
I tried and researched some things myself but its still occuring.
I put the CPU Voltage in offset mode + 0.1 cause reddit said the 5900x has some issues shutting down while idling.

these are some DMP files and event logs:
View: https://imgur.com/a/43CS2WG

https://drive.google.com/file/d/1katt5QxkQDvi45nsYtROHxNr0FCC-fcv/view?usp=drive_link

and these are the specs:
A520M-A-PRO
Ryzen 9 5900x
7700 XT
G.Skill f4-2400c 15-8GNT

really hope someone can help me out.. im out of ideas..
i am off for tonight but if u need more info i will get that.
 

Lutfij

Titan
Moderator
A520M-A-PRO
Ryzen 9 5900x

Your friend has the wrong board for that processor.

You also forgot to mention the make an model of the PSU and it's age. To add;
G.Skill f4-2400c 15-8GNT
I have a feeling that you upgraded the processor recently and this system, your friend has, was built without much thought or with too much constraint on making it as cheap as possible since Ryzen platforms benefit from having DDR4-3600MHz rams.
 
Last edited:

perez jens

Distinguished
Nov 8, 2013
258
0
18,790
A520M-A-PRO
Ryzen 9 5900x

Your friend has the wrong board for that processor.

You also forgot to mention the make an model of the PSU and it's age. To add;
G.Skill f4-2400c 15-8GNT
I have a feeling that you upgraded the processor recently and this system, your friend has, was built without much thought or with too much constraint on making it as cheap as possible since Ryzen platforms benefit from having DDR-3600MHz rams.
how? the board is AM4?..
yes she wanted it as cheaply as possible, but upgrading that later.. i suggested an AM5 build but she didnt want that... also the PSU is 750W Cooler master something i think. it has some age but never had problems with that before.
 

Lutfij

Titan
Moderator
I forgot to add, I won't provide my email credentials to gain access to the .dmp files, sorry.

As for your question, the board lacks heatsinks on it's VRM as well as having a lackluster VRM design on it which would be necessary for a high end Ryzen 9 processor's power draw.
 

perez jens

Distinguished
Nov 8, 2013
258
0
18,790
I forgot to add, I won't provide my email credentials to gain access to the .dmp files, sorry.

As for your question, the board lacks heatsinks on it's VRM as well as having a lackluster VRM design on it which would be necessary for a high end Ryzen 9 processor's power draw.
oh ok, i totally understand that. is there another way i can get those .dmp files uploaded?
and u think that could be the issue? or are there others?
 

perez jens

Distinguished
Nov 8, 2013
258
0
18,790
I forgot to add, I won't provide my email credentials to gain access to the .dmp files, sorry.

As for your question, the board lacks heatsinks on it's VRM as well as having a lackluster VRM design on it which would be necessary for a high end Ryzen 9 processor's power draw.
this is one
************* 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.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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


Loading Dump File [C:\Windows\Minidump\110524-14453-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 (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff805`81a00000 PsLoadedModuleList = 0xfffff805`8262a7c0
Debug session time: Tue Nov 5 15:12:39.639 2024 (UTC + 1:00)
System Uptime: 0 days 20:54:12.233
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols

Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`81dfe310 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff307`f93c7190=0000000000000139
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff307f93c74b0, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffff307f93c7408, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for Ntfs.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1500

Key : Analysis.Elapsed.mSec
Value: 9282

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

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

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

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

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

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

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.LegacyAPI
Value: 0x139

Key : Bugcheck.Code.TargetModel
Value: 0x139

Key : FailFast.Name
Value: CORRUPT_LIST_ENTRY

Key : FailFast.Type
Value: 3

Key : Failure.Bucket
Value: 0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatch

Key : Failure.Hash
Value: {3aede96a-54dd-40d6-d4cb-2a161a843851}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 139

BUGCHECK_P1: 3

BUGCHECK_P2: fffff307f93c74b0

BUGCHECK_P3: fffff307f93c7408

BUGCHECK_P4: 0

FILE_IN_CAB: 110524-14453-01.dmp

FAULTING_THREAD: ffffcb8857ebf040

TRAP_FRAME: fffff307f93c74b0 -- (.trap 0xfffff307f93c74b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb78a38383bb8 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffb78a388e1c68 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805872f5775 rsp=fffff307f93c7640 rbp=fffff8058730a2c0
r8=fffff307f93c7650 r9=7fffcb88595b5d08 r10=fffff80581c59ac0
r11=fffff307f93c75d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
Ntfs+0xf5775:
fffff805`872f5775 cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: fffff307f93c7408 -- (.exr 0xfffff307f93c7408)
ExceptionAddress: fffff805872f5775 (Ntfs+0x00000000000f5775)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000003

EXCEPTION_STR: 0xc0000409

STACK_TEXT:
fffff307`f93c7188 fffff805`81e12ba9 : 00000000`00000139 00000000`00000003 fffff307`f93c74b0 fffff307`f93c7408 : nt!KeBugCheckEx
fffff307`f93c7190 fffff805`81e13150 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000640 : nt!KiBugCheckDispatch+0x69
fffff307`f93c72d0 fffff805`81e10ff2 : fffff805`8730a2c0 fffff805`8720bb2f ffffb78a`3a1d9330 fffff307`f93c78b0 : nt!KiFastFailDispatch+0xd0
fffff307`f93c74b0 fffff805`872f5775 : fffff805`8730a2c0 ffffb78a`00000000 00000000`00000000 ffffb78a`3a1a35a0 : nt!KiRaiseSecurityCheckFailure+0x332
fffff307`f93c7640 fffff805`8730a2c0 : ffffb78a`00000000 00000000`00000000 ffffb78a`3a1a35a0 00000000`00000000 : Ntfs+0xf5775
fffff307`f93c7648 ffffb78a`00000000 : 00000000`00000000 ffffb78a`3a1a35a0 00000000`00000000 fffff307`f93c7600 : Ntfs+0x10a2c0
fffff307`f93c7650 00000000`00000000 : ffffb78a`3a1a35a0 00000000`00000000 fffff307`f93c7600 00000000`00000001 : 0xffffb78a`00000000


SYMBOL_NAME: nt!KiFastFailDispatch+d0

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.5007

STACK_COMMAND: .process /r /p 0xffffcb883bb02080; .thread 0xffffcb8857ebf040 ; kb

BUCKET_ID_FUNC_OFFSET: d0

FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatch

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3aede96a-54dd-40d6-d4cb-2a161a843851}

Followup: MachineOwner
 

perez jens

Distinguished
Nov 8, 2013
258
0
18,790
I forgot to add, I won't provide my email credentials to gain access to the .dmp files, sorry.

As for your question, the board lacks heatsinks on it's VRM as well as having a lackluster VRM design on it which would be necessary for a high end Ryzen 9 processor's power draw.
************* 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 (R) Windows Debugger Version 10.0.27725.1000 AMD64
Copyright (c) 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