There was WHEA 0x124 seen on 4/15/2018.
There should be no over clocking during the troubleshooting process.
How come you are overclocking knowing that you have a WHEA 0x124 problem?
We cannot troubleshoot if you over clock.
The BSOD are designed to reduce the harm to the hardware.
1) Return all settings to stock.
2) Reset the BIOS
3) Confirm in the thread when these are accomplished.
Open file explorer > this PC > C: > in the right upper corner search for:
1) win32k.sys-20180416-1200.dmp
or
2) win32k.sys
zip > post into the thread a one drive or drop box share link
3) C:\WINDOWS\MEMORY.DMP
Creation date: 04/15/2018 16:49:42
Size on disk: 998 MB
4) Post an image of the Whocrashed analyze report into the thread
Code:
Event[5978]: Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2018-04-15T16:49:48.015
Event ID: 1001
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: M-MaximusXHero
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffa3844a56d028, 0x00000000f2000040, 0x0000000000030005). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.
Code:
Event[5977]: Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 2018-04-15T16:49:47.999
Event ID: 1005
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: M-MaximusXHero
Description:
Unable to produce a minidump file from the full dump file.