![]() |
|
30 Sep 2012 | #1 |
|
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 ![]() |
My System Specs![]() |
. |
|
30 Sep 2012 | #2 |
![]() |
Welcome to SF
WOW, 32 GB of ram is allot ![]() 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 |
My System Specs![]() |
30 Sep 2012 | #3 |
|
sorry but .... noob here. you say no need for memtest86 yet. so how exactly do you mean
Quote:
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. |
My System Specs![]() |
. |
|
30 Sep 2012 | #4 |
![]() |
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 |
My System Specs![]() |
30 Sep 2012 | #5 |
|
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 :) |
My System Specs![]() |
30 Sep 2012 | #6 |
![]() |
Code:
MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption MEMORY_CORRUPTOR: LARGE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE Followup: memory_corruption --------- See you next. |
My System Specs![]() |
30 Sep 2012 | #7 |
|
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. |
My System Specs![]() |
30 Sep 2012 | #8 |
![]() |
Oh that
![]() |
My System Specs![]() |
30 Sep 2012 | #9 |
|
i must be doing something wrong
![]() Quote:
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 --------- |
My System Specs![]() |
30 Sep 2012 | #10 |
![]() |
i must be doing something wrong
![]() Quote:
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 --------- 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. Take your time and keep us posted... :) |
My System Specs![]() |
![]() |
Thread Tools | |
Similar help and support threads | ||||
Thread | Forum | |||
BSOD random, error 0x00000124, caused by address ntoskrnl.exe+4adb3c Hi, This problem started in Flight Simulator, but now its random. I have run memtest twice for four hours each, all is fine. I have a Western Digital HD, and ran their diagnostic tool for it from their site. I have reset the RAM after cleaning it also. I dust out the machine regularly. I... |
BSOD Help and Support | |||
BSOD on wake-up error 0x00000124, driver hal.dll, address ntoskrnl.exe Generous experts, I am getting somewhat random, though more often on "wake-up" BSOD. It seems that it may be related to the cpu, as the event view states: A fatal hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Cache... |
BSOD Help and Support | |||
BSOD when playing games, error 0x00000124, ntoskrnl.exe+14dca0 So been having recurring Bluescreens for a long time. They went away after I reduced the overclock as they were usually hal.dll errors but now I am getting ntoskrnl.exe errors. Any help? |
BSOD Help and Support | |||
BSOD playing Bad Company 2, error code 0x00000124 Hey guys. So recently I've been experiencing a BSOD with the above error code, but only in Bad Company 2. I've tried a multitude of fixes, including changing clock speeds/voltages etc, but no dice. Hopefully you guys can help out..? My rig is: Phenom II 955 @ 3.8GHz Crossfire AMD 6850's |
BSOD Help and Support | |||
BSOD random error 0x00000124, hal.dll at address ntoskrnl.exe+7cc40 I keep getting a random BSOD, I get it a lot in Lightroom 3 but have gotten the same error doing nothing. *** STOP: 0x00000124 (0x0000000000000000, 0xfffffa80053d5028, 0x00000000b2000040, 0x0000000000000800) *** hal.dll - Address 0xfffff80002c15a3b base at 0xfffff80002c03000 DateStamp ... |
BSOD Help and Support |
Our Sites |
Site Links |
About Us |
Find Us |
Windows 7 Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd All times are GMT -5. The time now is 09:56. |
![]() ![]() ![]() |