BSOD whenever playing games or videos

[evildeaddude]

Hello people I have been having this problem with my computer for sometime now where I have been been either playing a game or watching a movie and it simply crashes at any random point for some reason. I have unloaded and reloaded the drivers multiple times, tested the RAM, cleaned the computer our numerous times, threaded other places, deleted audio drivers and reinstalled them...its just getting to the point where i start ripping of the heads of fuzzy plush toys without relenting and I don't know what to do. If you guys could please help it would be immensly apprisiated. If not, well hasn't made my computer worse least...(knocks on desk wood). But anyways if you guys could help would love it, if not thats cool to.Here are some specs though...

windows 7 64 bit

AMD Phenom II X4 965 Black Edition Deneb 3.4GHz Socket AM3 1

ASUS M4A88T-V EVO/USB3 AM3 AMD 880G USB 3.0 HDMI ATX AMD Motherboard

G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3

ASUS EAH6850 DC/2DIS/1GD5/V2 Radeon HD 6850 1GB 256-bit GDDR

Viewsonic 1080 22" Flatscreen

Western Digital Caviar Green WD20EARS 2TB SATA 3.0Gb/s 3.5" Internal Hard Drive -Bare Drive

CORSAIR Enthusiast Series CMPSU-850TX 850W ATX12V v2.2 / EPS

COOLER MASTER Elite 430 RC-430-KWN1 Black Steel / Plastic Co

6x:APEVIA CF12SL-UBL 120mm Blue LED Case Fan, G.SKILL FTB-35

So there is most of what I could find but I have left the repot info that the site asked for and so here it is...enjoy?

 

[Maguscreed]

you are getting the WHEA error, this is pretty much exclusively a hardware based issue.
The only occurrences I have seen of it where damaged hardware was not involved was when overclocking was in use.

If you have anything overclocked I suggest removing that overclock now.

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: fffffa8004de2038, 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`033b66f0 fffff800`03cdbc59 : fffffa80`04de2010 fffffa80`039f5040 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`033b6c10 fffff800`03bbbfa7 : fffffa80`04de2010 fffff800`03c362b8 fffffa80`039f5040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`033b6c40 fffff800`03b235c5 : fffff800`03c97ac0 00000000`00000001 fffffa80`04daf1f0 fffffa80`039f5040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`033b6c80 fffff800`03aa3021 : fffff880`00c30e00 fffff800`03b235a0 fffffa80`039f5000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`033b6cb0 fffff800`03d3532e : 00000000`00000000 fffffa80`039f5040 00000000`00000080 fffffa80`039f0740 : nt!ExpWorkerThread+0x111
fffff880`033b6d40 fffff800`03a8a666 : fffff880`03164180 fffffa80`039f5040 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033b6d80 00000000`00000000 : fffff880`033b7000 fffff880`033b1000 fffff880`033b69e0 00000000`00000000 : nt!KiStartSystemThread+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_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

 

[evildeaddude]

ya i dont OC but thanks for the advice

 

[zigzag3143]

ya i dont OC but thanks for the advice

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

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 http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html