Windows 10: Repeated Crashes and Boot Errors Apparently Caused by Driver Updates

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

6) If you use Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

7) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

8) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
> on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
> on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread

9) In the left lower corner search type services > open windows error reporting service > scroll to the startup type column > right click > left click on properties > post an image into the thread

10) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
Resplendence Software - WhoCrashed, automatic crash dump analyzer
11) Click analyze > look for dead or deaddead in the results > post the results into the thread

12) Run the DM log collector after all of the above steps and post a zip into the thread:BSOD - Posting Instructions - Windows 10 Forums

BSOD - Posting Instructions - Windows 10 Forums

Windows Trusted Platform Module Management Step-by-Step Guide | Microsoft Docs




Code: Event[12135]: Log Name: System Source: volmgr Date: 2017-12-29T04:50:22.026 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-H2C94OF Description: Crash dump initialization failed![/quote] Code: Event[11413]: Log Name: System Source: TPM Date: 2017-12-20T22:32:07.229 Event ID: 17 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-H2C94OF Description: The Trusted Platform Module (TPM) hardware failed to execute a TPM command.[/quote] Code: Event[2967]: Log Name: System Source: cdrom Date: 2017-09-17T14:22:31.478 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-H2C94OF Description: The device, \Device\CdRom0, has a bad block.[/quote] Code: Event[11538]: Log Name: System Source: Disk Date: 2017-12-21T03:57:09.037 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-H2C94OF Description: The IO operation at logical block address 0x446b0dd8 for Disk 0 (PDO name: \Device\00000034) was retried.[/quote] Code: Event[11537]: Log Name: System Source: storahci Date: 2017-12-21T03:57:09.037 Event ID: 129 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-H2C94OF Description: Reset to device, \Device\RaidPort0, was issued.[/quote] Code: Event[11387]: Log Name: System Source: TPM Date: 2017-12-20T18:35:07.249 Event ID: 15 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-H2C94OF Description: The device driver for the Trusted Platform Module (TPM) encountered a non-recoverable error in the TPM hardware, which prevents TPM services (such as data encryption) from being used. For further help, please contact the computer manufacturer.[/quote] Code: Event[11386]: Log Name: System Source: Display Date: 2017-12-20T18:31:45.201 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-H2C94OF Description: Display driver amdkmdap stopped responding and has successfully recovered.[/quote] Code: Event[1174]: Log Name: System Source: volmgr Date: 2017-08-22T20:06:30.798 Event ID: 45 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-H2C94OF Description: The system could not sucessfully load the crash dump driver.[/quote]

 

Steps 1-5:

Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Volume label is OS.Stage 1: Examining basic file system structure ... 632832 file records processed.File verification completed. 43462 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 793848 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 80509 data files processed.CHKDSK is verifying Usn Journal... 39444792 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 975633897 KB total disk space. 630417216 KB in 426861 files. 272512 KB in 80510 indexes. 0 KB in bad sectors. 799461 KB in use by the system. 65536 KB occupied by the log file. 344144708 KB available on disk. 4096 bytes in each allocation unit. 243908474 total allocation units on disk. 86036177 allocation units available on disk.C:\WINDOWS\system32>chkdsk /scanchkdsk /scan

 

I still haven't done the forced crash, apologies for that. I got busy with the semester and didn't want to risk it, and the intermittent update failures were not seriously interfering with my ability to function. But lately Windows has installed an Update Assistant that is no more successful in completing updates, and it's insisting on restarts a lot more frequently, which is a major nuisance. Most recently when I watched the update process (earlier today), it stalled at 33%, restarted, and reverted to the older version of Windows. The error code the Assistant gives me is 0x80070652. Right now, I'd just be happy with a way to just stop the updater from forcing a restart as often as it has been.

 

It sounds as if your PC is repeatedly trying to upgrade to the next build and failing.

As an interim measure, you could disable Windows updates temporarily, or hide the upgrade (same terminology as Win 7), using Windows Update Minitool (free, easy to find). Use that to scan for the upgrade, then use it to hide the upgrade.




Click the +-H to hide/unhide the selected update.

Stop Windows 10 Updates Properly and Completely Solved - Windows 10 Forums
This combines this with another tool Windows Update Blocker.

 

While I'm on the update tool, I thought I'd share this in case it proves helpful.

 

A little over 2 months passed since the last communication.
Please perform all of the tests / steps in post #31 and post images into the thread.
If there are problems posting images please use one drive or drop box share links.
The computer can be tuned up and then an upgrade attempted to get new error messages and error codes.
Alternatively a backup image can be made followed by a clean install.
If the troubleshooting is preferred please post new results for any of the steps that were done 2 months ago and please post results for any of the steps that were not yet completed.

 

Steps 1-5:
Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc/scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Volume label is OS.Stage 1: Examining basic file system structure ... 641024 file records processed.File verification completed. 38938 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 752848 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 55913 data files processed.CHKDSK is verifying Usn Journal... 37708720 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 975633897 KB total disk space. 657134732 KB in 395186 files. 231620 KB in 55914 indexes. 0 KB in bad sectors. 806393 KB in use by the system. 65536 KB occupied by the log file. 317461152 KB available on disk. 4096 bytes in each allocation unit. 243908474 total allocation units on disk. 79365288 allocation units available on disk.C:\WINDOWS\system32>

Steps 7-9:

 

1) For startup and recovery system failure:
a) un-check automatically restart
b) change write debugging information from small memory dump to automatic memory dump
c) make sure the write debugging information no longer displays mini dump and now displays memory dump

2) Backup all files to another drive or to the cloud
3) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free
4) Make a brand new restore point

5) In post #31 start with step # 10 after making changes in this post (step #1)

 

I'm in the process. Macrium Reflect says it'll take until tomorrow morning or so to complete (hope I set it up correctly--I just went with all the defaults), but I'll try to do steps #10-12 tomorrow afternoon.

 

In the future if there is:
a) Malware
b) failure to boot
c) operating system corruption
d) registry corruption
etc
The Macrium backup has these options:
Backup and Restore with Macrium Reflect Windows 10 Tutorials
Use Macrium Reflect Rescue Media to Fix Windows Boot Issues Windows 10 Tutorials

 

All right, I'm going to have to find another place to put the backup image. My external hard drive doesn't have enough space, and I cannot put the backup on the same drive I'm imaging. Sorry for the delay.

 

Well, it's happened. I cannot boot up now; I think it again tried to install updates during the night; I woke up and had a black screen. Now it's in an endless boot loop (lasting only about 15 seconds total) of ASUS screen, recovering update, and reverting to a previous version of Windows. I can't figure out how to get to Windows RE. Any help?

 

Hi, there are threads where this situation has been resolved. I'm not personally that familiar with them, but here's one - feel free to search the forum for more e.g.
boot loop upgrade

Endless Reboot Solved - Windows 10 Forums

 

The problem is I can't sort out how to get to advanced startup options, which everyone seems to be doing in order to repair the boot; I'm pressing all the F keys on startup, and nothing, though I can get the basic boot manager with ESC. Does this mean I need to figure out how to boot from a USB?

 

If you boot from a Windows boot medium, you should be able to access those options by clicking Repair your Computer and navigating thru the prompts.