PC Freezing for short periods -> DistributedCOM Error?

1) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings > 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

2) For restore points it's always best to have them set to automatic so you have more options when you need them:
https://www.howtogeek.com/278388/how...nt-at-startup/

3) There are many in Ten Forums that use backup images.
For example: Acronis, Aoemi, EaseUS, Macrium, Paragon, etc.
Macrium Software | Your Image is Everything
Backup and Restore with Macrium Reflect | Tutorials

The memory tests are finished and ran fine:




Don't seem to be having luck finding the cause of the BSOD. If I remember correctly you said I may get info on it when it happens since I turned off the auto reboot. Maybe I need to just work on the computer and wait for that to happen again, then try to immediately find the dmp file.

Windows driver verifier is a tool which stresses drivers.
The drivers that are misbehaving typically produce BSOD.
The BSOD files are then debugged to identify the misbehaving drivers.
The drivers are then uninstalled and reinstalled.
The tool is generally ran for 48 hours.
Then after the last BSOD it is ran for an additional 36 hours of typical computer use.
If there are no longer any BSOD that will conclude the use of the tool.

Before turning on the tool you must understand the methods to turn off and/or recover from using the tool.
All important files should be backed up to another drive or to the cloud.
A backup image should be made and saved to another drive or to the cloud.

While using the tool the computer performance may change and the boots may become slow.

Make sure a brand new restore point is create before turning on the tool.

After each BSOD you will use the computer's windows advanced troubleshooting menu to return from the BSOD to the desktop. On the desktop you will run the BETA log collector and search for the memory dump. Post both share links.
Dump files will then be debugged and drivers uninstalled.
Drivers can be reinstalled immediately after they are uninstalled or at the end after all misbehaving drivers have been uninstalled. The result should be the same.

The testing will start out with three simultaneous customized tests on all non-Microsoft drivers.
If the performance and boot are ok the number of simultaneous test will be increased.

Enable and Disable Driver Verifier in Windows 10 | Tutorials

The tool can be started once you:
a) Understand the methods to turn off and recover from using the tool
b) Made a brand new restore point
c) Backed up all important files to another drive or the cloud
d) Made a backup image and saved the image to another drive or to the cloud.

To be sure I am sufficiently prepared, I have some questions:

After each BSOD you will use the computer's windows advanced troubleshooting menu

I'm not sure what "Windows advanced troubleshooting menu" is, or where it is. When I search Google, it comes up with info on Advanced Startup Options. Do you mean boot to the Windows screen where I can choose to do a restore point, or reset, etc?

to return from the BSOD to the desktop.

I haven't experienced "returning from a BSOD". I have been presuming if I get a BSOD that I would be locked up with a blue screen and need to hard reboot. Is there a process of returning from the BSOD I need to follow? Or am I just rebooting into the Windows screen I mentioned above?

(Sorry for all the questions...I tend to take things I read very literally, so want to be sure).

Dump files will then be debugged and drivers uninstalled.

Is that something that happens with the tools I am told to run; or is that something that I need to manually do myself? Or is the debugging done by you and I am told what drivers to remove / reinstall?

I have done an image backup, and created a restore point. I'll proceed once I hear back on my questions.

Once again...I really appreciate the efforts and support here.

Open administrative command prompt or administative powershell and type or copy and paste: shutdown /r /o /f /t 00

This command will reboot the computer into the Windows advanced troubleshooting menu.
This command is not applicable when recovering from a BSOD.

An alternative method is to hold down the shift key while clicking restart.

After each BSOD you will need to use the Windows advanced troubleshooting menu to turn off windows driver verifier using the commands in this link:

Enable and Disable Driver Verifier in Windows 10 | Tutorials


The methods to turn off or recvoer from using the tool should be done in order.
Advanced to the next method only if the prior method fails.
Using system restore often leads to a loss of the dump file and then little progress is made in the troubleshooting.

The first command should be using startup settings > restart > safe mode with command prompt > type:
verifier /reset

I have the driver verifier running now.

Do I need to be doing a bunch of stuff to hopefully utilize the offending driver to cause the BSOD, or is the Driver Verifier doing that in the background, and I can just leave it running?

While Windows driver verifier is running you can use the computer as typical use. Nothing extra needs to be done.
If there are no BSOD then the customized tests will be modified.
This link has approximately 19 simultaneous tests:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Every 1 - 2 hours increase the number of simultaneous tests by 3 or 4 so that there are 19 simultaneous tests.

zbook said:

While Windows driver verifier is running you can use the computer as typical use. Nothing extra needs to be done.
If there are no BSOD then the customized tests will be modified.
This link has approximately 19 simultaneous tests:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Every 1 - 2 hours increase the number of simultaneous tests by 3 or 4 so that there are 19 simultaneous tests.

I looked at the link, as well as a couple links embedded in that link, and also did a verifier.exe /? to look at command options. I can't find any reference about increasing simultaneous tests. Google search didn't bring up anything on that either.

I'm beginning the feel like a completely uneducated computer user.

See the link that was just posted:

Code:

Select everything.  For Win 8 and win 10  dont checkDDI compliance checking and randomized low resource simulation, then click "Next"

That is a total of approximately 19 simultaneous tests.
Starting with the Ten Forums 3 simultaneous tests and then increasing the number of simultaneous tests to a total of 19 is the goal.
Normally you can start with all 19 but there can be problems either with too much sluggishness, extremely slow boot, or boot loop. So this is a measured approach to add 3 or 4 additional tests per hour.

OH duh...it finally clicks. The initial instructions were to click on 3 things. Its the same screen, but I select more options.

Sorry for the density. It's been running for quite a while. I'll go add a few, and continue on.