Windows 10 BSOD indicates a hardware problem - but what hardware is the problem?

"Arlen Holder" wrote in message
...
On Sun, 16 Aug 2020 21:10:47 -0700, Corvid wrote:

Snip

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).


That sounds familiar.
I was given a media centre PC with an Intel i3 Gigabyte motherboard which
had failed to boot.
Got it home, turned it on & it booted fine.
Ran it for some time until one day it failed to boot.
I thought I had turned off the power at the wall but some weeks later it
tried to boot.
Next day it booted on it's own & ran fine for several years.

Last month I cloned the Windows drive to allow for a larger SSD.
The machine refused to boot from the new SSD but was fine with the old one.
I installed Windows (8.1) on the new drive using the old product key &
everything has been fine since.

I've asked various people that work on computers & no one has a reasonable
explanation for the cause of the non booting.

--
Regards
wasbit