BSOD playing Games only, normal computing completely fine

[yeHHH]

As the title says, I am bsoding when playing CS:GO. It just started happening today, my pc has been rock solid until now. Looking at the dumps it looks like a hardware issue, but I haven't changed any of my hardware recently. The crashes happen anywhere from 4 minutes in to an hour out.

What I've tried so far:
Updated all the drivers
Airdusted the inside of my case
Running memtest overnight - will update
Ran malwarebytes - nothing detected
Ran SFC /SCANNOW - it fixed something idk what it was but after restart I still got BSODs when playing CS:GO


PC Specs:
i7 4790k @4.4
ASROCK Z97
Corsair H50 Liquid Cooling
120 GB Samsung EVO SSD
250 GB Samsung EVO SSD
1 TB HDD
GTX 970 4GB
16 GB Ram @ 1866
600W PSU

I've attached the blue screen dumps below

 

[MistUnleashed]

As the title says, I am bsoding when playing CS:GO. It just started happening today, my pc has been rock solid until now. Looking at the dumps it looks like a hardware issue, but I haven't changed any of my hardware recently. The crashes happen anywhere from 4 minutes in to an hour out.

What I've tried so far:
Updated all the drivers
Airdusted the inside of my case
Running memtest overnight - will update
Ran malwarebytes - nothing detected
Ran SFC /SCANNOW - it fixed something idk what it was but after restart I still got BSODs when playing CS:GO


PC Specs:
i7 4790k @4.4
ASROCK Z97
Corsair H50 Liquid Cooling
120 GB Samsung EVO SSD
250 GB Samsung EVO SSD
1 TB HDD
GTX 970 4GB
16 GB Ram @ 1866
600W PSU

I've attached the blue screen dumps below

The minidumps aren't pointing to a specific driver, which is kind of annoying

Could you try to get the computer to BSOD again and upload the latest minidump from C:\Windows\Minidump

Thanks

 

[SGT Oddball]

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`02c5a000 PsLoadedModuleList = 0xfffff800`02ea1730
Debug session time: Thu Jun 11 00:57:12.184 2015 (UTC + 1:00)
System Uptime: 0 days 0:00:02.870
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[B]BugCheck 124,[/B] {0, fffffa800d06e8f8, 0, 0}
Probably caused by : [B]GenuineIntel[/B]
Followup: MachineOwner
---------
4: 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: fffffa800d06e8f8, 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_GenuineIntel
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`033a85b0 fffff800`02f1ecb9 : fffffa80`0d06e8d0 fffffa80`0ca48660 fffff8a0`00150b10 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`033a8ad0 fffff800`02dfd697 : fffffa80`0d06e8d0 fffff800`02e782d8 fffffa80`0ca48660 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`033a8b00 fffff800`02d646e5 : fffff800`02edaba0 00000000`00000001 fffff8a0`00150a88 fffffa80`0ca48660 : nt!WheapProcessWorkQueueItem+0x57
fffff880`033a8b40 fffff800`02cd84b5 : fffff800`030fc200 fffff800`02d646c0 fffffa80`0ca48600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`033a8b70 fffff800`02f68456 : 00000000`00000000 fffffa80`0ca48660 00000000`00000080 fffffa80`0c9b39c0 : nt!ExpWorkerThread+0x111
fffff880`033a8c00 fffff800`02cc02c6 : fffff880`03174180 fffffa80`0ca48660 fffff880`0317f0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033a8c40 00000000`00000000 : fffff880`033a9000 fffff880`033a3000 fffff880`033a8190 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE_PRV
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE_PRV
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache_prv
FAILURE_ID_HASH:  {81541344-bc50-ac27-6893-a85ccb2f6d33}
Followup: MachineOwner
---------

All the latest dumps I've checked point to a 124 fault, 0x124's are typically related to a hardware issue and can only be isolated by stress testing the major components.
If overclocking, reset all overclocks back to their default settings and then follow these:
RAM - run for a minimum of 8 consecutive passes
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
CPU - run the HIGH test
http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html
Video - run the FURMARK test for 20mins
http://www.sevenforums.com/tutorials/330579-graphics-card-problems-diagnose.html
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html
Storage - run the SHORT test using the DOS version
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[yeHHH]

All the latest dumps I've checked point to a 124 fault, 0x124's are typically related to a hardware issue and can only be isolated by stress testing the major components.
If overclocking, reset all overclocks back to their default settings and then follow these:
RAM - run for a minimum of 8 consecutive passes
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
CPU - run the HIGH test
http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html
Video - run the FURMARK test for 20mins
http://www.sevenforums.com/tutorials/330579-graphics-card-problems-diagnose.html
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html
Storage - run the SHORT test using the DOS version
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

I will post the RAM test results when I get back home, it was still running when I woke up today. Do I only need to run the seatools test for my HDD, or does it work for my 2 SSDs as well?