[wildair]

After I installed Registry Reviver, it found many problems which it said it fixed all. Each time it was used after that, it always had 50 give or take a few, empty register keys. Which it said it "fixed". If these are empty every single time, why doesn't the program remove them? I just now did a scan,(it also autmoatically scans every time I boot up) and it shows 33 empty registry keys and shows 33 fixed.

[Advertisements]

Easy solution: uninstall it. You don't need it. Registry Cleaners cause more problems than they solve.

[Neil Jones]

Easy solution: uninstall it. You don't need it. Registry Cleaners cause more problems than they solve.

[rshaffer61]

The question is if your system is having any issues due to it.
Slowing down
Freezing
Programs not working
Associations not working

[wildair]

The question is if your system is having any issues due to it.
Slowing down
Freezing
Programs not working
Associations not working

Yes, it is freezing several times, I'm not able to open programs, after the computer has sat for awhile either. And the computer can't find files to open the program. Do you also think I should uninstall Registry Reviver?

[rshaffer61]

Yep as stated before from our experience registry cleaners tend to cause more problems then they are worth.
Lets take a look and see what we can find.

• Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
• Double-click VEW.exe
• Under 'Select log to query', select (as appropriate):
  
  • Application
  • System
• Under 'Select type to list', select (as appropriate):
  
  • Error

Then use the 'Date of events' or 'Number of events' as follows:

Either:

• Click the radio button for 'Number of events'
  Type 6 in the 1 to 20 box (or any number from 1 to 20)
  Then click the Run button.
  Notepad will open with the output log.
  
  
• Click the radio button for 'Date of events'
  In the From: boxes type today's date (presuming the crash happened today) 13 07 2009
  In the To: boxes type today's date (presuming the crash happened today) 13 07 2009
  Then click the Run button.
  Notepad will open with the output log.

Please post the Output log in your next reply

[wildair]

Yep as stated before from our experience registry cleaners tend to cause more problems then they are worth.
Lets take a look and see what we can find.

• Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
• Double-click VEW.exe
• Under 'Select log to query', select (as appropriate):
  
  • Application
  • System
• Under 'Select type to list', select (as appropriate):
  
  • Error

Then use the 'Date of events' or 'Number of events' as follows:

Either:

• Click the radio button for 'Number of events'
  Type 6 in the 1 to 20 box (or any number from 1 to 20)
  Then click the Run button.
  Notepad will open with the output log.
  
  
• Click the radio button for 'Date of events'
  In the From: boxes type today's date (presuming the crash happened today) 13 07 2009
  In the To: boxes type today's date (presuming the crash happened today) 13 07 2009
  Then click the Run button.
  Notepad will open with the output log.

Please post the Output log in your next reply

[wildair]

Used both the Application choice and the system choice:

Vino's Event Viewer v01c run on Windows XP in English
Report run at 30/07/2010 6:39:30 AM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 29/07/2010 1:46:58 PM
Type: error Category: 0
Event: 0 Source: Media Center Scheduler
The event description cannot be found.

Log: 'Application' Date/Time: 28/07/2010 9:51:09 AM
Type: error Category: 0
Event: 8019 Source: NTBackup
End Operation: Warnings or errors were encountered. Consult the backup report for more details.

Log: 'Application' Date/Time: 28/07/2010 9:32:47 AM
Type: error Category: 0
Event: 5000 Source: MPSampleSubmission
EventType mptelemetry, P1 microsoft antimalware (bcf43643-a118-4432-aede-d861fcbcfcde), P2 2.1.6805.0, P3 timeout, P4 1.1.6004.0, P5 local, P6 unspecified, P7 unspecified, P8 NIL, P9 NIL, P10 NIL.

Log: 'Application' Date/Time: 28/07/2010 9:30:47 AM
Type: error Category: 0
Event: 5000 Source: MPSampleSubmission
EventType mptelemetry, P1 microsoft antimalware (bcf43643-a118-4432-aede-d861fcbcfcde), P2 2.1.6805.0, P3 timeout, P4 1.1.6004.0, P5 local, P6 unspecified, P7 unspecified, P8 NIL, P9 NIL, P10 NIL.

Log: 'Application' Date/Time: 28/07/2010 8:19:14 AM
Type: error Category: 0
Event: 11706 Source: MsiInstaller
Product: SolutionCenter -- Error 1706. An installation package for the product SolutionCenter cannot be found. Try the installation again using a valid copy of the installation package 'SolutionCenter.msi'.

Log: 'Application' Date/Time: 28/07/2010 5:37:46 AM
Type: error Category: 0
Event: 0 Source: Media Center Scheduler
The event description cannot be found.

