Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Laptop Sluggish and Mouse is Erratic

Started by Jackpine , Oct 16 2021 12:51 PM

Please log in to reply

#16
Jackpine

Posted 18 October 2021 - 12:11 PM

Member

Topic Starter
Member
490 posts

The driver installed. I had to reboot. Here is the LatencyMon Summary.

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:00:31 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        SHADOWFAX
OS version:                                           Windows 8.1, 6.3, build: 9600 (x64)
Hardware:                                             HP Pavilion 17 Notebook PC, Hewlett-Packard
CPU:                                                  AuthenticAMD AMD A6-5200 APU with Radeon™ HD Graphics
Logical processors:                                   4
Processor groups:                                     1
RAM:                                                  7643 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed:                                   1996 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs):   470.385223
Average measured interrupt to process latency (µs):   8.320009

Highest measured interrupt to DPC latency (µs):       466.281536
Average measured interrupt to DPC latency (µs):       3.051833

_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs):              96.512525
Driver with highest ISR routine execution time:       rtbth.sys - Ralink Bluetooth Adapter, Ralink Technology, Corp.

Highest reported total ISR routine time (%):          0.008503
Driver with highest ISR total time:                   storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

Total time spent in ISRs (%)                          0.008858

ISR count (execution time <250 µs):                   1240
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-1000 µs):               0
ISR count (execution time 1000-2000 µs):              0
ISR count (execution time 2000-4000 µs):              0
ISR count (execution time >=4000 µs):                 0

_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs):              560.089679
Driver with highest DPC routine execution time:       ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total DPC routine time (%):          0.015826
Driver with highest DPC total execution time:         storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

Total time spent in DPCs (%)                          0.077442

DPC count (execution time <250 µs):                   14288
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-10000 µs):              38
DPC count (execution time 1000-2000 µs):              0
DPC count (execution time 2000-4000 µs):              0
DPC count (execution time >=4000 µs):                 0

_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count:                 firefox.exe

Total number of hard pagefaults                       2184
Hard pagefault count of hardest hit process:          1091
Number of processes hit:                              6

_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       0.191117
CPU 0 ISR highest execution time (µs):                96.512525
CPU 0 ISR total execution time (s):                   0.002639
CPU 0 ISR count:                                      325
CPU 0 DPC highest execution time (µs):                406.231463
CPU 0 DPC total execution time (s):                   0.050483
CPU 0 DPC count:                                      10417
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       0.111658
CPU 1 ISR highest execution time (µs):                16.800601
CPU 1 ISR total execution time (s):                   0.002283
CPU 1 ISR count:                                      269
CPU 1 DPC highest execution time (µs):                560.089679
CPU 1 DPC total execution time (s):                   0.018239
CPU 1 DPC count:                                      1547
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       0.125228
CPU 2 ISR highest execution time (µs):                81.630261
CPU 2 ISR total execution time (s):                   0.002746
CPU 2 ISR count:                                      289
CPU 2 DPC highest execution time (µs):                343.227956
CPU 2 DPC total execution time (s):                   0.012443
CPU 2 DPC count:                                      1162
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       0.177066
CPU 3 ISR highest execution time (µs):                84.671844
CPU 3 ISR total execution time (s):                   0.003332
CPU 3 ISR count:                                      357
CPU 3 DPC highest execution time (µs):                450.499499
CPU 3 DPC total execution time (s):                   0.015009
CPU 3 DPC count:                                      1200
_________________________________________________________________________________________________________

#17
RKinner

Posted 18 October 2021 - 01:55 PM

Malware Expert

Expert
24,700 posts

That looks better. Latency Mon isn't complaining so the driver appears to have helped.

I don't think we have done this yet. This speeds up most systems a bit:

Search for

task scheduler

hit Enter

Click on the arrow in front of Task Scheduler Library then

Click on the arrow in front of Microsoft

Click on the arrow in front of Windows

Click on Application Experience. In the next pane to the right, right click on each Task and Disable. Should be three or four (later versions) tasks.

Click on Customer Experience Improvement Program. In the next pane to the right, right click on each Task and Disable. Should be two tasks.

Download OOSU10.exe:

https://www.oo-softw...com/en/shutup10

