BSOD having trouble figuring out what to do..

So i have recently just built my PC and i thought it all went quite well..
but when i was updating and of the hardware/software i would instantly get a blue screen error..
i first thought it was that i needed to update the bios... which i did..
and then updated everything in device manager apart from two that cannot be found.
firstly i got an error code that i couldnt quite get the number of but it had some 3s in it :L

After doing quite a bit of research i decided it must be the gpu as now i was only getting BSOD when i loaded up a game and started to play.. menus were fine but the actual game few secounds/minutes boom crash

i also moved the graphics card down a slot to see if that would work.. nope..


Please help i really to be rid of this problem...

Blue Screen of Death (BSOD) Posting Instructions

Hello Ventus, Welcome to SF

According to your dumps you are suffering from multiple 0x124 errors which are indicating a hardware error

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8010063028, be200000, 21136}
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
0: 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: fffffa8010063028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000021136, 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: f
STACK_TEXT:
fffff800`00ba8a98 fffff800`033fba3b : 00000000`00000124 00000000`00000000 fffffa80`10063028 00000000`be200000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02f8f443 : 00000000`00000001 fffffa80`0d4a6170 00000000`00000000 fffffa80`0d4a61c0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`033fb700 : 00000000`00000728 fffffa80`0d4a6170 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`033fb052 : fffffa80`0d4a6170 fffff800`00ba8e70 fffffa80`0d4a6170 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`033faf0d : 00000000`00000008 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`033eee88 : 00000000`00000001 fffff800`02ff3e80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02e774ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02e77353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 fffff880`050aec61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9cb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x2c61

STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner
---------
0: kd> !errrec [fffffa8010063028]
===============================================================================
Common Platform Error Record @ fffffa8010063028
-------------------------------------------------------------------------------
Record Id : 01ce630ce49a64a3
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 6/6/2013 23:51:06 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa80100630a8
Section @ fffffa8010063180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Data Read
Flags : 0x00
Level : 2
CPU Version : 0x00000000000306a9
Processor ID : 0x0000000000000000
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa80100630f0
Section @ fffffa8010063240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000000
CPU Id : a9 06 03 00 00 08 10 00 - bf e3 9a 7f ff fb eb bf
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 @ fffffa8010063240
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa8010063138
Section @ fffffa80100632c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : DCACHEL2_DRD_ERR (Proc 0 Bank 5)
Status : 0xbe20000000021136
Address : 0x00000002c1b1ecc0
Misc. : 0x0000007006038086

Have a read of this thread for some general info and things to do
Stop 0x124 - what it means and what to try

The dump indicates a level 2 cache error reported by the cpu although this does not necessarily mean the cpu is faulty
I would start by checking machine temperatures at idle and at load and see how fast/how high the temps rise to see if anything is overheating

If you want to stress test the cpu try Hardware - Stress Test With Prime95 but you need to monitor temps closely while doing it and dont leave unattended until you are sure temp has levelled out and be sure to abort the test if temps rise to high/too fast

Post back your temps and if they are ok then we can look at some other things