BSOD playing XCOM2 Error STOP: 0x00000124

Hello John and welcome to 7forums! :)

STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes: Hardware, Incompatibility, May be driver corruption
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)

That does not mean the processor itself is bad, though it could be. The cause could be the
compound between the processor and heatsink, the hearsink itself, BIOS, chipset drivers,
and other hardware problems (including damage to the motherboard or other hardware).

Well I'll start with one thing that I think is a necessary update but some here might not start at my end, anywho there is a BIOS update for your motherboard, yours is currently at P1.40 but the latest is at P1.90 and you can find it here:
ASRock > 990FX Extreme3

And if you are unfamiliar with how to do a BIOS update please follow this:
ASRock - BIOS Upgrade Instruction

Cheers, Boris :)

Hello John.

Sorry for not being very active, you could try either instant or Windows.

I'm out right now so I can't really help but I'll look into your problem later, sorry again for not responding sooner!

Cheers , Boris!

All 0x124 are read errors caught when the CPU wanted to execute the data.
I would suggest to start with removing certain software
Asrock software, so called bloatware, may cause problems because bloatware is usually improper coded
Daemon tools, some drivers created for Daemon tools are very buggy and causes problems including bluescreens even when the SPTD* driver isn't installed.
*SCSI Pass Through Direct (SPTD)

Code:

4: kd> !errrec fffffa80079c34b8
===============================================================================
Common Platform Error Record @ fffffa80079c34b8
-------------------------------------------------------------------------------
Record Id     : 01d168266688d347
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/15/2016 19:23:55 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80079c3538
Section       @ fffffa80079c3610
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Instruction Execute
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000004

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80079c3580
Section       @ fffffa80079c36d0
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000004
CPU Id        : 20 0f 60 00 00 08 08 04 - 0b 32 98 3e ff fb 8b 17
                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  @ fffffa80079c36d0

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80079c35c8
Section       @ fffffa80079c3750
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : ICACHELG_IRD_ERR (Proc 4 Bank 1)
  Status      : 0xb600000000100153
  Address     : 0x0000000000000000
  Misc.       : 0x0000000000000000

Have you by the way handled the 0x4A (1st crash of December)? This crash seems to be caused by the Avast file system minifilter driver, this may be totally irrelevant but it is the only 1 that isn't a 0x124 which is why it caught my eye.
Driver Reference Table - aswMonFlt.sys

So i should remove the ASRock software aswell as daemon tools? not using daemon tools anyway so thats gonna get deleted for sure.

Yes

about the 0x4a, i assume thats a BSOD aswell? well i've had BSOD in the past that were caused by avast antivirus. So if i am getting it right,(sorry for all the questions, i am not so good with this) The error now has something to do with the 0x4a? i am not sure if i solved it.. in the past.

The 0x4A is indeed a BSOD: BSOD Index
I'm not certain if that crash has something to do with the 0x124's, because of the wide range of the crashes and the difference in the frequency of their occurance which both are months. To add, because of the wide range and the frequency difference it certainly isn't hardware, or it has to be that everytime a device was connected. Same is for incompatibility. Regarding possible drivers it would depend on the related things that uses the drivers. To explain this more, there are several drivers on a system, not only hardware drivers but also software drivers like SPTD, depending on the usage of related things (software, hardware that isn't often connected or something else) at the time of the crashes you may have a clue of what it could be.

My suggestion is to certainly remove Daemon tools and Asrock software, for Avast it may be an optionality to temporary use MSE instead.