Welcome to SF
.
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.
Your bugchecks are consistently faulting on the L2 Cache on banks 5 & 7,
which leads me to believe that it is faulty but we will have to test the hardware to know for sure.
Code:
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800d2cb138
Section @ fffffa800d2cb2c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : GCACHEL2_ERR_ERR (Proc 6 Bank 5)
Status : 0xbe0000000100110a
Address : 0x000000022a086740
Misc. : 0x000000d086000086
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800d411138
Section @ fffffa800d4112c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : GCACHEL2_ERR_ERR (Proc 3 Bank 5)
Status : 0xbe0000000100110a
Address : 0x000000035d6656c0
Misc. : 0x0000025082000086
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800d42b138
Section @ fffffa800d42b2c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : GCACHEL2_ERR_ERR (Proc 7 Bank 7)
Status : 0xbe0000000100110a
Address : 0x0000000403d18a40
Misc. : 0x0000001086000086
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800d226138
Section @ fffffa800d2262c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : GCACHEL2_ERR_ERR (Proc 1 Bank 5)
Status : 0xbe0000000100110a
Address : 0x000000030b10b3c0
Misc. : 0x0000005086000086
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800d432138
Section @ fffffa800d4322c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : GCACHEL2_ERR_ERR (Proc 4 Bank 7)
Status : 0xbe0000000100110a
Address : 0x00000001df96fb80
Misc. : 0x0000009086000086
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800d1d6138
Section @ fffffa800d1d62c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : GCACHEL2_ERR_ERR (Proc 1 Bank 7)
Status : 0xbe0000000100110a
Address : 0x000000009aefbec0
Misc. : 0x0000009086000086
Do you have any spare parts (or another PC) to test with?
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).
- SATA-Power.
- 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.
i.e
Test for thermals and stability:
- Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 (test using the blend test first) for the CPU side and Furmark for the GPU.
- Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).
Reset the BIOS back to default:
Note
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.
Note
If any component is overclocked reset it back to stock speeds!
Good places to read more:
Keep us posted
.
