Random & infrequent BSOD

There were no dump files to debug.

Turn off Windows driver verifier:
Enable and Disable Driver Verifier in Windows 10

Place the computer in clean boot:
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts


Download to the desktop windows 10 1909 iso:
(make sure that you use 1909 and not 2004)

Windows Download - #1 Windows ISO Download Source
Microsoft Windows and Office ISO Download Tool
TechBench by WZT (v4.1.1)
UUP dump


Perform an in place upgrade repair:
Repair Install Windows 10 with an In-place Upgrade


After the in place upgrade repair:

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) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) 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

13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

14) Change clean boot to normal boot:
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

15) Make a new restore point:
Create System Restore Point in Windows 10


16) Restart Windows driver verifier with the 19 simultaneous customized settings in this link:
https://answers.microsoft.com/en-us/...3-c48669e4c983

17) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

I'm getting ready to start with the in-place re-install. Is there a setting I need to tweak so that dmp files will be collected when I get a BSOD

The in place upgrade repair is a trial and error step to see if fixes any underlying problem related to the formation of dump files.
If it works your set.
If it fails the next trial and error step is an in place upgrade repair to 2004.

Gotcha, Thanks.
It may be several days before I get this all done. Thanks again.

The in place upgrade repair (same version) typically fixes underlying operating system problems.
The in place upgrade repair (upgraded version) typically fixes underlying operating system and registry problems.

The settings for startup and recovery system failure and virtual memory could return to default and should be rechecked after each in place upgrade repair.

When performing in place upgrade repairs it's best to have only the windows drives connected.
Any additional drives whenever possible should be removed or have cables detached.

In place repair done.

Microsoft Windows [Version 10.0.18363.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.18363.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.18363.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 ...
809216 file records processed.
File verification completed.
15627 large file records processed.
0 bad file records processed.

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

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

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

1952412622 KB total disk space.
331631152 KB in 470101 files.
263896 KB in 89401 indexes.
0 KB in bad sectors.
977410 KB in use by the system.
65536 KB occupied by the log file.
1619540164 KB available on disk.

4096 bytes in each allocation unit.
488103155 total allocation units on disk.
404885041 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\POWERSPEC-PC\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 '\\POWERSPEC-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


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

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

C:\WINDOWS\system32>

Attachment 282236
Attachment 282237

Rebooting, then will make restore point & restart driver verifier

The above results and settings look good.

Verifier set. Rebooting. Now I wait.

- - - Updated - - -

That didn't take long. As soon as I rebooted, the PC had a BSOD. Reset driver verifier.
No new memory.dmp file, just the one from 05/20/2020 that I posted earlier.

New v2 file attached. Hope it helps.

The logs did not display any unexpected shutdowns or restarts (crash or BSOD).

Update the specs in the "My Computer" section:
System Specs - Fill in at Ten Forums
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)


Open the website for the computer or motherboard manufacturer > support > enter product or serial number or model > select operating system > drivers > post a share link into the thread

Place the computer into safe mode:
Boot into Safe Mode on Windows 10

Use safe mode for several days (continuously).
Report into the thread anytime there is a BSOD or unexpected shutdown or restart.

I added system specs for this computer as System 2

Links to PowerSpec B633 system
PowerSpec Support System Specs
PowerSpec System Specs

The system has been running unattended in normal mode now for several days without errors.
Will boot to Safe Mode for a while. After this next weekend, I won't be around this PC for several weeks.

I WILL let you know the results at some point when I get back.

Thanks,
Ken