BSOD every few weeks - various related to memory

Every few weeks I get a BSOD. It always seems to be related to memory so I occasionally run memory diagnostics, including the BIOS built-in and memtest86 (and memtest86+). It always passes the memory diagnostics.

Here's a list of BSODs I've gotten, going back a year (I take a photo when it happens):

Date	stopcode	other
2/25/2020	PAGE FAULT IN NONPAGED AREA	What failed:nvlddmkm.sys
7/21/2020	MEMORY MANAGEMENT
7/28/2020	FAULTY HARDWARE CORRUPTED PAGE
9/3/2020	FAULTY HARDWARE CORRUPTED PAGE
10/25/2020	FAULTY HARDWARE CORRUPTED PAGE
12/15/2020	FAULTY HARDWARE CORRUPTED PAGE
1/12/2021	FAULTY HARDWARE CORRUPTED PAGE
1/16/2021	MEMORY MANAGEMENT
3/20/2021	CRITICAL STRUCTURE CORRUPTION
4/26/2021	FAULTY HARDWARE CORRUPTED PAGE
5/19/2021	MEMORY MANAGEMENT

I tried using the log collector. Unfortunately it summarily stops & disappears after showing "Running system power report. . . "


I found folders on my Desktop, apparently created by it. I have manually zipped up the most recent of those folders, but I assume it is incomplete since the process did not complete.

I will appreciate any guidance, including how to get the logs collector to run through to the end.

Here is my Windows version: 20H2 (OS Build 19042.985)

Looks to be memory problems.

===================================================
Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review

Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

   Warning

MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.

If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

   Note

Both of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

Okay, good luck. You have 8GB so it will take awhile to complete 8 passes. Don't forget to capture screen output after the end of each 4 passes and post here.

32GB, right, sorry.

Run memtest86 as directed, it's a much better diagnostic. For 32GB it will take at least 8 hours. The free version will only run 4 passes so you need to run it twice in succession to get 8 passes.
Post pictures of each run, also as directed.

Thanks actually if you check you will see that I've already run the eight passes of memtest86 and posted the results that came up clean. My question is if I should do it even more and perhaps for a very long extended run? Or is that superfluous?

- - - Updated - - -

See the attachment BSOD - memtests.7z above for the results of the 8 passes of memtest86

Are you doing any over clocking or over/under volting? If so, restore everything to nominal and see what that does for you.

It would also be a good idea to try running Driver Verifier.

Run Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

Enable and Disable Driver Verifier in Windows 10

Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.