PC Freezing for short periods -> DistributedCOM Error?

There was no definitive misbehaving driver in the dump file.
To check the current drivers run Windows driver verifier for 48 hours using these settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Make a brand new restore point.
Make sure the Macrium backup image is up to date.
Restart Windows driver verifer with the above customized settings.

This link has the methods to turn off or recover from using the tool:
Enable and Disable Driver Verifier in Windows 10 | Tutorials

After any BSOD:
a) run the BETA log collector and post a new zip into the thread
b) post C:\windows\memory.dmp if the file size is < 1.5 GB using a zip and share link

Windows update attempted. Got this error:

Attachment 221248

I resolved it based on this post.

Intel Driver Assistant reporttted 3 drivers available. I have not installed yet, as I'm strictly following your instructions, which did not say to install:



I resolved it based on this post.

Intel Driver Assistant reported 3 drivers available. I have not installed yet, as I'm strictly following your instructions, which did not say to install:

4) Run HD Tune: (free edition)
https://www.hdtune.com/
Post images into the thread for results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan

5) Open administrative command prompt and type or copy and paste:
6) sfc /scannow
7) dism /online /cleanup-image /restorehealth
8) chkdsk /scan
9) wmic RecoverOS set AutoReboot = False
10) 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

Microsoft Windows [Version 10.0.17763.253](c) 2018 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files and successfully repaired them.For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.17763.1Image Version: 10.0.17763.253[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Volume label is Windows.Stage 1: Examining basic file system structure ... 254976 file records processed.File verification completed. 5735 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 613 reparse records processed. 349320 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 613 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 47173 data files processed.CHKDSK is verifying Usn Journal... 37133096 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 511403007 KB total disk space. 97040344 KB in 202407 files. 120924 KB in 47174 indexes. 0 KB in bad sectors. 377283 KB in use by the system. 65536 KB occupied by the log file. 413864456 KB available on disk. 4096 bytes in each allocation unit. 127850751 total allocation units on disk. 103466114 allocation units available on disk.C:\WINDOWS\system32>wmic RecoverOS set AutoReboot = FalseUpdating property(s) of '\\ROGERSLAPTOP\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'Property(s) update successful.C:\WINDOWS\system32>

I just noticed your last post. I'll attack that tomorrow.

I have a HP feedback request. I'm waiting to see how this goes before I reply. I"m not sure if they addressed something or not. Feels like they didn't.

The scannow command found operating system corruption.
It was able to fix the corruption.

What is the status of the computer freezing?

The event logs still display corrected hardware errors.

The drivers are best updated directly from the HP website.
These are the best tested drivers for the computer configuration.
If drivers are not displayed the best sources are the component manufacturer: Intel, AMD, Nvidia, Killer Networks, Realtek, etc.

The goal is to fix the freezing and to have unremarkable reports in the event logs.

Drivers can be updated and tested.
HP was supposed to test the hardware.
It was reported that they replaced the operating system but there were no hardware replacement.
If replacing the operating system and drivers continues to display corrected hardware errors then there may be problems that need to be addressed.

HP may only be willing to automatically fix problems under warranty when the problems are found by their hardware tests.

For corrected hardware errors in the logs it creates uncertainty.

For example how frequently do corrected hardware errors only remain as reports and not noticeable problems?
How frequently do corrected hardware errors turn into uncorrected hardware errors or BSOD?
How do corrected hardware errors impact the lifespan of the hardware?

While the computer is under warranty it seems like it's best to have the problems well documented in case there are any future problems.
Alternatively you may be able to report the findings for the vendor ID to HP from the prior post.

Vendor ID: 0x8086
Device ID: 0x9D13

Mobile 6th/7th Generation Intel(R) Processor Family I/O PCI Express Root Port #4


Also open a support ticket with Intel.

I am running the Verifier now.

I have in fact not had any instances of the computer freezing.

Looking at the event viewer, there have been 167 ERRORs in the past 7 days. So, I just did a Google on "Session "NT Kernel Logger" failed to start with the following error: 0xC0000035". Leads to this post.

So, is there any such thing as a Windows PC running w/o errors in the logs all the time? This is beginning to feel like it'd be a full time job to chase all the errors.

There are always entries in the event viewer.
If you plan to regularly evaluate the computer you can use the event viewer to search for: critical, warning, error
Then you can view these results to see if anything is actionable.

The easiest method for an end user though is not to use the event viewer and instead use the reliability control panel.
This software is much easier to use.
In the left lower corner search type: reliability > click on reliability control panel
On any day you can quickly see problems and there is a chart that displays the stability/instability

This is a link that explains how to use the software:
https://www.howtogeek.com/166911/rel...u-arent-using/

For Windows driver verifier the customized tests can be used to find more misbehaving rivers. Currently you should be using 3 simultaneous tests.
There are approximately 19 customized tests that can be used simultaneously.
Computer's may have changes in performance while using the tool.
There can be sluggishness or very slow boots.

Add 3 - 4 customized tests per hour until you have 19 simultaneous tests as in this link:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

For any BSOD:
a) post a new BETA zip
b) post a memory dump share link if the file size is < 1.5 GB

Thanks.

What you said is what I expected to hear. I definitely get more stuff, including errors, reported in the event viewer than the reliability report. Only error showing up in the reliability report is on that HP Comm error I referenced earlier.

I have all 19 testes running now, and performance is fine.

I'm debating whether to install the NordVPN again and see if it BSODs like it was on 1709.

Sometimes replacing drivers makes corrected hardware errors disappear.
The tool, windows driver verifier is being used to see if there were any misbehaving drivers.
If the corrected hardware errors do not disappear with up to date drivers that are not misbehaving then that leaves problematic hardware.
In an earlier post you reported that HP had replaced the operating system.

For a new computer there should be no corrected hardware errors.

If there are no misbehaving drivers after 48 hours of windows driver verifier using 19 simultaneous tests then that will rule out misbehaving drivers as a cause of the corrected hardware errors.

After there is 48 or even 72 hours of no misbehaving drivers then you can install any software.
This way you will have tested the computer with a new operating system and new drivers and have checked the event viewer to see if there are persistent corrected hardware errors.
That will then complete the testing for any driver that could have caused the corrected hardware error problem.

Then you can install any software for evaluation or testing.
Within windows driver verifier you can choose the drivers to test and can continue running the tool just to check the vpn driver(s).

Please update the thread with any communications from Intel.

The drivers are best updated directly from the HP website.
These are the best tested drivers for the computer configuration.
If drivers are not displayed the best sources are the component manufacturer: Intel, AMD, Nvidia, Killer Networks, Realtek, etc.

I'm just a little confused, so to be sure we are on the same page: I understand that the best source for drivers are the hardware mgr. According to HP Support Asst. I have no drivers to update, but the Intel app you had me run shows 3. So should I install those or not?

BTW...as of this morning, still no BSODs from the Verifier testing. Reliability Monitor is blank so far for today. For last hour, Event Viewer is empty. Past 24 hours has 13 errors, 7 of which are DistributedComm errors.

THanks for that Ed.

JFYI...I performed that very process on another update that was failing to come down. But at the moment, all updates are installed.