Random BSOD's [ntkrnlmp, ntoskrnl, rt640x64] + PC Freezes while Gaming

Page 1 of 3 123 LastLast

  1. Posts : 19
    Windows 10

    Random BSOD's [ntkrnlmp, ntoskrnl, rt640x64] + PC Freezes while Gaming

    Hello all!

    I have previously posted in this specific forum due to random BSOD's which had mostly taken the error of
    but it has been quite a while since that post [I'll link it here] and I have lacked the time. Nevertheless, since lowering the RAM frequency, I have been getting blue screens regardless and so I assume that it took no adverse effect to the problem.

    I'd like to also point out that rt640x64.sys was a particular cause into the
    error and so I manually found and downloaded the relevant driver for Realtek 8136/8168/8169 PCI/PCIe Adapters" as mentioned on WhoCrashed. Although, this did not resolve the issue.

    To add on to the problem of these blue screens, I have also witnessed many accounts of a whole PC freeze if not a blue screen while playing games such as Rocket League and more recently Killing Floor 2. These spikes have taken various amount of time and can either semi-freeze my PC (I can still communicate through Discord) or a complete halt on the system (reset required). I've also noticed my GPU load at 100% at these times and RAM usage is also at a constant ~4GB out of the total 8GB (all the time & at idle) which I'm curious about.

    Quite a bunch of information here, but any help whatsoever is much appreciated!
    Last edited by retr0; 05 Dec 2016 at 11:55.
      My Computer

  2. Ztruker's Avatar
    Posts : 13,740
    Windows 10 Pro X64 21H1 19043.1266

    Latest dump has:
    BugCheck 12B, {ffffffffc00002c4, 43b, 18287300, ffffad00f3853000}
    Probably caused by : memory_corruption
    This bugcheck indicates that a single bit error was found in this page.  This is a hardware memory error.
    Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
    Arg2: 000000000000043b, physical page number
    Arg3: 0000000018287300, zero
    Arg4: ffffad00f3853000, zero
    Time to test your RAM with memtest86+ (note the +). You have 8GB so 10 to 12 hours will be needed to let it run a minimum of 8 full passes. Any error indicates bad ram and you can stop the test and replace it.

    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
      My Computers

  3. Posts : 19
    Windows 10
    Thread Starter

    Hello, thanks for the advise and analysis!

    I have been able to run MemTest86+ for a whopping 20 hours and fortunately, I have accumulated 10 total passes an no errors! (see attached picture)
    So I assume the problem lies within the software side of things...?


    Attachment 112528
      My Computer

  4. Ztruker's Avatar
    Posts : 13,740
    Windows 10 Pro X64 21H1 19043.1266

    Yes, probably a drivr issue. Let's give Driver Verifier a try:

    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to
    and make sure the correct boxes are checked.

    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
      My Computers

  5. Posts : 19
    Windows 10
    Thread Starter

    Hello again!

    It's been a while since I've updated on what's going on but I've been running Driver Verifier since you posted, so a couple odd days. However, judging by the advice on how long you should be running it for (48 hours), I decided to turn it off today as I didn't have any BSOD's while it was on in the background.
    Unfortunately, while I left the PC for a while, I return to find it had Blue Screened , back with the same causes ntoskrnl.exe and ntkrnlmp.exe​. Would this mean I should re-enable DV again?

    I've attached the dump.

      My Computer

  6. Ztruker's Avatar
    Posts : 13,740
    Windows 10 Pro X64 21H1 19043.1266

    No, DV is only used to try to cause device driver failures by making them work harder. You should not run with it enabled normally. It slows things down for sure.

    I see some pretty old drivers on your system. For example:
    2008/07/26 14:29:37   \??\C:\Program Files (x86)\NZXT\CAM\CAM_V3.sys
    2011/07/12 22:00:01   \??\C:\Program Files\SUPERAntiSpyware\SASKUTIL64
    2011/07/22 00:03:00   \??\C:\Program Files\SUPERAntiSpyware\SASDIFSV64
    2012/12/04 09:49:28   C:\WINDOWS\system32\drivers\amdide64.sys
    2012/12/11 21:21:44   C:\WINDOWS\system32\drivers\amdsbs.sys
    2013/01/15 06:25:51   \??\C:\WINDOWS\SysWOW64\Drivers\AsrDrv101.sys
    They may be perfectly fine but appear to be left over from a previous install. Did you upgrade from Windows 7 or 8 to 10?
    If so, this might be a good time to backup your system then do a Clean Install of the latest available Windows 10 which is 14393. Apply all updates and it will make is 14393.479.

    Restore your data and see how it runs.
      My Computers

  7. Posts : 19
    Windows 10
    Thread Starter


    This was a clean OS install, via the USB-image install method. I am currently running build 14393.576 (recently updated) and while I haven't had any BSODs, I have been getting frequent lock ups when the GPU is on max load (ie. via gaming). I've also suffered general video driver crashes (due to Radeon WattMan? even though it's off) so I'm not sure if that has a correlation to this.

    However, I'll try and do a clean install as soon as and investigate whether the blue screens persist!
      My Computer

  8. Ztruker's Avatar
    Posts : 13,740
    Windows 10 Pro X64 21H1 19043.1266

    Ok, thanks for the update.
      My Computers

  9. Posts : 19
    Windows 10
    Thread Starter

    I've completely reinstalled the OS and all was going well. However, I've unfortunately received a blue screen today bearing the name
    and 2-3 lock ups. I've attached the dump, thanks!
      My Computer

  10. Ztruker's Avatar
    Posts : 13,740
    Windows 10 Pro X64 21H1 19043.1266

    Dump shows a problem with aswSnx.sys.
    BugCheck 1E, {ffffffffc0000005, fffff8025cb29815, 1, 863}
    *** WARNING: Unable to verify timestamp for aswSnx.sys
    *** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    This belongs to Avast anti-virus. Try uninstalling it and running with the built-in Windows Defender. This is what I use.
      My Computers


  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 16:34.
Find Us

Windows 10 Forums