Vino's Event Viewer v01c run on Windows XP in English
Report run at 30/07/2010 6:40:46 AM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/07/2010 1:47:22 PM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: TfFsMon TfSysMon

Log: 'System' Date/Time: 29/07/2010 1:47:22 PM
Type: error Category: 0
Event: 7022 Source: Service Control Manager
The HP CUE DeviceDiscovery Service service hung on starting.

Log: 'System' Date/Time: 29/07/2010 1:35:36 PM
Type: error Category: 0
Event: 2020 Source: Srv
The server was unable to allocate from the system paged pool because the pool was empty.

Log: 'System' Date/Time: 29/07/2010 1:34:55 PM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Log: 'System' Date/Time: 29/07/2010 1:34:55 PM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Log: 'System' Date/Time: 29/07/2010 1:34:53 PM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Vino's Event Viewer v01c run on Windows XP in English
Report run at 30/07/2010 6:40:46 AM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/07/2010 1:47:22 PM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: TfFsMon TfSysMon

Log: 'System' Date/Time: 29/07/2010 1:47:22 PM
Type: error Category: 0
Event: 7022 Source: Service Control Manager
The HP CUE DeviceDiscovery Service service hung on starting.

Log: 'System' Date/Time: 29/07/2010 1:35:36 PM
Type: error Category: 0
Event: 2020 Source: Srv
The server was unable to allocate from the system paged pool because the pool was empty.

Log: 'System' Date/Time: 29/07/2010 1:34:55 PM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Log: 'System' Date/Time: 29/07/2010 1:34:55 PM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Log: 'System' Date/Time: 29/07/2010 1:34:53 PM
Type: error Category: 0
Event: 2000 Source: Srv
The server's call to a system service failed unexpectedly.

Vino's Event Viewer v01c run on Windows XP in English
Report run at 30/07/2010 6:49:10 AM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 19/07/2010 2:24:51 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The MozyHome Backup Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 19/07/2010 2:24:51 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the MozyHome Backup Service service to connect.

Log: 'System' Date/Time: 19/07/2010 2:19:50 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The MozyHome Backup Service service failed to start due to the following error: Insufficient system resources exist to complete the requested service.

Log: 'System' Date/Time: 19/07/2010 2:14:49 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The MozyHome Backup Service service failed to start due to the following error: Insufficient system resources exist to complete the requested service.

Log: 'System' Date/Time: 19/07/2010 2:09:48 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The MozyHome Backup Service service failed to start due to the following error: Insufficient system resources exist to complete the requested service.

Log: 'System' Date/Time: 19/07/2010 2:08:39 PM
Type: error Category: 0
Event: 1 Source: sr
The System Restore filter encountered the unexpected error '0xC000009A' while processing the file 'drivetable.txt' on the volume 'HarddiskVolume1'. It has stopped monitoring the volume.

Log: 'System' Date/Time: 19/07/2010 2:08:39 PM
Type: error Category: 0
Event: 1 Source: sr
The System Restore filter encountered the unexpected error '0xC000009A' while processing the file 'pnC0B.tmp' on the volume 'HarddiskVolume1'. It has stopped monitoring the volume.

Log: 'System' Date/Time: 19/07/2010 2:04:47 PM
Type: error Category: 0
Event: 7034 Source: Service Control Manager
The MozyHome Backup Service service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 18/07/2010 12:48:31 AM
Type: error Category: 102
Event: 1003 Source: System Error
Error code 1000000a, parameter1 ffffffe0, parameter2 00000002, parameter3 00000000, parameter4 805373ee.

Log: 'System' Date/Time: 18/07/2010 12:47:56 AM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: TfFsMon TfSysMon

Log: 'System' Date/Time: 18/07/2010 12:47:56 AM
Type: error Category: 0
Event: 7022 Source: Service Control Manager
The HP CUE DeviceDiscovery Service service hung on starting.

Log: 'System' Date/Time: 18/07/2010 5:43:54 AM
Type: error Category: 0
Event: 7011 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for a transaction response from the W32Time service.

Log: 'System' Date/Time: 18/07/2010 12:02:56 AM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: TfFsMon TfSysMon

Log: 'System' Date/Time: 18/07/2010 12:02:56 AM
Type: error Category: 0
Event: 7022 Source: Service Control Manager
The HP CUE DeviceDiscovery Service service hung on starting.

Log: 'System' Date/Time: 16/07/2010 3:46:31 PM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: TfFsMon TfSysMon

Log: 'System' Date/Time: 16/07/2010 3:46:31 PM
Type: error Category: 0
Event: 7022 Source: Service Control Manager
The HP CUE DeviceDiscovery Service service hung on starting.

