Random BSODs since update last week

Windows version 1903. Ever since a middle of the night update last week (10/5) the system has random bsods. Also cannot access the system information app, "windows management files may be moved or missing." although running sfc /scannow reports everything is fine. The windows/system32/wbem/repository directory has a file called corrupted.rec.
Initially the scan did find some errors, ran dism /online /cleanup-image /scanhealth and /restorehealth, eventually we got to a place where they reported everything was good. But after almost 24 hours, another bsod.

Frustrating. Maybe someday computer error logs will contain information useful to normal users.

Any ideas and suggestions will be greatly appreciated.

The V2 log collector reported meta data errors and was not able to collect important logs and data.

Please post images of the scannow and dism results into the thread.

After completing all of the steps posted by Ztruker please upload both new V2 and DM log collector results:
BSOD - Posting Instructions

at one time all of the dism runs and the sfc / scannow ran clean. System lasted perhaps a day before the next bsod.

today sfc reports that there are problems it cannot fix.

I may try updating the realtek driver, although that does not seem to be a reason for the windows management files to be moved or missing, which was true even after all the dism and sfc running. I would like to resolve that issue. I will note that windows thinks all the drivers are up to date. Is the operating system not capable of determining this?

Norton has run on this computer for five years. I have seen advice as to uninstalling any other antivirus other than windows defender, but this would actually be a later resort.

Every bsod has different error codes. We've had system service exception, kmode exception not handled, system thread exception not handled (failed: dxgmms2.sys), kernal check security failure, and a system service exception (failed: win32kbase.sys) are some I've noted.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7

9) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

10) Post both V2 and DM after performing the above steps:
BSOD - Posting Instructions

updated the realtek driver, with a bsod in the middle of that process.
the last two asks here did not work because the wmi missing files....but I left the errors there. this is the one constant that stands out that has not been fixed by anything I've done.
will follow with the other logs shortly.

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 found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

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

[===========================99.9%========================= ] 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 found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is Windows7_OS.

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

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

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

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

957410562 KB total disk space.
379072168 KB in 482125 files.
290376 KB in 79343 indexes.
0 KB in bad sectors.
982526 KB in use by the system.
65536 KB occupied by the log file.
577065492 KB available on disk.

4096 bytes in each allocation unit.
239352640 total allocation units on disk.
144266373 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set auto reboot=false
ERROR:
Description = Invalid namespace

C:\WINDOWS\system32>wmic recoveros set autoreboot=false
ERROR:
Description = Invalid namespace

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
ERROR:
Description = Invalid namespace

C:\WINDOWS\system32>wmic recoveros set autoreboot =false
ERROR:
Description = Invalid namespace

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
ERROR:
Description = Invalid namespace

C:\WINDOWS\system32>wmic recoveros set DebugInfoType= 7
ERROR:
Description = Invalid namespace

C:\WINDOWS\system32>

Find a flash drive that you can format (> or = 8 GB).

Create a bootable Windows 10 iso:

https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10

Perform an in place upgrade repair with the Windows 10 iso:

Repair Install Windows 10 with an In-place Upgrade


1) Power on the computer
2) Open file explorer > this PC > C:
3) click on setup

the VR and DM logs

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: 10/16/2019 16:11:24
Size on disk: 820 MB

The posted link displayed 22 Bytes.
Run the DM log collector again.

Ran DM log collector again.
SNOWFALL-Wed_10_16_2019_182028_47.zip - Google Drive

- - - Updated - - -

Created the usb drive yesterday. As a side issue, trying to find out if doing the repair that way will wipe out any installed programs. Will try that repair later tonight.