Windows 7: BSOD playing Bad Company. Error 0x00000124. Address ntoskrnl.exe+7f140

hello, Did my first build. Moved over the ssd and hdd's to new build. all seemed well and good, as I install all drivers from gigabyte disk. pc seem to run fine until I play an online game I like, battlefield bad company 2 ( played it a TON on old rig and never ever had a BSOD) . no after about 5 to 15 minutes of play its happened every single time I try to play.

not sure what all more info you need , but I will provide any info I can. just ask

I run win7 ultimate and ubuntu (WUBI install). I made a backup with acronis true image 2013 w/ plus pack, via a boot cd with plus pack. placed that backup onto a brand new ssd (I bought a second ocz vertex 3 thinking of doing a raid 0 setup but decide against it do to loss of TRIM) and it was odd as one os either ubuntu or win7 would boot and work with networking but not both. the two ssd's are the same so i simply unplug the new one and plugged in the old one into the new build. and every thing (both os with networking) work fine. UNTILL I try to play bc2.

I have added a second gtx680 in SLI , using the 3 way SLI connnector as the spacing of the x16 slots on the mobo.

I greatly appreciate your help with this issue, not sure if I can replace the ntoskrnl.exe or whatever else it may be.

I have read the guide to posting here and believe I have followed it. if I did something wrong , please bear with me and I will do it properly .

again, I greatly appreciate your helping me correct my issues.

thanks and good day

Welcome to SF

WOW, 32 GB of ram is allot what are you going to do with all that?
Anyway, your dumps point toward defective/corrupted memory.

No need to test with memtest86+ right away, I would suggest you to manually
test each stick on different slots of your computer to identify the bad one.

For more information on your bug check go through the guide below:
→ Stop 0x124 - what it means and what to try

sorry but .... noob here. you say no need for memtest86 yet. so how exactly do you mean \

is that to say take all but one stick out and see if pc will boot? then take it out and go to next stick? so on and so forth? and if it boots and runs with one stick, that all sticks are good? and if so perhaps the mobo slot is bad?

could this be to lack of knowledge of bios and settings for memory? as I have none.

Running memtest for 8 passes on different slots with all those ram sticks will take lot of time.
So before running memtest you need to see how your computer performs on each stick.

And yes it could also be the mobo slot is bad.

Keep us posted

ok I will do that when I get up then :) . does it matter which slot I place the stick in? 4 slots on mobo.

and what part of crash dump was it that lead you to believe that memory is the problem and not something else? just trying to learn as I go mate :)

Yes, it will tell us if the mobo slot is bad.

This part:

Nice to know you're trying to learn. Unlike some who yell at us for trying to help them.

See you next.

thanks but as to learn , I meant what part as in tell me where I find this info not literally what info was.

I have downloaded "symbols" from MS page. bluescreenview and windbg x64. but lost as to how to find for instance the info u just posted about corruption in memory.

hate to be a pain or a bother but I would like to understand and perhaps better deal with such problems in the future on my own. thanks again :)

looked at more detail of mobo and memory , I see the mobo voltage , I suppose the word is default or stock for memory is 1.5V and the g.skill trident x default is 1.65V. would my problem be due to this difference?

and would a manual settings in bios possibly correct this issue I have?

this is all quite interesting to me, as this is my first build I have done.

this is the memory F3-2400C10D-16GTX. ddr3-2400 pc3-19200 . 8192MB x2. CL 10-12-12-31. 1.65V. i have two kits of this installed. and cpuz and speccy say deffo different numbers for memory.

and the mobo gigabyte G1.Sniper 3

I will report back tomorrow after try boot/run pc with only one stick (in turn) installed.

Oh that , click on the !analyze -v

i must be doing something wrong I clik that this is what I see :

That's your first dump, check the others and you'll find them there...

IYes that could be the problem.

Take your time and keep us posted... :)