BSOD playing Guild Wars 2 and League of Legends (F4 STOP)

Welcome

Is this a new build?

STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR Usual causes: Hardware, Incompatibility, May be driver corruption BSOD Index

You need to go through these steps carefully because its related to hardware and you are getting the same bug check 124: Stop 0x124 - what it means and what to try

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80079a78f8, 0, 0}

Probably caused by : hardware

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

3: 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: fffffa80079a78f8, 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`033705b0 fffff800`02d1dca9 : fffffa80`079a78d0 fffffa80`06a38b50 00000000`00000001 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03370ad0 fffff800`02bfe547 : fffffa80`079a78d0 fffff800`02c782d8 fffffa80`06a38b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03370b00 fffff800`02b65945 : fffff800`02cd9ae0 00000000`00000001 00000000`00000000 fffffa80`06a38b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03370b40 fffff800`02ae4841 : fffff880`01272f00 fffff800`02b65920 fffffa80`06a38b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03370b70 fffff800`02d71e6a : 00000000`00000000 fffffa80`06a38b50 00000000`00000080 fffffa80`069f5040 : nt!ExpWorkerThread+0x111
fffff880`03370c00 fffff800`02acbec6 : fffff880`03189180 fffffa80`06a38b50 fffff880`031940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03370c40 00000000`00000000 : fffff880`03371000 fffff880`0336b000 fffff880`03524790 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_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

I need your msinfo32 file to see some stuff.

Please upload your msinfo32.nfo file. To get this:

• Click on the Start
• Type msinfo32 into the Search programs and files box
• When it opens, go to File, Save
• Save as msinfo32.nfo and save in a place you will remember
• Let it finish the process of gathering and saving the system info
• Right click the .nfo file, click send to compressed (zipped) folder
• Upload the .zip file here.

Let us know what you've tried

The file does not open, can you upload it properly again?

Got it, thanks. I see no problematic software installed which is good.
What antivirus are you using?

While we troubleshoot, please uninstall AVG and keep MSE Microsoft Security Essentials - Free Antivirus for Windows

Lets enable driver verifier for ruling out buggy drivers

Driver Verifier - Enable and Disable

Capt.Jack Sparrow said:

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Upload the other dumps you got?