variety of BSoD on win 10 v2004

I am getting a variety of BSoD errors - each time I reboot my session lasts for a while and then crashes with a new message (lately '21a' seems to be the most prevalent). I am at v2004 (H1) of Windows 10 Pro.

When I do a 'sfc /scannow' I get this error upon completion:
Windows Resource Protection found corrupt files but was unable to fix some of them.For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.

I'm guessing this is related to my BSoD problems.
Is there a way I can find the corrupt files and replace them?

Thanks in advance to all who reply.
Dan

Ztruker said:

Please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

As for the SFC problem, run these commands in sequence up to 3 times or until you get a clean run.

Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth
SFC /scannow

Ztruker:
Thanks to your suggestion, I was able to get SFC to clean up my corrupt files, but I do have 2 follow-up questions:

1) why is there a 3 time max? Why even run it more than once: if it doesn't fix it the first time why will it fix it on another run?
2) for each run sequence, do the 2 DISM commands replace or repair the corrupt files that it finds by going to the MS website?

After running the DISM commands I've had no BSoD, but only time will tell.

I wasn't aware that I was supposed to supply the BSoD logs but I now know and will do so in the future. Does someone at TenForums actually take the time to review them? If so, thank you!

Thanks again for your help!
Dan

Ztruker said:

3 is a number that I and others have found will either fix the problem or the problem is un-fixable. Just a number pulled from experience.
DISM runs from local files. To verify, disconnect from the internet the next time you have a similar problem and you'll see hte same results.

Ztruker:
Sorry, I wasn't clear: What I meant was for DISM to repair all the corrupt files found by SFC, how does it do it? Do I have the vanilla version of those files on my local drive for DISM to simply replace the corrupt file with? Does DISM actually repair the file (somehow)? From what you said, it does NOT get a fresh copy from a MS repository, so I can only assume it somehow replaces or repairs...correct?
But now I wonder why it would ever have a problem, even if ALL my files were corrupt. Couldn't it just keep on repairing or replacing? If it's a matter of getting rid of corrupt files, why stop at 3 attempts? Why not just replace the whole library with a clean, fresh copy?
If I've beaten this to death feel free to close this issue; introducing me to the power of DISM is more than I expected, so thanks!
Dan

Ztruker said:

All the files need to repair/reinstall Windows 10 are kept on your hard drive somewhere, maybe winsxs but I'm not sure. They are not files used for anything else so don't get corrupted unless you have a catastrophic disk failure.

If you want to replace everything, do a Repair Install, that is what it does and it pulls the files from the same place SFC and DISM do.
A lot of files are in use and would not be possible to replace. That's why during a Repair Install at around 30% the system reboots, to replace the in use files with staged ones waiting to go in.

Understood!
Thanks very much for introducing me to the DISM command.
Dan

Fabler2 said:

I think the repair tools for Windows 10 are stored in the recovery partition. So if you don't create images on a regular basis it would not be a good idea to remove it.

Not hurting for storage so I never intended to remove the recovery partition - but thnx for the reply.
Just curious how DISM does its repair so I'll be familiarizing myself more with that command.

Dan