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 can't loads up. I can access the windows only in safe mode.

 

Windows 10 Pro x64

 

The dump has been uploaded.

 

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

 

Thank u.

[techbeck]

DL link does not work.

 

With that said, if Safe Mode works fine and not normal mode, probably a driver issue.  So I would start there.  Video first, the chipset, then work your way from there.

[raya2]

  On 13/09/2017 at 03:33, techbeck said:

DL link does not work.

 

With that said, if Safe Mode works fine and not normal mode, probably a driver issue.  So I would start there.  Video first, the chipset, then work your way from there.

Expand  

 

I think I found the cause of my problem. By launching "BlueScreenView", It showed that the cause of BSOD is from a file named "aswSnx.sys", that is a part of Avast antivirus.

[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:

 

https://ufile.io/8m729

 

or

 

https://mirrorace.com/m/axR9

[DevTech]

1. sfc /scannow

 

2. BSODS that keep changing is almost always a hardware failure. Test RAM, CPU, turn off any overclock, try an underclock etc