Download and Save it (You will get a popup while it's downloading. You can X out of it)
then Right click and Run As Admin.
Allow it to make a System Restore Point.
Click on Actions then on Apply Recommended Settings.

Close the program and reboot.

Let's get a benchmark:

https://www.userbenchmark.com

Click on Free Download. Save the file then right click and Run As Admin. Close all programs and pause your antivirus before starting.

When it finishes it will open a browser. Copy the URL and paste it into a Reply.

How is it running now? Still having problems with the mouse?

#18
Jackpine

Posted 18 October 2021 - 02:06 PM

Member

Topic Starter
Member
490 posts

I completed the Task Scheduler steps. But I have Windows 8.1. Will OOSU10 run properly?

#19
RKinner

Posted 18 October 2021 - 03:58 PM

Malware Expert

Expert
24,700 posts

OOPS. Forgot. It won't but the other stuff should be the same.

As an alternative try Windows Privacy Tweaker 3.0.2

https://www.majorgee...cy_tweaker.html

I think it's supposed to be easy to use just read the instructions.

#20
Jackpine

Posted 18 October 2021 - 04:03 PM

Member

Topic Starter
Member
490 posts

I ran the benchmark.. Here are the results. https://www.userbenc...serRun/47177866

I saw that you just posted another reply. I will run the Windows Privacy Tweaker and report back. The mouse doesn't hang up anymore. Although, it would work and not work before at random. Let me use it for about half an hour. Prior to you looking at my computer, it would stop working intermittently well within half an hour. Then when I clicked a few times, it would work again.

#21
Jackpine

Posted 18 October 2021 - 04:03 PM

Member

Topic Starter
Member
490 posts

I ran the benchmark.. Here are the results. https://www.userbenc...serRun/47177866

#22
Jackpine

Posted 18 October 2021 - 07:55 PM

Member

Topic Starter
Member
490 posts

I used the computer for about half an hour and the mouse was fine. However, I came back to it about 2 hours later, and the mouse wouldn't respond when I clicked on desktop programs and shortcuts. Even clicking on the Start button had no response. I found out that when I do Ctl-Alt-Del and click on Task Manager, the mouse will eventually respond.

#23
RKinner

Posted 18 October 2021 - 08:34 PM

Malware Expert

Expert
24,700 posts

Let's see if there are any errors in the event log that might give us a clue.

#24
Jackpine

Posted 26 October 2021 - 07:43 AM

Member

Topic Starter
Member
490 posts

I haven't heard anything since Oct 18. Are you OK?

#25
RKinner

Posted 26 October 2021 - 09:56 AM

Malware Expert

Expert
24,700 posts

Appears I forgot to paste in the following:

1. Please download the Event Viewer Tool by Vino Rosso
http://images.malwar...om/vino/VEW.exe
and save it to your Desktop:
2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:

* System

* Application
4. Under 'Select type to list', select:
* Error
* Warning

Then use the 'Number of events' as follows:

1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button and wait.
Notepad will open with the output log.

Please copy and paste the Output log into your next reply

#26
Jackpine

Posted 26 October 2021 - 10:21 AM

Member

Topic Starter
Member
490 posts

Here is the Event log:

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 26/10/2021 12:19:30 PM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 18/10/2021 9:58:27 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: UBMSkillBench.exe, version: 1.0.3.0, time stamp: 0x60d1e629 Faulting module name: XAudio2_9.dll, version: 6.3.9600.20144, time stamp: 0x615be9b3 Exception code: 0xc0000135 Fault offset: 0x00000000000ed170 Faulting process id: 0x46c Faulting application start time: 0x01d7c46b43f84844 Faulting application path: C:\Users\Robert\AppData\Local\Temp\UserBenchMarkTemp\UBMSkillBench.exe Faulting module path: XAudio2_9.dll Report Id: 85719498-305e-11ec-8767-5435306021e4 Faulting package full name: Faulting package-relative application ID:

Log: 'Application' Date/Time: 18/10/2021 2:16:35 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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 24/10/2021 10:01:46 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: 24/10/2021 10:01:46 PM
Type: Warning Category: 7
Event: 508 Source: ESENT
SearchIndexer (3588) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" at offset 237568 (0x000000000003a000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (33 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: 24/10/2021 10:00:40 PM
Type: Warning Category: 1
Event: 533 Source: ESENT
SearchIndexer (3588) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" at offset 237568 (0x000000000003a000) 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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 26/10/2021 2:38:42 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: 26/10/2021 2:38:11 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: 26/10/2021 2:04:18 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: 26/10/2021 2:03:48 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: 26/10/2021 2:01:09 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: 26/10/2021 2:00:39 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: 26/10/2021 12:57:54 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: 26/10/2021 12:47:21 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: 26/10/2021 12:46:51 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: 25/10/2021 8:28:33 AM
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: 25/10/2021 8:28:03 AM
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: 24/10/2021 11:34:48 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: 24/10/2021 11:23:44 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: 24/10/2021 11:23:14 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: 18/10/2021 3:27:43 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: 18/10/2021 3:27:13 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: 18/10/2021 2:10:23 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 18/10/2021 2:10:22 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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 26/10/2021 12:27:46 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: 25/10/2021 1:05:36 AM
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&296cc59a&5#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Log: 'System' Date/Time: 24/10/2021 9:58:25 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: 18/10/2021 8:59:32 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.mooseblood.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 18/10/2021 5:59:00 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: 18/10/2021 5:58:57 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: 18/10/2021 5:58:57 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: 18/10/2021 5:58:46 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: 18/10/2021 5:56:54 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: 18/10/2021 5:56:54 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: 18/10/2021 2:15:27 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: 18/10/2021 2:11:37 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: 18/10/2021 2:11:34 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: 18/10/2021 2:11:34 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: 18/10/2021 2:11:22 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.

#27
RKinner

Posted 26 October 2021 - 11:18 AM

Malware Expert

Expert
24,700 posts

I'm thinking this is the problem:

Log: 'Application' Date/Time: 24/10/2021 10:01:46 PM
Type: Warning Category: 7
Event: 508 Source: ESENT
SearchIndexer (3588) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" at offset 237568 (0x000000000003a000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (33 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: 24/10/2021 10:00:40 PM
Type: Warning Category: 1
Event: 533 Source: ESENT
SearchIndexer (3588) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" at offset 237568 (0x000000000003a000) 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.

Windows says it's faulty hardware but I think it's just a bad file. Let's see if this fixlist will help. It will require a reboot but shouldn't take very long.

Download the attached fixlist.txt to the same location as FRST

fixlist.txt 432bytes 155 downloads

Run FRST and press Fix

A fix log will be generated please post that

Reboot if the fix doesn't reboot it for you

#28
Jackpine

Posted 26 October 2021 - 11:53 AM

Member

Topic Starter
Member
490 posts

Fix result of Farbar Recovery Scan Tool (x64) Version: 20-10-2021
Ran by Robert (26-10-2021 13:42:06) Run:4
Running from C:\Users\Robert\Desktop
Loaded Profiles: Robert
Boot Mode: Normal
==============================================

fixlist content:
*****************
Unlock: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
File: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
CMD: SC stop WSearch
CMD: esentutl /p C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
CMD: SC start WSearch
File: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
CMD: FOR /F "usebackq delims==" %i IN (`wevtutil el`) DO wevtutil cl "%i"
Reboot:
*****************

"C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" => was unlocked

========================= File: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log ========================

C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
Catalog: Error1: CreateFileW function failed
File not signed
MD5: <==== ATTENTION (zero byte File/Folder)
Creation and modification date: 2021-10-15 15:32 - 2021-10-26 13:39
Size: 001048576
Attributes: ----A
Company Name:
Internal Name:
Original Name:
Product:
Description:
File Version:
Product Version:
Copyright:
VirusTotal: 0-byte

====== End of File: ======

========= SC stop WSearch =========

[SC] ControlService FAILED 1051:

A stop control has been sent to a service that other running services are dependent on.

========= End of CMD: =========

========= esentutl /p C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log =========

Extensible Storage Engine Utilities for Microsoft® Windows®
Version 6.3
Copyright © Microsoft Corporation. All Rights Reserved.

Error: Access to source database 'C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log' failed with Jet error -1032.

Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access file, the file is locked or in use) after 20.140 seconds.

