BSOD playing Rust, error code 0x0000000a

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 7 home premium 64 bit
       #1

    BSOD playing Rust, error code 0x0000000a


    I'm 90% sure it's not the ram because with just an A the end (coming from microsoft) it's ussually a software issue.



    Also some things i noticed were that firefox would randomly crash like last time my ram went bad.


    blue screen view results






    Hardware configuration:
    8gb vengeance 1600 8gb vengeance 1866
    msi 970a-g46 mobo
    750w seasonic mII 12 psu
    120gb pny xlr8 ssd
    some random mechanical drives.
    amd fx 8320 stock clocks
    gtx 770 stock clocks (recently installed. Had it for like a week now?)
    fresh beta drivers for the 770.


    Input devices:
    Blue snowball
    CM Storm Recon Mouse
    Corsair K70
    Headphones
    1080p monitor


    First time receiving this bsod (happened during rust not a very graphically intense game)


    Download for crash dump file:
    this was my dump on media fire but i'll upload the SF_DD_MM folder as a zip.


    If you need more info to help me post bellow and ill answer it.




    I've already run memtest 86 for a couple passes on each stick individually. I'll run it later with every stick in at the same time. I've taken out the 1866 I have for now though.




    While I was playing rust I was playing on the "Good" graphics setting and I was in the middle of talking when it cut out.


    Here's the advanced debug:
    * * - Pastebin.com
      My Computer


  2. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #2

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {38, 2, 0, fffff80002aaac27}
    
    Probably caused by : memory_corruption ( nt!MiResolveMappedFileFault+97 )
    
    Followup: MachineOwner
    ---------
    You need to test your RAM DIMM's/motherboard RAM slots for errors.

    Run a minimum of 8 consecutive passes, preferably overnight, or until errors occur using MemTest86+.

    Use this tutorial to help you use MemTest86+:
    RAM - Test with Memtest86+
      My Computer


  3. Posts : 6
    Windows 7 home premium 64 bit
    Thread Starter
       #3

    It's got to be the mother board. Thanks for the reply. Time to upgrade.

    Reason why I think this: I tested all of the ram dimms in one slot of the mobo for a few passes a couple times and none of them showed any error.
      My Computer


  4. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #4

    A few passes is not sufficient....you require a minimum of 8 passes to adequately test the RAM DiMM fully.

    I recommend running MemTest86+ overnight just to be sure.
      My Computer


  5. Posts : 6
    Windows 7 home premium 64 bit
    Thread Starter
       #5

    Golden said:
    A few passes is not sufficient....you require a minimum of 8 passes to adequately test the RAM DiMM fully.

    I recommend running MemTest86+ overnight just to be sure.
    3 passes on each individual stick isn't sufficient? Alright I guess I'll just run it with every stick over night then.
      My Computer


  6. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #6

    No, its not.

    Start with all RAM DiMM's inserted as normal, then run MemTest86+. Its only necessary to test individual DiMM's if there are errors in the previous test.
      My Computer


  7. Posts : 6
    Windows 7 home premium 64 bit
    Thread Starter
       #7

    I'll report back with findings in the morning.
      My Computer


  8. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #8

      My Computer


  9. Posts : 6
    Windows 7 home premium 64 bit
    Thread Starter
       #9

    ran it for 9 hours. It only did 2 passes. It did get errors though. on pass 1 and pass 2 it got errors on test 8 but that's the only test it got errors on. It totaled in about ~150 errors. I can't remember the exact #. I did run each stick for 2 passes and they didn't show any error. So what does this mean? Should i test each stick more or?
      My Computer


  10. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #10

    The fact that there are errors means that:
    • one or more RAM DiMM's are faulty; or

    • one or more motherboard RAM slots are faulty; or

    • both RAM Dimm's and motherboard slots are faulty


    To check, you need to do this:

    1. Take 1 RAM DiMM only and install it into motherboard RAM slot #1
    2. Run MemTest86+ for a minimum of 8 passes
    3. If it passes all tests, then it means that RAM DiMM and motherboard slot are good.
    - Now insert that same RAM DiMM into motherboard slot #2, and run MemTest86+ again for a minimum of 8 passes
    4. If the test in step 3 fails, then that RAM DiMM is faulty and can be discarded
    5. Repeat the same tests for RAM DiMM #2
      My Computer


 
Page 1 of 2 12 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 08:46.
Find Us