Windows 10: BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED ntoskrnl.exe Solved

  1.    10 Mar 2017 #1

    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
      My ComputerSystem Spec


  2. Posts : 5,684
    Windows 10 Pro X64 16299.192
       10 Mar 2017 #2

    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.
      My ComputersSystem Spec

  3.    11 Mar 2017 #3

    Ztruker said: View Post
    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
      My ComputerSystem Spec


  4. Posts : 5,684
    Windows 10 Pro X64 16299.192
       12 Mar 2017 #4

    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 )
    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.
      My ComputersSystem Spec


 

Related Threads
Hi everyone, Can somebody take a look on my bugcheck analysis? I really don't know what has caused the bsod i don't know much about this. bugcheck analysis: http://textuploader.com/5bz3l
Hello. I am getting a new BSOD. Came out of nowhere. I attach the DUMP FILES . I refer to the dump from 25/05/201681560
i just upgrade from win 10 build 10240 to 10586 and upgrade my nvidia drivers to 362.00 everything looks fine until i try to play any game that use nvidia card then bluescreen appeared with system_thread_exception_not_handled(nvlddmkm.sys) i also...
Hi! Recently, I'm getting random BSODs (while browsing, while gaming) and it never happened in the past. In the blue screen, it mentioned SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (nvlddmkm.sys) every time. I did clean install of the Nvidia...
Hey guys, I recently upgraded my Hardware (CPU and Graphics Card). Old: AMD FX-4300, Sapphire HD7870 New: AMD FX-8350, ASUS STRIX-R9 380-DC 2 OC Since then I frequently run into "SYSTEM_SERVICE_EXCEPTION" and...
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 22:34.
Find Us