========= End of CMD: =========

========= SC start WSearch =========

[SC] StartService FAILED 1056:

An instance of the service is already running.

========= End of CMD: =========

========================= File: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log ========================

C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
Catalog: Error1: CreateFileW function failed
File not signed
MD5: <==== ATTENTION (zero byte File/Folder)
Creation and modification date: 2021-10-15 15:32 - 2021-10-26 13:39
Size: 001048576
Attributes: ----A
Company Name:
Internal Name:
Original Name:
Product:
Description:
File Version:
Product Version:
Copyright:
VirusTotal: 0-byte

====== End of File: ======

========= FOR /F "usebackq delims==" %i IN (`wevtutil el`) DO wevtutil cl "%i" =========

========= End of CMD: =========

The system needed a reboot.

==== End of Fixlog 13:43:39 ====

#29
RKinner

Posted 26 October 2021 - 01:53 PM

Malware Expert

Expert
24,700 posts

Didn't work. Apparently because it couldn't stop the Search Service. Let's try doing it manually.

Search for:

services.msc

hit Enter

This should open the Services window. Scroll down to Windows Search. Right click on it and select Properties. Stop the service.

I don't have any problem stopping the service so it should work for you.

If you can stop the service (If it won't stop what error does it give) then see if you can get this fixlist to run:

fixlist.txt 483bytes 157 downloads

#30
Jackpine

Posted 26 October 2021 - 02:17 PM

Member

Topic Starter
Member
490 posts

I was able to stop the service. Fixlog is below:

Fix result of Farbar Recovery Scan Tool (x64) Version: 20-10-2021
Ran by Robert (26-10-2021 16:03:59) Run:5
Running from C:\Users\Robert\Desktop
Loaded Profiles: Robert
Boot Mode: Normal
==============================================

fixlist content:
*****************
Unlock: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
File: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
CMD: esentutl /p C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
File: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
CMD: SC start WSearch
File: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
CMD: FOR /F "usebackq delims==" %i IN (`wevtutil el`) DO wevtutil cl "%i"
Reboot:
*****************

"C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log" => was unlocked

========================= File: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log ========================

C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
Catalog: Error1: CreateFileW function failed
File not signed
MD5: <==== ATTENTION (File is in use)
Creation and modification date: 2021-10-15 15:32 - 2021-10-26 16:02
Size: 001048576
Attributes: ----A
Company Name:
Internal Name:
Original Name:
Product:
Description:
File Version:
Product Version:
Copyright:
VirusTotal: 0-byte

====== End of File: ======

========= esentutl /p C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log =========

Extensible Storage Engine Utilities for Microsoft® Windows®
Version 6.3
Copyright © Microsoft Corporation. All Rights Reserved.

Error: Access to source database 'C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log' failed with Jet error -1032.

Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access file, the file is locked or in use) after 20.266 seconds.

