BSOD playing call of duty modern warfare2

Hello
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\011412-22854-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e66000 PsLoadedModuleList = 0xfffff800`030ab670
Debug session time: Sat Jan 14 15:16:03.986 2012 (UTC + 8:00)
System Uptime: 0 days 0:13:55.593
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8005096028, f669c000, 135}
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: fffffa8005096028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f669c000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, 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: iw4sp.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff880`031dca88 fffff800`02e2fa3b : 00000000`00000124 00000000`00000000 fffffa80`05096028 00000000`f669c000 : nt!KeBugCheckEx
fffff880`031dca90 fffff800`02ff3513 : 00000000`00000001 fffffa80`0512dea0 00000000`00000000 fffffa80`0512def0 : hal!HalBugCheckSystem+0x1e3
fffff880`031dcad0 fffff800`02e2f700 : 00000000`00000728 fffffa80`0512dea0 fffff880`031dce30 00000000`00d89800 : nt!WheaReportHwError+0x263
fffff880`031dcb30 fffff800`02e2f052 : fffffa80`0512dea0 fffff880`031dce30 fffffa80`0512dea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031dcc80 fffff800`02e22e8f : 00000000`00d83e80 00000000`00000001 fffff880`031dceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031dccc0 fffff800`02ee152c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`031dccf0 fffff800`02ee1393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dce30 00000000`00585b54 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0b44eeac 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x585b54

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
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE
Followup: MachineOwner
---------

Attachment 193455

Attachment 193456

Hello usasma i hope it was a good monday for you, is there a way of looking at kernel dumps or do they only give as much information as the minidump, i was
wondering because i tried another prime95 test and got a bsod which showed up in event screen- as event 41 but in minidumps its not shown i thought every shutdown would cause another minidump? a bit confused.i am going to rma the gtx560ti but i have run prime95 on xp and it was ok until installing the gtx to xp and problems, upgrade to win7 and same problems as xp + TDR's which i had never
experienced, remove the gtx re-install 9600gt use same drivers and everything appears to work fine except stress testing bsods the pc.
thanks bedtime here
bye.

Hello usasma, i think i have worked out the problem, you were correct first off thinking it may be hardware related.
i removed evga program as suggested and ran prime95 and it was a bsod still, but something struck me about the test so after rebooting i opened up prime95 again
and what it was, well mmmmmmmm only three threads showing not four as there
should be, so i did a restart and went into bios and locked to 2 cores.
And prime95 ran fine. I ran 1hr 4 complete series and all passes, then ran intelburn (bsod immediately before) and ran standard and high tests fine.
Originally the cpu test (cant remember the name) was a pass, and with the gtx560ti i had locked back to two cores and problems had remained the same.
So i appologise for wasting your time and thank you as well, haha the finding of
dump files and zipping, pasting had me move out of my comfort zone and i'm sure
learnt more about my new windows7 in a week than i would in a year .
You have me curious usasma, but i have always wondered whats over the next hill
anyway.
You are a good person usasma to help like this.
As my wife likes to say to me sometimes- "you stupid, stupid man" with a smile.
cya.