View Single Post
  #14  
Old March 25th 20, 04:59 PM posted to alt.comp.os.windows-10
Arlen Holder
external usenet poster
 
Posts: 20
Default Windows 10 BSOD indicates a hardware problem - but what hardware is the problem?

On Wed, 25 Mar 2020 08:32:49 -0400, Paul 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 ?


Hi Paul,

Thanks again for sticking with me and for being purposefully helpful, where
I appreciate that you're looking at things I may have easily overlooked,
like the power supply.

While I don't yet know what is causing this plethora of BSODs in just a day
a. Memory management
b. System service exception
c. Kernel security check failure
d. Unexpected kernel mode trap
e. Kmode exception not handled

That power supply is the original, and this machine ran, for years, with 3
hard drives, where I've pulled two out along with the Nvidia card, so it's
carrying less weight now than before, and it still BSOD'd.
https://i.postimg.cc/Jnjw37By/bsod32.jpg

I even disconnected the second monitor when I pulled the Nvidia card out.
https://i.postimg.cc/K85TsBjg/bsod33.jpg

So there's _nothing_ in any of the expansion slots, and only 1 HDD now
(and it was BSOD'ing even with just that, although not yet today).

And, I've pretty much eliminated Windows from being the cause of the BSOD
(by wiping it out and re-installing); and the fact it froze in the middle
of the Ubuntu install seems to indicate it's not software (where I was
installing Ubuntu 18.04 from an externally powered USB optical drive).

So far, the only hardware removal that "might" have had any positive effect
is the removal of half the memory cards, as it ran all night (I turned off
all the power management which is something you taught me long ago to do
for another computer that wouldn't subsequently wake up reliably).

Have you fitted an oversized video card that requires
a PCI Express power connection ?


Good question. But there's nothing in the box except one HDD (I removed two
others), and two memory cards (I removed two others). Even the built-in
DVD/CD optical drive is disconnected.

One thing that caught my eye, is in your Event Viewer there
are some Kernel-Processor-Power events.


You have a sharp eye, where there _are_ myriad event-viewer events, where
the problem always is which ones make sense & which don't.

After years of trying, I've given up trying to make sense of that Event
Viewer. No wonder the Indian Microsoft Support calls told everyone to look
there for proof that the Indians needed to wipe out our systems remotely.


You also have a System Service Exception. I looked that one up
and the culprit for one poster was "MBAM.exe".


Good question. I had to look up what mbam.exe is, where it seems to be a
malware bytes executable, which is odd, 'cuz I don't use any anti-virus
programs ever (I don't even know how to use the one that comes with
Windows).
https://www.file.net/process/mbam.exe.html

Sure, like everyone, I went through all the stages of the freeware stuff,
but eventually I concluded it slowed things down more than it ever caught
any viruses.

Since this is a new install, I don't even know where mbam.exe came from,
where I don't use Cortana search so I ran the classic "salonb" command:
c:\ dir /s/a/s/on/b c:\tmp\salonb.txt

I use gvim so it's easy enough to search for mbam.exe which isn't there.
For most people, they'd just pipe it to a "findstr" command though.

What do you use for an AV ?


I haven't used an anti-virus program in many years, where previously, I
think I had the Windows Defender set up, but I didn't even bother turning
it on yet on this new installation, nor the Windows firewall.

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


You put more faith in the Event Viewer than I ever did!
Do you really find the Event Viewer messages useful?

If your memory testing is clean, it's time to move on, and
have a look at your installed software.


I haven't "fully" tested the memory, but, the good news is that I wasn't
expecting the machine to be alive this morning, but it survived the night.

Time will tell as I'll start using it today and I'll leave it running as
all the power settings have been disabled (it's on max performance, which
you kindly showed me how to do long ago).

It's too soon to blame the two memory cards sitting on my desk, yet.
--
Usenet is a public polite potluck where adults gather to discuss things.
Too bad this thread isn't archived by Google groups for future reference.
https://alt.comp.os.windows-10.narkive.com/oL7PTNKu/windows-10-bsod-indicates-a-hardware-problem-but-what-hardware-is-the-problem
Ads