24 BSODs in 1 month

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 10 Pro, 10.0.10586 Build 10586
       #1

    24 BSODs in 1 month


    Lots of BSODs and I'm tearing my hair out. Please help! If someone can look through and give me some clues, that would be great.

    1. I've tested memory with memtest so far
    2. HDD with chkdsk / HDD tune etc
    3. Checked internal cabling, everything is tightly connected
    4. Drivers are up to date

    Thanks!
      My Computer


  2. Posts : 9
    Windows 10 Pro, 10.0.10586 Build 10586
    Thread Starter
       #2

    Screenshot of 8 passes with memtest successful.

    Attachment 62659
      My Computer


  3. Posts : 9
    Windows 10 Pro, 10.0.10586 Build 10586
    Thread Starter
       #3

    Further I've just run Seatools on all three drives: SMART, Short DST and Short Generic all passed.
      My Computer


  4. Posts : 14,901
    Windows 10 Pro
       #4




    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


  5. Posts : 9
    Windows 10 Pro, 10.0.10586 Build 10586
    Thread Starter
       #5

    Thanks axe0, thats going to be my next step.

    Did you perhaps get any clue by looking at the dumps?

    Thanks!
      My Computer


  6. Posts : 14,901
    Windows 10 Pro
       #6

    The clue was memory corruption, as you already tested the memory, driver verifier is necessary to find any offending driver that may cause memory corruption.
      My Computers


  7. Posts : 9
    Windows 10 Pro, 10.0.10586 Build 10586
    Thread Starter
       #7

    Axe0, as soon as I turned on verifier, it failed to boot with a BSOD: DRIVER VERIFIER DETECTED VIOLATION. Stuck in a boot loop.

    I'm trying to boot back into Windows now by turning off Verifier.
      My Computer


  8. Posts : 9
    Windows 10 Pro, 10.0.10586 Build 10586
    Thread Starter
       #8

    OK, here's the update.

    1. Latest DM Log is attached.

    2. I took a look at the dump using BlueScreenViewer: shows crash caused by ndis.sys. But in the past its shown WdFilter.sys, win32kbase.sys, win32kfull.sys, nvlddmkm.sys, watchdog.sys, dxgmms1.sys, hiber_decrypt.sys... so I dont know what to conclude.

    Please let me know what next. Thanks.
      My Computer


  9. Posts : 14,901
    Windows 10 Pro
       #9

    This bugcheck can be caused with and without driver verifier enabled, this time it is without.

    This one is caused by the outdated TP-LINK USB network adapter drivers.
    Recommended is to either remove it or make sure to install Windows 10 compatible drivers.
    Code:
    *** WARNING: Unable to verify timestamp for athuwbx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athuwbx.sys
    
    1: kd> lmvm athuwbx
    start             end                 module name
    fffff800`59400000 fffff800`5969f000   athuwbx  T (no symbols)           
        Loaded symbol image file: athuwbx.sys
        Image path: athuwbx.sys
        Image name: athuwbx.sys
        Timestamp:        Wed Nov 20 04:43:49 2013 (528C2FF5)
        CheckSum:         0029DE77
        ImageSize:        0029F000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Please also update/remove following drivers/software, these drivers are all outdated in order of date.
    Driver Reference Table - i8042HDR.sys
    Driver Reference Table - pwdrvio.sys
    Driver Reference Table - truecrypt.sys
    Driver Reference Table - ASACPI.sys
    Driver Reference Table - dcrypt.sys
      My Computers


  10. Posts : 9
    Windows 10 Pro, 10.0.10586 Build 10586
    Thread Starter
       #10

    This one is caused by the outdated TP-LINK USB network adapter drivers. Recommended is to either remove it or make sure to install Windows 10 compatible drivers.
    Unfortunately, this is the latest version TP-Link has on its website for this device (TL-WN721N), and I use the WiFi USB on my desktop. Any other suggestion?

    Also, most of the BSODs happen when using photoshop, fewer when using lightroom, even fewer when general browsing. I play lots of games, and strangely enough there have been NO BSODs then.

    Trying to remove the other outdated drivers you mentioned one by one.
      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 01:49.
Find Us




Windows 10 Forums