Windows 10: BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED ntoskrnl.exe

I recently just reinstall windows 10 because i was getting problems and i just felt it would go away but I'm still getting the same error but i don't how to fix it can anyone please help out. I ran some memtest to see if it was my ram but i passed 4/4 times Attachment 124503

:)

 

Windows 10 BSOD system thread exception not handled.

Hi,

Recently (past few months) I've been getting a lot of BSODs all saying SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. I have run a crash analysis program which says that the crash was caused by ntoskrnl.exe. However
this is a windows file not a driver that can just be deleted and reinstalled. I have tried the windows recovery and it says that no errors were found.

All my drivers are up to date and I have also updated my BIOS. What else can I try?

My system is as follows:

Ryzen 5 1600

GTX 1060 6GB

Asrock AB350M pro4

8GB of RAM

 

I get "system thread exception not handled" error when finishing the Windows 10 Anniversary Update

Yes! Thank you.

setupmem.dmp 8/3/2016 12:26:17 AM
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c000001d
fffff801`c9d67109 ffffda81`32257518 ffffda81`32256d40
ntoskrnl.exe ntoskrnl.exe+14f109 x64
ntoskrnl.exe+14f109 C:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp
8 15 14393 152,628 8/3/2016 4:26:47 AM

It doesn't make a ton of sense to me. I suspect this is being caused by a driver for both OP and myself, but I'm not sure which.

 

There was only one dump in the zip file and it didn't have much useful info unfortunately.

memory_corruption, probably caused by a device driver. Enable Driver Verifier and see if that gives us any information that helps id the cause.
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to

PART TWO

and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file.

 

I'm not sure if driver verifier is on i did restart instead of reboot idk if that makes a difference but i got a lot of errorsAttachment 124673 thanks a lot

 

The 3/10 5:03PM dump was Driver Veriifier induced.
Code: BugCheck C9, {310, fffff806f44c1c41, ffffb5038a7d9010, 0} *** WARNING: Unable to verify timestamp for FiiOE10.sys *** ERROR: Module load completed but symbols could not be loaded for FiiOE10.sys Probably caused by : FiiOE10.sys ( FiiOE10+1c41 )[/quote] The driver is old: 11/25/2012 9:54:28 PM C:\Windows\system32\drivers\FiiOE10.sys. It belongs to FiiO E10 USB DAC Headphone Amplifier.

Here is a similar problem in Windows 8.1: Solved BSOD 'BUGCODE_USB_DRIVE New Computer Build - Any Situation

Solution there was to remove the Headphone Amp as no newer drivers were available.