Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Laptop Sluggish and Mouse is Erratic


  • Please log in to reply

#46
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 476 posts

I using a standard USB mouse.  I have tried 3 different mice in 3 different USB ports.  Same result.

 

I uninstalled the mouse from Device Manager and rebooted.  Same result.

 

Also, sometimes when I type, the cursor jumps to a random location in the text. 

 

Frustrating!

 

Another thing:  When the computer is on and I am not using it, I will look at the screen at one point and there will be a context menu.  It says the usual: Open, Pin File, etc.


Edited by Jackpine, 28 October 2021 - 11:47 AM.

  • 0

Advertisements


#47
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,034 posts
  • MVP

I went back and looked at your Speccy log.  Appears this is a notebook with a Synaptics PS/2 Port TouchPad.

 

Some of the symptoms you are reporting sound like those of an overly sensitive  or dying touchpad.  Go back into Device Manager and find the touchpad.  Right click on it and Disable.  Then reboot to make sure it is off.  See if that helps.


  • 0

#48
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 476 posts
I am out at the moment. I will disable the touchpad later tonight.
  • 0

#49
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,034 posts
  • MVP

OK.  It's supper time here and then I have to watch TV with the wife for a few hours so I will be off line for a while too.


  • 0

#50
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 476 posts

The disable button for the touchpad is greyed out.  The most I can do is Uninstall it or Unistall the device driver.


  • 0

#51
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,034 posts
  • MVP

See if this helps:

 

https://h30434.www3....ad/td-p/7091427

 

Appears there should be a box to check to disable the touchpad when a USB mouse is connected.  Try checking that.

 

Not sure about the search working on Win 8 but you can search for control panel and then look for the Mouse entry if their search doesn't work for you.


  • 0

#52
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 476 posts

I found the box to disable the touchpad when a USB mouse is connected.   I checked the box and rebooted.

 

I confirmed the touchpad mouse does not respond to my finger moving on the touchpad, and the USB mouse is able to move the cursor.

 

I will use the notebook as normal and report back tomorrow on how the mouse is responding.

 

Thanks for all your help so far!


  • 0

#53
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 476 posts

I think we have success!

 

I have used the USB mouse for a total of about an hour, and there is no problem with it!  The touchpad mouse was disabled yesterday, and the USB mouse functions the way it is supposed to.

 

None of the problems I reported in this topic have returned.  All mouse clicks result in the required action, such as minimizing a page, closing a program, opening a program, etc.  There are also no more "ghost" images of desktop icons being dragged along with the cursor, or typed text jumping at random to a new location in the document.

 

I am very grateful for the work that you have done on my notebook, and thank you very much.

 

Is it necessary to do a last scan to make sure that everything is clean, before removing all the programs that were downloaded onto the desktop?


  • 0

#54
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,034 posts
  • MVP

Up to you if you want another scan.  Maybe just do a quick VEW.


  • 0

#55
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 476 posts

There have been two times where the mouse did not respond since my last post.  This is over about a one hour period.  However, nothing as severe as before.

 

Here is the VEW scan:

 

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 29/10/2021 3:02:56 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 29/10/2021 1:36:02 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program rundll32.exe version 6.3.9600.17415 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.  Process ID: 11d4  Start Time: 01d7cc651e815ac2  Termination Time: 4294967295  Application Path: C:\Windows\System32\rundll32.exe  Report Id: 81659294-3858-11ec-8770-5435306021e4  Faulting package full name:   Faulting package-relative application ID:  

Log: 'Application' Date/Time: 28/10/2021 4:11:50 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

Log: 'Application' Date/Time: 27/10/2021 4:12:25 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "WmiApRpl" in DLL "C:\Windows\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

Log: 'Application' Date/Time: 27/10/2021 4:12:25 PM
Type: Error Category: 0
Event: 2004 Source: Microsoft-Windows-PerfNet
Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code.

Log: 'Application' Date/Time: 27/10/2021 4:12:25 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "MSDTC" in DLL "C:\Windows\system32\msdtcuiu.DLL" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

Log: 'Application' Date/Time: 27/10/2021 4:12:25 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "Lsa" in DLL "C:\Windows\System32\Secur32.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

Log: 'Application' Date/Time: 27/10/2021 4:12:25 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "ESENT" in DLL "C:\Windows\system32\esentprf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 3
Event: 7010 Source: Microsoft-Windows-Search
The index cannot be initialized.

Details:
    The specified object cannot be found. Specify the name of an existing object.  (HRESULT : 0x80040d06) (0x80040d06)


Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 3
Event: 3058 Source: Microsoft-Windows-Search
The application cannot be initialized.

Context: Windows Application

