Reccuring BSoD For Roughly 2 Weeks

Hi, for some reason about 2 weeks ago my PC started crashing and producing a BSoD report when I turn it back on. To start with it was about twice a week but the past few days it's been one or more times a day. It doesn't seem to matter what I'm doing at the time of the crash either, any help would be much appreciated. Here's the crash report:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80084328F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\080813-57455-01.dmp
C:\Users\*name*\AppData\Local\Temp\WER-99154-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008389038, 0, 0}

Probably caused by : AuthenticAMD

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: fffffa8008389038, 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:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031b65b0 fffff800`036ddca9 : fffffa80`08389010 fffffa80`06ad0040 fffff8a0`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031b6ad0 fffff800`035bee87 : fffffa80`08389010 fffff800`036382d8 fffffa80`06ad0040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031b6b00 fffff800`03526285 : fffff800`03699ae0 00000000`00000001 fffffa80`07b023c0 fffffa80`06ad0040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031b6b40 fffff800`0349c251 : fffff880`010b5e00 fffff800`03526260 fffffa80`06ad0000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031b6b70 fffff800`03730ede : 00000000`00000000 fffffa80`06ad0040 00000000`00000080 fffffa80`06a24040 : nt!ExpWorkerThread+0x111
fffff880`031b6c00 fffff800`03483906 : fffff880`02fd7180 fffffa80`06ad0040 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6c40 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`031b5e30 00000000`00000000 : nt!KiStartSystemThread+0x16


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_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

0: kd> !errrec fffffa8008389038
===============================================================================
Common Platform Error Record @ fffffa8008389038
-------------------------------------------------------------------------------
Record Id     : 01ce9474d7db1727
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/8/2013 20:21:29 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80083890b8
Section       @ fffffa8008389190
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f12
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008389100
Section       @ fffffa8008389250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 12 0f 60 00 00 08 04 00 - 0b 22 98 1e ff fb 8b 17
                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  @ fffffa8008389250

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008389148
Section       @ fffffa80083892d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHELG_WR_ERR (Proc 0 Bank 4)
  Status      : 0xf300000200190127

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try