Windows 10: Unable to install Windows Fall Creators Update

Fast start off.
No crash reports, probably cleaned out with CCCleaner

System Information (local)
Computer name: SHIVA
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH 990FX R2.0
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 16905240576 bytes total



Crash Dump Analysis
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

No valid crash dumps have been found on your computer

Conclusion
Crash dumps are enabled but no valid crash dumps have been found. In case you are experiencing system crashes, it may be that crash dumps are prevented from being written out. Check out the following article for possible causes: If crash dumps are not written out.

Bios link SABERTOOTH 990FX R2.0 BIOS & FIRMWARE | Motherboards | ASUS USA


Will spend some time on the bios

 

I assume you are referring to the msinfo32.nfo file in the unzipped log file. It tells me is is corrupt or incompatible with this version of System Info.

 

No traces of emisoft products found

 

For Ccleaner:
un-check:
a) Memory dumps
b) Windows log files
c) Windows Error Reporting

1) After making the changes with Ccleaner > open whocrashed > above analyze click tools > crash dump test > type: ACCEPT
2) Analyze
3) If there is a dump file > run the beta version of the log collector.

 

For startup and recovery:
un-check automatically restart
change write debugging information to automatic memory dump

On the performance options click the advanced tab > under virtual memory click change > post an image into the thread for the virtual memory window

Run the crash dump test after the above startup and recovery changes.
Then post a new zip with the beta log collector.

 

Crash Dump Analysis Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
No valid crash dumps have been found on your computer

SHIVA (2018-02-11 15 53).zip

 

On virtual memory:
1) check no paging file > ok > reboot
2) check automatically manage paging file size for all drives.
3) reboot
4) run crash dump test again.


If possible please post msinfo 32 either by:
beta log collector
DM log collector
Manual save to desktop as NFO
Manual save to desktop as txt.

 

After changing memory settings
Crash Dump Analysis
Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

No valid crash dumps have been found on your computer

msinfo32.7z

 

Checking file system on C:
The type of the file system is NTFS.
Volume label is Prime.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
1774336 file records processed.

File verification completed.
24775 large file records processed.

0 bad file records processed.


Stage 2: Examining file name linkage ...
2178012 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered to lost and found.


Stage 3: Examining security descriptors ...
Cleaning up 527 unused index entries from index $SII of file 0x9.
Cleaning up 527 unused index entries from index $SDH of file 0x9.
Cleaning up 527 unused security descriptors.
Security descriptor verification completed.
201839 data files processed.

CHKDSK is verifying Usn Journal...
37477400 USN bytes processed.

Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
1774320 files processed.

File data verification completed.

Stage 5: Looking for bad, free clusters ...
85406310 free clusters processed.

Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

499411967 KB total disk space.
155217360 KB in 1224041 files.
666716 KB in 201840 indexes.
0 KB in bad sectors.
1902651 KB in use by the system.
65536 KB occupied by the log file.
341625240 KB available on disk.

4096 bytes in each allocation unit.
124852991 total allocation units on disk.
85406310 allocation units available on disk.