Random BSOD, while gaming or just browsing the internet

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

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

Files that help describe the problem:
C:\Windows\Minidump\100912-26067-01.dmp
C:\Users\Josh\AppData\Local\Temp\WER-41870-0.sysdata.xml

A stop 0x124 error usually means a hardware problem. Your last dmp file was dated 10/9/2012 so may not have the most current info. But based on that dmp:

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa800814d4f8, 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:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031af6f0 fffff800`03114ca9 : fffffa80`0814d4d0 fffffa80`06a2d040 00000000`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031afc10 fffff800`02ff5547 : fffffa80`0814d4d0 fffff800`0306f2d8 fffffa80`06a2d040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031afc40 fffff800`02f5c945 : fffff800`030d0ae0 fffff800`02edb82d 00000000`00000010 00000000`00000206 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031afc80 fffff800`02edb841 : fffff880`010b8e00 fffff800`02f5c920 fffffa80`06a2d000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031afcb0 fffff800`03168e6a : 03030208`08051114 fffffa80`06a2d040 00000000`00000080 fffffa80`06a269e0 : nt!ExpWorkerThread+0x111
fffff880`031afd40 fffff800`02ec2ec6 : fffff880`02f64180 fffffa80`06a2d040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031afd80 00000000`00000000 : fffff880`031b0000 fffff880`031aa000 fffff880`037fd740 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

If you've OCed your computer I'd recommend restoring default values at least temporarily. Unplug all non-essential USB devices. And follow the troubleshooting steps here:

Stop 0x124 - what it means and what to try