Windows 7: event viewer error message

Hello everyone, I'm trying to find a resource for error code defintions to help me track down a problem.
This is a sample of one error, warning, and one of over 2000 in the log file since Monday 2/14 11 when I first activated the system. I am new to PC work and this being my first build I need some direction.


Log Name: Application
Source: ESENT
Date: 2/19/2011 7:09:14 PM
Event ID: 399
Task Category: Database Page Cache
Level: Warning
Keywords: Classic
User: N/A
Computer: XXXXXX
Description:
Catalog Database (1188) Catalog Database: The database page read from the file "C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb" at offset 12288 (0x0000000000003000) (database page 2 (0x2)) for 4096 (0x00001000) bytes failed verification. Bit 17200 was corrupted and has been corrected. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.
Event Xml:
<Event xmlns="Error">
<System>
<Provider Name="ESENT" />
<EventID Qualifiers="0">399</EventID>
<Level>3</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-02-20T03:09:14.000000000Z" />
<EventRecordID>2325</EventRecordID>
<Channel>Application</Channel>
<Computer>EM-PC</Computer>
<Security />
</System>
<EventData>
<Data>Catalog Database</Data>
<Data>1188</Data>
<Data>Catalog Database: </Data>
<Data>C:\Windows\system32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb</Data>
<Data>12288 (0x0000000000003000)</Data>
<Data>4096 (0x00001000)</Data>
<Data>17200</Data>
<Data>2 (0x2)</Data>
</EventData>
</Event>
I am trying to determin a cold start problem in Windows 7 that only happens in the morning.

Thanks for any help in advance

Well that issue is pointing to a possibly failing hard drive.
Have you checked it lately?
Disk Check

No I have not run a disc check yet.
Is there a resource to see these all code definitions and if so would that not be helpful as a troubleshooting guide?

I have a index for bsod's
BSOD Index

but for the error log codes you are probably best off just googling them.

Running the disk check would be the first obvious step. You could wind up chasing random codes caused by a bad hard drive for no reason.
I honestly would get that out of the way before digging.

Thankyou for the index info. I will check the disc next and post what I found. Many thanks for your time.

Hey, just an update, I found out the cause of my BSOD, cold start issues and file errors.
When I first loaded my OS I had all 6gb of Ram installed. One of the sticks was bad and caused difficulties with the OS install and I assumed the little glitches were normal. But there not, and because of my inexperience it's partially my fault that I had these problems. Live and learn. (I read somewhere 64bit OS are sometimes best installed with minimal Ram on some boards.) I dont know if that's true or not but I beleive that this may have also contributed to startup file corruption. I did a reinstall of the OS with only one stick installed and it went smooth as glass. I then tested all the dimm slots and the ram one at a time. On the last stick tested I got BSOD and to the bottom of it all. Thanks Maguscreed for your efforts. Cheers

A lot of people recommend installing with only 2 gigs of ram in the machine. Then adding the rest in after wards, just to avoid possible issues.

Unfortunately, I was unaware of this at the time of OS install. I could have avoided most of the problems I encountered.
Like I said, "I'm new at this and besides, an error is not a mistake until you refuse to correct it". I will live and learn and this first build was a lot of fun, I look forward to the next. Thanks again.

hey thanks for posting this. im having a similar problem im gonna give it a shot.