Solved Random BSOD while playing or exiting games

[Upgreyed]

I have been getting random bsod while or after playing games, I did want to notify that I do have gigabytes easytune app as well installed for fan control but it sets defaults to 3.80 ghz since I have an intel 4670k processor.

 

[badger906]

your system even has stated the following event: ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.

Basically your rig is over heating.

 

[Upgreyed]

Great I'll investigate the settings cause my radiator may not be at full setting

 

[Upgreyed]

Bsod while pc is not being heavily used.

I recently submitted a bsod dump a few days ago diagnosing pc was overheating. I configured my cooling system (I have a cooler master seidon 120xl aio) by setting the pump to full speed and having the fans at 60% until it needs more voltage to cool. still seeing bsod while using pc and not during heavy loads. Should I check thermal paste and reapply it along with checking to make sure it is making solid contact.

 

[Arc]

Checking the thermal paste is one of the jobs in your list, but before that you have to check a lot other things. Because a stop 0x124 may be caused by a lot of things, and overheating is one of them.

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: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

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.

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.

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

Stress test the CPU.
Hardware - Stress Test With Prime95

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.

Let us know the results. Will suggest the further things after seeing the results.

And, dont start multiple threads for the same issue?

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800744e8f8, 0, 0}

Probably caused by : GenuineIntel

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: fffffa800744e8f8, 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:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

STACK_TEXT:  
fffff880`035e75b0 fffff800`03ed4ca9 : fffffa80`0744e8d0 fffffa80`06d1b660 00000000`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`035e7ad0 fffff800`03db5ea7 : fffffa80`0744e8d0 fffff800`03e2f2d8 fffffa80`06d1b660 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`035e7b00 fffff800`03d1d275 : fffff800`03e90b40 00000000`00000001 fffffa80`0749ee10 fffffa80`06d1b660 : nt!WheapProcessWorkQueueItem+0x57
fffff880`035e7b40 fffff800`03c93261 : fffff880`01230e00 fffff800`03d1d250 fffffa80`06d1b600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`035e7b70 fffff800`03f262ea : 00000000`00000000 fffffa80`06d1b660 00000000`00000080 fffffa80`06ce4890 : nt!ExpWorkerThread+0x111
fffff880`035e7c00 fffff800`03c7a8e6 : fffff880`03365180 fffffa80`06d1b660 fffff880`0336ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035e7c40 00000000`00000000 : fffff880`035e8000 fffff880`035e2000 fffff880`032cc7e0 00000000`00000000 : nt!KxStartSystemThread+0x16


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_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae_prv

FAILURE_ID_HASH:  {435e2195-e498-1e77-0526-f8d7450275e5}

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

 

[Upgreyed]

So after reading the event log I saw a process called sensordetect which was associated with gigabytes easytune softwareware for the fan control which was causing the problem.

 

[Arc]

So after reading the event log I saw a process called sensordetect which was associated with gigabytes easytune softwareware for the fan control which was causing the problem.