Getting BSOD randomly, ntoskrnl.exe, different errors

Page 2 of 2 FirstFirst 12

  1. Posts : 10
    Windows 10
    Thread Starter
       #11

    I've reset the BIOS by removing CMOS battery then changed the Realtek driver (version was 9.x and is now 10.x), but I still got a BSOD. I'm attaching the file, but from my examination the error is memory corruption. Nothing specific. I'm now running a driver verifier to hopefully track this faster.

    File: https://www.dropbox.com/s/ipl9cz18cj...%2C03.zip?dl=0
      My Computer


  2. Posts : 10
    Windows 10
    Thread Starter
       #12

    This is the up to date file with BSODs, just got another one, another memory corruption. I'm done for today.

    https://www.dropbox.com/s/7r52gblqfj...%2C61.zip?dl=0
      My Computer


  3. Posts : 38,345
    windows 10 professional version 1607 build 14393.969 64 bit
       #13

    There were multiple bsod mini dump files indicating memory.
    One indicated a misbehaving driver: rt640x64.sys


    This appears to be a re-replacement of the misbehaving driver.
    Find all possible drivers for rt640.sys for each windows 10, 8.1 and 7.0
    Post the drivers into the thread.
    Record into the thread each step that you make in replacing this driver.


    1) Find a replacement driver Realtek
    2) Perform windows updates
    3) disable windows updates of non-Microsoft drivers:
    Enable or Disable Driver Updates in Windows Update in Windows 10 Windows 10 Windows Update Activation Tutorials
    4) Open device manager > identify Realtek RT640 NT Driver or family controller driver > right click properties > driver details > confirm rt640x64.sys > uninstall driver > replace with new driver
    5) report into the thread how the driver was displayed in device manager (name)



    Code:
    BugCheck 1E, {ffffffffc0000005, fffff8021d4e488a, 0, b8}Probably caused by : memory_corruption
    Code:
    ffffb101`997467f8  fffff80a`80cf5730Unable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for rt640x64.sys*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys rt640x64+0x5730
    Code:
    rt640x64     Realtek RT640 NT Drive Realtek RT640 NT Drive Kernel        Manual     Running    OK         TRUE        FALSE        4.096             933.888     0          27/06/2017 01:42:46    C:\WINDOWS\system32\drivers\rt640x64.sys         8.192


    rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver http://www.realtek.com.tw/downloads/...&GetDown=false


    Code:
    BugCheck 3B, {c0000005, fffff80d9a8f2885, ffffc700f1179c00, 0}*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption
      My Computer


  4. Posts : 10
    Windows 10
    Thread Starter
       #14

    Thank you, I will do it. This 'memory corruption'... is it possible that it's a RAM issue even though memtest got no errors for 10hrs+? Maybe memtest can't trigger the error that Windows can. I need to get my hands on some new RAM and try it.
      My Computer


  5. Posts : 38,345
    windows 10 professional version 1607 build 14393.969 64 bit
       #15

    Many bsod mini dump files when debugged initially implicate memory as memory is part of so many processes. In order to determine whether it is or is not RAM the Memtest86+ is useful if the testing criteria include sufficient passes to minimize the false negatives.
    There are multiple software companies that have memory testing applications. We use Memtes86+ as the tool to evaluate RAM/DIMM/MB. Testing needs to be at least 8 passes. Anything less than 8 passes is wasting time as there are too many false negatives. A false negative is a test pass with malfunctioning RAM. The amount of testing time is irrelevant. The number of passes is critical and the more the better.

    Run memtest86+ version 5.01 for at least 8 runs.
    This may take many hours so plan to run it overnight.

    http://www.memtest.org/

    When Memtest86+ has completed 8 or more runs use a camera or smart phone camera to take a picture and post images of the results into the thread.
    https://answers.microsoft.com/en-us/...f-ecc7b7ff6461
    MemTest86+ - Test RAM Windows 10 BSOD Tutorials
    Estimated testing time is 1 - 2 hours /GB RAM
    Just 1 error indicates malfunctioning RAM.
    If there is an error all RAM modules except 1 are removed and then RAM is tested 1 at a time in the same module. Each time 8 passes is used as a minimum to reduce the number of false negatives.
    If all RAM modules pass when tested 1 at a time after failing when tested together 1 RAM module is then tested in other DIMMs to evaluate them and the MB. The testing is done by the process of elimination.

    Memtest86+ version 5.01:
    Memtest86+ - Advanced Memory Diagnostic Tool
      My Computer


  6. Posts : 10
    Windows 10
    Thread Starter
       #16

    I've ran Memtest for 20hrs+ without errors. I've decided to just buy a new CPU, a Intel Pentium G4400, which was, in my mind, the only reasonable component left to replace, and It's been a week without BSODs, which has never happened before. I believe the CPU was faulty from the start, which is unfortunate, but at least now I can rely on my computer to work properly.

    Thank you, zbook, for you extensive help.
      My Computer


  7. Posts : 38,345
    windows 10 professional version 1607 build 14393.969 64 bit
       #17

    Your welcome. Glad to help.
    With 16 GB of RAM at 20+ hours how many passes were there?
      My Computer


  8. Posts : 10
    Windows 10
    Thread Starter
       #18
      My Computer


  9. Posts : 38,345
    windows 10 professional version 1607 build 14393.969 64 bit
       #19

    Nice test with 11 passes.. The 1 - 2 hours /GB RAM taking 20+ hours for 16 GB RAM was in the ball park.
    If you need any help please let us know.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 12:46.
Find Us




Windows 10 Forums