(Problem Event Name: BlueScreen) Need Help

[Doobieman]

Okay so I bought a computer two months ago from a guy who custom builds them but he hasn't responded to my questions so hopefully somebody here can help since im not very tech savvy. The computer started freezing on me once in a while about a week after the purchase but now I can barely play a game without it freezing. If I try to do a raid on world of warcraft thats a guarenteed freeze. Heres the message it gives me when I restart. It says windows has recovered from an unexpected shutdown and it gives me the option to find a solution to the problem which comes up with nothing.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80083E9038
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\041512-11450-01.dmp
C:\Users\Home\AppData\Local\Temp\WER-18798-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

 

[Doobieman]

Sorry didn't read the sticky post first. Just went through the instructions and attached the zip folder.

 

[writhziden]

Security Software (this is just to check that it is installed and working properly; nothing needs to be done with this information at this time):

wrsa.exe	c:\program files\webroot\wrsa.exe	756	8	200	1380	4/15/2012 11:08 AM	8.0.1.165	645.02 KB (660,504 bytes)	3/7/2012 1:29 PM
wrsa.exe	c:\program files\webroot\wrsa.exe	1576	8	200	1380	4/15/2012 11:08 AM	8.0.1.165	645.02 KB (660,504 bytes)	3/7/2012 1:29 PM

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Doobieman\Windows_NT6_BSOD_jcgriff2\041512-13494-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e4f650
Debug session time: Sun Apr 15 09:08:16.696 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:05.413
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80083de038, 0, 0}

Probably caused by : hardware

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: fffffa80083de038, 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_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02ffd6f0 fffff800`02eccca9 : fffffa80`083de010 fffffa80`0673ab60 fffff8a0`00190a70 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02ffdc10 fffff800`02dad577 : fffffa80`083de010 fffff800`02e272b8 fffffa80`0673ab60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02ffdc40 fffff800`02d14935 : fffff800`02e88ac0 00000000`00000001 fffff8a0`001909e8 fffffa80`0673ab60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02ffdc80 fffff800`02c91361 : fffff800`030aaf00 fffff800`02d14910 fffffa80`0673ab00 fffffa80`0673ab60 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02ffdcb0 fffff800`02f21fda : 00000000`00000000 fffffa80`0673ab60 00000000`00000080 fffffa80`066a3840 : nt!ExpWorkerThread+0x111
fffff880`02ffdd40 fffff800`02c789c6 : fffff880`009e9180 fffffa80`0673ab60 fffff880`009f3f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffd2c0 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_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

For the above crash, see http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following steps to supplement the information provided in that link.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.