BSOD is CPU damaged?

[atomicbigboy]

I need help figuring out if my CPU is having problems. From research it led to possible overheating on the CPU but temps are saying it's fine. Maybe someone can help me figure out what's wrong.

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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffb00c124c8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000060151, Low order 32-bits of the MCi_STATUS value.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.15063.674 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: To be filled by O.E.M.

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: FC

BIOS_DATE: 02/05/2013

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: 990FXA-UD3

BASEBOARD_VERSION: x.x

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb00c124c8028

BUGCHECK_P3: b0800000

BUGCHECK_P4: 60151

BUGCHECK_STR: 0x124_AuthenticAMD

CPU_COUNT: 8

CPU_MHZ: fb2

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: NGUYENPC

ANALYSIS_SESSION_TIME: 10-23-2017 08:46:16.0070

ANALYSIS_VERSION: 10.0.16299.15 amd64fre

STACK_TEXT:
fffff801`e1b71a68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE

PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_CACHE

TARGET_TIME: 2017-10-23T15:36:00.000Z

OSBUILD: 15063

OSSERVICEPACK: 674

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-09-29 00:20:26

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.15063.674

ANALYSIS_SESSION_ELAPSED_TIME: 1112

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_cache

FAILURE_ID_HASH: {b533751b-676e-7546-bcdc-24e6c40d0064}

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

0: kd> !errec ffffb00c124c8028
No export errec found
0: kd> !errrec ffffb00c124c8028
===============================================================================
Common Platform Error Record @ ffffb00c124c8028
-------------------------------------------------------------------------------
Record Id : 01d34bdfad194dc4
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 10/23/2017 15:36:00 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffb00c124c80a8
Section @ ffffb00c124c8180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal

Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Instruction Execute
Flags : 0x00
Level : 1
CPU Version : 0x0000000000600f20
Processor ID : 0x0000000000000000

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffb00c124c80f0
Section @ ffffb00c124c8240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000000
CPU Id : 20 0f 60 00 00 08 08 00 - 0b 32 98 3e ff fb 8b 17
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0 @ ffffb00c124c8240

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffb00c124c8138
Section @ ffffb00c124c82c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : ICACHEL1_IRD_ERR (Proc 0 Bank 1)
Status : 0xb080000000060151


here is the dmp file
https://drive.google.com/drive/folders/0B_7YQlD9F9tvQU5Pb2V6X2RQb3c?usp=sharing

 

[Kasper Jorgensen]

It's more likely a RAM problem than CPU. Download memtest86 and do a full pass or 2.

 

[atomicbigboy]

It's more likely a RAM problem than CPU. Download memtest86 and do a full pass or 2.

did one the other day 4 passes no errors.

 

[johnbl]

your memory dump shows that a error was detected in the cache RAM inside the CPU.
this problem would be unrelated to the RAM in the motherboard slots.

look for overheating, and overclocking drivers. certain cpu's have a bug that generate a bugcheck 0x124 when you have mixed memory modules running at certain clock rates.

look at the system up time at the start of the memory dump. if the time is under 15 seconds then often the motherboard logic reset the CPU and it restarted without stable voltages.

be sure to remove any overclock in bios and blow out the dust from the various fans, (cpu, gpu, and psu)
and make sure the fans are spinning up to proper speed.

a gpu that pulls too much power from the motherboard graphic slot can cause the voltage to the cpu to fluctuate or trigger the motherboard protection circuits that make the motherboard reset your cpu.

also check the voltages in bios if you can. maybe reset or update the bios if you have tweaked with voltages.

if you use any overclocking software, make sure you remove it.
provide the memory dump if you want me to take a look.