A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. - H2SO4
The generic nature of the 0x124
(Arg1=0) stop code means we would have to take
the trail & error approach.
Do you have any spear parts (or another PC) to test with, mainly a PSU?
The usual suspect of this kind of BCCode is the CPU but it's often not the the case which is why we need
to test other components to rule them out as the cause.
How old are your components?
What is the make an model of you PSU?
Fill out this form and post back the result:
Good practice, open up the case and re-seat all types of connection.
- SATA Cables (HDD/SSD/ODD).
- Motherboard 24-pin.
- Motherboard 4/8-pin (CPU).
- Re-seat the RAM.
- Re-seat the GPU.
Make sure that every slot / cable head is free of dust or other obstruction.
Make sure that every connection is seating properly and firmly in-place.
Also have a look at the motherboard and the GPU, search for any "bad caps", bulky, leaking bloated capacitors.
- Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
Reset the BIOS back to default in case you're unaware that your CPU is overclocked:
Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.
Good places to read more:
If any component is overclocked reset it back to stock speeds!