Hello everyone,
My computer has been experiencing multiple BSODs whenever my computer was under a load. ex: Adobe programs, video games.
I have a Intel 7800X processor on a Asus TUF Mark I motherboard
128gb ram
Zotac 3090 graphics card
Seasonic USA PRIME PX-1300 1300 Watt 80 Plus Platinum Power Supply
Fresh install of windows 10, all drivers are up to date.
If anyone can help I would greatly appreciate it, here is what windbg said the program is:
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
-- 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.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36
Code:
Microsoft (R) Windows Debugger Version 10.0.25921.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\120323-22265-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 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff806`49800000 PsLoadedModuleList = 0xfffff806`4a42a730
Debug session time: Sun Dec 3 19:21:43.288 2023 (UTC - 6:00)
System Uptime: 2 days 8:09:47.913
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000e3`94e08018). Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`49bfd6c0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffb980`81f628f0=0000000000000124
7: 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: ffff8389c15a3028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000001f0405, 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: 4577
Key : Analysis.Elapsed.mSec
Value: 7209
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 609
Key : Analysis.Init.Elapsed.mSec
Value: 9552
Key : Analysis.Memory.CommitPeak.Mb
Value: 98
Key : Bugcheck.Code.LegacyAPI
Value: 0x124
Key : Failure.Bucket
Value: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys
Key : Failure.Hash
Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2}
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffff8389c15a3028
BUGCHECK_P3: be200000
BUGCHECK_P4: 1f0405
FILE_IN_CAB: 120323-22265-01.dmp
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: aftershoot.exe
STACK_TEXT:
ffffb980`81f628e8 fffff806`49cb944a : 00000000`00000124 00000000`00000000 ffff8389`c15a3028 00000000`be200000 : nt!KeBugCheckEx
ffffb980`81f628f0 fffff806`48a015b0 : 00000000`00000000 ffff8389`c15a3028 ffff8389`bf1fd4f0 ffff8389`c15a3028 : nt!HalBugCheckSystem+0xca
ffffb980`81f62930 fffff806`49dbb74e : 00000000`00000000 ffffb980`81f629d9 ffff8389`c15a3028 ffff8389`bf1fd4f0 : PSHED!PshedBugCheckSystem+0x10
ffffb980`81f62960 fffff806`49cbad71 : ffff8389`c9d29ac0 ffff8389`c9d29ac0 ffff8389`bf1fd540 ffff8389`bf1fd4f0 : nt!WheaReportHwError+0x46e
ffffb980`81f62a40 fffff806`49cbb0e3 : 00000000`00000007 ffff8389`bf1fd540 ffff8389`bf1fd4f0 00000000`00000007 : nt!HalpMcaReportError+0xb1
ffffb980`81f62bb0 fffff806`49cbafc0 : ffff8389`bdef2508 f03af03a`00000001 00000000`00000000 a73ca73c`f82af82a : nt!HalpMceHandlerCore+0xef
ffffb980`81f62c00 fffff806`49cbb211 : 00000000`0000000c 00000000`00000001 00000000`00000000 afc4afc4`7e557f55 : nt!HalpMceHandler+0xe0
ffffb980`81f62c40 fffff806`49cba47b : 00000000`00000000 00000000`00000000 ffffb980`81f62ed0 15fd15fd`87378737 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffb980`81f62c70 fffff806`49cbccc5 : ffff8389`bdef2508 7e687e68`21352135 09460946`fc99fc99 7f5f7f5f`a0dda0dd : nt!HalpHandleMachineCheck+0x5f
ffffb980`81f62ca0 fffff806`49d12889 : 09970997`59255925 75067506`93349334 5a455a45`168d168d 78707870`8df38df3 : nt!HalHandleMcheck+0x35
ffffb980`81f62cd0 fffff806`49c0e2ba : f665f665`e571e571 f03af03a`f5d4f5d4 1ccd1ccd`15a71127 a73ca73c`f82af82a : nt!KiHandleMcheck+0x9
ffffb980`81f62d00 fffff806`49c0df77 : 00000000`00000000 00000000`00000000 00000000`00000800 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffb980`81f62e40 00007fff`f64612de : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
000000e3`984498e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`f64612de
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}
Followup: MachineOwner
---------
