BSOD playing any game after installing new RAM, error 0x0000124

[stevenromero02]

After changing out from 3x 2GB Kingston RAM to 6x 4GB G.Skill RipJawsX RAM (I have a triple channel motherboard), I have started getting the hardware BSOD 0x0000124 while playing games. It seems to only trigger under game usage, as I have left the computer on for awhile and it does not seem to crash otherwise.

As far as BIOS settings go, I put it back to defaults, as well as attempting to specify RAM timings, and making sure overclock was off. I also updated the BIOS version, and tried, although in vain, to update some of the older drivers that some software was stating that I needed to update. I also ran Memtest overnight, and had no errors.

Last night I decided to remove 3 of the sticks to see if the issue would go away, and I was able to play games half the night without error, which seemed like a "fix", given that the error would generally come up within 15 minutes of gameplay. I am not sure if the problem is related to voltage or something else - what should I check?

FYI - The specific G.Skill RAM model I purchased is: F3-12800CL9D-8GBBXL. I bought 3 of them, since they were dual kits.

 

[Arc]

Hi stevenromero02.

As you are narrowing the situation down, let us start with the place you are pointing at.
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

But, Overclocking is still present there? It appears so from the crash dumps.

CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2818

You should not let the hardware parts overclocked in a BSODing computer.
_________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 124[/COLOR], {[COLOR=Red]0[/COLOR], fffffa8012ac9028, fa000000, 400405}

Probably caused by : GenuineIntel

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