Windows 10: BSOD (System_thread_exception) when attempting backup of C:

Attachment 90971Attachment 90972Some background on the issue. I had the System thread BSOD when I restarted my computer and I tried to launch into safe mode but it still crashed at the logo, so instead I reinstalled windows and restored from a backup after reinstalling my drivers. However, now everytime I try to backup my files it gives me the System thread BSOD. Any ideas on fixing this?

:)

 

BSOD after upgrading to Windows 10

After upgrading to Windows 10 my laptop shows BSOD. The error shown mostly is System_Thread_Exception not handled. Also I tried rolling back to Windows 8.1 but it says that files needed for this have been deleted even though my windows.old folder still
exists.

 

BSOD occurs on laptop power up, but is fine after rebooting.

When every I power up my laptop after it has been shut off for several hours I get a BSOD (usually every morning).

Most of the time it is related to some driver and the stop code is SYSTEM_THREAD_EXCEPTION.

The last error was in FLTMGR.SYS.

The system reboots and then everything is fine until I power off the laptop and leave it off (again over night).

Is there a way I can figure out what is causing the issue?

Thanks.

Moved from: Windows / Windows 10 / Devices & drivers

 

The first thing I see is you are way back level on Windows Updates.

You are still at the release level 10240. The current version is 10586.494.

Please install all Windows Updates then test more. Meanwhile I'll take a look at the dump.

 

Looks like you are slightly under clocked. Is this intentional?

Code: kd> !sysinfo cpuspeed CPUID: "Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz" MaxSpeed: 3100 CurrentSpeed: 3093[/quote] All the dumps are the same:

Code: BugCheck 1000007E, {ffffffffc0000005, fffff80102176289, ffffd0002200cfa8, ffffd0002200c7c0} Probably caused by : ntkrnlmp.exe ( nt!RegRtlQueryValue+d5 )[/quote] Unfortunately this doesn't help at all.

There are some things you can do to stress the system and see if that brings out a bad driver or defective hardware.

Stress Non Microsoft drivers: Driver Verifier
Stress CPU: Prime95
Stress GPU: FurMark
Test RAM: Memtest86+

Directions follow:
===================================================
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 BSOD with a mini dump that will tell us what driver caused it.
===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums
===================================================
Follow this tutorials to stress test your GPU:
FurMark - GPU Stress Test - Windows 10 Forums

If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums



Information




MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning
MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note
MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
===================================================

Try them one at a time and post results.

 

Sorry, I kinda made this thread while panicking since it crashed so suddenly attempting the fixes now.

Yup just needed some updating