BSOD playing serveral games, error 0x0000124

I have a Custom builded PC, I builded it myself and actually had this problem before. I am getting this BSOD 0x0000124 and caused by ntoskrnl.exe. My build should be able to see at my profile and I have tried alot of stuff but I would be very happy and very thankful if you could help me fix this, because Idk what to do anymore.

If you want more info, just ask thanks for trying to help.

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800db606c8, 0, 0}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

0x124's are typically related to a hardware issue and can only be isolated by stress testing the major components.

If overclocking, reset all overclocks back to their default settings and then follow these:

RAM - run for a minimum of 8 consecutive passes
RAM - Test with Memtest86+

CPU - run the HIGH test
CPU - Stress Test Using IntelBurnTest

Video - run the FURMARK test for 20mins
Graphics Card Problems - Diagnose
Video Card - Stress Test with Furmark

Storage - run the SHORT test using the DOS version
SeaTools for DOS and Windows - How to Use

D4YN3X said:

Well I did the all test and I passed them, well could it be my PSU?

Its not possible to run 8 passes of MemTest86+ on 16GB of RAM in 2hrs. Don't take shortcuts. Read the instructions again.