Arlen Holder wrote:


I have connected & re-connected all power connections, where the power
supply is admittedly anemic at only 300W total (it's an HP 585008-001)
Liteon model PS 5301-08HA.

Would you say the PSU is well suited to the load ?

Have you fitted an oversized video card that requires
a PCI Express power connection ? For example, in my Optiplex
refurb, I fitted a 13W video card :-) Wouldn't want to
tax the poor thing.

*******

One thing that caught my eye, is in your Event Viewer there
are some Kernel-Processor-Power events. Microsoft does not
seem to explain these. Geoff Chappell, normally a sharp guy,
really has nothing here.

https://www.geoffchappell.com/studie...rnel-power.htm

You also have a System Service Exception. I looked that one up
and the culprit for one poster was "MBAM.exe". What do you
use for an AV ?

It could be that Event 55 is related to the "jiggler".

Windows 10 has a malware feature, where if certain things are
being hooked in the OS, the OS shuts down instantly. In microseconds.
The intent is, if the reason is suspected to be "novel", the OS
just dumps, so that the pest cannot gain a foothold. If Windows Defender
had some idea what it was, and could "handle it", the system would
stay up instead.

A third-party AV can be "broken on its own merits", like when
a definition file is released that causes the wrong thing(s)
to be quarantined (a false positive).

It's also possible for AV products to be compromises by an
attacker.

If your memory testing is clean, it's time to move on, and
have a look at your installed software. Since the Event Viewer
entries aren't necessarily going to be helpful, you're partially
flying blind here.

For the System Service Exception, you might look for a process
name, such as the "MBAM.exe" or the like. Any breadcrumb
could be useful from that, if it has details. Because the
Kernel-Processor-Power ones seem to be top secret.

Paul