Well the only way this can be good news is if you are overclocked, that would explain a hardware fault like this.
Also it can be the result of an overheat on rare occasions.
Other than that it's going to be an actual hardware problem.
The Whea error is pretty specific.
Code:
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: fffffa80069c6038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`031af6f0 fffff800`034e2d29 : fffffa80`069c6010 fffffa80`05219040 00000000`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031afc10 fffff800`033c2217 : fffffa80`069c6010 fffff800`0343c658 fffffa80`05219040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031afc40 fffff800`03329865 : fffff800`0349e3a0 00000000`00000001 fffffa80`069967f0 fffffa80`05219040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031afc80 fffff800`032a9a21 : fffff880`00c65e00 fffff800`03329840 fffffa80`05219000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031afcb0 fffff800`0353ccce : 00000000`00000000 fffffa80`05219040 00000000`00000080 fffffa80`05209040 : nt!ExpWorkerThread+0x111
fffff880`031afd40 fffff800`03290fe6 : fffff880`02f64180 fffffa80`05219040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031afd80 00000000`00000000 : fffff880`031b0000 fffff880`031aa000 fffff880`031aed90 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
I notice you are saying this is happening with a newer game, you may want to consider turning down the settings.
The easiest fix I know for this error is to remove any overclocks (cpu/ram/gpu) that may be in place.