On Wed, 16 Sep 2020 09:08:05 -0700, Mike Easter wrote:

That is, you started w/ your tweaked W10 and used either the installed
or the portable HeavyLoad running in its full cpu mode for 8 h.

Well, it only ran for as long as I slept, which was less than 8 hours.
o Maybe six? (I had expected a BSOD in the morning so I didn't time it.)

I don't think 'heavy load' testing is as important (in this context) as
'routine' type machine activity for longer period of time than hours.
More like days.

I agree since the problem is clearly either random or intermittent...
o What I'm gonna do is run the minidump analyzers the next BSOD.

Unfortunately, it's not easy to get a minidump output set up properly.
o That last BSOD didn't create a new log - but the next BSOD should
https://i.postimg.cc/YCZHCSnD/bsod212.jpg

What I _really_ think we need is a stress tester that tests things like
'cables' and 'caps' and 'card connections".

Something like some kind of looped browser testing for a few days.

Given it took 12 pages of "steps" to get the machine to boot on the last
BSOD of a couple days ago, I'm surprised you didn't ask what that last
"step" was that enabled it to finally boot.
o https://i.postimg.cc/0yV7YFP3/bsod211.jpg

Each "step" was really small, and lots were repetitive (e.g., you have to
boot three times before Windows will bring up the "Do you want to repair"?

The final step, believe it or not, that enabled me to get into the
"Do you want to repair" mode, was, get this, reseating the memory cards by
swapping them, from 1,2,3,4, to 4,3,2,1. Yup.

I don't know if this tells us anything, because it has to be repeatable,
but the next BSOD, after the third boot, if it won't bring up the "Do you
want to repair" option, I will swap the RAM back from 4,3,2,1 to 1,2,3,4.