Windows 10: Continued, random BSODs after previous thread

Discus and support Continued, random BSODs after previous thread in Windows 10 BSOD Crashes and Debugging to solve the problem; 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... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Veilyn, May 1, 2017.

  1. Veilyn Win User

    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!

    :)
     
    Veilyn, May 1, 2017
    #1

  2. Lots of BSOD's

    PS: after my previous/last replie i had 3 more BSOD's:

    seems like there are a lot of random once...

    MEMORY_MANAGEMENT win32kbase.sys

    MEMORY_MANAGEMENT ntoskrnl.exe

    ntoskrnl.exe
     
    florian de graef, May 1, 2017
    #2
  3. DPC_WATCHDOG_VIOLATION

    I have tried the driver verification method and it continuously in loop and got even worse and the bsod didn't even let it to verify it. somehow I got the restore to previous stage and bsod continued to for two days and now I don't even see a bsod after
    I cleaned my pc with AVG.
     
    invinciblenag, May 1, 2017
    #3
  4. Veilyn Win User

    Continued, random BSODs after previous thread

    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.
     
    Veilyn, May 2, 2017
    #4
  5. 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:




    Continued, random BSODs after previous thread [​IMG]
    Diagnostic Test
    Continued, random BSODs after previous thread [​IMG]
    RAM TEST

    Continued, random BSODs after previous thread [​IMG]
    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums


    Continued, random BSODs after previous thread [​IMG]



    Continued, random BSODs after previous thread [​IMG]
    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.
     
    BSODHunter, May 2, 2017
    #5
  6. U should also remove MSI Afterburner. Its known for causing bluescreens.
     
    BSODHunter, May 2, 2017
    #6
  7. zbook New Member
    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.
     
    zbook, May 2, 2017
    #7
  8. Veilyn Win User

    Continued, random BSODs after previous thread

    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.
     
    Veilyn, May 3, 2017
    #8
  9. Glad to hear that your problem is now fixed. Let us know if there are any other problems.
     
    BSODHunter, May 4, 2017
    #9
  10. Veilyn Win User
    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)
    • Malwarebytes
    • 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
     
    Veilyn, May 4, 2017
    #10
  11. Glad to hear that your problem is now fixed. Let us know if there are any other problems.
     
    BSODHunter, Apr 5, 2018
    #11
Thema:

Continued, random BSODs after previous thread

Loading...
  1. Continued, random BSODs after previous thread - Similar Threads - Continued random BSODs

  2. 0x8007042B-0x2000D - Continuation Thread

    in Windows 10 Installation and Upgrade
    0x8007042B-0x2000D - Continuation Thread: @rcairflyer Im having EXACTLY the same issue as you. Even down to the 28% Complete, then the dreaded restart to black screen and "Undoing changes". Im going to image my drive, safely stash it on an external overnight tonight, then strip down my AppData and User directories,...
  3. Previous question thread not working

    in Microsoft Windows 10 Store
    Previous question thread not working: Hi, Andrew Mott98, Igor Leyko, DaveM121. Sorry The previous question thread won't let me reply anymore, it just keeps saying Oops! Something went wron. Please try again. Anyway, I have had my laptop since before Windows 10 came out, I have installed software in the past,...
  4. Continuous BSOD after a Window update

    in Windows 10 BSOD Crashes and Debugging
    Continuous BSOD after a Window update: I installed an update in February 2019, then I face issue with continuous BSOD. BSOD error code says VIDEO_SCHEDULER_INTERNAL_ERROR or DPC_WATCHDOG_VIOLATION. I even did a clean install of OS but issue still persists. It turns out the issue is with my Nvidia GPU (might be...
  5. BSOD after I fixed previous BSODs

    in Windows 10 BSOD Crashes and Debugging
    BSOD after I fixed previous BSODs: Hey there, fixed 2 BSODs I had before and today got another new one. (Just once after several hours of running) Dmp: 1st: https://drive.google.com/open?id=1bF1LS8Gd_Wa-a-5ZPrBVoHS5i72vujSN 2nd: https://drive.google.com/open?id=1ME-B3Q9Xty_X3dXlhNSXNuwEaTwgeHM0 3rd...
  6. Thread stuck in device driver - Random BSOD

    in Windows 10 BSOD Crashes and Debugging
    Thread stuck in device driver - Random BSOD: Hi there. I bought a computer a year back or so and It has been working perfectly. Some time ago (cannot remember exactly when), I started getting BSOD crashes. These crashes can occur whenever, this stretches from browsing facebook all the way to playing intense games....
  7. Random but continuous BSOD, could really use the help...

    in Windows 10 BSOD Crashes and Debugging
    Random but continuous BSOD, could really use the help...: I have a new PC that I built, I've built many but this one has me stumped. I have reformatted several times trying different solutions, stripped all unnecessary hardware, tested both sticks of memory and the SSD. The voltage on the PSU 12v rail is a bit low ~11.8v and it...
  8. bsod continues

    in Windows 10 BSOD Crashes and Debugging
    bsod continues: Proceed to a new clean install, I will keep you informed 33725
  9. BSODs continue after clean install - hardware?

    in Windows 10 BSOD Crashes and Debugging
    BSODs continue after clean install - hardware?: Hello, I previously posted here regarding a variety of BSODs I was getting on my machine which included various stop codes: usbohci.sys faulty hardware corrupted page kernel security check failure memory management After trying a bunch of things (including some good...
  10. BSoD after random freeze

    in Windows 10 BSOD Crashes and Debugging
    BSoD after random freeze: I'm posting on behalf of a friend of mine. I've attached a DM log from his most recent BS and set my PC specs to reflect his. While he was telling me that he Blue Screened, I asked him a few questions to see what he was doing at the time, but he told me that he couldn't...