Dump shows probable CPU error:
Code:
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: ffffb1874351c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value
0: kd> !errrec ffffb1874351c028
===============================================================================
Common Platform Error Record @ ffffb1874351c028
-------------------------------------------------------------------------------
Record Id : 01d635077757d365
Severity : Fatal (1)
Length : 936
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 5/28/2020 15:49:13 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffb1874351c0a8
Section @ ffffb1874351c180
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 : 0x00000000000206a7
Processor ID : 0x0000000000000000
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffb1874351c0f0
Section @ ffffb1874351c240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000000
CPU Id : a7 06 02 00 00 08 10 00 - bf e3 9a 1f 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 @ ffffb1874351c240
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffb1874351c138
Section @ ffffb1874351c2c0
Offset : 664
Length : 272
Flags : 0x00000000
Severity : Fatal
Error : Internal timer (Proc 0 Bank 3)
Status : 0xbe00000000800400
Address : 0x00003802522fe5b9
Misc. : 0x000000000003ffff
Since removing the OC resolves the problem I'd say you need to replace the CPU, especially since you say Prime95 doesn't show any problems.
Your specs say you have a Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz which is a nice CPU that should be good enough to run most games without OCing.
Remove all OCing and run Prime95 again.
===================================================
Follow this tutorial to stress test your CPU:
Test with the Intel Processor Diagnostic Tool.
Also run Prime95 - Stress Test Your CPU - Windows 10 Forums
Also try OCCT: OCBASE / OCCT
For the above, read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall
For Intel CPUs (32 and 64 bit): Intel® Processor Diagnostic Tool
The purpose of the Intel® Processor Diagnostic Tool is to verify the functionality of an Intel® microprocessor. The diagnostic tool checks for brand identification, verifies the processor operating frequency, tests specific processor features, and performs a stress test on the processor.
Maybe test your RAM and see if that is contributing to the problem:
===================================================
Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review
Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:
- RAM will accept and keep random patterns of data sent to it
- There are no errors when different parts of memory try to interact
- There are no conflicts between memory addresses
They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.
Warning
MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.
If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.
Note
Both of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.
Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.
Take a picture when done and post in the forum please.
Also run Driver Verifier to see if it shows any driver problems that contribute to the problem as well:
Run Driver Verifier
Driver Verifier-- tracking down a mis-behaving driver.
Following the instructions in the above link will check for problems in all non-Microsoft drivers.
What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.
To check if verifier is active, open a Command Prompt and enter:
verifier /query
If not active it will respond with
No drivers are currently verified.
If you have questions, see this additional tutorial which may help to clear things up.
Enable and Disable Driver Verifier in Windows 10
If none of this helps you may have to replace the CPU. How old is it? Any chance it's still under warranty?