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

[hikerman]

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

 

[koolkat77]

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:
→ http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[hikerman]

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

I would suggest you to manually test each stick on different slots of your computer to identify the bad one.

\

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.

 

[koolkat77]

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

 

[hikerman]

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

 

[koolkat77]

Does it matter which slot I place the stick in? 4 slots on mobo.

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

what part of crash dump was it that lead you to believe that memory is the problem and not something else?

This part:

MODULE_NAME:[COLOR="red"] memory_corruption[/COLOR]

IMAGE_NAME: [COLOR="red"] memory_corruption[/COLOR]

FOLLOWUP_NAME: [COLOR="red"] memory_corruption[/COLOR]

[COLOR="red"]MEMORY_CORRUPTOR:  LARGE[/COLOR]

FAILURE_BUCKET_ID: [COLOR="Red"] X64_MEMORY_CORRUPTION_LARGE[/COLOR]

BUCKET_ID:  [COLOR="Red"]X64_MEMORY_CORRUPTION_LARGE[/COLOR]

Followup: memory_corruption
---------

just trying to learn as I go mate

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

See you next.

 

[hikerman]

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.

 

[koolkat77]

Oh that :banghead:, click on the !analyze -v

 

[hikerman]

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

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff80004208000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`009bbb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x7f140


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

BUCKET_ID: WRONG_SYMBOLS

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

 

[koolkat77]

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

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff80004208000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`009bbb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x7f140


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

BUCKET_ID: WRONG_SYMBOLS

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

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

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.

IYes that could be the problem.

Take your time and keep us posted...

 

[hikerman]

I'm lost ., sorry, I looked at all 5 dumps and see the same thing I posted in all of them .... SIGH, it sucks to a noob

;you any idea what the hay I'm doing wrong. using windbg 64. I keep seeing symbol not right stuff, I told windbg where the symbols folder is.

now I really have to get some shut eye. thanks for your time koolkat77

 

[koolkat77]

I'm lost ., sorry, I looked at all 5 dumps and see the same thing I posted in all of them .... SIGH, it sucks to a noob

;you any idea what the hay I'm doing wrong. using windbg 64. I keep seeing symbol not right stuff, I told windbg where the symbols folder is.

now I really have to get some shut eye. thanks for your time koolkat77

Haha, you need to close your eyes now so . We'll fix your symbols next time.
See you soon.

 

[hikerman]

not done trying each individual stick yet but wanted to let you know, I am on stick 3 of 4, the pc runs fine till I play the game. and I have noted the time. playing game right about 20 minutes into it is when the BSOD happens each time. be it will all 4 sticks in and with stick 1 and stick 3 (I numbered them by the slot they were in. now to test stick 2 and stick 4. btw this has been in slot one on mobo or the right most slot in other words.

EDIT: well I have run all individual sticks in slot one. they all work fine for browsing but all 4 sticks crashed after about 20 to 25 minutes in online game, bc2.

what should I do next ? as basically its taken roughly 2 hours to check all 4 sticks in the first slot.

since I thought of it last night i have to wonder if its not simply related to voltage. and being a noob didn't want to go mucking about with such stuff I don't understand.

and what about the "symbols" folder, does it perhaps have to be on the same drive? os drive is C, symbols folder in at E:\symbols

thanks again

 

[koolkat77]

what about the "symbols" folder, does it perhaps have to be on the same drive? os drive is C, symbols folder in at E:\symbols

I keep it in C drive so its less complicated for me.

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter Snipping tool in the Start button > Search box, hit
enter. Select the area you want to post and save to a convenient place.
→ How to Post a Screenshot in Seven Forums

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller
voltages are.

 

[hikerman]

here you go. I will be right back with the bios info

I looked at timings in bios all looked ok, mem at rated speed as well.

brb

EDIT: well I'm not sure where exactly to find "voltages:" u specify, I seen LOTS of voltage . confused

EDIT 2: is the memory look like the only problem in bsods as you read them? or are there other problems as well?

 

[hikerman]

copy these from "speccy" Voltage
CPU TERMINATION 1.056 V
VCC3 3.324 V
+12V 2.448 V
+VCC 3.340 V
vAXG 0.996 V
CPU CORE 0.936 V
DRAM 1.680 V
+3.3V 3.384 V

is this what you need?

 

[koolkat77]

Thanks

I've called a friend to look at those while he does, can you uninstall the following program and play your games.

Start Menu\Programs\GIGABYTE\ET6	Public:Start Menu\Programs\GIGABYTE\ET6	Public

Let me know if it BSODs again

 

[hikerman]

roger that it has been uninstalled with revo uninstaller, it removes all the chaf left behind by any program. I will try the game again shortly.

btw I took the liberty to take screenshots in bios and have uploaded them here --> http://imgur.com/a/tqZjg#4

I hope that will give you any voltage info you may need

 

[koolkat77]

roger that it has been uninstalled with revo uninstaller, it removes all the chaf left behind by any program. I will try the game again shortly.

 

[hikerman]

I edited last post, made this so you would know, with images in bios