Blue Screen Error

daken84

Reputable
Jan 21, 2016
1
0
4,510
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.28
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8006B06038
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\012116-15522-01.dmp
C:\Users\Daken.Brian-PC.001\AppData\Local\Temp\WER-25662-0.sysdata.xml


EDIT 1:
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02860000 PsLoadedModuleList = 0xfffff800`02aa5e90
Debug session time: Wed Jan 20 23:11:22.878 2016 (UTC - 5:00)
System Uptime: 0 days 0:00:08.909
*******************************************************************************
* *
* 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: fffffa8006b616c8, 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:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`033af6f0 fffff800`02b23d29 : fffffa80`06b616a0 fffffa80`05522b60 00000000`00000001 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`033afc10 fffff800`02a03217 : fffffa80`06b616a0 fffff800`02a7d658 fffffa80`05522b60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`033afc40 fffff800`0296a865 : fffff800`02adf3a0 00000000`00000001 00000000`00000000 fffffa80`05522b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`033afc80 fffff800`028eaa21 : fffff880`01244f00 fffff800`0296a840 fffffa80`05522b00 83728372`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`033afcb0 fffff800`02b7dcce : a4aba4ab`c32ec32e fffffa80`05522b60 00000000`00000080 fffffa80`05508040 : nt!ExpWorkerThread+0x111
fffff880`033afd40 fffff800`028d1fe6 : fffff880`03186180 fffffa80`05522b60 fffff880`031910c0 5dd75dd7`2db22db2 : nt!PspSystemThreadStartup+0x5a
fffff880`033afd80 00000000`00000000 : fffff880`033b0000 fffff880`033aa000 fffff880`033af6a0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
 
Solution
generally a bugcheck 0x124 with a short system uptime like yours (8 seconds) indicated the the CPU was reset because of a power condition.

look for overclocking/overheating, underpowered PSU for the GPU