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

Both methods have the command prompt option and that is what can be used for troubleshooting when system restore and startup repair fail.
When the recovery was created on the computer there could have been some problem with the os or registry that is now on the recovery.
In contrast the Windows 10 iso download is fresh and may be one less confounding factor in the troubleshooting.

Download Windows 10

 

First sequence on command prompt:

 

Still no boot. Moving on to the next step.

 

The chkdsk /f /r report displayed that there were corrections made in the volume bitmap.

Run these commands and post images and then continue with the prior steps:
There was a command for disk 1 but the command for disk 0 seems to have been skipped (steps 24 and 25) for the partition information. These are some additional commands.

1) diskpart
2) list disk
3) select disk 0
4) list volume
5) list partition
6) select partition 1
7) detail partition
8) select partition 2
9) detail partition
10) select partition 3
11) detail partition
12) select partition 4
13) detail partition
14) if there are any other partitions on disk 0 continue in the same fashion
15) exit
16) continue with prior steps

 

Last one. And when not booting from USB I still get the same rapid-sequence updating, reverting, restarting.

 

Scannow displayed no integrity violations.
Fixmbr >ok
Fixboot > access denied
scanos and rebuildbcd total windows installations not in the store = 0


These are abridged commands:
bcdedit /export c:\bcdbackup
attrib c:\boot\bcd -h -r -s
ren c:\boot\bcd bcd.old
bootrec /rebuildbcd

Please use a camera or smart phone camera to take pictures and post images into the thread.
There are more commands after these steps.



These are unabridged commands:
a) type: bootrec /rebuildbcd
(This searches for windows installations not included in the BCD and then asks if you would like to add to it)
(It will display that it successfully scanned all installations and the identified installations will be 0 or 1)
If 0 it displays: Total identified windows installations: 0 The operation completed successfully.
If 1 it displays: Total identified windows installations: 1 [1] D:\windows Add installation to boot list? Yes/No/All:
b) for option total identified installations 0 the BCD store exists and first needs to be removed manually and then rebuilt.
c) type: bcdedit /export c:\bcdbackup
(This will export the BCD store as a file: bcdbackup (a file extension is not needed)
(It should display: The operation completed successfully.)
d) type: attrib c:\boot\bcd -h -r -s
(This removes the hidden, read only and system attributes from the file BCD)
(The attributes had restricted the actions on the file and now it can be renamed)
e) type: ren c:\boot\bcd bcd.old
(now that it is renamed it should be able to be rebuilt)
f) type: bootrec /rebuildbcd
It should display:
Scanning all disks for Windows installations.
Please wait, since this may take a while...
Successfully scanned Windows installations.
Total identified Windows installations: 1
[1] D:\Windows
Add installation to boot list? Yes/No/All:
g) type: Y
then enter key
It should display :
The operationi completed successfully. (The BCD rebuild is complete.)
h) reboot

Please use a camera or smart phone camera to take pictures and post images into the thread.
There are more commands after these steps.

 

This is the result.

 

1) open command prompt
2) diskpart
3) list disk
4) select disk 0
5) list volume
6) select volume 2
7) assign letter=U:
8) exit
9) cd /d U:\efi\microsoft\boot
10) bootrec /fixoot
11) ren bcd bcd.old
12) bcdboot c:\windows /L en-us /s U:all
13) reboot
14) diskpart
15) list disk
16) list volume
17) select volume 2
18) remove letter=U:
19) exit
20) reboot
Please use a camera to take pictures and post images into the thread for the commands and results.

 

This is up to step 10. I assumed "/fixoot" was a typo and tried "/fixboot." Should I proceed?

 

There was a typo in the second image for the EFI command:
fixoot was typed instead of fixboot

sorry it was my typo in the earlier post and should have been:
fixboot

1) open command prompt
2) diskpart
3) list disk
4) select disk 0
5) list volume
6) select volume 2
7) assign letter=U:
8) exit
9) cd /d U:\efi\microsoft\boot
10) bootrec /fixboot
11) ren bcd bcd.old
12) bcdboot c:\windows /L en-us /s U:all
13) reboot
14) diskpart
15) list disk
16) list volume
17) select volume 2
18) remove letter=U:
19) exit
20) reboot
Please use a camera to take pictures and post images into the thread for the commands and results.

 

I got as far as step 13 and... it booted to desktop! I assume I should go on and enter the remaining commands into administrative command prompt?

 

Great.
Consider the repair fragile.
1) Backup all files to another drive or to the cloud
2) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free
3) Make a brand new restore point

4) Open administrative command prompt and type or copy and paste:
5) sfc /scannow
6) dism /online /cleanup-image /scanhealth
7) dism /online /cleanup-image /restorehealth
8) chkdsk /scan
9) 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

 

All right, I'm updating my back-ups, which may take a while. Should I still go in and remove the U: assignation?

 

That can be done later.
After the above steps check the drive:
Run HD Tune: HD Tune website
Post images into the thread for the test results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan

Overnight run this command using administrative command prompt:
chkdsk /x /f /r C:
Use the information in this link to find the chkdsk report in the event viewer. Copy and paste > notepad > post an image into the thread.
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials