PSA: Sometimes, maybe perhaps, it's a "good thing" to turn off fastboot,
hibernation, and/or sleep in Windows 10.

I've been working, on and off, sporadically, for months on this Windows 10
hardware-related BSOD which often DESTROYS Windows' ability to boot.
o Windows 10 BSOD indicates a hardware problem - but what hardware
is the problem?
https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/u0ay9h777Wg

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.

Why does a BSOD often but not always invariably corrupt the boot records?

I don't know why, but I suspect perhaps maybe a "sudden" BSOD "corrupts"
(somehow?) the hiberfile.sys or memory image or whatever because when I
turned off these three things, the BSOD's remained, but I could boot
afterward.
1. Turn off sleep
2. Turn off hibernation
3. Turn off fastboot

Now, when the machine hits a hardware BSOD, it won't reboot ever from its
own efforts, and it won't reboot even if I shut it down and reboot it
manually - but - if I remove the power cord such that all the LEDs go out
(after a minute or two) on the motherboard - THEN it boots again.

Before I turned off sleep/hibernation/fastboot, it _still_ often wouldn't
ever reboot, even after heroic efforts at a Windows-to-Windows repair.

The other thing I did was make copious system restore points, where I
haven't had to manually utilize them, but I don't know if the system
automatically uses them when it attempts an automatic repair.

In summary, TWO things might possibly save your boot records after a BSOD:
1. Copious system restore points, and/or
2. Turn off hibernation, fastboot, and sleep (I'm not so sure of sleep).

Why?
o I don't know why.

Do you?
--
Usenet is wonderful when everyone pitches in helpfully with knowledge.