The 5 DMP files were 2 each 1A and EF and 1 each 124 (also the memory.dmp) - the most common cause of all of them is a hardware issue.
Yes, this could be damaged/failing hardware and the GPU is not likely to be the cause though that is certainly still possible.
Any overheating of the CPU would be very consistent with this issue (or a motherboard, PSU, or other hardware problem causing the CPU to overheat).
Re-installing Windows Clean would be a valuable tool because if it does not help to resolve the issue then that points even more to a hardware cause.
You definitely need to reseat everything. A loose or slightly corroded contact (very prevalent on new equipment) could be the cause and it is BY FAR the most common cause of these issues on home builds.
Chasing hardware issues on a home build can be very problematic due to the lack of known good parts to swap in and out as well as none of the metering equipment available to the device makers and some computer shops.
Be sure to contact ASUS and the other major device makers for diagnostics help and possible RMAs'.
BiosVersion = 3601
BiosReleaseDate = 05/26/2021 <-- current BIOS
SystemManufacturer = ASUS
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = ROG CROSSHAIR VIII HERO (WI-FI)
Check with BOTH Asus and AMD for even newer chipset drivers!
======
======
Another error in the MTB file that did not produce a DMP file or you did not include it.
System errors:
=============
Error: (11:07:04 PM) (Source: Microsoft-Windows-WHEA-Logger) (User: NT AUTHORITY)
Description: A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: 3
Error Type: 9
Processor APIC ID: 9
The details view of this entry contains further information.
Error: (07/09/2021 11:07:03 PM) (Source: BugCheck) (User: )
Description: 0x00000124 (0x0000000000000000, 0xffff900e741d4028, 0x00000000bc000800, 0x0000000001010135)C:\WINDOWS\MEMORY.DMPed8f58cc-3642-4914-88c3-f2531b9d8389
Each pair of BugCheck were essentially identical to each other. The analysis of all collectively are all over the place consistent with hardware issues.
BugCheck 124, {0, ffff900e741d4028, bc000800, 1010135}
Probably caused by : AuthenticAMD
Detailed analysis indicated:
DeviceId : SWD\MMDEVAPI{0.0.0.00000000}.{74244709-c9fa-4d57-9f38-db3431f369c7}
Name: LC32G7xT (NVIDIA High Definition Audio)
Description: Audio Endpoint
Class Guid: {c166523c-fe0c-4a94-a586-f1a80cfbbf3e}
Manufacturer: Microsoft
Service:
Device ID: SWD\MMDEVAPI{0.0.0.00000000}.{74244709-C9FA-4D57-9F38-DB3431F369C7}
&
Processor Report: (Note all the FATAL)
=============================================
Common Platform Error Record @ ffff900e741d4028
Record Id : 01d7751dd7065270
Severity : Fatal (1)
Length : 936
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 7/10/2021 3:06:31 (UTC)
Flags : 0x00000000
=============================================
Section 0 : Processor Generic
Descriptor @ ffff900e741d40a8
Section @ ffff900e741d4180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
=============================================
Section 1 : x86/x64 Processor Specific
Descriptor @ ffff900e741d40f0
Section @ ffff900e741d4240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
=============================================
Section 2 : x86/x64 MCA
Descriptor @ ffff900e741d4138
Section @ ffff900e741d42c0
Offset : 664
Length : 272
Flags : 0x00000000
Severity : Fatal
Error : Unknown (Proc 0 Bank 0)
Status : 0x0000000000000000
BugCheck EF, {ffff8e0896eb9080, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+10e )
ntkrnlmp.exe is a Windows component which means something else drove it into Fault.
Further detailed analysis did not help which is the usual expected result this BugCheck most commonly caused by hardware.
BugCheck 1A, {41792, ffff913ffd9a3cb0, 4000000, 0}
Probably caused by : memory_corruption ( ONE_BIT )
DeviceId : USB\VID_0BDA&PID_0411\9&2ce41060&0&4 <-- USB 0BDA Realtek Semiconductor Corp. 0411 Hub - a USB HUB? could be any USB device with a Realtek chip in it - may be a USB adapter? May or may not be the root cause.
- Try ALL the methods above and in my previous post.
- Try reducing the system down to as simple as possible and see if that helps.
Here to help,
Rob
Standard Disclaimer: Those may be non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.
Please let us know the results and if you need further assistance. Feedback definitely helps us help all.