On Tue, 15 Sep 2020 19:58:41 +1000, Lucifer wrote:

I got my first BSOD in days, this morning, when I woke up.
It took me about six hours of repetitive booting to get the OS back.

A faulty power supply can cause very strange errors.

Thanks for your purposefully helpful advice, as I'm determined, as always,
to methodically track down the cause of this intermittent BSOD, where
yesterday, I rebooted a score of times, changing only a single minor
variable each time, in an attempt to recover Windows without needing to
rebuild the OS after the BSOD chewed it up.

It took literally a dozen pages of steps, every one of which I wrote down:
o https://i.postimg.cc/0yV7YFP3/bsod211.jpg

So that today, it's running with aplomb, as if nothing happened yesterday.

Moving on, since I'm determined to find what is causing these BSODs...
o I have been checking voltages - but I don't know what they should be.

Looking at the OCCT results while I run the furmark, valley, prime95 &
intelburn benchmarks shows each of the voltages in tabular form
(e.g, CPU VCore 2.14V, VIN1 2.14V, +3.3V, +5V, +12V, -12V, -5V, and +5V
VCCH) where that table is in the form of current value, minimum, & max
value.

The +5V is slightly glitchy but I'm not sure what to compare it to.
o https://i.postimg.cc/26yJTkFZ/voltage01.jpg

In addition to looking at voltages during benchmarks, I have temps too:
o https://i.postimg.cc/X79V9Lv0/voltage02.jpg

But again, it's not so much knowing the temp, but what it should be.
o Voltages
o Temperatures
o Fan speeds
etc.

In addition, since the BSODs are intermittent, I've been "recording"
performance with the Microsoft Windows Performance Recorder from the
Microsoft SDK (C:\path-to-ms-sdk\Windows Performance Toolkit\WPRUI.exe),
but I'm not sure yet how to analyze the results yet.
--
As with religion & God, both computers & Microsoft work in mysterious ways.