Details:
    The specified object cannot be found. Specify the name of an existing object.  (HRESULT : 0x80040d06) (0x80040d06)


Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 3
Event: 3028 Source: Microsoft-Windows-Search
The gatherer object cannot be initialized.

Context: Windows Application, SystemIndex Catalog

Details:
    The specified object cannot be found. Specify the name of an existing object.  (HRESULT : 0x80040d06) (0x80040d06)


Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 3
Event: 3029 Source: Microsoft-Windows-Search
The plug-in in <Search.TripoliIndexer> cannot be initialized.

Context: Windows Application, SystemIndex Catalog

Details:
    The specified object cannot be found. Specify the name of an existing object.  (HRESULT : 0x80040d06) (0x80040d06)


Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 3
Event: 3057 Source: Microsoft-Windows-Search
The plug-in manager <Search.TripoliIndexer> cannot be initialized.

Context: Windows Application

Details:
    (HRESULT : 0x8e5e01f5) (0x8e5e01f5)


Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 1
Event: 7042 Source: Microsoft-Windows-Search
The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.

Details:
    The content index catalog is corrupt.   0xc0041801 (0xc0041801)


Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 1
Event: 7040 Source: Microsoft-Windows-Search
The search service has detected corrupted data files in the index {id=4810 - enduser\mssearch2\search\ytrip\common\util\jetutil.cpp (167)}. The service will attempt to automatically correct this problem by rebuilding the index.

Details:
     0x8e5e01f5 (0x8e5e01f5)


Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 3
Event: 454 Source: ESENT
SearchIndexer (14872) Windows: Database recovery/restore failed with unexpected error -501.

Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 3
Event: 465 Source: ESENT
SearchIndexer (14872) Windows: Corruption was detected during soft recovery in logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 1 (0x00000001). This logfile has been damaged and is unusable.

Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 3
Event: 477 Source: ESENT
SearchIndexer (14872) Windows: The log range read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" at offset 4096 (0x0000000000001000) for 4096 (0x00001000) bytes failed verification due to a range checksum mismatch.  The expected checksum was 782629228953728487 (0xadc75231e9ff5e7) and the actual checksum was 782629228953728484 (0xadc75231e9ff5e4). The read operation will fail with error -501 (0xfffffe0b).  If this condition persists then please restore the logfile from a previous backup.

Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 3
Event: 465 Source: ESENT
SearchIndexer (14872) Windows: Corruption was detected during soft recovery in logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 1 (0x00000001). This logfile has been damaged and is unusable.

Log: 'Application' Date/Time: 27/10/2021 12:45:44 AM
Type: Error Category: 3
Event: 477 Source: ESENT
SearchIndexer (14872) Windows: The log range read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" at offset 4096 (0x0000000000001000) for 4096 (0x00001000) bytes failed verification due to a range checksum mismatch.  The expected checksum was 782629228953728487 (0xadc75231e9ff5e7) and the actual checksum was 782629228953728484 (0xadc75231e9ff5e4). The read operation will fail with error -501 (0xfffffe0b).  If this condition persists then please restore the logfile from a previous backup.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 29/10/2021 12:40:24 AM
Type: Warning Category: 3
Event: 3036 Source: Microsoft-Windows-Search
Crawl could not be completed on content source <winrt://{S-1-5-21-3511957844-2261570385-1743981658-1005}/>.

Context:  Application, SystemIndex Catalog

Details:
    The parameter is incorrect.  (HRESULT : 0x80070057) (0x80070057)


Log: 'Application' Date/Time: 28/10/2021 1:19:16 PM
Type: Warning Category: 7
Event: 508 Source: ESENT
SearchIndexer (3456) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" at offset 229376 (0x0000000000038000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (34 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Log: 'Application' Date/Time: 28/10/2021 1:19:00 PM
Type: Warning Category: 1
Event: 533 Source: ESENT
SearchIndexer (3456) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" at offset 229376 (0x0000000000038000) for 4096 (0x00001000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Log: 'Application' Date/Time: 28/10/2021 12:26:07 AM
Type: Warning Category: 3
Event: 3036 Source: Microsoft-Windows-Search
Crawl could not be completed on content source <winrt://{S-1-5-21-3511957844-2261570385-1743981658-1005}/>.

Context:  Application, SystemIndex Catalog

Details:
    The parameter is incorrect.  (HRESULT : 0x80070057) (0x80070057)


Log: 'Application' Date/Time: 27/10/2021 12:26:00 PM
Type: Warning Category: 3
Event: 3036 Source: Microsoft-Windows-Search
Crawl could not be completed on content source <winrt://{S-1-5-21-3511957844-2261570385-1743981658-1005}/>.

Context:  Application, SystemIndex Catalog

