Solved BSOD during games 0x0124

[Xenoix]

BSOD became more frequent over time. Have tried most recent CCC for the past few variations, as well as version 10.5 which was advised as stable. BSOD during random points while playing League of legends or civ 5. Been struggling with this for some time. Please help. Attached logs from SF_Diagnostic_Tool

 

[Arc]

I am seeing it is marked as solved. Is it? If not, unmark it.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Seatool for dos: SeaTools | Seagate download. Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know about your PSU wattage. Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

How old the build is?

Let us know, and upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

________________________________________________________________________________________
BSOD ANALYSIS:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800852b028, b6004000, f4000135}

Probably caused by : AuthenticAMD

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

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

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  CivilizationV.

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`01e65a88 fffff800`03201a3b : 00000000`00000124 00000000`00000000 fffffa80`0852b028 00000000`b6004000 : nt!KeBugCheckEx
fffff880`01e65a90 fffff800`02d95443 : 00000000`00000001 fffffa80`0851b930 00000000`00000000 fffffa80`0851b980 : hal!HalBugCheckSystem+0x1e3
fffff880`01e65ad0 fffff800`03201700 : 00000000`00000728 fffffa80`0851b930 fffff880`01e65e30 00000000`3d1e0000 : nt!WheaReportHwError+0x263
fffff880`01e65b30 fffff800`03201052 : fffffa80`0851b930 fffff880`01e65e30 fffffa80`0851b930 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`01e65c80 fffff800`031f4e8f : 00000000`0b045c84 00000000`00000001 fffff880`01e65eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`01e65cc0 fffff800`02c7d4ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`01e65cf0 fffff800`02c7d353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`01e65e30 00000000`00903a86 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0b045bec 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x903a86


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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