Jump to content

HELP - I need to fix errors and MOFCOMP.LOG is gone.


Alan_B

Recommended Posts

At 08:28:56 this morning pagefile.sys was initiated after power-up.

At 08:29:59 I logged on.

 

At 08:29:52 C:\WINDOWS\system32\CatRoot2\dberr.txt started posting :-

CatalogDB: 08:29:52 11/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 08:29:52 11/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 08:30:27 11/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 08:30:28 11/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 08:34:56 11/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 08:34:56 11/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 09:05:05 11/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 09:05:05 11/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 09:35:16 11/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 09:35:16 11/08/2009: File #2 at line #1236 encountered error 0x00000057

 

There were another 4 lines starting at 10:05:33, and I expect more at 1 hour 28 second intervals.

My system has been like this every day since 01/08/2009

 

What is going wrong ?

Is this an error I need to fix ?

How can I fix or suppress this ?

What is this "File #2" with an error at line #1236 ?

Could it be oem43.CAT (which does not exist) or KB972260-IE7.cat

which has copies in C:\WINDOWS\$hf_mig$\KB972260-IE7\update and

C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} ?

 

The transition from normal to bad is :-

CatalogDB: 10:49:57 31/07/2009: Adding Catalog File: oem43.CAT

CatalogDB: 10:49:58 31/07/2009: DONE Adding Catalog File: oem43.CAT

CatalogDB: 10:51:18 31/07/2009: Adding Catalog File: oem43.CAT

CatalogDB: 10:51:19 31/07/2009: DONE Adding Catalog File: oem43.CAT

CatalogDB: 10:52:40 31/07/2009: Adding Catalog File: oem43.CAT

CatalogDB: 10:52:40 31/07/2009: DONE Adding Catalog File: oem43.CAT

CatalogDB: 10:53:07 31/07/2009: Adding Catalog File: KB972260-IE7.cat

CatalogDB: 10:53:07 31/07/2009: DONE Adding Catalog File: KB972260-IE7.cat

CatalogDB: 21:43:00 01/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 21:43:01 01/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 21:53:24 01/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 21:53:25 01/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 15:15:32 02/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 15:15:32 02/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 19:31:55 02/08/2009: File #2 at line #1236 encountered error 0x00000057

CatalogDB: 19:31:56 02/08/2009: File #2 at line #1236 encountered error 0x00000057

 

I thought at first the KB972260-IE7.cat was an Active'X kill-bits patch,

and it was not only in-effective in its stated purpose but had actually done damage.

 

I have a fear this error is related to Security Patches, and any future patches may fail to take effect or otherwise suffer.

 

On 06/08/2009 I noticed several Application event errors upon 01/08/2009 16:49:12

and started a thread as a result and am awaiting a response at

http://forum.piriform.com/index.php?showtopic=23462

 

I hoped those errors were a consequence of something going wrong with the hotfix,

and hoped that no further errors indicated that "autorecovery" had then automatically cured the problem.

I should have known that would be to good to be true.

 

I now realise that there were many reboots between 10:53:07 31/07/2009 and 21:43:00 01/08/2009,

and assume that if the patch did damage it should have been autorecovered on the first reboot.

 

The other thing which happened before 21:43:00 01/08/2009 was use of RevoUninstaller to assist with the removal of Eset Antivirus and Comodo Firewall, and to supplement with additional post-un-installation things supplied by ESET and the Comodo forum to zap any residual traces, and there was a residual Comodo registry key that took much abuse before it went. After which I installed Comodo CIS.

 

This incessant error in dberr.txt is the only evidence that something is amiss.

 

I would greatly appreciate advice.

 

Regards

Alan

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.