Details:
    The parameter is incorrect.  (HRESULT : 0x80070057) (0x80070057)


Log: 'Application' Date/Time: 27/10/2021 2:26:05 AM
Type: Warning Category: 3
Event: 3036 Source: Microsoft-Windows-Search
Crawl could not be completed on content source <winrt://{S-1-5-21-3511957844-2261570385-1743981658-1005}/>.

Context: Windows Application, SystemIndex Catalog

Details:
    The parameter is incorrect.  (HRESULT : 0x80070057) (0x80070057)


Log: 'Application' Date/Time: 27/10/2021 1:26:04 AM
Type: Warning Category: 3
Event: 3036 Source: Microsoft-Windows-Search
Crawl could not be completed on content source <winrt://{S-1-5-21-3511957844-2261570385-1743981658-1005}/>.

Context: Windows Application, SystemIndex Catalog

Details:
    The parameter is incorrect.  (HRESULT : 0x80070057) (0x80070057)


Log: 'Application' Date/Time: 27/10/2021 1:25:59 AM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Full Index Reset}.


Log: 'Application' Date/Time: 27/10/2021 12:46:09 AM
Type: Warning Category: 3
Event: 3036 Source: Microsoft-Windows-Search
Crawl could not be completed on content source <winrt://{S-1-5-21-3511957844-2261570385-1743981658-1005}/>.

Context: Windows Application, SystemIndex Catalog

Details:
    The parameter is incorrect.  (HRESULT : 0x80070057) (0x80070057)


Log: 'Application' Date/Time: 27/10/2021 12:46:03 AM
Type: Warning Category: 1
Event: 1008 Source: Microsoft-Windows-Search
The Windows Search Service is starting up and attempting to remove the old search index {Reason: Index Corruption}.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 28/10/2021 4:16:26 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/10/2021 2:11:53 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 29/10/2021 1:43:00 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 29/10/2021 1:42:29 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 29/10/2021 1:18:37 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 29/10/2021 1:18:07 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 28/10/2021 4:30:15 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 28/10/2021 4:16:46 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 12:05:45 PM on ?2021-?10-?28 was unexpected.

Log: 'System' Date/Time: 28/10/2021 4:04:50 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 28/10/2021 1:29:14 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 28/10/2021 1:28:44 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 27/10/2021 1:16:14 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 27/10/2021 1:05:14 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 27/10/2021 1:04:44 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 27/10/2021 1:30:23 AM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 70.

Log: 'System' Date/Time: 27/10/2021 1:30:22 AM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 70.

Log: 'System' Date/Time: 27/10/2021 1:30:22 AM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 70.

Log: 'System' Date/Time: 27/10/2021 1:30:22 AM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 70.

Log: 'System' Date/Time: 27/10/2021 1:30:22 AM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 70.

Log: 'System' Date/Time: 27/10/2021 1:30:22 AM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 70.

Log: 'System' Date/Time: 27/10/2021 1:30:22 AM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 70.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/10/2021 12:45:59 PM
Type: Warning Category: 0
Event: 48 Source: BTHUSB
The local adapter does not support reading the encryption key size for a connected device. Insecure devices may be able to connect to this system.

Log: 'System' Date/Time: 29/10/2021 1:31:54 AM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit http://support.microsoft.com/kb/197571for more information.

Log: 'System' Date/Time: 29/10/2021 1:31:50 AM
Type: Warning Category: 0
Event: 4291 Source: Tcpip
The network adapter with hardware address 54-35-30-60-21-E3 has indicated packet coalescing capability without indicating support for one or more prerequisite receive filter capabilities (IPv4 0x00000000).

Log: 'System' Date/Time: 29/10/2021 1:31:50 AM
Type: Warning Category: 0
Event: 4291 Source: Tcpip
The network adapter with hardware address 54-35-30-60-21-E3 has indicated packet coalescing capability without indicating support for one or more prerequisite receive filter capabilities (IPv6 0x00000000).

Log: 'System' Date/Time: 29/10/2021 1:31:40 AM
Type: Warning Category: 0
Event: 48 Source: BTHUSB
The local adapter does not support reading the encryption key size for a connected device. Insecure devices may be able to connect to this system.

Log: 'System' Date/Time: 29/10/2021 1:24:27 AM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit http://support.microsoft.com/kb/197571for more information.

Log: 'System' Date/Time: 29/10/2021 1:24:23 AM
Type: Warning Category: 0
Event: 4291 Source: Tcpip
The network adapter with hardware address 54-35-30-60-21-E3 has indicated packet coalescing capability without indicating support for one or more prerequisite receive filter capabilities (IPv4 0x00000000).