Log: 'System' Date/Time: 16/07/2010 1:55:20 PM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: IntelIde TfFsMon TfSysMon

Log: 'System' Date/Time: 16/07/2010 1:55:20 PM
Type: error Category: 0
Event: 7022 Source: Service Control Manager
The HP CUE DeviceDiscovery Service service hung on starting.

Log: 'System' Date/Time: 16/07/2010 1:53:52 PM
Type: error Category: 0
Event: 1 Source: sr
The System Restore filter encountered the unexpected error '0xC0000001' while processing the file '' on the volume 'HarddiskVolume1'. It has stopped monitoring the volume.

Log: 'System' Date/Time: 16/07/2010 12:42:06 AM
Type: error Category: 102
Event: 1003 Source: System Error
Error code 1000000a, parameter1 ffffffe0, parameter2 00000002, parameter3 00000000, parameter4 805373ee.

Log: 'System' Date/Time: 16/07/2010 5:35:58 AM
Type: error Category: 0
Event: 7011 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for a transaction response from the W32Time service.

Log: 'System' Date/Time: 16/07/2010 12:04:19 AM
Type: error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: TfFsMon TfSysMon

Log: 'System' Date/Time: 16/07/2010 12:04:19 AM
Type: error Category: 0
Event: 7022 Source: Service Control Manager
The HP CUE DeviceDiscovery Service service hung on starting.


Vino's Event Viewer v01c run on Windows XP in English
Report run at 30/07/2010 6:51:27 AM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 18/07/2010 2:58:05 AM
Type: error Category: 0
Event: 11706 Source: MsiInstaller
Product: SolutionCenter -- Error 1706. An installation package for the product SolutionCenter cannot be found. Try the installation again using a valid copy of the installation package 'SolutionCenter.msi'.

Log: 'Application' Date/Time: 18/07/2010 12:47:31 AM
Type: error Category: 0
Event: 0 Source: Media Center Scheduler
The event description cannot be found.

Log: 'Application' Date/Time: 18/07/2010 12:02:31 AM
Type: error Category: 0
Event: 0 Source: Media Center Scheduler
The event description cannot be found.

Log: 'Application' Date/Time: 16/07/2010 5:18:09 PM
Type: error Category: 0
Event: 11706 Source: MsiInstaller
Product: SolutionCenter -- Error 1706. An installation package for the product SolutionCenter cannot be found. Try the installation again using a valid copy of the installation package 'SolutionCenter.msi'.

Log: 'Application' Date/Time: 16/07/2010 5:17:57 PM
Type: error Category: 0
Event: 11706 Source: MsiInstaller
Product: SolutionCenter -- Error 1706. An installation package for the product SolutionCenter cannot be found. Try the installation again using a valid copy of the installation package 'SolutionCenter.msi'.

Log: 'Application' Date/Time: 16/07/2010 5:17:25 PM
Type: error Category: 0
Event: 11706 Source: MsiInstaller
Product: SolutionCenter -- Error 1706. An installation package for the product SolutionCenter cannot be found. Try the installation again using a valid copy of the installation package 'SolutionCenter.msi'.

Log: 'Application' Date/Time: 16/07/2010 3:46:05 PM
Type: error Category: 0
Event: 0 Source: Media Center Scheduler
The event description cannot be found.

Log: 'Application' Date/Time: 16/07/2010 1:54:55 PM
Type: error Category: 0
Event: 0 Source: Media Center Scheduler
The event description cannot be found.

Log: 'Application' Date/Time: 16/07/2010 12:42:10 AM
Type: error Category: 0
Event: 11706 Source: MsiInstaller
Product: SolutionCenter -- Error 1706. An installation package for the product SolutionCenter cannot be found. Try the installation again using a valid copy of the installation package 'SolutionCenter.msi'.

Log: 'Application' Date/Time: 16/07/2010 12:03:54 AM
Type: error Category: 0
Event: 0 Source: Media Center Scheduler
The event description cannot be found.

[rshaffer61]

First try this and see if it helps.
Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem


Then to let you know this file TfSysMon is showing up in your Event log and has been know to be part of a infections.
I suggest you go to the Malware Removal and Spyware Removal Forum and run all the steps located in the
START HERE. These self-help tools will help you clean up 70% of problems on your own.
If you are still having problems after doing the steps, then please post the reguested logs in THAT forum.
If you are unable to run any of the tools then start a new topic in the malware forum and put this in the subject line...I am unable to run any malware tools

If you are still having problems after being given a clean bill of health from the malware expert, then please return to THIS thread and we will pursue other options to help you solve your current problem(s).

Add a link to this topic so that malware tech can see what steps have been taken here