playing call of duty ghost and looking torch

Welcome to SF :) .

All of the bug checks are 0x124 with varying L1 Cache errors, that spells a faulty CPU.

Code:

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

Error         : DCACHEL1_DRD_ERR (Proc 5 Bank 0)
  Status      : 0xb65da000d2000135
  Address     : 0x000000015f6652c0
  Misc.       : 0x0000000000000000
Error Type    : Cache error
Operation     : Data Read
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007bd7138
Section       @ fffffa8007bd72c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_EVICT_ERR (Proc 5 Bank 0)
  Status      : 0xb6004000dc000175
  Address     : 0x0000000000000d80
  Misc.       : 0x0000000000000000
Error Type    : Cache error
Operation     : Generic
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007bfe138
Section       @ fffffa8007bfe2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_DRD_ERR (Proc 4 Bank 0)
  Status      : 0xb671200000000135
  Address     : 0x00000001459801f0
  Misc.       : 0x0000000000000000
Error Type    : Cache error
Operation     : Data Read
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007bdf138
Section       @ fffffa8007bdf2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_DRD_ERR (Proc 5 Bank 0)
  Status      : 0xb600200041000135
  Address     : 0x00000001aff7d480
  Misc.       : 0x0000000000000000
Error Type    : Cache error
Operation     : Data Read
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007c2a148
Section       @ fffffa8007c2a2d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_DWR_ERR (Proc 4 Bank 0)
  Status      : 0xf606a000de000145
  Address     : 0x0000000003eddb00
  Misc.       : 0x0000000000000000
Error Type    : Cache error
Operation     : Data Write
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007b67138
Section       @ fffffa8007b672c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_DRD_ERR (Proc 4 Bank 0)
  Status      : 0xb66e40005d000135
  Address     : 0x000000012768e480
  Misc.       : 0x0000000000000000
Error Type    : Cache error
Operation     : Data Read
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007bab138
Section       @ fffffa8007bab2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_DRD_ERR (Proc 4 Bank 0)
  Status      : 0xb66cc000b5000135
  Address     : 0x00000000030aaa00
  Misc.       : 0x0000000000000000
Error Type    : Cache error
Operation     : Data Read

This type of bugcheck is 99% of the time a hardware issue,
but your OS "release" is a bit peculiar where did you get it?
Please follow this tutorial and post it in your next post.

• Windows Genuine and Activation Issue Posting Instructions

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 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, model and age of your PSU?
Fill out this form and post back the result:

• Power Supply Calculator

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 HWinfo and post a Screenshot of the sensors window, one at idle and another while putting load on the PC using Prime95 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).
  
  

Testing the RAM:

koolkat77 said:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• Pay close attention to part 3 of the tutorial "If you have errors"
• Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.

Reset the BIOS back to default:

• CLR CMOS

   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:

• Stop 0x124 - what it means and what to try
• Stop 0x124 Troubleshooting - 'New Method'

What about the rest of the asked for information?

You didn't :) .
Just to clarify, you installed the CPU from the system posted on this thread in a different machine
then stressed tested it and got the same error?

You're welcome and I'm sorry to hear that :\.
It's hard to say, so I won't try to estimate.

If you feel the thread is resolved, please mark the thread as such by clicking the green Mark as Solved
as the bottom of the page :) .