BSOD starting Windows Backup w/2 active "users"

Another problem, the msinfo file is corrupt...
Can you open the msinfo.nfo file on your computer after creating one?

Unfortunately it is corrupted again for me.

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc /scannow" (without quotes) and press enter
• When it is finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of the result and post it.

I ran SFC /SCANNOW within the last week (i.e., after the crash) and it came up clean. Is there any reason to suspect that today's run would be any different??

(By the way, all my messages in this thread have been entered from the machine which crashed, so we can safely say that it is de-facto working... and, for the record, my habit is to only run as Admin *when necessary,* following the principle of using "least necessary privileges" to minimize potential privilege-based disruptions.)

The usual thing is that many do not run sfc where sfc resolved the msinfo corruption after running it.

Has SFC been run since yesterday afternoon? Yesterday was the monthly patchday, many unfortunate users have sometimes problems with the updates.

No SFC hasn't been run since before yesterday afternoon... 'twas about a week ago, but Patch Tuesday is a non-issue: I turned off automatic Windows Update several months ago, because my laptop was quite stable and I was getting more undesirable stuff shoved down my pipe than I was willing to waste time on. So it's easier to pick-and-choose, pro-actively, the updates I -want- to apply. (hint, NOTHING related to WinX )

The only routine value I was getting from WinUpd was MSSE updates... but it turns out there's a three-click-and-a-filename method to download those daily. (Except on days when I never power-up the machine, of course but this tactic -does- do a full-download of the MSSE definitions, not just a differential... so I'm still well-covered.)

(Happy to provide the daily MSSE three-click-and-a-filename details if desired, but obviously should be a different thread.) I'll run another SFC /SCANNOW later, just for the halibut.

I would suggest that you install all available updates, it takes a single update missing to have problems.

Ran SFC again (to satisfy your run-twice recommendation) ...
Results attached, but in a nutshell:

C:\Windows\system32>SFC /scannow
Beginning 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>

The only distinction I see, is the first-run included "Repairing 0 components" ... "Repair complete" ... and the second did not.

Is that a distinction without a difference??