Bluescreen Help...

I have been on the receiving end of more frequent blue screens... I am trying to learn how to understand the .dmp file, but without much software/programming knowledge i am letting myself down. ANy Help?

I have opened /dmp to find :

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: ffffba08fa217028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.

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

fffff8014782a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8014782a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8014782a3c8: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 4

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on THEPRODIGY

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 4

Key : Analysis.Memory.CommitPeak.Mb
Value: 74

Key : Analysis.System
Value: CreateObject


00 ffffa380`f86a7b58 fffff801`473a4188 nt!KeBugCheckEx
01 ffffa380`f86a7b60 fffff801`4bd81920 hal!HalBugCheckSystem+0xd8
02 ffffa380`f86a7ba0 fffff801`47741092 PSHED!PshedBugCheckSystem+0x10
03 ffffa380`f86a7bd0 fffff801`473a5ae6 nt!WheaReportHwError+0x382
04 ffffa380`f86a7c90 fffff801`473a5f7a hal!HalpMcaReportError+0x72
05 ffffa380`f86a7df0 fffff801`473a5e54 hal!HalpMceHandlerCore+0xf2
06 ffffa380`f86a7e40 fffff801`473a60c0 hal!HalpMceHandler+0xe0
07 ffffa380`f86a7e80 fffff801`473a5168 hal!HalpMceHandlerWithRendezvous+0xd4
08 ffffa380`f86a7eb0 fffff801`473a6347 hal!HalpHandleMachineCheck+0x5c
09 ffffa380`f86a7ee0 fffff801`476a4e30 hal!HalHandleMcheck+0x37
0a ffffa380`f86a7f10 fffff801`475d13ba nt!KiHandleMcheck+0x10
0b ffffa380`f86a7f40 fffff801`475d106f nt!KxMcheckAbort+0x7a
0c ffffa380`f86a8080 fffff801`474c932e nt!KiMcheckAbort+0x26f
0d ffffa20a`b7c371c0 00000000`00000000 nt!KeQueryValuesThread+0x14e

5: kd> kd
ffffa380`f86a7b50 ????????
ffffa380`f86a7b54 ????????
ffffa380`f86a7b58 473a4188
ffffa380`f86a7b5c fffff801
ffffa380`f86a7b60 00000124
ffffa380`f86a7b64 00000000
ffffa380`f86a7b68 00000000
ffffa380`f86a7b6c 00000000
ffffa380`f86a7b70 fa217028
ffffa380`f86a7b74 ffffba08
....
....

 

Okay, you've probably already figured out that this is the CPU (probably) self-reporting a hardware error.

The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

WHEA_UNCORRECTABLE_ERROR Parameters
WHEA_UNCORRECTABLE_ERROR Parameters
Parameter 1 0x0
Parameter 2 Address of WHEA_ERROR_RECORD structure.
Parameter 3 High 32 bits of MCi_STATUS MSR for the MCA bank that had the error.
Parameter 4 Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error.
Cause of error A machine check exception occurred.
These parameter descriptions apply if the processor is based on the x64 architecture, or the x86 architecture that has the MCA feature available (for example, Intel Pentium Pro, Pentium IV, or Xeon).

Comments
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 condition.

For information about WHEA, see Windows Hardware Error Architecture Design Guide within the WDK documentation .

Note This bug check is not supported in Windows versions prior to Windows Vista. Instead, machine check exceptions are reported through bug check 0x9C.

WinDbg Output Examples:
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: fffffa800677f8f8, 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.

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: 00000004, PCI Express Error
Arg2: 84e39024, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000
Arg4: 00000000

1st of 3 posts on 0x124's: https://bsodtutorials.wordpress.com/2015/07/24/the-complete-debugging-guide-to-stop-0x124-part-1/
Slightly older but perhaps better for an overview (if it still shows up): http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html
MSDN details: https://docs.microsoft.com/en-us/wi...-whea-uncorrectable-error?redirectedfrom=MSDN

It's not the easiest BSOD type to learn from, way too many variables/subtypes! After ~20 examples you may or may not begin to get some useful clues/shortcuts.