On 2019-2-12 10:05, Paul wrote:
...
You can use Driver Verifier to check for memory
leaks or the like in a driver. But this isn't
happening in regular running mode. And the drivers
that load in Safe Mode, would be a subset of the
ones in Normal Mode. I had one case, where running
Driver Verifier, actually stopped a problem, rather
than allowing analysis of where the problem might be.

Since the drivers that load in Safe Mode are a subset of the ones in
Normal Mode, and I can enter Normal Mode without problem, then the
problem should not relate to a driver, isn't it? And my driver set is
near standard; I only install official drivers except one or two that I
surely know what they are for.

You could do an AV scan. Or, it was an AV product
which damaged something. I don't have any information
there, to indicate what to do next.

I do not have any AV product. My habit of using computer is
conservative: I only use software that truly needed, download them from
official site, check signature if there be one, and periodically
optimize and clean the system. I feel no need for AV software to
deteriorate performance; only worms that actively spread by OS bug (like
Sasser?) could infect me, which AV product could not defend against either.

I've had one case here, where a problem did not respond,
to a Clean Install. Which is pretty scary. Later, it seemed
to be a RAM problem that was at the heart of the matter,
but I'm not 100% convinced that's all of it. It could have
been two problems. The RAM being half of it. The RAM seemed
to be bad on my machine, near where some driver was running.
It would cause a crash after 15GB of writes to disk.

Should not RAM problem be random? The phenomenon I encounter is 100%
reproducible, and I have no blue screen or unexpected crash problem in
normal mode usage.

--
Regards,
Lu Wei
IM:
PGP: 0xA12FEF7592CCE1EA