Windows 10 won't boot after freezing up and clean shutdown

My mom's computer suddenly won't boot. The system continually goes into the automatic repair process on boot, does a diagnostic gets a stop code of 0000011a or 0000021a , can't fix what ever it has detected then displays the shutdown option or Advanced option.
In the Advanced options I've tried a system restore from a few days ago, it errors out. The I tried one from last week - this time it errored and I saw the message that the restore point file was corrupted.
Then I tried safemode multiple different levels of safe mode each does not boot, but goes into the Automatic repair mode after not booting.
So next I went into the CMD prompt Here I think I might be getting some good info - the cmd prompt has the message at the very top that some cmd was not able to run because if insufficient systems resources.
Next I tried a reset it went all the way to 90% done then rebooted and and upon reboot instead of the error message I got the typical win10 rotating circle and a message saying "Undoing Changes" it rebooted twice during this process saying "Undoing Changes" and then started repeating the There was an error in starting your machine automatic repair will try to find and fix the error.
So I did look at the bios and system reports 4 1 GB DIMMs, but there is not testing. The Drive is reporting bacl, but once again the old Dell 745 Optiplex is not testing the drive and all the old Del emergency management software has long ago been lost with the new HD replacement.
I'm at a loss at what steps I could take next.... Any Ideas?

What is the status of the drive?
What tests were ran and when?
It reported?
Was the drive replaced and is it new?

These are some options: (some will need flash drives that you can format)

1) If files are backed up or if there is a backed up image then clean install
2) If files are not backed up or if there is no back up image boot rescue software can be used to copy and paste the important files to another drive.
3) The failure to boot can be troubleshooted using the windows advanced troubleshooting menu on the Windows 10 iso.
Commands can be run to troubleshoot the operating system, registry, boot, drive file system, etc.
4) There is software that can attempt to fix boot.
5) From the opening post a reset save files failed. When this happens often a custom install can be performed which is another method to save files and clean install the operating system.
6) Reset remove files which is similar to clean install


For troubleshooting using command prompt the steps will be:
startup options disable driver signature enforcement
revertpending actions
chkdsk /r
scannow
boot repair
etc.

Thanks for your quick replay. It's been a long time since I've done this type of trouble shooting. The HD drive was replaced years ago and Win 7 installed has been working for years; was upgraded to win 8 and then 8.1 and finally 10 so I have no disc from which to run the the repairs. Is there a download site to get this WIN 10 ISO for repair?
What would you recommend for the boot fixing software? Is it any better than manually running CHKDSK and scan fixboot? Thanks again.

Update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums | Windows 10 Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums
Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)





Failure to boot can be multifactorial.
Using command link in Windows RE multiple commands can be run and then depending on the displayed results additional commands can be run to potetially fix the probilems displayed in the results.
The boot fix software is pre-programed to fix the boot and I've not seen it used enough to see whether it is better to run first or last compared to running command line first or last. Command line can troubleshoot boot failure caused by windows updates, operating system corruptions, registry problems, etc. that are not fixed by the software.

To troubleshoot using command line and if you need to backup files at any time:

1) Find two flash drives that you can format

2) Create a bootable Windows 10 iso build 1803:
Download Windows 10
Download Windows 10 ISO File | Windows 10 Tutorials

3) To backup files create a Kyhi boot rescue flash drive:
Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums
4) With the boot rescue you can copy and paste the Users folder, subfolders or files to another drive.

5) With the boot rescue software you can open browsers to temporarily download and install software to test the drive:
It is trial and error as some software will/will not install/work.
HD Tune: https://www.hdtune.com/
Run tests and post images for:
a) Health (SMART)
b) Benchmark
c) Full error scan (this may take several hours to complete)

6) In case there are any problems running HD Tune then see if you can run HD Sentinel (free edition):
Hard Disk Sentinel - HDD health and temperature monitoring
Post images for overview, temp, SMART


Perform these additional steps:
a) There are two log collectors: DM and BETA > run each and post zip into this thread >
BSOD - Posting Instructions - Windows 10 Forums
(for the beta log collector use extract all > open)
b) Open disk management > by default the columns are compressed > widen these two columns: Status and Volume > make sure that the characters in each row are in full view and that no letters are cut off > post an image into the thread




7) Once the drive has passed/failed then boot using the Windows 10 iso clicking the applicable F key.
List of PC brands with their corresponding hot-keys

