Random BSOD caused ntoskrnl.exe driver


  1. Posts : 3
    Windows 7 Ultimate x64
       #1

    Random BSOD caused ntoskrnl.exe driver


    For a couple of months i got this BSOD happening randomly,it can sometimes all be fine for a week but it happen again.Most of the time i watch some video or movie on internet,just surfing(random).Maybe it has some connection with this issue that i have,which i mention in this forum thread:
    https://www.sevenforums.com/hardware-...sometimes.html
    Short story,glitch pixels that looks like this as BSOD it happens sometimes.

    Here is a txt file with recent dumps recorded with bluescreenviewer.
    Any ideas,thank you.
    Last edited by Zedara; 23 Jun 2015 at 14:42.
      My Computer


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


  3. Posts : 3
    Windows 7 Ultimate x64
    Thread Starter
       #3

    oh sorry,i edited post. Thanks
      My Computer


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

    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff800030519b1, fffff880009a9898, fffff880009a90f0}
    
    Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )
    
    Followup: MachineOwner
    ---------
    Code:
    BugCheck A, {fffffa7fffffffd0, 2, 1, fffff800030cfe7c}
    
    Probably caused by : memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+54c )
    
    Followup: MachineOwner
    ---------
    Test your RAM modules for possible errors. Run memtest86+ for at least 8 consecutive passes.

    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    Take a camera snap of the memtest86+ screen before closing teh program and upload the image for us.
      My Computer


  5. Posts : 3
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Okay so i left it for a whole night(10 hours) and when i woke up i saw no errors but only 4 passes,and it said that test is done and press esc to exit forget to picture that.When i restarted test started again but right as it started bunch some errors popped.

    I took a picture and ESC.
      My Computer


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

    So memory corruption is detected.

    Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

    Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

    How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
    How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
    No code has to be inserted here.
    It is a RAM, a bad RAM.

    But if you have got a result like that:
    No code has to be inserted here.
    It is a motherboard issue. The particular slot is bad.

    If it is a bad RAM, you need to change the RAM. Take the other existing (good) RAM to the shop and get one of the exactly same specification. The best is, get a totally new RAM KIT.

    If it is a bad slot, it is a motherboard issue. But changing the motherboard needs a preparation for most of us; so dont populate that slot for the time being.
      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:35.
Find Us