ESENT ERROR IN EVENT VIEWER

(SECOND ENTRY, DID NOT SEE FIRST ENTRY)

I have a Dell Studio XPS 9100 computer with Windows 7 Prof, with 12gb of
ram, and two internal HDs. The computer normally operates without any major
errors noted in computer management event viewer. However, ESENT errors
appears shortly after I complete the monthly MS security updates, and I will
see multiple ESENT entries. I would appreciate any help in resolving this
problem. Thanks Sam.

The following is an example of one of the entries:

Log Name: Application

Source: ESENT

Date: 11/01/2012 6:59:42 AM

Event ID: 474

Task Category: Database Page Cache

Level: Error

Keywords: Classic

User: N/A

Computer:

Description:

Catalog Database (1196) Catalog Database: The database page read from the
file
"C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb"
at offset 17862656 (0x0000000001109000) (database page 4360 (0x1108)) for
4096 (0x00001000) bytes failed verification due to a page checksum mismatch.
The expected checksum was [77547754d6bb9432] and the actual checksum was
[77567756d6bb9492]. The read operation will fail with error -1018
(0xfffffc06). If this condition persists then please restore the database
from a previous backup. This problem is likely due to faulty hardware.
Please contact your hardware vendor for further assistance diagnosing the
problem.



Event Xml

On 1/14/2012, Sam posted:
> (SECOND ENTRY, DID NOT SEE FIRST ENTRY)

It is in the thread called

"Going to do a "slash 'n burn" reinstall...", starting with

Message-ID: <pyOPq.33809$>

A mild sort of oopsie :-)

--
Gene E. Bloch (Stumbling Bloch)

Sam wrote:
> (SECOND ENTRY, DID NOT SEE FIRST ENTRY)
>
> I have a Dell Studio XPS 9100 computer with Windows 7 Prof, with 12gb of
> ram, and two internal HDs. The computer normally operates without any major
> errors noted in computer management event viewer. However, ESENT errors
> appears shortly after I complete the monthly MS security updates, and I
> will
> see multiple ESENT entries. I would appreciate any help in resolving this
> problem. Thanks Sam.
>
> The following is an example of one of the entries:
>
> Log Name: Application
>
> Source: ESENT
>
> Date: 11/01/2012 6:59:42 AM
>
> Event ID: 474
>
> Task Category: Database Page Cache
>
> Level: Error
>
> Keywords: Classic
>
> User: N/A
>
> Computer:
>
> Description:
>
> Catalog Database (1196) Catalog Database: The database page read from the
> file
> "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb"
> at offset 17862656 (0x0000000001109000) (database page 4360 (0x1108)) for
> 4096 (0x00001000) bytes failed verification due to a page checksum
> mismatch.
> The expected checksum was [77547754d6bb9432] and the actual checksum was
> [77567756d6bb9492]. The read operation will fail with error -1018
> (0xfffffc06). If this condition persists then please restore the database
> from a previous backup. This problem is likely due to faulty hardware.
> Please contact your hardware vendor for further assistance diagnosing the
> problem.
>
>
>
> Event Xml

There appears to be a corruption of the file mentioned. MS suggest
faulty hardware.
My experience tells me that when one system file goes corrupt, others do
too. So do a system file check.
CMD (Command Prompt)
sfc /VERIFYONLY

The next step depends on the results from that. Let us know.
You might also try a full scan of the hard drive too, from inside
Windows and with all the boxes ticked; which will ensure that Windows
closes before running the scan.

Ed

Gene and Ed, many thanks for your replies. Ed, I just ran the sfc
/VERIFYONLY COMMAND and the results was - windows resource protection did
not find any integrity violations. I should note that about three weeks
ago, I ran a full error checking (check disk) and it did not find any errors
or problems. Any other suggestions would be very much appreciated, Sam.



"Ed Cryer" wrote in message news:jev2jm$m9u$...


There appears to be a corruption of the file mentioned. MS suggest
faulty hardware.
My experience tells me that when one system file goes corrupt, others do
too. So do a system file check.
CMD (Command Prompt)
sfc /VERIFYONLY

The next step depends on the results from that. Let us know.
You might also try a full scan of the hard drive too, from inside
Windows and with all the boxes ticked; which will ensure that Windows
closes before running the scan.

Ed

Sam wrote:
> Gene and Ed, many thanks for your replies. Ed, I just ran the sfc
> /VERIFYONLY COMMAND and the results was - windows resource protection
> did not find any integrity violations. I should note that about three
> weeks ago, I ran a full error checking (check disk) and it did not find
> any errors or problems. Any other suggestions would be very much
> appreciated, Sam.
>
>

Right, then, the problem lies apparently solely with the file mentioned;
"C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb"

You'll have to run a repair tool on the database. This page shows how;
http://tinyurl.com/7mcq9cc
It consists of stopping the service, run repair program, restart service.
Followed by a validation run.

Ed

Ed thanks again for your response. Will try the suggested procedure, will
post the results. Sam



"Ed Cryer" wrote in message news:jf195b$oe4$...

Sam wrote:
> Gene and Ed, many thanks for your replies. Ed, I just ran the sfc
> /VERIFYONLY COMMAND and the results was - windows resource protection
> did not find any integrity violations. I should note that about three
> weeks ago, I ran a full error checking (check disk) and it did not find
> any errors or problems. Any other suggestions would be very much
> appreciated, Sam.
>
>

Right, then, the problem lies apparently solely with the file mentioned;
"C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb"

You'll have to run a repair tool on the database. This page shows how;
http://tinyurl.com/7mcq9cc
It consists of stopping the service, run repair program, restart service.
Followed by a validation run.

Ed