BSOD system thread exception not handled

SOLVED Discussion in 'Crashes, BSODs and Debugging' started by raya2, Sep 11, 2017.

  1. raya2

    raya2

    Joined:
    Nov 25, 2015
    Messages:
    8
    Likes Received:
    1
    Recently I got this BSOD:

    SYSTEM THREAD EXCEPTION NOT HANDLED

    The first time, Its said about a file named "fltMgr.sys"; But after that, Everytime It only shows "SYSTEM THREAD EXCEPTION NOT HANDLED"

    Windows 10 Pro x64

    The dump has been uploaded.

    https://mirrorace.com/m/6k1k

    Thank u.
     
    raya2, Sep 11, 2017
    #1
    1. Advertisements

  2. raya2

    Trouble Noob Whisperer Moderator

    Joined:
    Nov 19, 2013
    Messages:
    10,407
    Likes Received:
    1,564
    Location:
    Northwest Indiana U.S.A.
    Nope.....
    Don't know what that is, but it's definitely not a dump file.
     
    Trouble, Sep 11, 2017
    #2
    1. Advertisements

  3. raya2

    raya2

    Joined:
    Nov 25, 2015
    Messages:
    8
    Likes Received:
    1
    So give me the location of the dump file, Then I will upload it.
     
    raya2, Sep 11, 2017
    #3
  4. raya2

    Trouble Noob Whisperer Moderator

    Joined:
    Nov 19, 2013
    Messages:
    10,407
    Likes Received:
    1,564
    Location:
    Northwest Indiana U.S.A.
    The location of the or a dump file is dependent on how you've configured your system to write them

    Capture.PNG
     
    Trouble, Sep 11, 2017
    #4
  5. raya2

    raya2

    Joined:
    Nov 25, 2015
    Messages:
    8
    Likes Received:
    1
    OK, here:
     

    Attached Files:

    raya2, Sep 12, 2017
    #5
  6. raya2

    Trouble Noob Whisperer Moderator

    Joined:
    Nov 19, 2013
    Messages:
    10,407
    Likes Received:
    1,564
    Location:
    Northwest Indiana U.S.A.
    The driver mentioned in the dump file is
    aswSnx.sys
    Part of the Avast Antivirus Program.
    You might want to start there and see if uninstalling it, including the vendor specific, proprietary removal tool
    https://www.avast.com/uninstall-utility
    To remove all remants, will result in ending your blue screens.

    You can always re-install it later if you want to experiment further.
    AND
    IF after you uninstall it, your machine is still suffering the same or similar issues, just....
    Attach any new dump files to your next post.
     
    Trouble, Sep 12, 2017
    #6
    raya2 likes this.
  7. raya2

    raya2

    Joined:
    Nov 25, 2015
    Messages:
    8
    Likes Received:
    1
    Thank u.
    I will contact Avast Support, so maybe they could fix it.
    And will update this thread for further updates.
     
    raya2, Sep 12, 2017
    #7
  8. raya2

    raya2

    Joined:
    Nov 25, 2015
    Messages:
    8
    Likes Received:
    1
    Update: I uninstalled Avast antivirus from my PC, but still recieving BSOD. [​IMG]

    The only change in BSOD is the message it shows:

    Driver Verifier Detected Violation

    I ran BlueScreenView app to see the Driver that caused it:

    vmci.sys

    It was related to VMWare, So I uninstalled VMWare apps and restart, But again I received BSOD & this time with another driver.

    I removed that driver But again & again the BSOD comes with other drivers. Till now I removed 6 drivers or their apps, But Still I have BSOD.

    I must say that All BSODs have the same message:

    Driver Verifier Detected Violation

    But each time with different drivers + a windows system file named "ntoskrnl.exe" (NT Kernal & System).

    Newest Dump file attached.
     

    Attached Files:

    raya2, Sep 15, 2017
    #8
  9. raya2

    Trouble Noob Whisperer Moderator

    Joined:
    Nov 19, 2013
    Messages:
    10,407
    Likes Received:
    1,564
    Location:
    Northwest Indiana U.S.A.
    The only driver I see mentioned in this dump file is
    ISCTD64.sys (Intel Smart Connect Technology Driver) and then it suggests
    Probably caused by : memory_corruption
    So ....
    Check with Intel for a possible updated driver specifically for Windows 10
    Use the native CHKDSK utility to inspect your hard drive for possible errors
    and then

    Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
    Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.

    See this Guide to using Memtest 86+
     
    Trouble, Sep 15, 2017
    #9
    raya2 likes this.
  10. raya2

    raya2

    Joined:
    Nov 25, 2015
    Messages:
    8
    Likes Received:
    1
    I removed the old miniDUMPs

    Also, I removed Intel Smart Connect Technology Driver but Immediately after that, here is the new dump with another driver!
    this time about "ScpVBus.sys".

    Its the 7th Driver that caused the BSOD!

    I think its not possible that all these drivers start to act faulty at the same times, When I was using them for more than 1 year!

    CHKDSK returned this error:

    "C:\Windows\System32>chkdsk C: /f /r /x
    The type of the file system is NTFS.
    Cannot lock current drive.
    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)"

    I will report about Memtest86+ results, some hours later.
     

    Attached Files:

    raya2, Sep 15, 2017
    #10
  11. raya2

    Trouble Noob Whisperer Moderator

    Joined:
    Nov 19, 2013
    Messages:
    10,407
    Likes Received:
    1,564
    Location:
    Northwest Indiana U.S.A.
    That's not an error
    You have to respond by typing a Y as indicated to let it run on next reboot.
    Be aware that it will take a long time and may not show progress as expected, just let it run and the machine will reboot automatically when done.
    That's an astute observation and applicable assuming you don't have a problem with the hard disk or the memory that may be causing some files to become corrupted.
    AND
    You should probably turn off Driver Verifier
    from the run dialog box type
    verifier.exe
    select delete existing settings and click finish
     
    Last edited: Sep 15, 2017
    Trouble, Sep 15, 2017
    #11
    raya2 likes this.
  12. raya2

    Saltgrass

    Joined:
    Oct 1, 2014
    Messages:
    1,210
    Likes Received:
    141
    You do have some older drivers. Your system does not seem to be updating Win 10 for some reason.

    Here are the oldest ones I see. Doesn't mean they are bad, but suspect or may need updating. Something on your system may have changed, possibly a Windows update which started having problems for some reason.

    ScpVBus.sys Sun May 5 16:31:26 2013
    fetn63a.sys Mon Mar 25 20:20:02 2013
    tap0901_openvpn_accl.sys Thu Feb 9 08:31:04 2012
    ISODrv64.sys Wed Nov 20 19:22:28 2013
     
    Saltgrass, Sep 16, 2017
    #12
    raya2 and Trouble like this.
  13. raya2

    raya2

    Joined:
    Nov 25, 2015
    Messages:
    8
    Likes Received:
    1
    OK, I think my problem has been solved.

    I removed about 7-8 drivers & Also did a CHKDSK. And voila, BSOD gone.

    Thanks to anyone that helped me here. :D
     
    raya2, Sep 16, 2017
    #13
    Trouble likes this.
    1. Advertisements

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads
  1. tomstrong
    Replies:
    1
    Views:
    5,650
    remostalin
    Aug 2, 2015
  2. ignorant

    error system thread exception not handled

    ignorant, Aug 7, 2015, in forum: Windows 10 Support
    Replies:
    13
    Views:
    22,890
    Monafraj
    Mar 9, 2017
  3. andycrofts

    System - and I mean SYSTEM language, not UI language.

    andycrofts, Aug 24, 2015, in forum: Installation, Setup and Updates
    Replies:
    9
    Views:
    2,526
    CMoon
    Mar 15, 2017
  4. Bruceyfamily
    Replies:
    7
    Views:
    1,776
    Bruceyfamily
    Apr 17, 2016
  5. Win10RAP

    .ods default app not handled correctly

    Win10RAP, Jul 26, 2016, in forum: Windows 10 Support
    Replies:
    1
    Views:
    330
    Regedit32
    Jul 27, 2016
  6. chopper
    Replies:
    8
    Views:
    10,190
    Norton
    May 2, 2017
  7. DET007

    Windows Bad Image Exception Processing Message

    DET007, Mar 16, 2017, in forum: Windows 10 Support
    Replies:
    3
    Views:
    11,132
    bridgetrowing
    Mar 22, 2017
  8. TJ Loveland

    Windows bad image exception

    TJ Loveland, Apr 7, 2017, in forum: Windows 10 Support
    Replies:
    1
    Views:
    1,295
    Regedit32
    Apr 8, 2017
Loading...