On Sun, 16 Aug 2020 21:10:47 -0700, Corvid wrote:

For example, I can remove all extraneous hardware from the desktop,
and then re-install Windows 10 from scratch, and invariably, when it
BSODs, the machine might often_never_ reboot successfully after that
BSOD.

Invariably, it might often never, huh?

I am sorry if the language was too complex, where the main point was the
PSA that turning off the fancy fastboot & hibernation features of Windows
"seems" to have prevented the operating system from chewing itself up.

What happened _before_ I turned off fastboot & hibernation was:
a. The machine would run fine (for days or weeks on end).
b. At some point, it would BSOD (due to an unknown hardware issue).
c. The machine would attempt to reboot forever, after that BSOD.
(each time with a different BSOD message as described earlier)

If I let it reboot on its own, almost all the time it would fail.
(Every once in a while, it would reboot but almost never.)

Even with a manual reboot (using the power switch), it would almost
never reboot successfully.

Even after putting in a Windows 10 DVD and booting off of that, would it
almost never successfully repair the corrupted boot record (using all the
commands to fix the boot records already described in this thread).

In fact, it would _never_ reboot successfully, after that BSOD, until I
turned off the power to the desktop (I generally pull the power cord) and
until I waited for the LED on the motherboard to go out (I have the side
panels removed so I can see inside easily).

Then _sometimes_ after the BSOD, would it reboot - but only then.
o But even so, it almost never rebooted successfully after that.

In contrast to those "almost never" circumstances, so far, it has _always_
rebooted (or fixed the MBR on its own) once I did one simple thing:

I turned off hibernation & fastboot (and sleep).

Now that you know the circumstances, Corvid, in more detail, what can you
say to HELP on the problem set (or do you only play silly childish games)?