Question Recent issues with bsod and random crashing (minidump analyze posted)

[sprite5415123]

Hello, the past month I've been having issues on and off with my system either crashing with a bsod or just everything going black and restarting under load, I've never seen this happen when just browsing the net, it's always when gaming. The crashes goes away once i disable CPB which makes me think one of the cores might be screwed and i just need to rma the CPU, would like a confirmation if possible

Spoiler: minidump 1

************* 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.032 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-6406-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff803`3ca00000 PsLoadedModuleList = 0xfffff803`3d62a7c0
Debug session time: Tue Nov 5 17:34:18.047 2024 (UTC + 2:00)
System Uptime: 0 days 1:06:01.669
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000071`56ed5018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`3cdfe310 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffe700`f7cee950=0000000000000124
12: 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: ffff85014882b028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000fc800800, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000060c0859, 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_PROCESSOR_GENERIC_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_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2359

Key : Analysis.Elapsed.mSec
Value: 7844

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

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

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

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

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

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

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: 0x124

Key : Bugcheck.Code.TargetModel
Value: 0x124

Key : Failure.Bucket
Value: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

Key : Failure.Hash
Value: {035dcc87-485b-74b3-1c1b-ee50cb0c2865}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff85014882b028

BUGCHECK_P3: fc800800

BUGCHECK_P4: 60c0859

FILE_IN_CAB: 110524-6406-01.dmp

FAULTING_THREAD: ffff8501581b2080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: TL.exe

STACK_TEXT:
ffffe700`f7cee948 fffff803`3ceba21a : 00000000`00000124 00000000`00000000 ffff8501`4882b028 00000000`fc800800 : nt!KeBugCheckEx
ffffe700`f7cee950 fffff803`38d115b0 : 00000000`00000000 ffff8501`4882b028 ffff8501`473f3cb0 ffff8501`4882b028 : nt!HalBugCheckSystem+0xca
ffffe700`f7cee990 fffff803`3cfbc82d : 00000000`00000000 ffffe700`f7ceea29 ffff8501`4882b028 ffff8501`473f3cb0 : PSHED!PshedBugCheckSystem+0x10
ffffe700`f7cee9c0 fffff803`3cebbb41 : ffff8501`4d47a900 ffff8501`4d47a900 ffff8501`473f3d00 ffff8501`473f3cb0 : nt!WheaReportHwError+0x3dd
ffffe700`f7ceea90 fffff803`3cebbeb3 : 00000000`0000000c ffff8501`473f3d00 ffff8501`473f3cb0 00000000`0000000c : nt!HalpMcaReportError+0xb1
ffffe700`f7ceec00 fffff803`3cebbd90 : ffff8501`45cfe8a0 00000000`00000000 ffffe700`f7ceee00 00000000`00000000 : nt!HalpMceHandlerCore+0xef
ffffe700`f7ceec50 fffff803`3cebb2d5 : ffff8501`45cfe8a0 ffffe700`f7ceeef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffe700`f7ceec90 fffff803`3cebda95 : ffff8501`45cfe8a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9
ffffe700`f7ceecc0 fffff803`3cf13919 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
ffffe700`f7ceecf0 fffff803`3ce0f57a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffe700`f7ceed20 fffff803`3ce0f237 : 00000000`00000000 00000000`00000000 00000071`41b5f890 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffe700`f7ceee60 00007ffb`5bf490aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
00000071`41b5f818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`5bf490aa


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .process /r /p 0xffff85015d047340; .thread 0xffff8501581b2080 ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

Spoiler: minidump 2

************* 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.032 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-10125-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff800`56c00000 PsLoadedModuleList = 0xfffff800`5782a7c0
Debug session time: Tue Nov 5 22:59:28.601 2024 (UTC + 2:00)
System Uptime: 0 days 0:21:58.186
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000024`a8961018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`56ffe310 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff8380`87e9b950=0000000000000124
6: 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: ffffe0850d82b028, 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_PROCESSOR_GENERIC_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_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2140

Key : Analysis.Elapsed.mSec
Value: 3093

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

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

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

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

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

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

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: 0x124

Key : Bugcheck.Code.TargetModel
Value: 0x124

Key : Failure.Bucket
Value: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

Key : Failure.Hash
Value: {035dcc87-485b-74b3-1c1b-ee50cb0c2865}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe0850d82b028

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

FILE_IN_CAB: 110524-10125-01.dmp

FAULTING_THREAD: ffffe0851ea4d080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: cs2.exe