8) If it is a custom computer then temporarily modify the BIOS boot order so that the external USB HD is on top.
9) Boot to the external USB HD
10) It may take 5 - 10 minutes for the iso to load while viewing the Microsoft Windows icon
11) Select language, time, currency, and keyboard, or click next
12) In the left lower corner click repair your computer (do not click install)
13) Click troubleshoot
14) Start with startup repair > this is expected to fail but may generate a new srttrail.txt file which can be viewed
15) Click system restore > this is expected to fail > start with the oldest restore point and keep repeating to the newest restore point > if system restore fails or if there are not restore points then advance to the next step
16) Click command prompt > this should open a black box with title bar: Administrator: X:\Windows\System32\cmd.exe and with prompt: X:\Sources>

17) Find a camera or smart phone camera to take pictures and post images into the thread. In case there are problems posting images please use share links (one drive, drop box, or google drive)

18) Type these commands. Comments will be in parenthesis.

19) bcdedit /enum
20) bcdedit | find "osdevice"
(make note of the partition drive letter as this drive letter will be used for many of the next steps)
21) dism /image:K:\ /cleanup-image /revertpendingactions[/FONT][FONT="Open Sans",sans-serif,Arial,Tahoma,Calibri,Geneva,sans-serif](replace K with the drive letter for the partition drive letter displayed in step #20)
22) (reboot) > (if boot returns to normal then it was likely a Windows update caused the boot failure.) (If boot failure did not change then advance to the next step)
23) chkdsk /r K:
(change the drive letter to the partition drive letter displayed in step#20)

(reboot as necessary)

(This may take many hours and typically displays ETA)
24) (reboot) >

[FONT=Open Sans] (if boot returns to normal then it was likely problems with the drive files system that caused the boot failure.) (If boot failure did not change then advance to the next step)
25) sfc /scannow /offbootdir=K:\ /offwindir=K:\windows
(change both letters K: to the partition drive letter seen in step #20)
(report the findings into the thread)
25) (reboot) >

(if boot returns to normal then it was likely problems with the operating system that caused the boot failure.) (If boot failure did not change then advance to the next step)
26) bootrec /fixmbr
27) bootrec /fixboot
28) bootrec /scanos
30) bootrec /rebuildbcd
31) (reboot) >

(if boot returns to normal then it was likely problems with the boot files that caused the boot failure.) (If boot failure did not change then advance to the next step)
32) c:
33) dir
34) d:
35) dir
36) e:
37) dir
38) cd \windows\system32\config
39) dir
40) cd..
41) cd..
42) cd..
43) X:
44) diskpart
45) list disk
46) list volume
47) select disk 0
48) detail disk
49) list partition
50) select partition 1
51) detail partition
52) select partition 2
53) detail partition
54) select partition 3
55) detail partition
56) select partition 4
57) detail partition
58) select disk 1
59) detail disk
60) list partition
61) exit
62) (reboot)
63) Please take pictures and post images into the thread or use share links (one drive, drop box, or google drive)

Update:
ran a chkdsk /f /r /x after that I exited and tried a another restore of the latest restore point. That failed; the system rebooted again and this time the auto repair process said it would try to fix the file system and that it would probably take more than an hour. When I came back the system was sitting at the "Auto repair failed screen" and I choose to go into advanced options again and then to the command prompt. I cd to D:\windows\system32\logfiles\srt and piped the srttrial.txt file to more and there were all the test results. All were a Success except the last one
boot critical file d:\boot\resources\custom\bootres.dll is corrupt could not repair.
I think at this point the only saving thing would be the fix boot software. I have a very old copy of bootbcd or something like that, but I'd have to find it. Thanks.

I didn't see your previous responce before I made my last update. I'll go through those steps and be back to you, maybe a day or two Thanks!!!

I can't create the Win10XPE Project because the builder can't find the install.wim file in the sources directory of the WIn10 install usb I created from the links you listed.???

I can't create the Win10XPE Project because the builder can't find the install.wim file in the sources directory of the WIn10 install usb I created from the links you listed.???

The Windows 10 iso should be able to be created on any working computer.
The iso could be created on a work computer, at a public library, or it could be borrowed from a friend, neighbor, or relative.


These are some links on the iso/rescue media:
Win10XPE - Build Your Own Rescue Media - Windows 10 Forums
Download Windows 10
Download Windows 10 ISO File | Windows 10 Tutorials

I'm sorry I guess I was unclear. I couldn't create the
Kyhi boot rescue flash drive as described in the
Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums
the WIN10XPE tool reports the ISo and USB boot flash drive created by the media creation tool do not contain the install.wim image file in the sources directory

Anyway I've gone through all the steps the big error seems to the sfc /scannow command does not work because it states a system repair is waiting for a reboot to complete and this flag never seems to be cleared. Ok I've uploaded some screen shots.