Windows 10: Windows update failing - version 1709 Update - no real error message.

Please post an image of the startup and recovery window.
The logs display that the automatically restart is still checked.

 

Sorry my mistake, I didn't realise the forum had auto attached my original log files - the actual new ones are now attached.
LASERBEAK (2018-01-22 16 56).zip

Window shows:

 

Nice work.

The BSOD crash dump worked.

If the computer becomes unstable and crashes it now can produce dump files.
The dump files then can be debugged to look for misbehaving hardware or software drivers or malfunctioning hardware.

 

Great - so does that mean you want me to re-run one of the earlier sets of instructions for you? Such as re-attempt the in place upgrade?

 

There will be more steps before the next upgrade attempt.

1) Backup all files to another drive or to the cloud.

2) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free

3) Place the backup image onto another drive or into the cloud

4) Make a brand new restore point

5) Read these links on Windows drive verifier:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

Please don't use the tool yet until it is communicated in the thread

6) Open Ccleaner > click the Windows tab > scroll down to system and advanced > post an image into the thread

 

Ok, all files moved, image created and saved in the cloud with Macrium. Articles read - not 100% I completely understand some of what is in them - but they are read *Shock
New Restore Point has been created as well.

Ccleaner image here:

 

For Ccleaner please un-check:
Memory dumps
Windows log files

After making the changes with Ccleaner perform a Whocrashed test dump, then analyze.
Post an image into the thread
Run the log collector and post a zip into the thread:
log collector v2-beta08.zip

 

Ok, changes made to CCleaner, Crash Dump test run - results below.


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump



On Tue 23/01/2018 07:23:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012318-3218-01.dmp
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19B41837, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\Windows\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.



On Tue 23/01/2018 07:23:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19B41837, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\Windows\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.



On Mon 22/01/2018 16:48:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012218-12406-01.dmp
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19B4007E, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\Windows\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Here is the zip from the log collector run after the Crash Test Analyser.
LASERBEAK (2018-01-23 07 26).zip

 

The crashes created dumps and the dump formed mini and memory dumps.
The mini dump files were able to be debugged.
So the computer environment is now ready for using windows driver verifier.
If you run it now you will be on your own. After each BSOD run whocrashed > analyze > uninstall the misbehaving driver.
Some drivers may not be able to be analyzed by whocrashed. Our tools perform a more thorough debugging. So after the dumps run the log collector and post zips into the thread for debugging.
At this time I'm heading to bed and will check in with you later in the day.

Make sure that you have created a brand new restore point.
Sometimes the computer becomes sluggish when using windows driver verifier.
Other times it may be unable to boot.
If there is difficulty booting the number of custom active tests will need to be reduced.
If there are no problems plan to use the tool for 48 hours.
After the last BSOD plan to use the tool for an additional 36 hours of typical computer use.

 

Thanks Zbook, I was lucky, first driver failure seemed to be the culprit. All updated now with build 1709. Really appreciate all the help and guidance *Smile

 

That's great news.
You are welcome.
Which driver was it?
Please post a new zip.
log collector v2-beta08.zip

 

It was a driver for one of my flight controls, as I play flight simulators. Once that was removed all was ok and update went ok. I am off for work at the moment so unable to post another log. I will try to post one over the next few days.