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

Page 1 of 3 123 LastLast

  1. Posts : 14
    win7 ultimate 64
       #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 Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    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
      My Computer


  3. Posts : 14
    win7 ultimate 64
    Thread Starter
       #3

    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.
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #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 Computer


  5. Posts : 14
    win7 ultimate 64
    Thread Starter
       #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 Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    hikerman said:
    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.

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

    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
    ---------
    hikerman said:
    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.
      My Computer


  7. Posts : 14
    win7 ultimate 64
    Thread Starter
       #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 Computer


  8. Posts : 15,026
    Windows 10 Home 64Bit
       #8

    Oh that , click on the !analyze -v
      My Computer


  9. Posts : 14
    win7 ultimate 64
    Thread Starter
       #9

    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
    ---------
      My Computer


  10. Posts : 15,026
    Windows 10 Home 64Bit
       #10

    hikerman said:
    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...

    hikerman said:
    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... :)
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About 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 22:07.
Find Us