========= End of CMD: =========

========================= File: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log ========================

C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
Catalog: Error1: CreateFileW function failed
File not signed
MD5: <==== ATTENTION (File is in use)
Creation and modification date: 2021-10-15 15:32 - 2021-10-26 16:02
Size: 001048576
Attributes: ----A
Company Name:
Internal Name:
Original Name:
Product:
Description:
File Version:
Product Version:
Copyright:
VirusTotal: 0-byte

====== End of File: ======

========= SC start WSearch =========

[SC] StartService FAILED 1056:

An instance of the service is already running.

========= End of CMD: =========

========================= File: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log ========================

C:\ProgramData\Microsoft\Search\Data\Applications\Windows\edb.log
Catalog: Error1: CreateFileW function failed
File not signed
MD5: <==== ATTENTION (File is in use)
Creation and modification date: 2021-10-15 15:32 - 2021-10-26 16:02
Size: 001048576
Attributes: ----A
Company Name:
Internal Name:
Original Name:
Product:
Description:
File Version:
Product Version:
Copyright:
VirusTotal: 0-byte

====== End of File: ======

========= FOR /F "usebackq delims==" %i IN (`wevtutil el`) DO wevtutil cl "%i" =========

========= End of CMD: =========

The system needed a reboot.

==== End of Fixlog 16:05:25 ====