PC Freezing for short periods -> DistributedCOM Error?

Thanks. I don't know how you knew it was the Synaptics, but glad you did. I was looking at HP, as opposed to non-HP drivers.

I've done the install, and will run the tests again.

New BSOD

Link to Memory Dump: LINK

Link to Log Collector file: LINK

Attachment 218738

Download and install the HP Support Assistant if not already installed:
Driver - HP ENVY x360 - 15-aq292cl | HP® Customer Support

Run the HP support assistant to search for any drivers to update > update all drivers

Turn off Windows driver verifier

Open device manager > click view > click show hidden devices > expand keyboards > right click uninstall device and check the box to uninstall driver > click action > click scan for hardware changes

Run the HP support assistant to update drivers after the removal of the driver

Perform Windows updates

Reboot

Restart Windows driver verifier

All done. No updates from either method were found, so nothing installed.

Re-ran verifier. FYI...it BSODs during boot (I wasn't watching last time, so didn't know that.) I suspect it will show the same thing. Links below.

Question: what do you think the chances are that the files will be repaired if I load Windows recovery, and do a 'non-destructive repair'?

Link to the memory.dmp file: LINK
Lin to the log collector: LINK

By the way, if you think maybe I should go ahead and run the verifier with fewer tests, I can certainly do that.

Well, I just went out and tried a "Startup Recovery". Of course w/o verifier running, it does not BSOD.

It did not find anything, so my only choice for using recovery will be to allow it to remove all programs. I'll hold off that until you get tired of messing with me on this. It seems to be fighting us.

Were you not able to use verifier /reset?
Was verifier /bootmode resetonbootfail used?

When you power on now what do you see?
Are you able to open the computer's Windows advanced recovery menu?

Find a flash drive that you can format ( > or = 8 GB)
On a working computer create a bootable windows 10 iso:
Download Windows 10
Download Windows 10 ISO File | Tutorials

The same driver has appeared in the dumps.
For Windows driver verifier view the available drivers and do not check this driver for testing:
HpqKbFiltr64.sys

Report into the thread the steps that were made to uninstall.
Were you able to view the driver that had been installed by Windows when the hardware was uninstalled with the driver?

When you are back on the desktop for the next run of Windows driver verifier if there is too much sluggishness or problems with slow boot then choose any 10 simultaneous tests available in the link for testing and restart Windows driver verifier to see if there are any other misbehaving drivers. The problematic will not be troubleshooted for the time being. Once all other drivers have been troubleshooted we can return to this one.

Were you not able to use verifier /reset?Was verifier /bootmode resetonbootfail used?

One of the ways listed in the documents to turn off verifier was to run it, and select the Delete option. That is how I've been turning it off. It is working, otherwise I would have come back with BSODS

When you power on now what do you see?Are you able to open the computer's Windows advanced recovery menu?

Yes I am. In fact the way I've been getting to a Administer CMD after the BSOD is by going through recovery, and booting to safe mode, then to an admin cmd, and doing the delete.The computer always boots with the option to ESC and select multiple ways to boot.

Find a flash drive that you can format ( > or = 8 GB)On a working computer create a bootable windows 10 isoownload Windows 10Download Windows 10 ISO File | Tutorials

I actually had that on hand when I started, just in case. But going through safe mode, as outlined above, haven't needed it.

The same driver has appeared in the dumps.For Windows driver verifier view the available drivers and do not check this driver for testing:HpqKbFiltr64.sys

That's a great idea. I hadn't paid enough attention to the list to realize I could do that. I went out and started it running based on that test, and it is running it now. (FYI...computer is not really sluggish).

FYI...some testing I did while waiting on the next response here, I determined that the test that tests that driver and fails is the 19th one on the list, Code Integrity Checks.

So, it has booted now and that driver is not being tested.

Were you able to view the driver that had been installed by Windows when the hardware was uninstalled with the driver?

Not sure what you mean by that. What I did and saw was this:

• Launched device manager
• Browsed down to the keyboard, and uninstalled the requisite keyboard
• That keyboard disappeared from the list of hardware
• I used the HP Download/Install option to install the new driver
• Once rebooted after that install, the version of the driver was the same as what had been there
• It still caused a BSOD when testing if I had Code Integrity Checks test checked (and of course that driver checked)

So, right now, 19 tests are running with all drivers except for MIcrosoft drivers and also not HpqKbFiltr64.sys. I plan to let it run overnight doing it's thing, unless it BSODs before I go to bed.

I'll report status in the morning, or after the next BSOD.

Dunno what all has been said here... really don't care. I've had Windows 10 for about a month now with nothing but problems. This post as well as many others. It's been what.. four years or so wince Win 10 was released and you guys still don't have a stable OS???? Garbage, just Garbage company you are. I've almost got my company convinced to go to Linux because of how many bugs this garbage OS STILL has after how many years? You're OS is crap, just absolute crap. You had a good thing with 7 and you tried to re-invent the wheel... very stupid. If it's not broke don't fix it stupids! Can't believe I was a believer in Microsuck for so long, garbage! If any of your staff that thought up Windows 10 are thinking of suicide, they should do it. We don't need people like that in this world. Buh Bye Microsuck, hello Linux.

When the hardware and driver are uninstalled the listing usually disappears from device manager and there usually is a prompt to reboot to completely remove the driver.
Was there are prompt for reboot or was the driver reinstalled before the reboot?
Perform the step again deleting the hardware and driver and then look for the device hardware ID and post an image into the thread.

Click properties
> driver tab > driver details > post an image of the whole window into the thread
> details tab > scroll in property to hardware IDs > view values > post an image of the whole window into the thread

Do not reinstall the driver and use the Microsoft default driver.
Restart Windows driver verifier with all non-Microsoft drivers checked.
If there is a BSOD then post a BETA log collector zip and memory dump into the thread.