Log: 'System' Date/Time: 29/10/2021 1:24:23 AM
Type: Warning Category: 0
Event: 4291 Source: Tcpip
The network adapter with hardware address 54-35-30-60-21-E3 has indicated packet coalescing capability without indicating support for one or more prerequisite receive filter capabilities (IPv6 0x00000000).

Log: 'System' Date/Time: 29/10/2021 1:24:13 AM
Type: Warning Category: 0
Event: 48 Source: BTHUSB
The local adapter does not support reading the encryption key size for a connected device. Insecure devices may be able to connect to this system.

Log: 'System' Date/Time: 28/10/2021 4:16:52 PM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit http://support.microsoft.com/kb/197571for more information.

Log: 'System' Date/Time: 28/10/2021 4:16:52 PM
Type: Warning Category: 0
Event: 4291 Source: Tcpip
The network adapter with hardware address 54-35-30-60-21-E3 has indicated packet coalescing capability without indicating support for one or more prerequisite receive filter capabilities (IPv6 0x00000000).

Log: 'System' Date/Time: 28/10/2021 4:16:52 PM
Type: Warning Category: 0
Event: 4291 Source: Tcpip
The network adapter with hardware address 54-35-30-60-21-E3 has indicated packet coalescing capability without indicating support for one or more prerequisite receive filter capabilities (IPv4 0x00000000).

Log: 'System' Date/Time: 28/10/2021 4:16:39 PM
Type: Warning Category: 0
Event: 48 Source: BTHUSB
The local adapter does not support reading the encryption key size for a connected device. Insecure devices may be able to connect to this system.

Log: 'System' Date/Time: 28/10/2021 4:05:51 PM
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. Please visit http://support.microsoft.com/kb/197571for more information.

Log: 'System' Date/Time: 28/10/2021 4:05:48 PM
Type: Warning Category: 0
Event: 4291 Source: Tcpip
The network adapter with hardware address 54-35-30-60-21-E3 has indicated packet coalescing capability without indicating support for one or more prerequisite receive filter capabilities (IPv4 0x00000000).

Log: 'System' Date/Time: 28/10/2021 4:05:48 PM
Type: Warning Category: 0
Event: 4291 Source: Tcpip
The network adapter with hardware address 54-35-30-60-21-E3 has indicated packet coalescing capability without indicating support for one or more prerequisite receive filter capabilities (IPv6 0x00000000).

Log: 'System' Date/Time: 28/10/2021 4:05:37 PM
Type: Warning Category: 0
Event: 48 Source: BTHUSB
The local adapter does not support reading the encryption key size for a connected device. Insecure devices may be able to connect to this system.

Log: 'System' Date/Time: 28/10/2021 1:19:39 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ip-info.ff.avast.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/10/2021 1:16:44 PM
Type: Warning Category: 0
Event: 48 Source: BTHUSB
The local adapter does not support reading the encryption key size for a connected device. Insecure devices may be able to connect to this system.

Log: 'System' Date/Time: 27/10/2021 9:46:27 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Garmin&Prod_VVAHR_Flash&Rev_1.00#6&16b314f5&5#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.


 


Edited by Jackpine, 29 October 2021 - 01:08 PM.

  • 0

Advertisements


#56
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,034 posts
  • MVP

Looks like we did have a problem yesterday:

 

Log: 'Application' Date/Time: 28/10/2021 1:19:16 PM
Type: Warning Category: 7
Event: 508 Source: ESENT
SearchIndexer (3456) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" at offset 229376 (0x0000000000038000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (34 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Log: 'Application' Date/Time: 28/10/2021 1:19:00 PM
Type: Warning Category: 1
Event: 533 Source: ESENT
SearchIndexer (3456) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" at offset 229376 (0x0000000000038000) for 4096 (0x00001000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

 

 

No problems today tho.  If these keep happening you may want to run a disk check and also do a manual defrag.  If it's trying to write to a bad spot on the drive that might help. Alternatively you can just turn off the Search service like we did before. 


  • 0

#57
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 476 posts

OK.  How do I run a disk check?


  • 0

#58
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,034 posts
  • MVP

Search for

cmd

When it finds Command Prompt, right click and Run As ADmin

type:

chkdsk  /r  c:

Hit Enter.  It will say it can't do it now and ask if you want to schedule it for the next reboot.

 

Tell it

y

and then the next time you reboot it will start and usually takes several hours to complete.  Should boot into Windows when done.  If you let it run while you sleep you might want to mute the speakers so it doesn't wake you up.


  • 0

#59
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 476 posts
Ok, I will report back tomorrow.
  • 0

#60
Jackpine

Jackpine

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 476 posts

So I ran chkdsk and the computer rebooted.  However, I don't see any message of what was done.


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP