BSOD Frustration

So I built my own PC. I have done this several times without issue and I built this one back in April and it has been running fine until about a month ago. I had a memory stick go bad, so I troubleshot it and found that issue and then replaced the memory stick a week or two later (ran with only 3 8 gig sticks instead of 4 for a week or two) and during that time the BSODs started. They calmed down after I added back in the 4th stick (same manufacturer and everything), but then started back up again. Restoring back to a restore point helped, but things got bad again after a week or two. So last night I decided that it must be because of the OS I installed, some special OS from Microsoft as part of my MSDN Subscription, so I formatted my hard drive and installed Window 10 PRO to resolve the issue and then spend the day reinstalling all my stuff. Ironically, tonight, I got another BSOD, so that lets me know it was not a OS issue, which I believed. During the bad times, my Chrome stopped working. Sometimes my start menu wouldn't work. It was super irritating. Here is my system information:
Computer name: DESKTOP-F89KSBU
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\Windows
Hardware: ASRock, AB350 Pro4
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 34288099328 bytes (31.9GB)

and I am attaching the zip upload from your BSOD reporting link. Any help you can give would be super appreciated.

Thanks ahead of time for the help.

Update:
BIOS (ASRock > AB350 Pro4)
Test:
RAM with HCI memtest (Test RAM with HCIDesign Memtest | Sysnative Forums)
Drivers with Driver Verifier (Enable and Disable Driver Verifier in Windows 10)

Thanks for the suggestions.

I ran the memory tests as requested. I ran them for several hours to get to at least 100% with multiple instances. Attached are the logs. Working to run the driver exercise tests now.

- - - Updated - - -

So only took 20 minutes after I turned on Device Verifier per the instructions to get the first dump. Here it is attached.

Please post a share link using one drive, drop box, or google drive for C:\windows\memory.dmp

Code:

Crash dump found at C:\Windows\MEMORY.DMP
Creation date: 11/02/2019 14:56:19
Size on disk: 1321 MB

In that case, turn off Driver Verifier after which
1. Turn on Driver Verifier Manager
2. Select "Create custom settings (for code developers)"
3. Enable all settings labeled "Standard" and two settings "Additional" ("Force pending I \ O request") ("IRP Logging")
4. Select "Select driver names from a list"
5.
Select the list of all drivers except those from Microsoft
6. Accept the changes and restart the computer

zbook said:

Please post a share link using one drive, drop box, or google drive for C:\windows\memory.dmp

Code:

Crash dump found at C:\Windows\MEMORY.DMP
Creation date: 11/02/2019 14:56:19
Size on disk: 1321 MB

Isn't that included in the zip file I uploaded from the V2 Log collector?

- - - Updated - - -

MrPepka said:

In that case, turn off Driver Verifier after which
1. Turn on Driver Verifier Manager
2. Select "Create custom settings (for code developers)"
3. Enable all settings labeled "Standard" and two settings "Additional" ("Force pending I \ O request") ("IRP Logging")
4. Select "Select driver names from a list"
5.
Select the list of all drivers except those from Microsoft
6. Accept the changes and restart the computer

Thanks MrPepka. That is how I setup Driver Verifier the first time (except for the standard), but with the IO request and force pending and IRP logging and all non microsoft drivers. I will go ahead and reset it to what you have specified and give it another try shortly. Appreciate the help.

When possible please post the share link.
(No it is not collected > so it was requested)

zbook said:

When possible please post the share link.
(No it is not collected > so it was requested)

Ok. working on that, but copying to the google drive, a 1 gig+ file is taking a while :)

Sorry, I thought that was the whole purpose of the V2 Log Collector. It grabbed so much from my system, I just assumed it got that also.

- - - Updated - - -

bondrjr said:

Ok. working on that, but copying to the google drive, a 1 gig+ file is taking a while :)

Sorry, I thought that was the whole purpose of the V2 Log Collector. It grabbed so much from my system, I just assumed it got that also.

Sorry, turns out it wouldn't copy it from my C:\windows drive as that is protected, so I had to move it somewhere else and then it copied very fast :)

Here is the link:
MEMORY.DMP - Google Drive

- - - Updated - - -

Just got a crash with the new driver verifier settings but it didn't give me a dump. The BSOD came up and disappeared right away and the computer rebooted. Added the V2 Log Collector file to my BSOD directory on Google Drive. Here is the link.
BSOD - Google Drive

I will leave the driver verifier settings on in hopes of getting a dump from the next crash.

Microsoft Windows [Version 10.0.18362.418]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.418

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.418

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
208384 file records processed.
File verification completed.
4158 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
7355 reparse records processed.
293646 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
7355 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
42632 data files processed.
CHKDSK is verifying Usn Journal...
37878360 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

153007103 KB total disk space.
83550548 KB in 155758 files.
107220 KB in 42633 indexes.
0 KB in bad sectors.
319483 KB in use by the system.
65536 KB occupied by the log file.
69029852 KB available on disk.

4096 bytes in each allocation unit.
38251775 total allocation units on disk.
17257463 allocation units available on disk.

C:\Windows\system32>wmic recoveros set autoreboot=false
Updating property(s) of '\\DESKTOP-F89KSBU\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros set debuginfotype=7
Updating property(s) of '\\DESKTOP-F89KSBU\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\Windows\system32>

I don't use overclocking.

results of the first two tests in hdtune uploaded to Google Drive (BSOD link above) in a word document titled Testing1.docx

I will run the other ones overnight. I am unsure about the memory tests. You mention testing all RAM sticks at once, but then the next is to test two at a time for two tests each. So does that mean put stick 1 in dimm 1 and stick 2 in dimm 2 and then run another test with that reversed (stick 2 in Dimm 1 and stick 1 in Dimm 2) and then the same for Stick 3 and stick 4 in Dimm 1 and Dimm 2 respectively and then reversed. If I ran all sticks at once, how would that be accomplished. Stick 1 in Dimm 1, Stick 2 in Dimm 2, etc and then reverse the order (Stick 4 in Dimm 1, Stick 3 in Dimm 2, etc). I don't understand how the 2 sticks at a time would be faster (seems that would be 4 tests vs the 2 tests with all sticks tested at once). I am just not sure I am comprehending what is being asked there, so I want to make sure I am doing it right.

Thanks again for the help.

- - - Updated - - -

Ah. Also meant to mention that I just recreated and reformatted all partitions for this computer Thursday night to reinstall the operating system (mentioned in original post), so the results from those tests would be for the recent disk activity after the reformat/repartition activity. The last drive is an external USB drive, so I won't scan it in the Seatools tests unless that is needed. Thanks!