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

spritexd · November 6

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

************* 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

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 ***