Hi jadors,
Welcome to the 10forums :)
This is a generic post for the 0x124 crash, due to the reason why the CPU reported the crash.
In all the dumps I've looked in the exact same is shown, an internal unclassified error.
An internal unclassified error means that the error hasn't been publicly documented so we would have to see the documentation of Intel to find out exactly what happened, however this can be time consuming hence the reason why I post a generic version.
Code:
3: kd> !errrec ffffe001`0a912028
===============================================================================
Common Platform Error Record @ ffffe0010a912028
-------------------------------------------------------------------------------
Record Id : 01d1a8603a248f69
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 5/7/2016 13:01:06 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffe0010a9120a8
Section @ ffffe0010a912180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Micro-Architectural Error
Flags : 0x00
CPU Version : 0x00000000000306c3
Processor ID : 0x0000000000000003
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffe0010a9120f0
Section @ ffffe0010a912240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000003
CPU Id : c3 06 03 00 00 08 10 03 - bf fb da 7f ff fb eb bf
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0 @ ffffe0010a912240
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffe0010a912138
Section @ ffffe0010a9122c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : Internal unclassified (Proc 3 Bank 4)
Status : 0xba00000052000402
The error 0x124 WHEA_UNCORRECTABLE_ERROR (Windows Hardware Error Architecture)
This means that there are problems with your hardware, but this error is also caused by overclocking, faulty drivers or BIOS problems.

STOP 0x124 Troubleshooting

Read carefully before proceeding.

Warning
If you're overclocking your system, revert back to stock clocks now.

Note
Test the system once the overclock is removed before continuing with the steps outlined below.
Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

CPU TEST
Run Prime95 and/or IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums & CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

Warning
Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

TWO

RAM TEST
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note
MemTest86+ needs to be run for
at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for
zero errors here. Even a single error will indicate RAM failure.
Make a photo of the result and post it please.
Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

THREE

HDD TEST
Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests
- Short Drive Self Test
- Short generic
- Long generic
If the short generic fails, no need for the long generic.

Note
Do not run SeaTools on an SSD as the results will be invalid.
Post screenshots/photos of the test results
Run chkdsk
Disk Check - Windows 7 Help Forums
Run HDTune to
- scan for errors, no quick scan but full scan
- check the health,
- benchmark.
It may take some time, but please take the time you need to perform it properly.
Let me know what the results are
- of the error scan,
- make a screenshot of the health of every hard drive and post the screenshots,
- post screenshots with the benchmark of the
- transfer rate,
- access time,
- burst rate,
- cpu usage.
Best is to make screenshots/photos of these test results too.

FOUR

GPU TEST
Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

Note
Run Furmark for around 30 minutes.

Warning
Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.