BSOD error unsure on what to do.

Hey there ive been getting BSOD for awhile since i built my PC and have been trying to fix it myself, at first i thought it was the RAM so i manually tried to do the timings to what the manufacturer said to put them at, was a tad unsure on all the other settings in the menu..

Thinking it could be the graphics card now though I have uninstalled and re-installed all drivers and still no help.

Hi Heaty.

A stop 0x124 is supposed to be a hardware issue, mainly, but some other things are included in its scope, sometimes.

Dont overclock.

Code:

CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3510

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Let us know the results. Also, upload your MSINFO32.nfo file for any future need.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

_________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800f592028, be200000, 21166}

Probably caused by : GenuineIntel

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

5: 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: fffffa800f592028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000021166, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`03498b58 fffff800`03a29a3b : 00000000`00000124 00000000`00000000 fffffa80`0f592028 00000000`be200000 : nt!KeBugCheckEx
fffff880`03498b60 fffff800`03bec463 : 00000000`00000001 fffffa80`0cfb6ea0 00000000`00000000 fffffa80`0cfb6ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`03498ba0 fffff800`03a29700 : 00000000`00000728 fffffa80`0cfb6ea0 fffff880`03498f30 fffff880`03498f00 : nt!WheaReportHwError+0x263
fffff880`03498c00 fffff800`03a29052 : fffffa80`0cfb6ea0 fffff880`03498f30 fffffa80`0cfb6ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03498d50 fffff800`03a28f0d : 00000000`00000008 00000000`00000001 fffff880`03498fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03498d90 fffff800`03a1ce88 : 00000000`00000002 fffff880`03490180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`03498dc0 fffff800`03ad44ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03498df0 fffff800`03ad4313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03498f30 fffff880`055a3c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`034b8b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache

FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}

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