Getting BSOD 0x124 error

[Damianos]

Recently in the past few months (once in a month or two) I've been getting random BSOD's with the same code which is 0x124.

 

When I first got it, I did a bit of research, and it seems to be caused by heating issue as it seems to be from me OC-ing my CPU, which is what I recently did with my i5 2500K (OC-ed it to 4.5 GHz on air cooling with CM Hyper 212+), and so I listened to the suggestions and lowered (or increased , can't remember exactly) VCore and reduced the clock speeds and I thought my problem was gone.

 

A month or two later the same problem appeared out of nowhere, and that time I decided to clean my PC from all the dust and debris which gathered inside while resetting my CPU clock and VCore back to normal. A day or two after that no BSOD's appeared, so then I decided to OC my CPU again back to 4.5 GHz and stress test it to see if the problem will appear again. After doing all of that, no problem was appearing and the stress test was successful so I thought I was ok and that everything was normal.

 

Fast forward a month (and a half maybe?) today and the problem appeared for the third time out of nowhere, and I honestly have no idea what is causing this, so I came for help here if you folk would have any suggestions on what might cause this issue.

 

I'd like to mention that the first time the problem appeared, nothing was running in the background of my PC and I was only playing Witcher 3, a game which I'm pretty sure is more GPU intensive than CPU.

 

The second time it appeared, again nothing was running in the background and I was only watching a youtube video.

 

The third time that it appeared today, was out of my sight because I left my Origin to download my Battlefield 3 and when I came back from my friend, I saw my screen stuck on BSOD.

 

If anyone might know what causes this issue, please help.
If you guys wish any more information just ask, 
also here is current statistic of my PC printed from CPUID HWMonitor:

 

I'm sorry for the long post, but I thought that I should be as detailed as possible.

 

Thanks.

[Ryujin2003]

You'll have to provide your dump reports.

[Jumper118]

Needs more vcore. 

[Evolution90]

Seems a bad chip.. for a 2500k, you are already pushing 1.4v through it at 4.5ghz ... wow.

[Damianos]

Ok, but how do you open the dump files ?

[Damianos]

2 minutes ago, Evolution90 said:

Seems a bad chip.. for a 2500k, you are already pushing 1.4v through it at 4.5ghz ... wow.

If you mean that VID, that's not the CPU's VCore, the top one printing out 1.296 is my VCore.

[Evolution90]

Just now, Damianos said:

If you mean that VID, that's not the CPU's VCore, the top one printing out 1.296 is my VCore.

Oh in that case try 1.33v

[Jumper118]

Just now, Damianos said:

If you mean that VID, that's not the CPU's VCore, the top one printing out 1.296 is my VCore.

What's it set to in the bios? 

[Damianos]

1 minute ago, Jumper118 said:

What's it set to in the bios? 

1.3 I believe.

[Jumper118]

1 minute ago, Damianos said:

1.3 I believe.

It needs more then. 124 is more vcore on sandy

[Damianos]

These are the only things I could get from my dump file right now (using WhoCrashed)

 

Crash dump file:        C:\Windows\memory.dmp
Date/time:              8/9/2017 11:31:57 AM GMT
Uptime:                 01:35:11
Machine:                HOME-PC
Bug check name:         WHEA_UNCORRECTABLE_ERROR
Bug check code:         0x124
Bug check parm 1:       0x0
Bug check parm 2:       0xFFFFFA800758C028
Bug check parm 3:       0xBE200000
Bug check parm 4:       0x5110A
Probably caused by:     Unknown
Driver description:     
Driver product:         
Driver company:         
OS build:               Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
Architecture:           x64 (64 bit)
CPU count:              4
Page size:              4096