Question Windows 11 BSOD - - - - is it CPU related ?

[rikerik]

Hello community, I need help troublehooting a system that I built for the neighbours kid a year back.

F-o-r-t-n-i-t-e results in BSOD after 15-60 mins of gameplay, havent noticed any cooling issues, systems boots right back up without issues. S-t-a-r-s-t-a-b-l-e online generally works without BSOD. BSOD has occurred once during M-i-n-e-c-r-a-f-t gameplay. I guess F-o-r-t-n-i-t-e puts the most amount of stress on the system.

However, there was an incident during build:

- after installing the CPU cooler I was about to install the RAMs, I had to rotate the cooler 180 degress since the cooler was in the way of the RAM slots.

- The CPU then got ripped right out its socket along with the cooler. I then managed to separate the cooler from the CPU, gently.

- I found no visible physical damage to either the socket nor the CPU or its pins after this incident. But maybe something broke? I did not re-apply any cooling paste. its still the original paste on the CPU

Memcheck86 found no errors
chkdsk reports no errors, is there a better test that chkdsk that I should run?
Mobo is flashed with latest firmware

I guess, otherwise, a next step would be clean install of the OS? or potentially even changing the somewhat old 256gb SSD stat drive to a 1TB m2?

What about the PSU? worth trying another one?

SPEC:
ASUS PRIME A520M-K Moderkort
AMD Ryzen 5 5600 Wraith Stealth CPU
Corsair Vengeance LPX DDR4-3200 C16 BK DC - 16GB
Inter-Tech Argus RGB-650W CM II
NVIDIA Geforce ASUS ROG strix 1080 (Bought used)

Thanks for any help!

Here is the minidump analysis by windbg:

Microsoft (R) Windows Debugger Version 10.0.22621.3233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\050824-4296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`71c00000 PsLoadedModuleList = 0xfffff801`72813110
Debug session time: Wed May 8 15:07:43.876 2024 (UTC + 2:00)
System Uptime: 1 days 23:43:49.476
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
..................
For analysis of this file, run !analyze -v
8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe0875e060028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000001010135, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_MEMORY_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_MEMORY_ERROR_SECTION ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6499

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 16218

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

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

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


FILE_IN_CAB: 050824-4296-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe0875e060028

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: F-o-r-t-n-i-t-eClient

STACK_TEXT:
ffffb900`84b6e938 fffff801`720ffa6b : 00000000`00000124 00000000`00000000 ffffe087`5e060028 00000000`bc000800 : nt!KeBugCheckEx
ffffb900`84b6e940 fffff801`710e10c0 : 00000000`00000000 ffffb900`84b6ea19 ffffe087`5e060028 ffffe087`5bcf9b30 : nt!HalBugCheckSystem+0xeb
ffffb900`84b6e980 fffff801`7220ef8f : 00000000`00000000 ffffb900`84b6ea19 ffffe087`5e060028 00200067`006e0069 : PSHED!PshedBugCheckSystem+0x10
ffffb900`84b6e9b0 fffff801`7210149a : ffffe087`5e6cc410 ffffe087`5e6cc410 ffffe087`5bcf9b80 fffff801`71f7effe : nt!WheaReportHwError+0x38f
ffffb900`84b6ea80 fffff801`721018f0 : 00000000`00000008 ffffe087`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffffb900`84b6ebf0 fffff801`72101784 : ffffe087`5bb72600 00200072`00000000 ffffb900`84b6ee00 006f0079`00000000 : nt!HalpMceHandlerCore+0x138
ffffb900`84b6ec50 fffff801`72100c17 : ffffe087`5bb72600 ffffb900`84b6eef0 00000000`00000000 0067006f`00720070 : nt!HalpMceHandler+0xe0
ffffb900`84b6ec90 fffff801`7210339b : ffffe087`5bb72600 00200075`006f0079 0074006e`00610077 0020006f`00740020 : nt!HalpHandleMachineCheck+0x97
ffffb900`84b6ecc0 fffff801`72169999 : 66005114`0000003f 74002000`6e006100 6e006900`6e007500 6f006300`20006700 : nt!HalHandleMcheck+0x3b
ffffb900`84b6ecf0 fffff801`7202a8be : 00680054`14000000 0069006d`00200065 0075006d`0069006e 00750064`0020006d : nt!KiHandleMcheck+0x9
ffffb900`84b6ed20 fffff801`7202a4d3 : 00000000`00000000 00000000`00000000 00000191`8fb63510 ffffb900`84b6eef0 : nt!KxMcheckAbort+0x7e
ffffb900`84b6ee60 00007ff6`1ae89646 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
00000027`edeff7e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`1ae89646


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b0905187-9dbc-d607-4dc5-8630b9eddb7f}

Followup: MachineOwner
---------

 

[Lutfij]

Welcome to the forums, newcomer!

Inter-Tech Argus RGB-650W CM II
I would first replace this unit with something that's reliably built with at least 550W of power for the entire system.

I need help troublehooting a system that I built for the neighbours kid a year back.
Where did you source the installer for the OS? Did you let the OS install drivers for your GPU on it's own?

Mobo is flashed with latest firmware
What BIOS version are you on for your motherboard?

 

[rikerik]

Hi Lutfij, thank you.

Mobo driver was downloded from ASUS website (The previous version that I flashed from was over 2 years old):
BIOS Version/Date " American Megatrends Inc. 3607, 3/22/2024"

The OS installer file was downloaded from microsoft.com, the license is OEM.

The GPU drivers was initially downloded from Nvidia but has therafter been managed by 'Nvidia experience', currently at 'gameready v536.67' and there was an update!

I have built a similar system for myself that play CS2 and Starfield on:
PSU: Corsair cv-series-cv650
nvidia gtx 1080 (again, bought used)
ryzen 5600

Has been working great!
Maybe I should just switch the PSUs and see if the issue suddenly switches computer

 

[rikerik]

Problem seems to have been solved by disabling "Precision
Boost Overdrive" in the Asus Bios.

CPU temperature have dropped from idling around 85-91 C under f-o-r-t-n-i-t-e load to 70-80 C.

Worth mentioning is that before disabling PBO I stresstested :
- GPU load through "Matthew-x83"
- CPU load through Prime95
simultaneously

and this didnt trigger any BSODs etc, system was/is fine under heavy constant load for longer periods.