Daily BSOD with Custom Build

nickiek · 06 Feb 2014

About five months ago I decided to invest in a custom build. It ran fine for the first couple months. After that I began to have the occasional BSOD with increasing frequency. Strangely enough, they seemed to occur regularly for about a week and would then stop only to start up again a week or so later. Now, the problem has escalated to nearly every night.

I do game often but have only had one crash while doing so. The rest occur randomly while watching a video online or while the computer is on sleep.

Unfortunately, I do not know enough to pinpoint the exact problem. From what I've seen with other threads, "ntoskrnl.exe" often takes the blame for the crash but isn't necessarily the cause. Rather than risk causing more damage, I thought I'd seek advice from those more knowledgeable than myself. Any help is greatly appreciated.

I have attached the SF Diagnostic Tool .zip file from my crash. Please let me know if there is any other information I have forgotten to include.

Custom Build Specs (as purchased from Newegg):
ASUS GRYPHON Z87 LGA 1150 Intel Z87 HDMI SATA 6Gb/s USB 3.0 uATX Intel Motherboard
Intel Core i5-4670K Haswell 3.4GHz LGA 1150 84W Quad-Core Desktop Processor Intel HD Graphics BX80646I54670K
EVGA 02G-P4-2763-KR GeForce GTX 760 2GB 256-bit GDDR5 PCI Express 3.0 SLI Support w/ EVGA ACX Cooler Video Card
G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 2133 (PC3 17000) Desktop Memory Model F3-2133C10D-8GXM

CORSAIR Hydro Series H60 (CW-9060007-WW) High Performance Water / Liquid CPU Cooler
XIGMATEK FCB (Fluid Circulative Bearing) Cooling System XLF XLF-F1455
PC Power and Cooling Silencer Mk III Series 600W Modular Power Supply features 100% Japanese 105°C rated Capacitors Intel 4th Gen CPU Haswell

SAMSUNG 840 EVO MZ-7TE250KW 2.5" TLC Internal Solid State Drive (SSD) With Desktop Bundle Kit
(2) Seagate Barracuda ST2000DM001 2TB 7200 RPM 64MB Cache SATA 6.0Gb/s 3.5" Internal Hard Drive Bare Drive [RAIDED]

Windows 7 Professional x64

Arc · 07 Feb 2014

Hi nickiek.

A stop 0x124 is some sort of hardware issue.

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

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 .

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

Let us know the results.
__________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80108ba028, be000000, 100110a}

Probably caused by : GenuineIntel

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

1: 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: fffffa80108ba028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, 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`03308a58 fffff800`02e27a3b : 00000000`00000124 00000000`00000000 fffffa80`108ba028 00000000`be000000 : nt!KeBugCheckEx
fffff880`03308a60 fffff800`02fea463 : 00000000`00000001 fffffa80`105b2da0 00000000`00000000 fffffa80`105b2df0 : hal!HalBugCheckSystem+0x1e3
fffff880`03308aa0 fffff800`02e27700 : 00000000`00000728 fffffa80`105b2da0 fffff880`03308e30 fffff880`03308e00 : nt!WheaReportHwError+0x263
fffff880`03308b00 fffff800`02e27052 : fffffa80`105b2da0 fffff880`03308e30 fffffa80`105b2da0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03308c50 fffff800`02e26f0d : 00000000`00000004 00000000`00000001 fffff880`03308eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03308c90 fffff800`02e1ae88 : 00000000`00000000 fffff880`03300180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`03308cc0 fffff800`02ed24ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03308cf0 fffff800`02ed2313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03308e30 fffff880`04c9d9c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03328b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2


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
---------

1: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=3099]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 0903
BiosReleaseDate = 05/07/2013
SystemManufacturer = ASUS
SystemProductName = All Series
SystemFamily = ASUS MB
SystemVersion = System Version
SystemSKU = All
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = GRYPHON Z87
BaseBoardVersion = Rev 1.xx
1: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3405