Random BSOD 000000a ntoskrnl.exe


  1. Posts : 2
    Windows 7 Pro X64
       #1

    Random BSOD 000000a ntoskrnl.exe


    Just to lay the story right. I just bought and built up this PC last Oct 2012, it does not have any problems till Jan when it starts to BSOD during WoW gameplay only.

    I went thru many rounds of troubleshooting, reformatting before I decided to see if removing one of my 2 4GB RAM helps. Luckily when i removed one of them, I have not seen a BSOD ever since (Been 1 month+) And the BSODs back then are consistently 000003B pointinfg to ntoskrnl.exe.

    I deduced i pulled out that one defective RAM although i did run memtest before.

    Then I decided to go to my local manufacturer for a one to one exchange on the faulty RAM and got one. I just installed last week and when I play WoW there was no problem.

    But this week recently I had my very first new BSOD ever since i plugged in the 2nd new replacement RAM and the error is 0X000000A instead.

    Im perplexed and it was not playing WoW, i was surfing the web randomly and streaming anime to watch when it BSOD on me twice.

    To play safe, i disabled hardware acceleration on my IE9 thereafter, and now still monitoring. Meanwhile I would appreciate if someone can take a look at my dmp files and see if I miss anything.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    From the last two crash dumps:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffff70440200f80, 0, 1, fffff80002ce61c9}
    
    Probably caused by : memory_corruption ( nt!MiUpdateWsle+2b9 )
    
    Followup: MachineOwner
    -------------------------------------------------------------------------------------------------
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffff7063fbc7d04, 0, 1, fffff80002cde1c9}
    
    Probably caused by : memory_corruption ( nt!MiUpdateWsle+2b9 )
    
    Followup: MachineOwner
    ---------
    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.


    It it comes clean, free from errors, enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  3. Posts : 2
    Windows 7 Pro X64
    Thread Starter
       #3

    Hi all,

    I have swapped both 4GB modules out and so far there has been no BSOD ever since, hence I deduced it was hardware issues. U can close this for now, thanks!
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    It's ok.
    For any further issue, post back.
      My Computer


 

  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 01:13.
Find Us