View Single Post
  #12  
Old March 25th 20, 10:27 AM 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 Tue, 24 Mar 2020 23:35:25 -0400, n/a wrote:

It does look like a memory problem - but it could be several other things
also.


Thanks for your purposefully helpful adult advice, where I agree that I
need to fully test the memory, but that it could be almost any hardware.

1. Test memory. Removing two sticks and or swapping them is a good first
step. Should always start by removing and reinserting the memory sticks to
insure nothing is loose and/or that there is any corrosion on the contacts.


I agree.
a. There was still a BSOD after re-inserting all memory so I'm currently
testing with only two memory cards in place (memory bank 3 & 4).

Running Windows memory test - well if it's a solid failure, it may find it.
You really need to run MemTest86 https://www.memtest86.com/ and run *all*
the tests. All memory manufacturers will tell you to run that if they don't
have their own diagnostic.


That's good advice, as these memory tests take a long time to run, so it's
good to know which memory tests are the best bang for the buck.

Also, most memory have lifetime warranties.


Interesting. where the memory cards are labeled "PATRIST Memory" & "Viper"
https://i.postimg.cc/Fs7S953Z/bsod31.jpg
PV38G 160C0KGN
PE000283
8GB 1600MHZ (10 - 10 - 10 - 27) DDR3
1.5V UDIMM (2x4GB) KIT

I recently replaced 4 sticks (matched pairs) of Crucial memory on one of my
test systems which MemTest found were picking bits on two sticks - one in
each matched pair. Corsair overnighted replacements right after I sent them
the log from MemTest86. Windows memory test never once found a single
error even after running all night.


As you noted, so far anyway, the Windows memtest shows zero errors:
https://i.postimg.cc/kMc0xdvD/bsod26.jpg

Although I only ran the STANDARD Windows memory tests so far:
https://i.postimg.cc/d3xZzxrd/bsod24.jpg

2. CPU. Be sure the CPU is seated and that it is not overheating. CPU fan
good?


The CPU fan seems to be good, nice & quiet, and certainly spinning.
http://download.gigabyte.us/FileList/Manual/mb_installation_guide.pdf

I haven't checked temperatures, but it's still winter so the house if
pretty chilly where if it's overheating, it would be an anomoly.

I could install the cpu-gpu-fan-temperature testing utilities, of which
there are many, but I'm not sure what value they may add to the mix.

Here's the list that I have in my archives, that I can run at any time:
o cpu-z
o geekbench4
o gpuz
o sandra
o speedfan
o tmeter
o crystaldiskinfo
o easus
o aomei

And for temperature I can install any of these which are in my archives:
o coretemp
o hwmonitor
o openhardwaremonitor
o realtemp
o speedfan

But I can only test one thing at a time...where the goal is to aim for
whatever it might most likely be (memory being the current key suspect).

3. Power supply. Check your BIOS settings to see if it shows the power
supply voltage readings and make sure they are within specs. Not unusual to
see the lower voltages flicker a bit but as a rule of thumb, all voltages
should be within 10% tolerance. May want to check that all power
connections are seated properly.


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.
--
Usenet is most useful when everyone is polite, helpful, and detailed.
Ads