Continued, random BSODs after previous thread

  1. Posts : 21
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free

    Continued, random BSODs after previous thread

    Hi there,

    I made a thread here a couple of weeks back when I was struggling with multiple BSODs a day. Users here were able to find a few drivers and programs that were causing these crashes and it seemingly fixed it. However, I'm still getting crashes, sometimes 2 in one day. I haven't installed any programs that were causing me crashes previously, and I've checked to see if the drivers that were causing me crashes previously had come back and they haven't. Most of the crashes happen whilst I'm playing a game but it can happen out of nowhere.

    I've attached a DM Log below. Thank you!
      My Computer

  2. Posts : 21
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
    Thread Starter

    As a follow up for more information, the crashes always seem to happen after my PC has been turned on for a while. I don't think it's overheating as I regularly dust my computer with compressed air, and I have space beneath my PSU, an intake and an exhaust fan, coupled with a Hyper 212 Evo CPU Cooler.
      My Computer

  3. Posts : 934
    Windows 10 Pro

    There are many different bugchecks in the dumpfiles.

    The cause for different error codes are usually hardware and lower level problems.

    U should begin with:

    Diagnostic Test


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note
    MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

    Make a photo of the result and post it.
      My Computer

  4. Posts : 934
    Windows 10 Pro

    U should also remove MSI Afterburner. Its known for causing bluescreens.
      My Computer

  5. Posts : 39,995
    windows 10 professional version 1607 build 14393.969 64 bit

    If the mem test results are ok then you may consider running windows driver verifier.

    Before using it you should be comfortable navigating through the windows advanced troubleshooting menu.

    In the system properties startup and recovery settings unchecking automatically restart will allow you time to read the stop codes and misbehaving driver.

    BSOD Finding and fixing them - Microsoft Community

    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    Installing third party software such as whocrashed and/or bluescreenview give immediate bsod results for the misbehaving drivers.

    Malfunctioning drivers and / or applications are then uninstalled.

    New applications are then installed.

    The computers manufacturer's web site is then viewed for the tested drivers for the computers build and operating system.
    The drivers are then reinstalled.

    There may be some drivers that produce bsod after reinstalling an application. If this happens you can continue using the application know that it has the propensity to produce bsod or choose another application.

    On one of my computers every uninstallation and reinstallation of cyberlink did not alter the windows driver verifier bsod. I was used to cyberlink so I now know that it is likely to be the cause of a bsod. VLC media player is an alternative option.

    The WIKI recommends that the windows driver verifier is repeated until there a no longer any bsod. Then windows driver verifier is kept on for 36 hours of normal use. Once that is achieved windows driver verifier is turned off and the preventative maintenance has been completed.

    To start it type verifier in the left lower corner search.
    Then click on verifier run command.
    Then check the boxes for the settings in windows driver verifier as in the link.

    When you view a bsod it will have a stopcode. Typically it is windows driver verifier detected violation. It may or may not display the misbehaving driver.

    To turn off windows driver verifier you will navigate through the windows advanced troubleshooting menu to startup options. In startup options choose number 6 safe mode with command prompt. Then type verifier /reset. Once the verifier is reset type shutdown /r to reboot.

    When back on the desktop run whocrashed and bluescreenview to analyze the minidump and memory.dmp files. Then uninstall the misbehaving driver or application associated with that driver.

    Repeat the process until there are no more bsod. Use the computer for 36 hours of normal use. If there are no more bsod then turn off windows driver verifier.
      My Computer

  6. Posts : 21
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
    Thread Starter

    The issue/one of the issues was one of my sticks of RAM. I could boot the computer with every stick (I had tried whilst troubleshooting before I made my first thread) and assumed that was fine. After running MemTest I received multiple errors and ran it with one of my newer sticks of RAM - I bought two more sticks in January and that's around when the crashes started - and that one was causing issues.

    I'll run it again tonight to see if there's any other RAM issues, but fingers crossed it's as simple as removing that one stick.
      My Computer

  7. Posts : 934
    Windows 10 Pro

    Glad to hear that your problem is now fixed. Let us know if there are any other problems.
      My Computer

  8. Posts : 21
    Microsoft Windows 10 Pro 64-bit 14393 Multiprocessor Free
    Thread Starter

    As an update just to help anyone who stumbles across this thread from Google attempting to troubleshoot, I wanted to round up everything I did to help reduce (and now hopefully fix) my BSODs.

    I'm on Windows 10 and was receiving regular BSODs upwards of 2 a day. These were completely random but many happened whilst I would be exiting a game or watching Twitch primarily. ntoskrnl.exe was the most blamed 'cause' of these crashes in the blue screen window, but the crashes were actually caused by the following drivers/programs -

    MSI Afterburner & MSI Command Center (NTIOLib_X64 & amifldrv64.sys)
    Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver (Xinput drivers)
    WmBEnum & WmXlCore from Logitech WingMan Virtual Bus Enumerator Driver - I believe this was caused by an old Logitech program used for steering wheels.
    Nvidia Display Drivers (nvlddmkm.sys) I used the Display Driver Uninstaller and then reinstalled from Nvidia only installing the Graphics Driver and PhysX Driver.

    I checked my motherboard suppliers website to make sure I had the most appropriate drivers for my motherboard - some were/are outdated, but are likely to be more stable.
    Once these were uninstalled/fixed, my crashes were significantly reduced but still happened. I had previously tried to boot my PC with each stick of RAM 1 by 1 individually to see if any of them were causing a problem, but my PC would boot. However, Memtest was able to show that one of my sticks was causing issues. After taking this out, I ran a driver test and had a full day of running a twitch stream & playing multiple games - I didn't have a single crash.

    Hopefully this helps someone who stumbles across this thread. My specs are in my little tab, but I'll add them below to hopefully help with google visibility for anyone trying to troubleshoot.

    And finally, a huge thank you to everyone who has helped me diagnose my crashes, Lifetec in particular has been incredibly helpful. Again, thank you to every single one of you. Fingers crossed I won't need to make another thread in the future!

    • Microsoft Windows 10 Pro 64
    • Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
    • MSI Z97 PC Mate(MS-7850)
    • 4x4gb HyperX Fury DDR3 @ 1866MHz
    • NVIDIA MSI GeForce GTX 970

      My Computer

  9. Posts : 934
    Windows 10 Pro

    Glad to hear that your problem is now fixed. Let us know if there are any other problems.
      My Computer


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

Windows 10 Forums