SOLVED BSOD system thread exception not handled

[raya2]

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.

 

[Trouble]

The dump has been uploaded.

Nope.....
Don't know what that is, but it's definitely not a dump file.

 

[raya2]

Nope.....
Don't know what that is, but it's definitely not a dump file.

So give me the location of the dump file, Then I will upload it.

 

[Trouble]

The location of the or a dump file is dependent on how you've configured your system to write them

 

[raya2]

OK, here:

 

[Trouble]

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.

 

[raya2]

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.

Thank u.
I will contact Avast Support, so maybe they could fix it.
And will update this thread for further updates.

 

[raya2]

Update: I uninstalled Avast antivirus from my PC, but still recieving BSOD.

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.

 

[Trouble]

The only driver I see mentioned in this dump file is

STACK_TEXT:
ffffa100`ecf461f8 fffff802`b6d94330 : 00000000`000000c4 00000000`00002000 fffff80a`5de39154 00000000`00000000 : nt!KeBugCheckEx
ffffa100`ecf46200 fffff802`b68ab1f7 : ffffb98b`1093f060 fffff802`b6d8c452 fffff802`b6d868a0 00000000`00000003 : nt!VerifierBugCheckIfAppropriate+0x48
ffffa100`ecf46240 fffff802`b6d8c340 : 00000000`54435349 fffff802`b6981824 fffff80a`5de39154 ffffa100`ecf46460 : nt!VfReportIssueWithOptions+0x103
ffffa100`ecf46290 fffff802`b6d8a325 : 00000000`54435349 ffffa100`ecf46460 00000000`00000000 00000000`001c001a : nt!VfCheckPoolType+0x90
ffffa100`ecf462d0 fffff80a`5de39154 : 00000000`00000000 ffffb98b`10ac2e60 ffffb98b`10ac0034 fffff80a`5de3e073 : nt!VerifierExAllocatePoolEx+0x21
ffffa100`ecf46310 00000000`00000000 : ffffb98b`10ac2e60 ffffb98b`10ac0034 fffff80a`5de3e073 00000000`00000000 : ISCTD64+0x9154

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+

 

[raya2]

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+

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.

 

[Trouble]

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)"

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.

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!

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

 

[Saltgrass]

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

 

[raya2]

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.