STACK_TEXT:
ffff8380`87e9b948 fffff800`570ba21a : 00000000`00000124 00000000`00000000 ffffe085`0d82b028 00000000`bc000800 : nt!KeBugCheckEx
ffff8380`87e9b950 fffff800`53c815b0 : 00000000`00000000 ffffe085`0d82b028 ffffe085`0afebd60 ffffe085`0d82b028 : nt!HalBugCheckSystem+0xca
ffff8380`87e9b990 fffff800`571bc82d : 00000000`00000000 ffff8380`87e9ba29 ffffe085`0d82b028 ffffe085`0afebd60 : PSHED!PshedBugCheckSystem+0x10
ffff8380`87e9b9c0 fffff800`570bbb41 : ffffe085`0ae68ac0 ffffe085`0ae68ac0 ffffe085`0afebdb0 ffffe085`0afebd60 : nt!WheaReportHwError+0x3dd
ffff8380`87e9ba90 fffff800`570bbeb3 : 00000000`00000006 ffffe085`0afebdb0 ffffe085`0afebd60 00000000`00000006 : nt!HalpMcaReportError+0xb1
ffff8380`87e9bc00 fffff800`570bbd90 : ffffe085`0acfe450 8b48d68b`00000000 ffff8380`87e9be00 880fc085`44244489 : nt!HalpMceHandlerCore+0xef
ffff8380`87e9bc50 fffff800`570bb2d5 : ffffe085`0acfe450 ffff8380`87e9bef0 00000000`00000000 7402a850`478b003b : nt!HalpMceHandler+0xe0
ffff8380`87e9bc90 fffff800`570bda95 : ffffe085`0acfe450 ffc4ba50`e8cf8b48 ffc4b588`e8cf8b48 f60b8b68`24448948 : nt!HalpHandleMachineCheck+0xe9
ffff8380`87e9bcc0 fffff800`57113919 : 8b480d75`c0854850 8ce9ffc5`b482e8cf 8d41c033`45000001 242ee8c8`8b480150 : nt!HalHandleMcheck+0x35
ffff8380`87e9bcf0 fffff800`5700f57a : 0fc03345`000000b8 4de8c88b`484c50b6 8948d88b`48ffc4b6 2475c085`48782444 : nt!KiHandleMcheck+0x9
ffff8380`87e9bd20 fffff800`5700f237 : 00000000`00000000 00000000`00000000 0000016a`2ac4e130 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff8380`87e9be60 00007ff8`5e76a418 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
00000024`a9f7b280 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`5e76a418


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .process /r /p 0xffffe0851e14e340; .thread 0xffffe0851ea4d080 ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {035dcc87-485b-74b3-1c1b-ee50cb0c2865}

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

PC Specs
Ryen 5800x
RTX 3070
GSkill DDR4 3000mhz
Corsair rm850
b450 gaming x

 

[ubuysa]

These two dumps are hardware error caused (most likely) and if disabling Core Performance Boost stops the BSODs then the CPU is most likely to be the problem. Try disabling CPB and then run the Prime95 tests as instructed below...

1. Download Prime95 and a CPU temperature monitor (CoreTemp will do).
2. Keep the temperature monitor running all the time you run Prime95. Your CPU will get hot!
3. Run each of the three Prime95 tests (smallFFTs, largeFFTs, and Blend) one after the other for a minimum of 1 hour per test, 2 hours per test would be better.
4. If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp approaches 90°C (Tmax for your CPU), then stop Prime95 and let us know what happened.

Note that a properly cooled and stable CPU should be able to run all Prime95 tests pretty much indefinitely.

FYI: The small FFT test stresses the CPU more than RAM. The large FFT test stresses RAM more than the CPU. The Blend test is a mixture of the two. I expect your CPU to fail on the smallFFTs test.

 

[sprite5415123]

These two dumps are hardware error caused (most likely) and if disabling Core Performance Boost stops the BSODs then the CPU is most likely to be the problem. Try disabling CPB and then run the Prime95 tests as instructed below...

1. Download Prime95 and a CPU temperature monitor (CoreTemp will do).
2. Keep the temperature monitor running all the time you run Prime95. Your CPU will get hot!
3. Run each of the three Prime95 tests (smallFFTs, largeFFTs, and Blend) one after the other for a minimum of 1 hour per test, 2 hours per test would be better.
4. If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp approaches 90°C (Tmax for your CPU), then stop Prime95 and let us know what happened.

Note that a properly cooled and stable CPU should be able to run all Prime95 tests pretty much indefinitely.

FYI: The small FFT test stresses the CPU more than RAM. The large FFT test stresses RAM more than the CPU. The Blend test is a mixture of the two. I expect your CPU to fail on the smallFFTs test.

I'll run the tests in a few hours once I get home but you said "Try disabling CPB and then run the Prime95 tests as instructed below...", perhaps you meant for me to enable the CPB and then run the tests as I have CPB disabled already.

I've also reinstalled the windows completely to try and rule out some driver/software issues.

 

[ubuysa]

No. DISABLE CPB and run the test. We already know that CBP causes BSODs, you want to see whether the CPU is stable at its default frequency.

 

[sprite5415123]

No. DISABLE CPB and run the test. We already know that CBP causes BSODs, you want to see whether the CPU is stable at its default frequency.

I ran the test for an hour each, one after the other straight, no crashes or errors.

https://imgur.com/a/CxGkxZh

View: https://imgur.com/a/CxGkxZh
- screen shot from the tests even though there's nothing to see really, included with the max temps I got from those tests.

Also forgot to mention system doesn't even boot if i turn on xmp, not sure if its related

 

[ubuysa]

That's gopod news, and I'm surprised the CPU didn't fail. However, that it BSODs with CBP enabled does suggest that the CPU is unstable when overclocked.

XMP is a RAM overclock. Your RAM is certified up to 3000MHz but it's native (SPD) clock speed is 2133MHz. The CPU is certified to handle RAM speeds up to 3200MHz, so if applying a 3000MHz XMP profile causes it to not boot then the problem is either that the RAM is flaky over 2133MHz or that the CPU is unhappy with RAM clocked over 2133MHz.

I think more information will help, can you please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

That upload will include the dump files and I'd like to check in there to see whether it's the same logical processor that's failing. But I'd also like to check other troubleshooting data in that upload.

 

[sprite5415123]

That's gopod news, and I'm surprised the CPU didn't fail. However, that it BSODs with CBP enabled does suggest that the CPU is unstable when overclocked.

XMP is a RAM overclock. Your RAM is certified up to 3000MHz but it's native (SPD) clock speed is 2133MHz. The CPU is certified to handle RAM speeds up to 3200MHz, so if applying a 3000MHz XMP profile causes it to not boot then the problem is either that the RAM is flaky over 2133MHz or that the CPU is unhappy with RAM clocked over 2133MHz.

I think more information will help, can you please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

That upload will include the dump files and I'd like to check in there to see whether it's the same logical processor that's failing. But I'd also like to check other troubleshooting data in that upload.

SysnativeFileCollectionApp.zip uploaded to OneDrive, ram runs at 2666mhz according to task manager but I wont even try OCing manually till I've sorted out the CPB issue.

 

[ubuysa]

I think you have a flaky CPU sadly. Of the five dumps, three fail on logical processor #12, one on processor #6, and one on processor #13. However, in your System log, there are a lot of WHEA logger warning messageas reporting a corrected hardware error...

Log Name:      System
Source:        Microsoft-Windows-WHEA-Logger
Date:          05/11/2024 23:05:54
Event ID:      19
Task Category: None
Level:         Warning
Keywords:    
User:          LOCAL SERVICE
Computer:      DESKTOP-91615RR
Description:
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Unknown Error Source
Error Type: Cache Hierarchy Error
Processor APIC ID: 6

The details view of this entry contains further information.

The APIC ID (the logical procvessor) is different in most of these, so it doesn't look to be a specific processor or core at fault but it a general issue across the whole PC.

What PSU do you have in there (make, model, power output) and how old is it? This issue could very easily be power related.

 

[sprite5415123]

Its an CORSAIR RM850, honestly no idea how old it is, the warranty is for sure gone on that one already, it was an older piece I got from a friend, I'm guessing I should start by replacing the PSU then?

I think you have a flaky CPU sadly. Of the five dumps, three fail on logical processor #12, one on processor #6, and one on processor #13. However, in your System log, there are a lot of WHEA logger warning messageas reporting a corrected hardware error...

Log Name:      System
Source:        Microsoft-Windows-WHEA-Logger
Date:          05/11/2024 23:05:54
Event ID:      19
Task Category: None
Level:         Warning
Keywords:   
User:          LOCAL SERVICE
Computer:      DESKTOP-91615RR
Description:
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Unknown Error Source
Error Type: Cache Hierarchy Error
Processor APIC ID: 6

The details view of this entry contains further information.

The APIC ID (the logical procvessor) is different in most of these, so it doesn't look to be a specific processor or core at fault but it a general issue across the whole PC.

What PSU do you have in there (make, model, power output) and how old is it? This issue could very easily be power related.

 

[ubuysa]

I would start with the PSU for these reasons...

• You only get BSODs when enabling turbo boost
• Prime95 runs clean whithout CBP enabled which suggests the CPU is probably good
• You are seeing many corrected cache hierarchy errors in the logs, so something is not stable with the CPU

All the above makes me think that flaky power may be a more liklely cause than a flaky CPU, so I would replace the PSU first.