Constant BSOD while playing any game.

While I am playing any kind of game ranging from modern, to 1997 games, the computer will always blue screen on me.
Instead of describing it to you I will just post my minidump files.

Code:

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


Loading Dump File [C:\Windows\Minidump\041313-28140-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`03252000 PsLoadedModuleList = 0xfffff800`03495670
Debug session time: Sat Apr 13 20:30:42.390 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:20.687
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80064e0038, b2032000, 175}

Probably caused by : AuthenticAMD

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

1: 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: fffffa80064e0038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2032000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f1a08 fffff800`0321ba3b : 00000000`00000124 00000000`00000000 fffffa80`064e0038 00000000`b2032000 : nt!KeBugCheckEx
fffff880`009f1a10 fffff800`033de443 : 00000000`00000001 fffffa80`064b7d50 00000000`00000000 fffffa80`064b7da0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f1a50 fffff800`0321b700 : 00000000`00000728 fffffa80`064b7d50 fffff880`009f1db0 00000000`00000000 : nt!WheaReportHwError+0x263
fffff880`009f1ab0 fffff800`0321b052 : fffffa80`064b7d50 fffff880`009f1db0 fffffa80`064b7d50 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f1c00 fffff800`0320ee8f : fffffa80`060c4118 00000000`00000001 fffff880`009f1e30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f1c40 fffff800`032c64ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`009f1c70 fffff800`032c6353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f1db0 fffff880`015e2921 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03737b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : rdyboost!memmove+0xc1


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

 

Hello and welcome to MajorGeeks!

This appears to be a problem with either your processor or the drivers within the operating system for it.

What processor do you have? Some processor models from AMD need extra driver fix components.

 

0x124's are commonly triggered by overclocking, if you are overclocking - stop and set it back to defaults.

0x124 errors can be tricky to diagnose, they mean that the hardware, often the CPU, is self-reporting an error; in this case, it looks like the error reported was a Machine check error reported in the cache on the CPU.

However, the CPU may not be at fault, it may be a driver issue, or possibly in this case (see the Stack text, the oldest (bottom) entry was ReadyBoost), it may be an error in the expected data between a ReadyBoost drive and the CPU cache. It could be that the CPU is not fully supported by the motherboard/BIOS - or many other possibilities!

If you zip and upload the dump, I could try to delve deeper.

A good thread on 0x124's is here.